> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/guides/email-content/how-to-use-email-preheaders.md).

# Tutorial: How to use email preheaders

This tutorial shows how to add a preheader to an email in eMarketeer.

The video covers adding a preheader in emails built from older templates. For newer templates, you find the preheader in the email settings section.

{% embed url="<https://www.youtube.com/watch?v=XN8TcivLJu4>" %}

## What a preheader is

A preheader is the text that appears next to the subject line when an email arrives in the inbox. By default it shows the first piece of text in the content, but you can customize it. Use the preheader to complement the subject line or summarize what the email contains. The subject line gets the contact to open the email — the preheader gives you extra space and words to raise open rates.


---

# 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://support.emarketeer.com/guides/guides/email-content/how-to-use-email-preheaders.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.