> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/guides/marketing/marketing-center/email-marketing/campaigns/creating-campaigns.md).

# Creating Campaigns

As an Admin, you can create Email Marketing Campaigns that send automated emails to Agents’ contacts for them. You can do this right from your dashboard without switching into each Agent’s account. These emails will automatically include the Agent’s signature at the bottom. You can see all the campaigns you’ve created or sent on your Insights page.

Agents can preview campaigns you’ve made in the Marketing Center or check all campaigns on their Insights page. If an Agent isn’t already included in a campaign, they can choose to join or save it for later. If they unsubscribe, it only affects their account, not the whole campaign.

Agents can also control whether you can add them to future campaigns. To protect privacy, you’ll only choose recipients by selecting the Agent’s tags—you won’t be able to see individual contacts.

{% embed url="<https://rechatq.wistia.com/medias/jyx359cavz>" %}


---

# 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://help.rechat.com/guides/marketing/marketing-center/email-marketing/campaigns/creating-campaigns.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.