## Why "Sent" Is Not the Same as "Delivered" When an SMS campaign finishes, the first number most people look at is how many messages went out. That number feels like a result, but it only tells you that your platform handed the messages to a provider. It says nothing about whether those texts actually reached a handset.
Between the moment you press send and the moment a phone buzzes, a message passes through several hands. Your sending platform passes it to an SMS provider. The provider passes it to a carrier, sometimes through one or more intermediate routes. The carrier tries to reach the handset, which might be switched off, out of coverage, roaming, or attached to a number that no longer exists.
Any of those steps can fail, delay, or silently drop the message. Delivery reports, usually shortened to DLRs, are how you find out what happened after the handoff. They are status updates that travel back along the same chain, from the carrier to the provider and from the provider to your platform. Reading them well is the difference between guessing at campaign performance and actually knowing it.
This guide explains what delivery reports are, what the common statuses mean, why some reports never arrive, and how to turn delivery data into decisions about routes, lists, and timing. It is written for teams that send bulk SMS through one or more providers and want their reporting to reflect reality rather than optimism. ## What a Delivery Report Actually Is A delivery report is a message about a message.
When a provider accepts your SMS, it usually returns an identifier right away. That first response means the provider took the message, not that anyone received it. Later, once the carrier knows more, a second status comes back tied to that identifier. That later status is the delivery report. There are usually two separate moments worth tracking: - **Submission.** Your platform sends the message to the provider and the provider accepts or rejects it.
A rejection here is immediate and usually caused by something on your side, such as a malformed number, a missing sender, an empty message, or an account problem with the provider. - **Delivery outcome.** After acceptance, the provider and carrier attempt delivery. The outcome comes back later, sometimes in seconds, sometimes after hours, and sometimes not at all. Mixing these two moments together is the most common reporting mistake.
A campaign can show near-perfect submission and still have poor delivery. If your dashboard only counts accepted messages, a struggling route will look identical to a healthy one. ### Where delivery reports come from Delivery reports start with the carrier that serves the recipient's number. The carrier tells the upstream route what happened, the route tells the provider, and the provider tells your sending platform, typically through a callback or webhook.
Every link in that chain affects the quality of the report you finally see. That is why two providers sending to the same country can produce noticeably different delivery data. One route might pass back detailed, timely reports. Another might return fewer reports, delayed reports, or generic statuses that hide the real reason a message failed. The quality of delivery reporting is itself a property of the route you choose.
## The Common Delivery Statuses and What They Mean Every provider uses its own vocabulary, and the exact names vary. Most of them, however, map onto a small set of outcomes. Learning those outcomes lets you compare providers on equal terms even when their labels differ. ### Delivered The carrier confirmed that the handset received the message. This is the strongest signal you can get.
It does not mean the recipient read the text or acted on it, only that it arrived. Treat "delivered" as the foundation of every other metric. Click rates, replies, and conversions should be calculated against delivered messages rather than sent messages. Otherwise a route problem looks like a copy problem, and you end up rewriting messages that were never seen.
### Failed or undelivered The carrier or route reported that the message could not be delivered. Failures fall into two broad groups, and the distinction matters for what you do next. - **Permanent failures.** The number does not exist, has been disconnected, is not a mobile number, or cannot receive SMS. Retrying will not help. These numbers should be suppressed so they stop costing money and dragging down delivery rates on future sends.
- **Temporary failures.** The handset was off, out of coverage, had a full inbox, or the network was congested. These may succeed later, and many routes retry them automatically for a period before giving up. If your provider returns error codes alongside the failure, keep them. A pile of "failed" results means little on its own. A pile of failures that are all "unknown subscriber" tells you the list is stale.
A pile that are all "blocked" or "filtered" tells you something about your content, sender, or route. ### Expired The route kept trying to deliver the message but gave up when its validity period ran out. Expired messages usually point to handsets that stayed unreachable for a long time, such as phones that are switched off, travelling, or attached to numbers that are rarely used. A small share of expired messages is normal.
A rising share is worth investigating. It can mean your list contains many inactive numbers, or it can mean a route is struggling to reach a particular network. ### Rejected The message was refused before a real delivery attempt. Rejection can happen at the provider, at an intermediate route, or at the carrier.
Common reasons include a sender ID that is not allowed in the destination country, content that triggers filtering, a destination the route does not cover, or account-level limits. Rejections are usually the most actionable status because they often have a fixable cause. A spike in rejections right after you change a sender, a template, or a route is a strong hint about where to look.
### Pending, accepted, or buffered The message is somewhere in the chain and no final outcome has come back yet. Pending is normal for a short time after sending. It becomes a problem when large numbers of messages stay pending for hours. Messages that never leave pending are effectively unknown. Some may have been delivered without a report, others may have been dropped. Treat a stubborn pending share as a reporting gap, not as success.
### Unknown Some routes return an explicit "unknown" status, and some never return anything at all. Either way, you do not know what happened. Unknown is not the same as failed, and it is definitely not the same as delivered. ## Why Some Delivery Reports Never Arrive It is tempting to assume that every message eventually produces a report. In practice, there are several reasons the chain can break.
- **The carrier does not return reports.** Some networks provide limited delivery information or none at all, especially on certain international paths. - **The route does not pass reports upstream.** An intermediate route may receive a status and never forward it, or may forward a generic status instead of the real one.
- **Your callback is not set up or not reachable.** If the provider sends reports to a webhook that is misconfigured, offline, or rejecting requests, the reports are lost on your side even though they existed. - **Reports arrive after you stop looking.** Some reports for temporary failures and expired messages can arrive many hours after the send. A dashboard that only looks at the first hour will miss them.
- **The provider identifier was not stored.** A delivery report is matched to the original message by the identifier returned at submission. If that identifier was never saved, the report cannot be attached to anything. The practical lesson is simple: measure your reporting coverage. For every route, track the share of accepted messages that end up with a final status.
A route with excellent delivery but poor coverage may just be a route that hides its problems. ## How to Calculate Delivery Metrics That Hold Up Once you have statuses, the way you calculate rates determines whether the numbers are useful. A few rules keep the math honest.
### Use a consistent denominator Decide whether your delivery rate is calculated against messages submitted, messages accepted, or messages with a final status, and keep that choice consistent across routes and campaigns. Comparing a provider measured one way to a provider measured another way produces misleading conclusions. A common, practical set of rates looks like this: - **Acceptance rate:** accepted messages divided by submitted messages. - **Delivery rate:** delivered messages divided by accepted messages.
- **Failure rate:** failed, rejected, and expired messages divided by accepted messages. - **Reporting coverage:** messages with any final status divided by accepted messages. ### Report the unknown share se
Related Articles
Sent is not delivered. Learn to read SMS delivery receipts, map carrier status codes, and turn DLRs into suppression, retry, and reporting ops.
SMS drip campaigns send the right text at the right step of the journey. Here’s how to design sequences that stay compliant, feel personal, and drive action.
SMS has no undo. Use this pre-send QA checklist to catch segment surprises, broken merge fields, bad links, wrong senders, and mistimed sends.
Learn how AI intent scoring ranks inbound SMS replies so your team answers high-value leads first — without losing the human touch.
Customers do not experience your channels separately. They experience one brand that either feels coordinated or chaotic.
Discover how to accurately measure and significantly boost your SMS marketing ROI. Learn key metrics, best practices, and advanced strategies for maximizing returns in 2026.
New subscribers are the most attentive people you will ever text. Learn how to plan a short SMS welcome series: what to send, when, and how to measure it.
SMS works because it is personal and immediate. That same intimacy makes compliance non-negotiable.
Explore SESender
SESender brings audience preparation, contact validation, sender and provider controls, scheduling, delivery tracking, and campaign reporting into one workspace. Review the current product and pricing information before deciding whether the platform fits your messaging workflow.
Explore the platform or review pricing.