BroadNet
The JournalIndustry
Industry

The economics of SMS deliverability in 2026: why cost-per-delivered-message is the only number that matters.

A rate card ranks providers by price per message. Your finance team should rank them by price per delivered message. The gap between those two numbers is where grey routes hide — and where most A2P budgets quietly leak. Here is how to measure the number that counts.

BroadNet Operator Solutions
10 min read
Industry · Issue 24
10 min read

ost-per-delivered-message is total spend divided by messages that actually reached a handset — and it is the only SMS cost metric that predicts business outcomes. A low price per message means nothing if a fifth of those messages fail silently on a grey route, because you pay to re-send, you lose the conversion the message was meant to drive, and your sender ID degrades along the way. This article shows how the two numbers diverge and how to measure the one that counts.

Where the two numbers split

A2P SMS has a real cost floor: the destination operator's A2P termination fee, which a legitimate provider pays to deliver over a direct route. When a quote sits well under that floor, the difference is not efficiency — it is a grey route, A2P traffic disguised as consumer P2P through SIM boxes, foreign HLR backdoors, or undeclared interconnects. It delivers cheaply until an operator firewall fingerprints and blocks it, after which delivery becomes intermittent. See what a grey route is.

Rule of thumb: if a per-country quote is more than ~40% below the next reputable provider, you are almost certainly pricing a grey route. The saving is on paper; the cost reappears as re-sends and lost conversions.

The hidden costs that close the gap

  • Re-sends — every undelivered message you retry is paid for twice (or more), so a 15% failure rate is not a 15% problem, it is a multiplier on your unit cost.
  • Lost conversions — an OTP that arrives late or never is an abandoned login or checkout; the cost of that failure usually dwarfs the message price.
  • Sender-ID degradation — grey routes cannot carry your registered alphanumeric sender ID reliably, so messages arrive from a raw number, cutting trust and response.
  • Operational drag — chasing oscillating delivery rates and generic error codes costs engineering time that a transparent route would not.
  • Compliance exposure — traffic that bypasses operator agreements carries regulatory and reputational risk that never shows up on the rate card.

A worked comparison

Consider two providers quoting for the same country. The numbers below are illustrative — plug in your own route-test figures — but the mechanism is exact. Provider A quotes $0.020 per message and delivers ~80%; Provider B quotes $0.023 per message on a direct route and delivers ~98%. Cost-per-delivered-message is simply the headline rate divided by the delivery rate, because every message you pay for that fails still has to be re-sent to reach the same person. So Provider A costs $0.020 ÷ 0.80 = $0.025 per delivered message, while Provider B costs $0.023 ÷ 0.98 ≈ $0.0235 per delivered message. Provider B — the pricier route on the rate card, 15% more per submit — is about 6% cheaper for every message that actually arrives. Put another way, landing 1,000,000 messages on handsets means sending 1,250,000 via Provider A (at $0.020 = $25,000) versus 1,020,408 via Provider B (at $0.023 ≈ $23,470): the direct route saves roughly $1,500 to deliver the same volume, before you even count the conversions Provider A's missing 20% cost you. That is why the direct route routinely wins on the number that matters. See how to reduce SMS costs the right way and how to improve delivery rates.

How to measure it yourself

  1. Run a paid test campaign to your real target countries, not a vendor's demo destinations.
  2. Audit the delivery-receipt (DLR) feed: direct routes return operator-specific error codes; grey routes return generic UNKNOWN failures. See what a DLR is.
  3. Track delivery rate by country and operator over two to three weeks — grey routes oscillate as firewalls catch and the aggregator re-routes.
  4. Compute spend ÷ delivered messages for each provider, then add the business value of the conversions that failed sends cost you.
  5. Validate lists with an HLR lookup first so you are not blaming the route for texting dead numbers. See HLR lookup.
BroadNet runs direct A2P routes to 200+ countries through 1,000+ operator connections at a 99.99% platform SLA, and returns operator-level DLRs so cost-per-delivered-message is auditable, not a guess. Ask for a route audit on your own traffic.

Frequently asked questions

What is cost-per-delivered-message?

It is total SMS spend divided by the number of messages that actually reached a handset, rather than the number you submitted. Because failed messages still cost money to send and to retry — and cost you the conversion they were meant to drive — cost-per-delivered-message reflects real economics in a way that the headline price per message does not.

Why is a cheaper SMS rate often more expensive?

Because the cheapest rates are usually grey routes with lower, unstable delivery. Once you factor in re-sending failed messages, degraded sender IDs, and lost conversions from OTPs and alerts that never arrive, the effective cost per delivered message on a cheap route commonly exceeds that of a higher-priced direct route.

How can I tell if I am on a grey route?

Three signals: a per-country price far below the reputable market rate; delivery rates that swing week to week as firewalls catch and the aggregator re-routes; and generic DLR error codes (UNKNOWN, 0x000000FF) instead of operator-specific reasons. Run a test campaign and audit the DLR feed to confirm.

Does validating numbers really lower cost?

Yes. An HLR lookup identifies invalid, inactive, or ported numbers before you send, so you stop paying to text numbers that can never deliver and you route correctly to the current operator. On large lists this removes a meaningful slice of wasted spend and sharpens your delivered-message denominator.

References

Was this useful?

How we write and review content

Written by

BroadNet Operator Solutions

Operator Solutions builds and runs SMS firewalls, SS7 protection, and revenue assurance for mobile operators. They have been doing it on MENA networks since 2003. They write about what they see.

The Journal, by email

One essay a month. Nothing else.

Subscribe and we'll send the next piece — engineering, regulation, or industry — the day it ships. No drip campaigns, no product pitches, no third-party sharing. Unsubscribe in one click.

We send one email a month. Unsubscribe anytime. See our privacy policy.

What you'll get
  • Long-form, not link bait
    Six to eleven minutes of focused writing on a single topic.
  • Written by operators
    Engineers, regulatory leads, and product writing in-house.
  • Region-aware
    MENA-grounded view on regulators, operators, and channel mix.
  • Once a month
    No drip campaign. One essay when there is one to share.
Stop reading. Start shipping.

Most of what we write we learned in production.

If this piece made you nod, we should probably talk. Bring the use case, the volumes, the markets — we'll come back with routing, pricing, and a reference customer you can call.

$ curl -X POST https://api.broadnet.me/sms/sendSms