> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/user-documentation/working-with-documents-and-reports/running-an-email-batch.md).
# Running an Email Batch
{% stepper %}
{% step %}
## Run the email batch
Once you have created an email batch, you must run it in order to send the emails. To run an email batch, click the last run date. If you have not run the batch before, this will appear as "Never Run".
{% endstep %}
{% step %}
## Create the email batch
This will take you to the email batch history page. To proceed with running the email batch, click "Create Email Batch".
{% endstep %}
{% step %}
## Confirm
You will be prompted to confirm the creation of the batch. This prompt will include the number of emails to be generated, as it will count the cases that will be processed.
Click "OK" to proceed and send the emails.
{% endstep %}
{% step %}
## View history
Once the batch has run, you will be presented with an overview of emails generated and a link to them within each case.
{% endstep %}
{% step %}
## View emails
Clicking the link in the mail merge history will take you to the corresponding case page and display the email.
{% endstep %}
{% step %}
## Batch history updates
As you run an email batch multiple times, each instance will be recorded on the "Email Batch History" page. Clicking any of the records under "See Results" will allow you to view the emails sent in each batch.
{% endstep %}
{% step %}
## Last run
On the "Email Batch" page, the "Last Run" column will update with the date and time the batch was last run.
{% endstep %}
{% endstepper %}
---
# 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://docs.agilecase.com/user-documentation/working-with-documents-and-reports/running-an-email-batch.md?ask=&goal=
```
`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.