> 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/sms-not-delivered-to-participant.md).

# SMS Message Not Delivered to a Participant

A participant says they didn't receive an SMS? The most common cause is an incorrect phone number in the system. Before looking for other reasons, confirm with the participant that the phone number on their profile is correct.

## Check the message status

You can check the status of every sent SMS in the communication history. Go to the ***Communication*** tab → ***SMS communication history***. Each message shows a delivery status.

Here's what each status means:

* **Delivered** — the message reached the recipient.
* **Sent** — the message was sent, but the operator hasn't returned a delivery report yet. This status usually appears shortly after sending.
* **Accepted** — the message was accepted by the operator for delivery.
* **Not delivered** — the message did not reach the recipient. The most likely cause is an incorrect phone number — verify it with the participant and resend the message.
* **Expired** — the operator attempted to deliver the message, but the recipient's phone was switched off or out of range during all delivery attempts.


---

# 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/sms-not-delivered-to-participant.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.