> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/messages/sending-mailouts/delivery-report.md).

# Delivery Report

Open the Message Toolkit and select Mailout Counter.

Open the **Message** Toolkit and select **Mailout** Counter.

Search for the **Alert, Invitation or Newsletter** you would like to check delivery status for by setting your search criteria under the **Criteria** tab.

Under the **Criteria** tab you can specify your search criteria

* Sender
* Recipient
* Subject
* Status (Scheduled, Started, Completed, Cancelled)
* Scheduled before/after date and time
* Completed before/after date and time
* Message type (Invitation, Newsletter, Notification)
* Devliveries before/after date and time

Click the **Search** button.

Under the Results tab you will see the results based on your search criteria.

Click on the **Document Icon** (<i class="fa-file-alt">:file-alt:</i>), next to the **Subject**, to open the Delivery Report for that **Mailout**.

Scroll down to the bottom of the page and under the **Successful Deliveries** heading, you will find a list of all the deliveries and status of delivery for each mailout. If a detailed delivery report for a specific recipeint is required, click on the **Magnifying Icon** (<i class="fa-search">:search:</i>) next to the Recipeint's mailout to view the detailed report.


---

# 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://docs.shiftiq.com/help/messages/sending-mailouts/delivery-report.md?ask=<question>&goal=<user_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.