SMS Not Delivered? Causes, DLR Codes and How to Fix Them

Is the sender ID registered and accepted?

If failures are concentrated on one operator or one country, suspect the sender ID. Many countries require alphanumeric sender IDs to be registered with the operators or regulator before they can be used. Unregistered IDs may be rejected, or replaced by a numeric sender, depending on the network.

Checks:

1. Confirm whether the destination requires registration. The sender ID checker and our country pages, for example Nigeria, list the rules.
2. Confirm the registered ID matches what you send, character for character (case and spaces matter on some networks).
3. Check that the registration covers the use case. In some markets registrations are made per use case (transactional or promotional).
4. Look for a change: a new ID, a changed account or a new route often triggers failures.

Our team can prepare and file registrations with you through the registration service. Approval decisions stay with operators and regulators, so plan ahead and allow for the lead times published on each country page.

Is content or link filtering blocking the message?

If delivery fails across operators for specific campaigns but works for others, look at the content. Operators filter A2P traffic with SMS firewalls and look for patterns that resemble spam or phishing.

Common triggers:

• Shortened or unfamiliar links, especially public link shorteners shared by many senders. Use a branded domain.
• Phishing-like wording: urgent account warnings, requests to "verify" details, prize language.
• Identical text to many recipients at high speed from a new sender ID.
• Wrong traffic type: promotional content sent as transactional.
• Blocked keywords that vary by country and operator.

Fixes: put your brand name first, keep the message short, use one clear link on a domain you own, and send promotional and transactional traffic separately. Text length also matters: Arabic and other non-GSM characters change encoding and segment counts, which affects cost and rendering. The SMS character counter shows segments, and our guide to Unicode and Arabic SMS explains the limits that follow from 3GPP encoding rules.

Is a do-not-disturb registry blocking promotional traffic?

In some countries subscribers can register to block promotional messages, and operators enforce it. In Nigeria, for example, the NCC's DND service lets any subscriber text STOP to 2442 to block unsolicited promotional messages, or pick categories they still want. Promotional messages to registered numbers are suppressed.

What to do: check the destination country rules, separate marketing from transactional traffic honestly, keep proof of consent and honour opt-outs. See our bulk SMS Nigeria guide for a worked case, and the DND registry glossary entry. Labelling a promotion as transactional to avoid a registry is a policy violation that can get the sender ID blocked.

Is the route the problem?

If numbers, sender IDs and content are clean but delivery still swings from day to day, suspect the route. Signs include missing receipts on one operator, sender IDs replaced by random numbers, long delays and receipts for phones that are off.

Check with your provider which route carries the traffic to that operator, and read grey route vs direct route SMS. Test on your own handsets, on each operator, at different times. If your provider cannot say how the path reaches the operator, that is your answer.

What is the fix checklist?

Work through this list in order and stop when the data explains the failures.

1. Pull a sample of failed messages with status, error code, operator and sender ID.
2. Group by operator, then by sender ID, then by campaign.
3. Identify the status: UNDELIV or REJECTD (go to steps 4 to 6), EXPIRED (step 7), no receipt (step 8).
4. Validate and normalise numbers; remove dead ones.
5. Confirm sender ID registration for each affected country and operator.
6. Review content and links; test a plain version of the message.
7. Review the validity period and retry policy; do not retry stale OTPs.
8. Test on your own handsets per operator; ask the provider about the route and receipts.
9. Fix one variable at a time and re-measure delivery per operator.

Worked example: a clinic chain's missing reminders

"Palmview Clinics" (synthetic) sends appointment reminders and sees many patients on one operator reporting nothing. The DLR report shows a block of UNDELIV on that operator, while the others deliver. The sender ID turns out to be registered on two of three networks. The team files the missing registration, switches reminders to plain text with the clinic name first, and runs an HLR check on the patient list, which removes a set of disconnected numbers.

Two weeks later delivery on the third operator matches the others. The team also sets a validity period of a few hours for reminders, so patients do not receive stale messages after an appointment passes.

How do you keep delivery rate high over time?

• Monitor delivery by operator and destination, not as one global figure.
• Alert on drops, since a registration change on one network can silently affect a whole segment.
• Keep opt-out and consent records, and clean lists regularly.
• Use fallback for critical messages, for example WhatsApp then SMS.
• Review sender IDs and templates whenever you add a country.

How OmniChannels.ai helps

SMS on OmniChannels.ai runs over BroadNet Technologies' direct operator connectivity, with summary and advanced delivery reports, filters and CSV export, and delivery webhooks that normalise statuses. HLR and number lookup is available, and we prepare and file sender ID registrations with you. If you want us to review a failing destination, book a demo and bring a sample of your delivery report. When SMS fails, a call can help; see the voice API for call fallback page.