> 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/getting-started/campaign-basics/basics-send-email.md).
# How to send an email
The simplest path to sending an email in eMarketeer, from a finished email component to a delivered send-out.
This article walks through the simplest path to send an email in eMarketeer — from a finished email component to a list of contacts.
We skip the more advanced features here and focus on a straight-up send.
{% hint style="info" %}
Before you start, you need a finished email component. See [Creating your first email](/getting-started/campaign-basics/basics-creating-email.md) if you do not have one yet.
{% endhint %}
{% stepper %}
{% step %}
### Start the send-out
Go to the campaign that contains the email and click **Send**.
{% endstep %}
{% step %}
### Choose Send Now
This guide covers sending immediately. You also have the option to schedule the email for a later time.
{% endstep %}
{% step %}
### Send a test email or send to your contacts
**Option A — Send a test email to yourself (optional)**
To preview the email in your own email client, send yourself a quick test. Type your email address in the **Quick send** field and click **Send now**.
**Option B — Send the email to your contact list**
If you do not have a contact list yet, see:
* [How to create a new contact list](/guides/contacts-lists/new-contact-list.md)
* [Importing contacts from Excel or a spreadsheet](/guides/contacts-lists/import-contacts-from-excel.md)
First, select **eMarketeer Contact Database**.
Second, select **Contact List**.
Third, choose your contact list in the dropdown and click **Add this List**.
The list now shows as added to the send-out. To send to more lists, choose another list and click **Add this List** again. When you have added all the lists you want, click **Next**.
{% endstep %}
{% step %}
### Continue to the checklist
The next page, **2. Send Options**, shows the chosen list of recipients and offers options for more complex send-outs. For a simple send, you can skip the details here.
Click **Next** to proceed.
{% endstep %}
{% step %}
### Review the checklist and launch
The checklist shows whether any contacts from your list will be excluded from the send. eMarketeer automatically blocks contacts who are unsubscribed or otherwise should not receive the email. You do not usually need to worry about the numbers here — they are handled for you.
If you want the details, see [Understanding the email checklist](/references/references/email/checklist-explained.md).
Click **Launch E-mail** to address and send the email to the contacts in the list.
{% endstep %}
{% step %}
### The send-out is complete
After launch, the email is handed to the email servers, which usually finish addressing and sending within a few minutes.
{% endstep %}
{% endstepper %}
### What to do next
You can track the send-out and see detailed stats in the email report. See [Email report explained](/references/references/email/email-report-explained.md).
---
# 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/getting-started/campaign-basics/basics-send-email.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.
