SMS deliverability
The proportion of sent SMS messages that are actually delivered to a recipient handset.
No account required · Results in under 60 seconds
SMS deliverability is the proportion of messages you send that actually reach a recipient's handset. It is distinct from send volume in a way that costs businesses real money: a messaging platform will accept, process and bill for a message aimed at a disconnected number that could never have been delivered.
Deliverability is not a single lever but the compound result of several independent factors. List quality, line type, sender registration, content, sending patterns and carrier reputation each contribute, and a failure in any one of them depresses the whole. That is why teams often find deliverability frustrating to debug: the symptom is a single falling percentage, but the causes are plural and largely invisible.
What is SMS deliverability?
Deliverability measures outcomes, not attempts. If you send ten thousand messages and seven thousand reach a handset, your deliverability is seventy percent regardless of how many the platform accepted or how many you were billed for.
The gap between accepted and delivered is where the interesting failures live. A message can be accepted by your provider, passed to a carrier, and then dropped by a spam filter without any party returning a meaningful error. It can be aimed at a landline that has no mechanism to receive it. It can target a number disconnected months ago whose owner never told you.
- ✓Accepted — your provider took the message and billed you for it.
- ✓Sent — it was handed to a carrier for delivery.
- ✓Delivered — a handset actually received it, which is the only figure that matters.
- ✓Failed — it was blocked, filtered, or aimed at a number that cannot receive SMS.
This makes SMS materially harder to diagnose than email. Email bounces return structured reason codes that distinguish a full mailbox from a nonexistent address. SMS commonly returns either nothing or a generic status that cannot separate a blocked message from an unreachable handset.
It is also worth separating deliverability from engagement. A delivered message that nobody reads is a content problem. A message that never arrives is a deliverability problem. Teams that track only click rates conflate the two and end up rewriting copy when the real issue is that a third of the list cannot receive messages at all.
Finally, deliverability is not static. The same list sent the same content through the same channel can perform differently month to month as numbers decay, carrier filtering evolves, and sender reputation shifts in response to past behaviour.
How SMS deliverability works
Every message runs a gauntlet. The provider applies its own acceptable use checks. An aggregator enforces throughput. The carrier evaluates registration status, applies spam filtering, checks the content against known patterns, and finally attempts delivery to the handset. Failure at any stage ends the journey.
Line type is the first and most absolute constraint, and it applies before any filtering logic engages. Landlines cannot receive SMS. VOIP numbers vary entirely by provider, with some supporting messaging and others discarding it silently. Only mobile numbers are reliably reachable.
- ✓Line type — landlines cannot receive SMS at all, and VOIP support varies by provider.
- ✓Number validity — unassigned and disconnected numbers fail permanently and should be suppressed.
- ✓Sender reputation — carriers score you on delivery outcomes, complaints and opt-out rates.
- ✓Content — restricted categories and public URL shorteners are common filter triggers.
- ✓Sending pattern — a sudden burst from a number with no history looks like an attack.
Number validity is the next. A number that was never assigned, or that has been disconnected and not yet reissued, fails permanently. These are hard bounces in email terms: retrying them achieves nothing and signals to carriers that the list is not maintained.
Sender reputation then governs how carriers treat the traffic that clears those hurdles. Carriers score senders on behaviour, including delivery success rates, complaint volumes, opt-out rates and sending patterns. A sender with a poor score sees more aggressive filtering applied to messages that would otherwise have landed.
Content filtering operates independently of everything above. Certain categories are restricted outright, links from public URL shorteners are frequently blocked because spammers rely on them, and phrasing that resembles known campaigns can trip heuristics. A perfectly registered sender with a clean list still loses messages to content rules.
Sending patterns matter too. A sudden burst from a number with no sending history looks like exactly what carriers are built to stop. Ramping volume gradually on a new number establishes a pattern that filtering treats more generously.
Finally, throughput shapes perceived deliverability. A campaign granted low messages-per-second does not fail when sent to a large list, it drains slowly, and a time-sensitive message that arrives hours late has effectively not been delivered even though it counts as a success.
Track delivery rate by segment rather than in aggregate. A single site-wide number hides the patterns worth acting on — failures concentrated in one carrier, one line type, or one acquisition source usually point straight at the cause.
Why SMS deliverability matters for SMS and outreach teams
The direct cost is the easiest to quantify. SMS is billed per send attempt, and carrier surcharges apply on top of provider rates. Every message aimed at a number that cannot receive it is paid for in full and returns nothing. Across a list of any size that waste is substantial and entirely avoidable.
The compounding cost is worse. Because carriers score senders partly on delivery outcomes, sustained failures degrade the treatment applied to your whole traffic stream. The undeliverable portion of a list does not merely waste its own send fee, it actively reduces delivery for the portion that would have succeeded.
There is a revenue dimension beyond cost. A message that does not arrive cannot convert, so poor deliverability caps campaign performance invisibly. Teams frequently respond by increasing send volume, which makes the underlying reputation problem worse rather than better.
Time-critical messaging suffers disproportionately. A one-time passcode that arrives after the login session expired is worse than useless, because the customer has already failed to complete the action and may have abandoned it entirely. Deliverability for transactional traffic is a conversion and support issue, not just a marketing metric.
Deliverability problems also mask themselves as other problems. Falling response rates get attributed to copy, offers or timing when the actual cause is that a growing share of the list stopped being reachable months ago. Measuring delivery separately from engagement is what prevents that misdiagnosis.
Getting started with SMS deliverability
Begin by establishing a baseline you trust. Measure delivery rate separately from open and click rates, and break it down by carrier, line type and acquisition source. Without that breakdown you cannot tell a content problem from a list problem.
- 1Baseline your delivery rate — Measure delivery separately from engagement, broken down by carrier, line type and source.
- 2Validate the list — Append line type and validity so landlines, unreachable VOIP and dead numbers can be removed before they fail.
- 3Suppress hard failures permanently — Invalid and disconnected numbers will never succeed; retrying them is one of the clearest signals of a neglected list.
- 4Warm up new numbers — Build volume over days rather than opening with a large burst, which is the pattern filtering catches hardest.
- 5Audit your content — Replace public URL shorteners with a branded domain and keep the sender identity recognisable.
Then revalidate on a schedule. Contact data decays continuously as people change carriers and abandon numbers, so a list cleaned once at import drifts back toward the state it started in.
Key takeaways: SMS deliverability
- ✓Deliverability is the share of sent messages that reach a handset, which is not the same as the number a platform accepted and billed for.
- ✓Landlines cannot receive SMS at all, and VOIP support varies entirely by provider, so line type is the first constraint.
- ✓SMS rarely returns diagnostic errors, making a blocked message hard to distinguish from an unreachable handset.
- ✓Carriers score senders on delivery outcomes, so undeliverable numbers degrade delivery for the reachable part of the list.
- ✓Billing is per send attempt, so every unreachable number is paid for in full and returns nothing.
- ✓Measure delivery by carrier, line type and acquisition source; a single aggregate rate hides the cause.
Frequently asked questions about SMS deliverability
What is a good SMS deliverability rate for a business campaign?
Why did my SMS delivery rate suddenly drop?
Do landline numbers affect my overall SMS deliverability?
How is SMS deliverability different from email deliverability?
Does sending more messages improve or hurt deliverability?
How often should I revalidate my phone list to protect deliverability?
Related terms and concepts
- List hygiene — Keeping a contact list accurate and current by removing or flagging unusable records.
- Soft bounce — A temporary message delivery failure that may succeed on a later retry.
- 10DLC — The US carrier framework for sending registered application-to-person SMS from a 10-digit local number.
- Line type — The classification of a phone number as mobile, landline, VOIP, or invalid.
- Disconnected number — A number that is no longer assigned to an active subscriber and cannot be reached.
Check your list before your next send
Upload a CSV and PhoneCheckr flags every mobile, landline, VOIP, and invalid number so you only pay to reach contacts who can actually receive your message.
Validate your phone list