SMS not delivered? Why text messages fail and how to fix each cause

First, read the status properly

With an SMS not delivered, the temptation is to resend. Resist it, because a second attempt with the same cause fails the same way and may annoy the recipient if the first one arrives late. Start by finding out what the status actually says.

Your provider's status and error code live in the delivery receipt, which arrives by webhook. If you are new to this, read our guides on delivery receipts and SMS delivery reports, and keep the error code list open.

The 12 most common reasons an SMS is not delivered

Problems with the number

1. Wrong format. The number lacks the country code or has extra digits. Use E.164 everywhere.
2. Inactive or disconnected number. The subscriber left the network or the number was recycled.
3. Landline or non-SMS line. Many landlines cannot receive texts. A HLR lookup shows the line type before you send.
4. Do-not-disturb registration. Some countries let people block marketing messages, and promotional traffic to them is refused.

Problems with the sender

1. Unregistered sender. Many countries require sender IDs, templates or campaigns to be registered. See sender IDs, 10DLC and DLT registration.
2. Sender not allowed in that country. Alphanumeric senders are accepted in some markets and replaced or blocked in others.
3. Poor sender reputation. High complaint or opt-out rates lead operators to filter your traffic.

Problems with the content

1. Template mismatch. In India the text must match the approved template exactly, including variables.
2. Blocked words or links. Public URL shorteners and some phrases trigger spam filters.
3. Encoding surprises. One emoji or accented letter changes the encoding and can split a message into several parts; see segments and encoding.

Problems with the route and the handset

1. Operator filtering or congestion. A route that is slow or filtered for one operator will show up as failures only on that network.
2. Handset off or out of coverage. The operator holds the message until the validity period ends, then reports it undelivered.

How to find the cause, step by step

1. Pull the message record. Get the id, the destination, the sender, the text and the final status with its error code.
2. Group failures. Count by country, operator, sender, template and hour. One group usually stands out.
3. Validate the number. Check format, status and line type with the number lookup.
4. Compare the text. Check it against the approved template or campaign and run it through the Unicode checker.
5. Test one handset. Send the same message to a phone on the affected operator and watch the receipt.
6. Escalate with evidence. If it still fails, send the ids and error codes to support so they can trace the route.

Delayed is not the same as failed

A message that arrives twenty minutes late has not failed, but for a one-time code it might as well have. Delays have a different set of causes from failures: a busy operator queue, a handset reconnecting, a sending window that holds promotional messages until morning, or your own rate limit pushing messages into a queue. For urgent traffic such as OTP SMS, use the transactional route, keep messages short and offer a fallback after a few seconds.

Message validity matters here too. If a message is given a short life and the phone is off, it expires and shows as undelivered. A longer validity helps for reminders and a shorter one for codes that become useless after a few minutes.

Failed, undelivered and delayed compared

Billing for failed and undelivered messages depends on the route and the country, so check your own rates rather than assuming. The SMSC at the operator is the system that holds a message for an unreachable phone and tries again until it expires, which is why undelivered statuses can arrive hours after the send. The SMS standard itself guarantees nothing about timing.

Checking the recipient side

Sometimes the platform did everything right and the person still did not see the text. It is worth a short checklist before you escalate. Ask whether the phone has signal and is not in flight mode, whether the sender is in a blocked or filtered folder, whether the phone has a spam filter that sorts unknown senders, and whether the number on the account is actually the one they use today. Ask for the time they checked, because a message that arrived overnight may simply have been missed.

For customers abroad, roaming can add delay or block messages from some senders. International numbers also behave differently from domestic ones, because some operators accept messages only from sender types they recognise. If a customer is travelling, a fallback to email or an app notification saves a support ticket.

Preventing delivery problems

• Validate numbers on entry and clean your list before large sends.
• Register senders, templates and campaigns before you launch in a new country. Our country rules guide lists what each needs.
• Keep message text in line with what was approved and avoid public link shorteners.
• Honour STOP immediately and read our guide on opt-outs and sending windows.
• Respect rate limits and spread large sends over time.
• Alert on delivery rate by operator so you see a drop within minutes, not days. The analytics dashboard shows this.

When messages are urgent or high value, use a second channel as a fallback, such as WhatsApp or a voice call, and compare the options in our guide to SMS, WhatsApp and RCS.

Reading a failed delivery event

{
  "id": "msg_8f3a2c",
  "status": "failed",
  "error": { "code": "TEMPLATE_MISMATCH", "detail": "Text does not match approved template" },
  "to": "+919812345678",
  "operator": "Example Telecom"
}

The event above is illustrative. The error code names the category, and the detail tells you what to change. Log both against your own record.

Treat every failed message as a clue. The pattern across many messages usually tells you more than any single one.