Channel Fallback & Routiing (3)

Your SMS program is reaching Safaricom numbers. Except the ones that silently dropped. And the campaign you sent after 6 PM that delivered to no one. And the branded sender name you configured that only works on transactional messages, not promotional ones, something your provider may not have mentioned when you set it up.

Pakistan's mobile market is one of the largest in South Asia and one of the least addressed in business messaging guides. With 193 million mobile subscribers, a population of 253 million of whom approximately 61% live in rural areas, and 116 million internet users as of early 2025, Pakistan is a market where SMS remains the most reliable channel for reaching audiences across both urban centers and rural communities where data connectivity is intermittent or unavailable. For development sector organizations, agricultural programs, financial services, and operational programs coordinating across geographically distributed teams, the case for building a Pakistan SMS program is straightforward. The compliance and carrier architecture that makes it work requires attention to four carriers that behave differently from each other, a national do-not-call registry that must be checked before promotional sends, and a data protection framework that is still developing.

India's SMS compliance system is unlike every other market in this series. In Nigeria, Kenya, and Tanzania, the core requirement is registering a sender name with each operator. In Australia and the US, you register with a centralized authority or registry. India requires you to register three distinct things, your business entity, your sender header, and the exact text of every message you intend to send, before a single message can reach a recipient. Miss any one layer, or let a single character in your message body differ from the registered template, and the carrier's system drops the message silently. Your platform shows it as sent. It never arrives.

Bangladesh gives its two SMS traffic categories names you will not find in any other market covered in this series. What most markets call an alphanumeric sender ID, Bangladesh calls masking SMS. What most markets call a numeric sender, Bangladesh calls non-masking SMS. The distinction is not just terminological. It determines whether your messages can reach NDNC-registered numbers, whether you can send outside business hours, which BTRC-licensed aggregator route is appropriate, and whether your brand name appears in the sender field at all. Getting the category wrong means either your messages reach the wrong numbers through the wrong route, or they fail to reach anyone reliably.

Most teams building SMS programs in Ghana discover the Sunday restriction after their first failed Sunday campaign. The setup seemed correct. The sender ID was registered. The contact list was clean. The messages were sent. And then the delivery reports came back empty, because promotional SMS cannot be sent on Sundays in Ghana, and it cannot be sent before 8 AM or after 7 PM on any day of the week.

Zambia is one of the more active SMS markets in Southern Africa for development sector, agricultural finance, and mobile money programs, and one where a specific carrier-level restriction catches international teams most often. MTN Zambia, the market leader, does not support dynamic alphanumeric sender IDs. A sender ID that has not been pre-registered and approved on MTN's network will generally be replaced by a generic numeric string, or may not deliver as intended. For a program targeting national reach across Zambia, that is not a technical footnote. MTN's market leadership means this requirement shapes how any program with national ambitions must be designed from the start.

A hotel group operating in Phuket, Koh Samui, and Chiang Mai has a messaging problem that most platforms do not design for. Its Thai guests expect to hear from it on LINE, Thailand's dominant super-app with approximately 56 million monthly active users and an open rate for business messages that exceeds 90%. Its international guests, arriving from Europe, Australia, China, the Middle East, and North America, expect WhatsApp, the app that was on their phone long before they landed in Thailand. SMS sits underneath both as the guaranteed-delivery layer for OTPs, booking confirmations, and critical operational alerts. And since October 2025, the National Broadcasting and Telecommunications Commission (NBTC) has required operators to flag international SMS with an alert symbol before delivery, which means unregistered international SMS increasingly arrives looking like a potential scam warning rather than a trusted hotel confirmation.

Every promotional SMS sent in the UAE must carry a specific prefix before the sender name or the message will not be delivered. The prefix is "AD-" and it has been mandatory since November 3, 2020, under TDRA regulation. A sender ID registered as "ACMELOGISTIC" cannot be used for promotional messages. It must be registered and submitted as "AD-ACMELOGISTIC." A sender ID without the "AD-" prefix will not be approved for promotional use, and promotional messages sent without it are likely to fail or be blocked at the carrier level. Most teams building UAE programs for the first time discover this requirement at sender ID registration, not during planning.

Beneath every customer-facing messaging channel sits a coordination layer that most platforms do not expose: the logic that decides when a message is sent, which channel it travels through, what happens if it fails to deliver, and whether the intended outcome was confirmed. This is the orchestration layer and it is what determines whether a communication system actually works, not just whether it sends messages.

Most communication systems look simple from the outside. A company sends messages, triggers reminders, or responds to customers on SMS, WhatsApp, Viber, or whatever channel is popular in that region. The experience looks straightforward. The reality beneath it is anything but.

Since August 12, 2024, every business SMS sent in Vietnam must include the organization's brand name or application name in the message body itself, and that name must match the registered alphanumeric sender ID exactly. Not in the sender field alone, which is how every other market in this compliance series handles brand identification, but in the body of the message, as a mandatory line of content. A hotel sending a booking confirmation, an agricultural program sending a field update, a logistics company sending a delivery alert: all of them must open each message with the brand identifier that matches the registered sender name, every time.

Connectivity completeness is the principle that a communication platform should be able to reach any recipient, on any channel, through any network without requiring the sender to manage that complexity. Routing decisions, fallback logic, and multi-network coverage are handled at the platform level. The operator decides who needs to receive a message and what it should say. The platform determines how to get it there.

Telerivet offers a complete connectivity solution for organizations to communicate in real time with customers, stakeholders, or staff anywhere in the world with an unmatched choice of providers.