SMS Delivery Reports: How to Read, Understand, and Profit from the Data

The metric that separates shooting in the dark from data-driven decisions

Most business owners who use SMS send a message, see that "it went," and that's it. No idea how many actually arrived, who didn't get it, why, and what to do about it. That's an expensive mistake. Delivery reports (DLRs for short) are the eagle's eye of any campaign — and they can shift profitability by tens of percent.

This article explains exactly what a delivery report shows, how to read it correctly, which actions to take based on it, and how to turn it from a data sheet into a daily work tool.

The three statuses — and what each one means

Every SMS that goes out comes back with one of three primary statuses. Understanding each is critical.

Delivered

The message reached the recipient's device. The ideal status. Healthy target: 97%+ of messages sent.

Important to know: "delivered" does not mean "read." There's a difference. Reads can only be measured directly when there's a link and someone clicks, or via read receipts on some systems.

Failed

The message didn't arrive. Possible reasons: wrong number, device off for a long time, carrier blocked it, or a temporary technical issue. Healthy target: under 3%.

When you have a failure rate above that, it's a warning sign — usually about the list, not the system.

Pending

The message was sent but no delivery confirmation yet. Usually this updates within minutes. If after 24 hours it's still "pending" — most likely it won't arrive (device off, or in extended airplane mode).

What a good delivery report must show

Not every SMS system offers the same level of detail. These are the fields a quality delivery report must include:

• Precise send time — down to the second

• Delivery time — to compute latency

• Current status — delivered/failed/pending

• Error code in case of failure (e.g., 404 — number doesn't exist, 420 — device off)

• Carrier of the recipient (Pelephone, Cellcom, Partner, HOT Mobile)

• Message cost — what you actually paid

• Unique ID per message (Message ID) for follow-ups

In Vibrate all of these are available in the UI and the API, with Excel export for deeper analysis.

Reading the data — what should actually worry you

Delivery rate below 95%

If only 90% of your messages are delivered, there's a problem — but not necessarily with the system. Most likely your list isn't current. Numbers that were replaced, typos, blocked numbers. The fix: list cleanup. In the guide to building an SMS list we detailed how to do this properly.

Delivery hit on a single campaign

If on a specific campaign the delivery rate suddenly dropped to 85%, there's a good chance the carrier blocked some messages. This happens when content looks suspicious (too many exclamation points, keywords like "free!!!"), or when the sender is unidentified. Check the message wording and the Sender ID.

High latency

If a message was sent at 10:00:00 and delivered at 10:00:47 — that's fine. If it was delivered at 10:15:00 — not fine. Delays of more than a minute or two hurt urgency-based campaigns ("today only!"). Check with your provider.

Differences between carriers

Sometimes you'll see 99% delivery on Pelephone but only 93% on Partner. It's rare but happens. Usually it's one of two things: an unintentional Sender ID block at a specific provider, or temporary technical noise on that provider's network.

Pay only for delivered messages — a fair model

An important principle not every SMS provider offers: pay only for messages that actually reached the destination. If a message failed, you don't pay. Makes sense, but some providers charge for attempts, not results.

Why is it important? Because it aligns interests. The provider earns only when you earn. In Vibrate the model is built in — you pay only for messages with "delivered" status.

Pre-send number validation (HLR Lookup)

HLR (Home Location Register) is a check that tells you whether a number is valid, active, and on which network — before sending the message. The check costs agorot. Sending to an invalid number costs whole agorot, plus reputation damage with the providers.

When is it worth running HLR?

• Before sending to an old list (over 6 months without contact)

• Before a big campaign (over 10,000 messages)

• Before sending to numbers that came from an unverified form

• Once a quarter, on the whole list, as routine cleanup

Excel export and deep analysis

The dashboard is good for a quick scan, but real analysis happens in Excel or Google Sheets. A good system lets you export the delivery report down to every detail — dates, statuses, error codes, costs.

What to check in the export?

• Breakdown by hour: at which hours are failures highest? (If there's a spike around 22:00, devices may be off)

• Breakdown by carrier: is there a specific carrier with low delivery?

• Breakdown by segment: do longtime customers get more messages than new ones?

• Repeated failures on the same number: same number failed 3 times in a row? Remove from the list.

The connection between delivery reports and ROI

Delivery analytics alone isn't enough. You need to combine it with conversion metrics. In measuring ROI on SMS campaigns we laid out the full formula. A simple example:

• You sent 10,000 messages, 9,700 delivered (97%)

• 800 clicked the link (CTR 8.2% of deliveries)

• 80 made a purchase (10% of clickers)

• Average order value: ₪250

• Revenue: ₪20,000

• Campaign cost: ₪582 (only on the 9,700 delivered)

• ROI: 3,336%

Without a delivery report you wouldn't know the 3% that didn't arrive didn't arrive, and you'd wonder why CTR was "only" 8%.

Click tracking — the step after delivery

A delivery report says the message arrived. Click tracking says someone acted on it. It's done via short links with built-in tracking. In SMS the system converts your long link (e.g. vibrate.co.il/signup) to a short link that redirects automatically, collecting data: who clicked, when, from what device.

Combining the two reports — delivery + clicks — gives you the full picture. From there you can start to see what's actually working and what needs to improve.

Automatic actions based on reports

The advanced level: use reports not just to understand, but to trigger automations. Examples:

• A number fails 3 times in a row → automatic removal from the active list

• A message wasn't clicked within 24 hours → send a follow-up with an alternative offer

• A message was clicked but no purchase completed → reminder with a coupon

• Successful delivery → add the customer to an "active" list for future campaigns

Automations like this are a broad topic — in the ecommerce automations guide we detailed 9 essential automations.

The standard you should expect

When choosing an SMS provider, check that it provides:

• Real-time delivery report (not "within 24 hours")

• Access via UI and API

• Excel/CSV export in a click

• At least 12 months of history

• Detailed error codes (not just "failed")

• Webhooks to receive automatic updates in your system

The decision is yours — but the data should be visible

In Vibrate the delivery report is a basic part of the system, not an add-on. Every message sent is fully documented, every status updates in real time, and everything is exportable. You see exactly what you paid for and what you got. Start free and see what a delivery report looks like when done right.