Who can use this
- RevOps and managers maintaining shared template guidance.
- Reps creating personal reusable templates, when allowed.
Before you start
- Confirm who owns the template and who should use it.
- Draft a clear name, description, and body.
- Remove customer-specific details from reusable examples.
Steps
- Open template settings.
- Create a new email template or select an existing one.
- Add or edit the template name, description, and content.
- Add variables only when they are supported and clearly documented.
- Save the template.
- Test by generating or composing a draft that should use the template.
- Delete old templates only after confirming they are no longer needed.
What to expect
- Template APIs support create, update, list, and delete for email templates.
- Template variables can also be created, updated, listed, and deleted.
- Changes apply to future draft generation and do not automatically rewrite drafts already in the Drafts queue.
- Email templates and Slack templates are separate template types.
Common issues
- The description does not explain when Ergo should use the template.
- The body contains stale names, dates, or customer-specific examples.
- A variable is deleted while a template still references it.
- Users expect an edited template to change drafts that already exist.