> For the complete documentation index, see [llms.txt](https://help.activenow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.activenow.io/en/communication/message-delivery-statuses.md).

# Checking If a Message Reached a Participant

If a client says they didn't receive an email or SMS, you can verify it quickly in the communication history. ActiveNow logs every message sent, along with its delivery status — so you can see exactly whether it arrived or where it got stuck.

## Email communication history

Go to *Communication → E-mails history*. Each message shows a delivery status on the right.

<figure><img src="https://2983515171-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL5ksnUuhXGAx5afQd3MB%2Fuploads%2Fgit-blob-40d004a43d085bc4ec3b6b5d69c7a5fa4ed52116%2FZrzut%20ekranu%202026-05-25%20153754.png?alt=media" alt=""><figcaption></figcaption></figure>

## Email statuses

* **Accepted for delivery** — the email has been handed off for sending. No further information is available yet. Messages stay in this status briefly after being sent.
* **Delivered** — confirmed that the email reached the recipient's mailbox.
* **Temporarily undelivered** — the email was rejected by the recipient's server but will be retried automatically.
* **Delivery failure** — the email was permanently rejected. This usually happens when the address doesn't exist. Invalid addresses are automatically blocked to reduce this error.

{% hint style="info" %}
A participant says they didn't receive an email? Read more [here](/en/communication/email-not-delivered-to-participant.md).
{% endhint %}

## SMS communication history

Go to *Communication → SMS.* You will see all sent messages with the date, recipient, content, and delivery status.

![](https://2983515171-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL5ksnUuhXGAx5afQd3MB%2Fuploads%2Fgit-blob-bf1d3cd332d857409f5317482e150b61c081c65f%2FZrzut%20ekranu%202026-05-25%20153811.png?alt=media)

## SMS statuses

* **Delivered** — the message reached the recipient.
* **Sent** — the message was sent, but the operator hasn't returned a delivery report yet.
* **Accepted** — the message was accepted by the operator for delivery.
* **Not delivered** — the message did not reach the recipient. The most common cause is an incorrect phone number.
* **Expired** — the operator attempted to deliver the message, but the recipient's phone was switched off or out of range during all delivery attempts.

{% hint style="info" %}
A participant says they didn't receive an SMS? Read more [here](/en/communication/sms-not-delivered-to-participant.md).
{% endhint %}


---

# 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://help.activenow.io/en/communication/message-delivery-statuses.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.
