Who can use this
- RevOps and managers standardizing follow-up style.
- Reps who want reusable starting points for common emails.
Before you start
- Decide which use case the template should cover.
- Collect example language that is safe to reuse.
- Decide which variables belong in the template.
Template parts
- Name: the label users see.
- Description: the routing guidance or purpose for the template.
- Content: the reusable email body pattern.
- Variables: placeholders that Ergo can fill from configured default or custom variables.
- Type: email templates are separate from Slack templates.
What to expect
- Templates can be created, edited, listed, and deleted.
- Template changes affect future draft generation; they do not rewrite already-created drafts.
- AI may adapt a template to context unless your workspace intentionally uses strict template behavior.
- Variables need clear names and descriptions so users understand what they represent.
Common issues
- The template description is too vague, so Ergo applies it to the wrong situation.
- Template content includes customer-specific or stale details.
- A variable is missing, duplicated, or unclear.
- Users expect template edits to update drafts that were already generated.