SMS Delivery Receipts (DLRs): Statuses, Handling, and Fakes

Why 'sent' tells you almost nothing

When an SMS API returns queued or sent, it means one thing: the provider accepted your request. Not that a carrier took it. Not that a handset received it. The SMS delivery receipt (the DLR) is the asynchronous callback that reports what actually happened, and it can arrive seconds or minutes later. Treating the send response as delivery is the single most common mistake in SMS integrations, and it hides every real delivery problem you have. For the authoritative reference, see A2P 10DLC registration.

Get DLR handling right and you gain the one thing that makes SMS operable at scale: ground truth. Get it wrong and you are flying blind, believing a 99% 'sent' rate while a chunk of it never lands.

The status lifecycle

The two that teach you the most are expired and undelivered. A cluster of either on one destination is your early warning of a route problem or a number-quality problem. That is exactly the signal the firewall and grey-route articles describe from the carrier side. Single fa

Handling callbacks without shooting yourself

DLRs arrive by webhook, out of order, sometimes twice, sometimes late. Four rules keep the handler correct. The same ones the Node.js tutorial implements in code.

• Be idempotent. Key every update on the message id. Duplicate DLRs are normal; a non-idempotent handler double-counts them.
• Acknowledge fast, process async. Return 200 immediately, then do the work. A slow endpoint gets your callbacks throttled or dropped by the provider.
• Respect ordering. A late sent can arrive after delivered. Never let an older status overwrite a newer terminal one. Track a state machine, not a last-write-wins field.
• Record the timestamps. delivered minus sent is your real latency distribution. Graph it per country. It is the metric users actually feel, per our OTP latency method.

Spotting fake DLRs

Here is the uncomfortable part: not every 'delivered' is true. Grey-route operators and low-quality aggregators sometimes fabricate delivery receipts, because a fake delivered hides their real failure rate and keeps you paying. A DLR you cannot trust is worse than no DLR — it is a lie with a green checkmark.

1. Seed real SIMsKeep a panel of prepaid SIMs you control in your key destinations. They are your source of truth.
2. Compare DLR to handset realitySend to the panel; a message the provider marks 'delivered' that never appears on the handset is a fabricated receipt. This is the core check in our delivery benchmark method.
3. Watch impossible timingSub-second 'delivered' receipts across every message, or delivery rates that never dip regardless of destination, are statistically implausible. Real networks have variance.
4. Cross-check against verification rateIf DLRs say 99% delivered but your OTP entry rate is far lower than usual, the receipts and the users disagree — trust the users.

SMSRoute is a no-KYC SMS API with crypto billing (BTC, ETH, USDT, XMR, LTC, and SOL) on direct routes, and our position on DLRs is the one this article argues for: we return real carrier-sourced receipts you can audit against your own seed SIMs, and we would rather you run that test than take our word. Fund the $5 credit, send to phones you control, and compare. Honest DLRs survive that check; fabricated ones do not.

SMSRoute's published route pages list delivery from $0.004/message (premium direct-carrier corridors up to $0.035) with sub-100ms median submission and ~98.6% delivered success (smsroute.cc route pages, 2026).

Related reading

FAQ