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

# Features documentation

- [Features](https://support.mailmergehow.com/support/features.md): Here is the list of our features, and related documentation
- [Rich emails](https://support.mailmergehow.com/support/rich-emails.md)
- [Attachments](https://support.mailmergehow.com/support/attachments.md): Discover how to add attachments : to your mails with Mail Merge for Gmail
- [Multiple recipients](https://support.mailmergehow.com/support/multiple-recipients.md): In this page, you will learn how to add multiple recipients in Mail Merge for Gmail
- [Images](https://support.mailmergehow.com/support/images.md): On this page, you will learn about the different ways to add an Image to your Mail Merge template
- [Email Tracking](https://support.mailmergehow.com/support/email-tracking.md): On this page, you will learn how to know if your emails sent with Mail Merge for Gmail📣have been opened.
- [Unsubscribe link](https://support.mailmergehow.com/support/unsubscribe-link.md): Adding an unsubscribe link lets your recipients opt out of your emails, thus reducing the risk of being flagged as spam, and to have a cleaner mailing list.


---

# 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.mailmergehow.com/support.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.