What happens when a business text fails to deliver
The difference between sent, delivered and read, the common reasons a text never arrives (unregistered number, landline, carrier filtering, blocked), and what your system should do about each.
Frontiva · · 4 min read
"Sent" means your provider accepted the message. "Delivered" means the carrier reported it reached the phone. Nothing in between guarantees the customer saw it, and a message can be "sent" and never arrive. The common causes are an unregistered sending number, a landline or invalid number, carrier spam filtering, and a customer who blocked the number. Each shows up differently, and a good system tells you which one happened and does something about it.
Sent, delivered, read
Sent: your platform handed the message to the messaging provider. It says nothing about arrival.
Delivered: the carrier confirmed delivery to the handset. This is the status that means something, and it is not always available; some carriers do not report it.
Read: SMS has no read receipts. Channels like WhatsApp and Messenger do. If a system shows "read" for an SMS, it is guessing.
Failed: the carrier rejected it, with an error code that usually says why.
Cause 1: unregistered number
U.S. carriers filter or block business texts from 10-digit numbers that are not registered through A2P 10DLC. The symptom is quiet: messages show as sent, some or all never arrive, and reply rates collapse. Fix: register before sending. Our 10DLC guide covers it. If you were sending fine and delivery dropped, check whether a campaign registration expired or was rejected.
Cause 2: landline or invalid number
Landlines cannot receive SMS. Numbers with typos do not exist. Both come back as failures with a clear code, and the system should mark the contact so it does not keep trying. For landline callers, route to a voicemail-to-callback flow instead of texting.
Cause 3: carrier filtering
Even from a registered number, carriers filter messages that look like spam: lots of links, shortened URLs from public shorteners, all-caps, phrases associated with scams, or a sudden spike in volume. The message may be silently dropped. Fix: plain wording, links on your own domain, steady volume, and a registered campaign whose description matches what you actually send.
Cause 4: blocked or opted out
A customer who replied STOP is opted out, and the platform must not send; that is not a failure, it is correct. A customer who blocked the number on their phone will show as delivered or failed depending on the carrier, and you will not know for certain. If a customer who used to reply has gone completely silent across several messages, assume they do not want them.
What the system should do
- Show the real status per message: sent, delivered, failed, with the reason.
- Stop retrying numbers that failed as invalid or landline, and flag them on the record.
- Alert someone when the delivery rate drops, because that is how registration problems and filtering show up.
- Never mark an SMS as read.
- Fall back to another channel where one exists and the customer consented: email for a confirmation, a call for something urgent.
What to check when reply rates drop
Delivery rate first. If delivered is far below sent, it is registration or filtering. If delivered is fine and replies fell, it is the wording or the timing. Then check whether the number changed, whether a campaign was edited, and whether volume spiked. Most "the texts stopped working" problems are one of those.
Frequently asked questions
Why does a message show delivered when the customer says they never got it?
Delivered means the carrier reported reaching the handset. The customer's phone may have filtered it into an unknown-senders folder, or they may have missed it. Ask them to check; if it happens repeatedly, the number may be flagged on their device.
Should I resend a failed message?
Only if the failure was transient (a carrier timeout). Invalid numbers and landlines will fail again. The system should know the difference from the error code.
Is WhatsApp more reliable?
It has delivery and read receipts and no carrier filtering, but the customer has to have WhatsApp and to have messaged you first. Reliable for those customers; not a replacement for SMS.
What Frontiva does here
Frontiva tracks delivery status per message back from Twilio and shows it in the unified inbox. Numbers and 10DLC registration live in your own Twilio account today, so registration problems show up there first. Delivery-drop alerts are not built. See A2P 10DLC for the most common cause of silent failures.