> For the complete documentation index, see [llms.txt](https://daisychain.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daisychain.gitbook.io/help/email/email-overview.md).

# Email Overview

Daisychain supports sending personalized, mobile-friendly emails as part of [Automations](/help/organizing/automations.md). Daisychain doesn't currently support one-off email broadcasts or standalone campaigns — emails can only be sent through automation steps.

To get started, you’ll need to [configure your domain](/help/email/email-configuration.md) and [create your message](/help/creating-emails.md) when building an automation.

#### Unsubscribes and Deliverability

Daisychain automatically handles unsubscribe links in all email sends. If you have an integration with [Action Network](/help/integrations/action-network.md), unsubscribes are synced back, helping keep your lists clean and compliant.


---

# 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://daisychain.gitbook.io/help/email/email-overview.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.