> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/features/customer-engagement-platform/message/email.md).

# Email

An email message is composed of header information and a body. The body can be designed directly in Batch or uploaded as a pre-built HTML template.

All fields support [personalization](https://doc.batch.com/getting-started/features/customer-engagement-platform/message/personalization), except the sender address, which must be selected from predefined options configured in **Settings**.

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2FcmiQEn5DlG1RECur5rkr%2Fimage.png?alt=media&#x26;token=30d44184-a13d-4d79-8f8d-bb4b2ca42ec5" alt="email composer"><figcaption></figcaption></figure>

***

### Header Information

#### Email sender

The sender name and address are displayed as the source of the message. Senders are categorized by orchestration type (marketing or transactional) and must be configured in **Settings** before use. Learn how to configure email senders in .

{% hint style="info" %}
To know more about transactional email sending in Batch, check .
{% endhint %}

#### Reply-To *(optional)*

By default, replies are directed to the sender address. You can override this by specifying a custom reply-to address.

If a **Default Reply-To** has been configured in your Channel Settings, it will be pre-filled here automatically. You can edit, change, or remove it for this specific orchestration without affecting the default.

#### Subject line

The subject is the first element recipients see in their inbox. Personalization is supported and recommended to improve open rates.

#### Preheader *(optional)*

The preheader is the short text displayed next to the subject line in most email clients. By default, it is taken from the beginning of the email body. You can override it with custom text for better control over the preview.

***

### Email body

The email body can be created in two ways:

#### 1. Email Composer

Batch's **Email Composer**, powered by Stripo, lets you design emails visually from scratch or from existing templates and modules.

Useful resources:

* [Email guides](https://doc.batch.com/guides-and-best-practices/message/email)
* [Stripo Education Portal](https://stripo.email/education/)

**Timer Block**

{% hint style="info" %}
Timer block is a paid offering. Contact your CSM or Account Manager to learn more.
{% endhint %}

{% hint style="warning" %}
**Replication behavior:** When an email is replicated (via orchestration replication, A/B test, or multi-language variants), timer blocks are **synchronized** across all copies. Any change made to one timer block will apply to all others. If you need each variant to have an independent countdown, **duplicate the timer block** within each copy to break the synchronization and ensure they are distinct.
{% endhint %}

#### 2. Upload HTML template

If you have a pre-designed email template, you can upload it directly as HTML.

See: [How to upload your email templates?](https://doc.batch.com/guides-and-best-practices/message/email/templates-and-modules-management/how-to-upload-your-email-templates)

***

### Preview

Use the **Desktop** and **Mobile** preview modes to verify how your email renders across different screen sizes before sending.

***

### Send a test

You can send a test email at any stage of composition. A few things to note:

* The subject line is prefixed with **\[TEST]** for easy identification.
* The **list-unsubscribe header** is not included in test emails.
* Other behaviors are consistent with test messages across all channels. See  for details.

***

### Email Quality Assistant

The Email Quality Assistant analyzes an email template and reports what could be improved, and why. It runs on demand: click **Analyze** in the email builder toolbar. The analysis is purely advisory and doesn't block a send.

The analysis runs on the email version currently open, so each language version and each A/B test variant is analyzed separately.

Each check adapts to the email it reads. A transactional email such as an order confirmation or a password reset is not judged on persuasion the same way a promotional email is.

{% hint style="info" %}
The Email Quality Assistant is in beta and is available for emails designed in the Email Composer. Templates uploaded as HTML are not analyzed.
{% endhint %}

#### **Severity levels**

Findings are ranked by severity, so the most pressing issues surface first.

| Severity       | Meaning                                                                                                        |
| -------------- | -------------------------------------------------------------------------------------------------------------- |
| **Critical**   | The issue breaks part of the email, makes content unusable, or misses a legal requirement for marketing email. |
| **Warning**    | The issue is likely to reduce performance or deliverability without breaking the email.                        |
| **Suggestion** | An optimization opportunity.                                                                                   |

When a safe rewrite exists, a finding comes with a one-click fix that applies the suggested change to the email.

#### **What it checks**

The analysis covers the copy of your email, its layout and accessibility, and its deliverability. Findings are returned ordered by severity.

**Content & impact:**&#x20;

| Check                      | What it looks at                                                                                                 | Severity               |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------------------- |
| Subject line and preheader | Presence, length, and whether the preheader simply repeats the subject                                           | Suggestion to critical |
| Spelling and grammar       | Errors in the copy, quoted in the finding                                                                        | Warning                |
| Clarity and readability    | Long or convoluted sentences, and unexplained shifts in tone                                                     | Suggestion             |
| Content consistency        | A value (date, price, duration) stated differently in two places, or unintended language mixing                  | Warning                |
| Persuasive strength        | The hook, the benefit framing, the cognitive triggers used, and stronger alternatives when a field reads generic | Suggestion or warning  |
| Call to action             | Vague CTA wording, with benefit-driven rewrites suggested                                                        | Suggestion             |
| Personalization            | Whether the email uses any visible personalization                                                               | Suggestion             |
| Structure and use-case fit | The narrative flow against the likely goal of the email (welcome, promotion, abandoned cart, win-back, event)    | Suggestion             |
| Reading time               | Whether the email runs longer than the recommended reading time                                                  | Suggestion or warning  |

**Layout & accessibility:**&#x20;

| Check                     | What it looks at                                                                | Severity               |
| ------------------------- | ------------------------------------------------------------------------------- | ---------------------- |
| Alt text                  | Missing, vague, or filename-based alt text on meaningful images                 | Warning or critical    |
| Color contrast            | Text-to-background contrast, on CTAs and the unsubscribe link in particular     | Warning or critical    |
| Font size and hidden text | Undersized body text, and text hidden anywhere in the email                     | Suggestion to critical |
| Image weight              | Heavy images that slow loading on mobile                                        | Warning or critical    |
| Unsubscribe usability     | Whether the wording and styling of the unsubscribe or preference link are clear | Suggestion             |

**Deliverability & compliance:**&#x20;

| Check                      | What it looks at                                                                                                                                | Severity               |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- |
| Spam-trigger wording       | Aggressive or spammy phrasing, excessive capitals, and strings of "!" or "?"                                                                    | Warning or critical    |
| Subject and sender honesty | A subject promising what the body does not deliver, a reply or forward prefix on a first-touch marketing email, or a From and Reply-To mismatch | Warning or critical    |
| Unsubscribe link           | Required in marketing email                                                                                                                     | Critical               |
| Physical mailing address   | Required in marketing email                                                                                                                     | Warning or critical    |
| Email weight               | How close the template is to the Gmail clipping limit                                                                                           | Warning or critical    |
| Image-to-text ratio        | An image-heavy or image-only email                                                                                                              | Suggestion             |
| Links                      | Shortened, insecure, malformed, or mismatched links, and a large share of links on unrelated domains                                            | Suggestion to critical |
| Visual noise               | Heavy bold text, emoji use, and colors that may not render correctly in dark mode                                                               | Suggestion or warning  |
| Preheader accuracy         | Whether the configured preheader matches the teaser embedded in the sent HTML                                                                   | Warning                |
| Store badge accuracy       | An app store badge pointing to the wrong store                                                                                                  | Warning                |

{% hint style="info" %}
The placement estimate is based on the content of the email only. Actual inbox placement also depends on sender reputation and authentication.
{% endhint %}

#### **Verdict**

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2FSquVYvkzidXYO8KXeNhc%2Fimage.png?alt=media&amp;token=ca5f9021-ada0-46d9-bea8-206950b8b83c" alt="" width="563"><figcaption></figcaption></figure>

Once every check has run, Batch assigns an overall verdict, so you know at a glance whether it is ready to send or needs another pass.

The verdict is based on critical findings and warnings only. Suggestions are excluded, so an email can carry open suggestions and still reach the highest verdict.

***

### Opt-in management

#### Unsubscribe link

An unsubscribe link is **required** in all marketing emails. When a recipient clicks it:

* They are unsubscribed from your marketing emails.
* They are redirected to a confirmation landing page. See how to proceed in [Choosing a confirmation landing page](https://doc.batch.com/guides-and-best-practices/message/email/link-and-tracking-settings/how-to-add-an-unsubscribe-link-to-your-email-template-1#choosing-a-confirmation-landing-page).

Learn how to add an unsubscribe link: [How to add an unsubscribe link to your email template?](https://doc.batch.com/guides-and-best-practices/message/email/link-and-tracking-settings/how-to-add-an-unsubscribe-link-to-your-email-template-1)

#### Suppression Rules

Batch automatically maintains a suppression list based on the following rules:

| Event                      | Outcome                                                                                          |
| -------------------------- | ------------------------------------------------------------------------------------------------ |
| Hard bounce                | Address added to suppression list for **all** emails (marketing & transactional)                 |
| 5 consecutive soft bounces | Address added to suppression list for **marketing** emails only                                  |
| Spam complaint             | Recipient marked as **unsubscribed** (marketing); address is *not* added to the suppression list |

#### **Open tracking consent**

You can add a consent withdrawal link in your email templates. When a recipient clicks it:

* The profile's native attribute `$email_open_tracking_consent` is set to `denied`.
* Batch stops inserting the open tracking pixel in emails sent to that profile.
* The recipient is redirected to a confirmation landing page.

See more information in [Managing Email Tracking Pixels](/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/email-open-tracking-and-tracking-pixels/managing-email-tracking-pixels.md)

***

### Email Deliverability

Batch provides detailed resources on deliverability, sender reputation, and IP warm-up strategies. See [Email Deliverability](https://doc.batch.com/guides-and-best-practices/email-deliverability).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.batch.com/getting-started/features/customer-engagement-platform/message/email.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
