Read the state in the conversation
Receipts depend on the channel and receiving device. A conversation can continue even when a particular receipt is unavailable. A message state and an inbound reply are separate events.
- Pending: the send has not finished. It may be waiting for a device, dispatch, or a receipt.
- Sent: the send was accepted by the sending system. This is not proof of a reply.
- Delivered: a delivery receipt was recorded. It does not show that the recipient read or agreed to the message.
- Read: a read receipt was recorded where supported. Not every conversation or device provides one.
- Failed: the send reported an error. Read its explanation before deciding what to do next.
When a message is pending or times out
Check the selected number’s availability and the conversation’s latest messages. A timeout can mean the confirmation did not arrive in time; it does not always prove that the recipient received nothing.
Avoid repeatedly pressing send while the result is uncertain. If you need support, share the project, number, approximate time with timezone, and the message or request ID when available. Do not include API keys or passwords.
Uploads and message delivery are separate
Uploading a file makes it available for a send. The attachment’s message still needs to be sent and delivered. If a recipient cannot view it, check the message result, file format, and whether the file opens correctly on a test device.
Measure responses separately
Use Analytics to see how new leads respond. Delivered and read messages do not count as a contacted lead by themselves. A qualifying reply or confirmed human call answer is required for the new lead contact rate.