> 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/docs/docs_se/guider/guides/email-content/how-to-use-email-preheaders.md).

# Guide: Så här använder du e-postpreheaders

Hur du lägger till en preheader-text i ett e-postmeddelande så att mottagarna ser en anpassad sammanfattningsrad bredvid ämnesraden i inkorgen.

Den här guiden visar hur du lägger till en preheader i ett e-postmeddelande i eMarketeer.

Videon täcker hur du lägger till en preheader i e-postmeddelanden byggda från äldre mallar. För nyare mallar hittar du preheadern i e-postinställningssektionen.

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

## Vad en preheader är

En preheader är texten som visas bredvid ämnesraden när ett e-postmeddelande anländer i inkorgen. Som standard visar den den första texten i innehållet, men du kan anpassa den. Använd preheadern för att komplettera ämnesraden eller sammanfatta vad e-postmeddelandet innehåller. Ämnesraden får kontakten att öppna e-postmeddelandet — preheadern ger dig extra utrymme och ord för att höja öppningsfrekvensen.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.emarketeer.com/docs/docs_se/guider/guides/email-content/how-to-use-email-preheaders.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.