# View Messages

Go to **TXT > View Messages** to see all TXT messages sent to and from your UbiQuity account. Click on any message to see the full content.

Note that only inbound messages matching a keyword for a TXT Programme in your account will appear here. Random or misdirected messages that do not match a keyword will not show up.

If you have sent TXT Outs, you can also view TXT history at the contact level by opening a database contact and viewing their contact history.

***

### TXT statuses

The Status column on the View Messages screen shows the current delivery status of each message. Statuses can sometimes update for a few days after a TXT Out has been sent as delivery receipts come back from carriers.

<table><thead><tr><th width="164.109375">Status</th><th>Meaning</th><th>Common examples</th><th>What happens next</th></tr></thead><tbody><tr><td>Scheduled</td><td>UbiQuity is preparing the message for delivery or attempting to deliver it.</td><td>The TXT Out is still being processed. The recipient's inbox may be full. UbiQuity may be having trouble reaching the carrier.</td><td>UbiQuity will either send the message successfully or attempt to resend.</td></tr><tr><td>Pending</td><td>UbiQuity has processed the message and it is queued for delivery.</td><td>—</td><td>The message will be delivered or move to another status.</td></tr><tr><td>Soft-bounce / Transient Failure</td><td>UbiQuity was unable to deliver the message and the retry schedule has been exhausted.</td><td>The recipient's inbox is full. The handset has insufficient funds. The carrier is experiencing temporary issues. UbiQuity is experiencing temporary issues.</td><td>The message will not be sent.</td></tr><tr><td>Error</td><td>UbiQuity has failed to process part of the TXT.</td><td>UbiQuity is unable to find a phone network for the recipient's number.</td><td>The message will not be sent.</td></tr><tr><td>Cancelled</td><td>The entire TXT Out has been cancelled.</td><td>A user cancelled the TXT Out using the Cancel button on the TXT dashboard.</td><td>The message will not be sent.</td></tr><tr><td>Hard-bounce / Permanent Failure</td><td>UbiQuity has failed to process the message or received a permanent failure from the carrier.</td><td>Number unreachable — the phone may be roaming or the shortcode may be blocked. The carrier rejected the message. A required merge field contained a blank value.</td><td>The message will not be sent. The contact will be automatically flagged as GNA and excluded from future TXT Outs.</td></tr><tr><td>Delivered</td><td>UbiQuity has successfully submitted the message to the carrier for delivery.</td><td>—</td><td>The contact should receive the message.</td></tr><tr><td>Received</td><td>UbiQuity has successfully received this message. Applies to inbound TXTs and STOP requests only.</td><td>—</td><td>—</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.ubiquity.co.nz/documentation/channels/txt/view-messages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
