Short answer
SMS messages usually fail to deliver because the number is invalid or inactive, the phone stayed off past the validity period, the sender ID is not registered for that country, the content was filtered as spam, or promotional rules blocked the send. Delivery reports show which: UNDELIV, EXPIRED or REJECTD each point to a different cause.
What are the most common causes?
| Symptom | Likely cause | Fix |
|---|---|---|
| UNDELIV or FAILED | Wrong format, inactive or ported number | Normalise to E.164 and clean the list with HLR lookups |
| EXPIRED | Phone off or out of coverage | Retry later or fall back to another channel |
| REJECTD or REJECTED | Unregistered sender ID or blocked content | Register the ID; review links and wording |
| No receipt at all | Operator returns no receipts | Ask your provider which routes return receipts |
| Marketing only fails | Quiet hours, DND list or missing opt-in | Send within permitted hours to opted-in contacts |
How do I diagnose a delivery problem?
- Check the API response: a rejected submission never reached the network.
- Read the delivery report status and error code for the failed messages.
- Group failures by country and operator to spot a pattern.
- Confirm the sender ID is registered for that destination and use case.
- Send a test to a known phone on the same operator.
- Share message IDs with your provider if the pattern persists.
What else can block SMS in the GCC?
UAE and Saudi operators expect registered sender IDs, and unregistered IDs are typically blocked. Promotional SMS is barred during quiet hours: 21:00 to 07:00 in the UAE under TDRA's spam policy, and 22:00 to 09:00 in Saudi Arabia under CST rules. Operator SMS firewalls also block suspicious links and traffic arriving over unsanctioned routes.
How can I recover failed messages?
For important messages, use channel fallback: if SMS fails, try WhatsApp or RCS, or the reverse. OmniChannels.ai supports configurable fallback order and normalises delivery statuses into one webhook format.