> ## Documentation Index
> Fetch the complete documentation index at: https://jetemail.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Templates

> Create, reuse, organise, duplicate, test, and manage Marketing email templates.

A template stores the reusable content and sender configuration used by broadcasts, workflows, and the Marketing transactional API.

## What a template contains

* Internal template name
* Subject line and inbox preview text
* From name, verified from address, and optional reply-to address
* Design blocks or full HTML
* Generated plain-text alternative
* Global styles or a saved theme
* Personalisation and unsubscribe tokens
* Internal tags

<Note>
  The sender belongs to the template. A broadcast can override the subject, but it inherits the template's from name, from address, and reply-to address.
</Note>

## Create a template

1. Go to **Marketing** → **Templates**
2. Click **New template**
3. Choose **Blank template** or a starter
4. Enter an internal name in the top bar
5. Set the subject and preview text
6. Choose a sender on an active Marketing domain
7. Create the content
8. Send a test
9. Click **Create**

Available starters include practical layouts for account notices, product updates, welcome mail, simple notes, password resets, promotions, and newsletters. Every starter is fully editable.

### Starter examples

| Starter            | Starting structure                                | Example subject               |
| ------------------ | ------------------------------------------------- | ----------------------------- |
| **Account notice** | Centred logo, security alert, numbered next steps | `New sign-in to your account` |
| **Product update** | Centred logo, changelog, single action link       | `What’s new this month`       |
| **Welcome**        | Hero panel, feature cards, closing CTA            | `Welcome to Acme`             |
| **Simple note**    | Plain, letter-style text                          | `A quick note from Acme`      |
| **Password reset** | Centred transactional panel and one action        | `Reset your password`         |
| **Promotion**      | Full-width bands, hero, quote, benefits           | `Save 30% on Acme`            |
| **Newsletter**     | Editorial digest, article links, CTA card         | `The latest from Acme`        |

Choosing a starter copies its blocks, styles, subject, and preview text into the new template. It does not remain linked to the starter, so later edits affect only your template.

## How templates are reused

The same template system powers three sending paths:

| Sending path                | How the template is used                                                                                         |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Broadcast**               | Choose a template and audience. The broadcast inherits its design and sender, while allowing a subject override. |
| **Workflow**                | Each email step references a template. Edit the template when the sequence needs updated content.                |
| **Marketing transactional** | Your application selects a template UUID and supplies the recipient-specific merge values.                       |

For example, a customer-onboarding set might contain:

* `Welcome — day 0`
* `Getting started — day 2`
* `Need help? — day 7`

Each remains a separately testable template, while the workflow controls their order and delays.

## Name, subject, and preview text

The template name is only for your team. The subject and preview text are recipient-facing:

* **Subject line** is the main inbox title
* **Preview text** is the supporting text many inboxes show beside or below the subject

JetEmail inserts preview text as a hidden preheader in the sent HTML. It does not appear as a visible block in the message body.

## Configure the sender

Under **Sender**:

1. Enter a recognisable from name
2. Enter the local part of the address
3. Select an active Marketing domain
4. Optionally enter a reply-to address

For example:

```text theme={null}
JetEmail Updates <news@updates.example.com>
Reply-To: support@example.com
```

If the sender domain is not available, [add and verify it](/docs/marketing/domains) first.

## Choose an editing mode

The editor has four views:

| View        | Purpose                                                    |
| ----------- | ---------------------------------------------------------- |
| **Design**  | Build visually from blocks and reusable sections           |
| **HTML**    | Paste or write complete HTML with a live preview           |
| **Text**    | Inspect the automatically generated plain-text alternative |
| **Preview** | Review the rendered message at desktop or mobile width     |

Design and HTML are alternative sources of truth. Switching a visual design to HTML renders its current blocks into editable markup. Switching back to Design can replace hand-written HTML with the block design, and JetEmail asks for confirmation when that would discard changes.

See [Template editor](/docs/marketing/editor) for blocks, sections, styles, themes, and shortcuts.

## Personalise the content

Insert built-in fields such as `{{firstName}}`, custom contact properties, or the per-recipient `{{unsubscribe_link}}`.

```html theme={null}
Hi {{firstName}},

Your {{planName}} renewal is ready.
```

See [Personalisation & merge fields](/docs/marketing/personalization) for field creation and safe testing.

## Test before sending

JetEmail includes a test-send system in the template editor. It sends the current render to one address so you can check the message in a real inbox before using it in a broadcast, workflow, or application.

1. Set a valid sender on the template
2. Click **Send test**
3. Enter a recipient address you can inspect
4. Click **Send test**

The test uses the current subject, preview text, sender, HTML, and generated plain-text version. It does not send to an audience, and test sends do not count toward a Marketing quota.

<Tip>
  You can send a test while editing, before the template is used anywhere. Repeat the test after changing a theme, responsive columns, important links, or sender details.
</Tip>

Check at least:

* Desktop and mobile layout
* Subject and preview text
* From and reply-to identities
* Dark-mode behaviour in common clients
* Images and alt text
* Every destination URL
* Plain-text readability
* Personalisation and unsubscribe placement

Test sends appear in **Marketing** → **Logs**, where you can confirm their delivery result and inspect the event timeline.

### Preview versus test send

| Tool                       | Best for                                                            |
| -------------------------- | ------------------------------------------------------------------- |
| **Desktop/mobile preview** | Fast visual checks while editing                                    |
| **Text view**              | Checking the generated plain-text alternative                       |
| **Send test**              | Real inbox rendering, sender identity, links, and delivery evidence |

Use all three before a high-impact send. Browser preview cannot reproduce every transformation made by Gmail, Outlook, Apple Mail, and security gateways.

## Save and unsaved changes

Click **Create** for a new template or **Save** for an existing one. `Command-S` on macOS or `Control-S` elsewhere also saves.

If you navigate away with unsaved edits, the dashboard asks for confirmation.

## Manage the template library

The Templates page supports:

* Search by name or subject
* Filter by tag
* Edit
* Duplicate
* Copy template UUID
* Delete
* Pagination for larger libraries

Duplicating copies the sender, editor mode, blocks, styles, HTML, text, and tags. The copy receives a new UUID and `(copy)` in its name.

The UUID is used by the [Marketing transactional API](/docs/marketing/transactional) as `transactionalId`.

<Warning>
  Before deleting a template, check broadcasts and workflows that use it. A workflow email step must reference an existing template.
</Warning>