# SMS Delivery Receipts Explained | ZafeConnect

> What “delivered” means in an SMS delivery report, the other statuses you will see, why some destinations return less detail, and how to use the data.

Canonical URL: https://www.zafeconnect.com/blog/sms-delivery-receipts-explained
Language: en
Last modified: 2026-11-09

## Delivery receipts explained: what “delivered” really means

URL: https://www.zafeconnect.com/blog/sms-delivery-receipts-explained

Published: 2026-11-09

A delivery receipt tells you what happened to a message after you sent it. It is the most useful signal in messaging, and also the most misread.

Key takeaways:
- “Delivered” generally means the operator confirmed the message reached the handset. It does not mean the person read it.
- Status names differ between providers, but the stages are the same: accepted, sent, delivered, failed, expired or rejected.
- Receipts can be late, less detailed or missing in some destinations.
- Track delivery by country and operator, not as one global number.

### The statuses you will see
Names differ between providers, but most reports follow the same stages.
Status | Usually means | What to do
Accepted or queued | The provider has the message and will send it | Nothing yet
Sent or submitted | The message has been handed to the operator network | Wait for the final status
Delivered | The operator confirmed that the message reached the handset | Count it as a success
Failed or undelivered | The operator could not deliver it, for example because the number is invalid or blocked | Read the reason code; retry only if it makes sense
Expired | The operator kept trying until the validity period ended | Consider another channel
Rejected | The message was refused before sending, for example because of the sender or the content | Fix the cause

### What “delivered” does and does not mean
SMS has no read receipt. “Delivered” says the message reached the phone, not that anyone looked at it.

It is also not equally precise everywhere. In some destinations an operator reports “delivered” when the message is accepted by its own network rather than confirmed on the handset. This is one reason to look at delivery per country and operator.

### Why receipts can be late, missing or surprising

- The phone was off or out of coverage, so the final status arrives hours later or never
- Some operators return limited or no receipts for certain traffic
- Receipts can arrive out of order, for example “delivered” before “sent”
- Roaming and number porting can change which network answers

### How to use the data

- Delivery rate by country and by operator, to spot a weak route early
- Time from send to delivered, which matters most for one-time codes
- Failure reasons, to separate bad numbers from route or content problems
- A fallback rule: if a code is not delivered within a set time, offer another way
- A cross-check of your invoice, if you pay per delivered message

### How ZafeConnect fits
ZafeConnect passes on real operator delivery reports, includes analytics, and charges only for delivered messages. ZafeConnect reports a message delivery rate of over 98%, which is a reported rate and not a guarantee of delivery.

FAQ:
Q: Is a delivery receipt a read receipt?
A: No. SMS has no read receipt. A delivery receipt only says the message reached the handset, as far as the operator reports.

Q: Why does a message stay at “sent”?
A: The operator has not reported a final result yet, often because the phone is off or out of coverage. It usually ends as delivered or expired.

Q: Can I be sure every message is delivered?
A: No. Delivery depends on the destination, the operator and the recipient’s device. That is why reports and fallback rules matter.