> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bizzyco.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Using Email Templates
> Preview, version history, and referencing templates from automations and agents
The template detail page is where you iterate on an existing template. It has
tabs for editing, previewing, and reviewing version history.
## Tabs
| Tab | Contents |
| ------------ | ------------------------------------------------------------------ |
| **Settings** | Edit name, description, subject, body. Validation runs on save. |
| **Preview** | Fill sample variable values and see the rendered email update live |
| **History** | Version snapshots — view or restore any previous version |
## Previewing
Open the **Preview** tab:
1. The list on the left shows every variable Bizzy extracted from the subject
and body.
2. Type sample values for each.
3. The rendered subject and body update as you type.
The preview shows the final delivered email: your rendered body wrapped in the
same standard layout Bizzy applies when the email is sent. Unsafe HTML —
scripts, event handlers, and embedded frames — is removed during rendering,
and because the preview and the send path share the same renderer, the
preview shows the exact sanitized document that is delivered. A plain-text
alternative is also generated automatically at send time for email clients
that prefer it.
Use this to verify that your variable names match what your automations actually
pass.
## Version history
Every meaningful change to the subject or body creates a new version. The
**History** tab shows:
* When the version was saved
* Who saved it
* A **View** button to inspect that version
* A **Restore** button to promote that version back to current
Restoring a version becomes the new current version — older versions remain in
history.
## Sending from an automation
In an automation's instructions, reference the template by name or by ID. Under
the hood, the automation calls `renderEmailTemplateContent` with the variable
data it has available and the rendered result goes out via the configured
sender.
Because Mustache silently ignores missing variables, make sure the automation
actually has the data it needs before the send step.
## Sending from an agent
Agents can call a `send_email` tool that accepts a template reference and a map
of variable values. Tool permissions apply — see
[Tool permissions](/user-guide/agents/tool-permissions) — and a human can be
required to approve each send.
## Deleting
Use the dropdown on the list or detail page to **Delete** a template. Deletion
is soft — the row is hidden but version history and references are preserved.
## Next steps
Trigger a template send from an event
Ask an agent to send using a template