> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/email/send-email-campaign/step-1-setup.md).
# Email step 1: Setup
Start an email campaign in Step 1 by naming it and continuing with the Text notification type; mail templates are selected in the next step.
For your **e-mail campaign**, the only available notification type option is **Text**. However, when you proceed to the **What** page, you will be able to select from all the designed mail templates you have created previously.
In this step, you need to:
* Enter a **Campaign Name**.
* Click **Save & Continue** to proceed to the next step.
#### Campaign name
The **Campaign Name** serves as an internal label to help you identify and differentiate between your email campaigns. It does **not** replace or override the Mail Subject line and will **not** be visible to your recipients.
This name is especially useful when managing multiple campaigns that may have similar subjects or content, allowing for better organization and tracking within your email marketing platform.
---
# 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://user.netmera.com/netmera-user-guide/omnichannel-engagement/email/send-email-campaign/step-1-setup.md?ask=&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.
