> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/analysis/outbound-history.md).

# Outbound History

## Purpose

Review execution results for outbound sends and campaign deliveries, including delivery states shown on the [Dashboard](/syntphony-messaging-portal/dashboard.md).

## Who this is for

Operators and supervisors validating campaign execution and resolving delivery issues.

## Prerequisites

* At least one outbound send or broadcast has been executed.
* Access to the Analysis module.

## Delivery states

Outbound and dashboard **Message Stats** use these states:

| Status        | Meaning                                                                |
| ------------- | ---------------------------------------------------------------------- |
| **Delivered** | Message reached the recipient channel endpoint.                        |
| **Read**      | Recipient read the message when read receipts apply.                   |
| **Pending**   | Message is queued or awaiting final delivery confirmation.             |
| **Failed**    | Delivery did not complete; review failure reason in the record detail. |

## What to track

* Delivery status by time range.
* Volumes sent by source.
* Failure reasons for retries or template corrections.
* Exported records for offline review.

## Steps

1. Open **Analysis** and go to **Outbound History**.
2. Select date range and source filters.
3. Open the outbound records list and review status per recipient or batch.
4. Investigate failure reasons when status is not delivered.
5. Export a report when operational follow-up or compliance review is required.

## Expected outcome

Operations teams can validate campaign execution, reconcile dashboard delivery stats, and act on delivery issues.

## Related pages

* [Analysis](/syntphony-messaging-portal/messaging-tools/analysis.md)
* [Message History](/syntphony-messaging-portal/messaging-tools/analysis/message-history.md)
* [Broadcast Message](/syntphony-messaging-portal/messaging-tools/communication/broadcast-message.md)
* [Dashboard](/syntphony-messaging-portal/dashboard.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://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/analysis/outbound-history.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.