SMS

Bulk SMS delivery reports explained

7 min read

Sending a message is only half the job. The other half is knowing what happened to it. A delivery report, often shortened to DLR, is the record that tells you whether a message reached the recipient’s handset, failed on the way or is still waiting. This guide explains what the common statuses mean, why reports sometimes disagree with reality, and how to use them in your own systems.

What a delivery report is

When you submit a message, the gateway accepts it and passes it on to the operator’s message centre. The operator then tries to deliver it to the handset and, where the network supports it, returns a status. The gateway collects these statuses and gives them to you, either through the dashboard, the API or a webhook. A report is therefore a chain of confirmations, and each link can add a delay or a gap.

Common statuses

  • Submitted or accepted: the gateway has your message, but it has not yet been delivered
  • Sent: the message has been passed to the operator
  • Delivered: the operator reports that the handset received the message
  • Failed or undeliverable: the message could not be delivered, with a reason where available
  • Expired: the message could not be delivered within its validity period, for example because the phone was off
  • Rejected: the message was refused, for example because of a template or sender ID mismatch
  • Unknown: the operator did not return a clear status

Gateways that use the SMPP protocol receive these as standardised values such as delivered, expired, deleted, undeliverable, accepted, unknown and rejected. A REST API usually presents them in friendlier words, but they map to the same ideas. Our guide to SMPP versus REST explains how reports arrive in each case.

Why “delivered” is not always final

A delivered status means the operator’s network reports handing the message to the handset. It does not prove that the person read it. Messages can also be delivered to a phone that is then lost, or to a device where notifications are muted. Treat delivered as strong evidence of delivery, not of attention.

Why some reports are late or missing

  • The handset is off or out of coverage, so the network keeps retrying until the validity period ends
  • Some networks return statuses slowly or in batches
  • A small share of messages may end with an unknown status when the network gives no final answer
  • Reports can arrive out of order, so a late “sent” should never overwrite an earlier “delivered”

Common reasons for failure

  • The number is invalid, inactive or switched off for a long period
  • The recipient has registered a do-not-disturb preference and the message is promotional
  • The template or sender ID does not match what is registered
  • The message contains a link or content that is not allowed for its category
  • The route is temporarily congested or the operator is having a problem

If many failures share a reason, fix the cause rather than resending. Re-sending a message that fails because of a template mismatch will only fail again. Our guides to DLT templates and promotional versus transactional messages cover the most common causes.

Using delivery reports in your system

  • Store every report against your own message reference, together with the time it arrived
  • Never overwrite a final status with an earlier one, and ignore duplicate events
  • For OTPs, offer a resend after a short wait if no delivered report arrives, and consider a voice call as a fallback
  • For campaigns, review failures afterwards and remove numbers that are permanently invalid
  • For support, let agents see the history of what was sent and what happened

Handling webhooks safely

If your gateway sends reports to a webhook, your endpoint should respond quickly, verify that the call really came from the gateway, and process each event in a way that is safe to repeat. Delivery reports may be retried when your endpoint is slow, so the same event can arrive twice. Use the message identifier to detect repeats. Keep the endpoint available during peak sends, since that is when reports arrive in volume.

Reading campaign results

After a campaign, compare the number submitted with the number delivered, failed and still pending. A high delivered share suggests clean data and a sound route, while a large unknown or expired share suggests list quality or timing issues. Look at the breakdown by operator and by failure reason rather than only the total. Avoid judging a campaign on the first few minutes, because slower networks report later.

Billing and reconciliation

Messages are normally billed by what is submitted and accepted, and long messages count by segment. Reconcile your invoice against your own sent log and the delivery reports, and ask your provider how failed messages are treated. Our guide to SMS segments explains why a single message can count as more than one.

Every SMS receives a delivery report through Orian’s messaging service. Include the message reference when contacting support about a specific issue.

Related services