--- title: "Getting messages into the Gulf: sender IDs, licensed aggregators and the AD marker" summary: "Business messaging in the UAE and Saudi Arabia is a registration and licensing question before it is a technical one, and a global platform does not inherit local standing." canonical: https://cpaas.co/en/learn/gcc-sender-id-registration kind: use-case depth: applied origin: original published: 2026-08-28T16:26:18.899Z updated: 2026-10-14T16:26:19.474Z topics: ["MENA", "Compliance", "A2P"] language: en --- # Getting messages into the Gulf: sender IDs, licensed aggregators and the AD marker Teams that have launched messaging in Europe or North America consistently underestimate the Gulf. The API integration is the same; the path to being allowed to send is not. Sender IDs are registered per operator, promotional traffic is marked and time-restricted, and in Saudi Arabia traffic must pass through a licensed provider. None of this is difficult, but it is serial and slow, and it decides the launch date. The details below reflect common practice as described by regulators and licensed providers in 2025–2026. Rules change; confirm current requirements with your provider before you plan around them. ## United Arab Emirates Business SMS is overseen by the Telecommunications and Digital Government Regulatory Authority (TDRA). In practice: - **Sender IDs are registered with each operator** (e& and du), not in one central registry. Approval from one does not cover the other. - **Promotional sender IDs carry an "AD-" prefix**, which providers report has been required since late 2020. Because sender IDs are limited to 11 characters, the prefix leaves eight for the brand. - **Transactional traffic** — codes, alerts, confirmations — uses a separate, unprefixed sender ID. - **Promotional sending hours are restricted.** Providers commonly cite no promotional SMS between 9pm and 7am. - **Consent must be documented**, and the UAE's personal data protection law (Federal Decree-Law No. 45 of 2021) applies alongside telecom rules. ```diagram:share # A promotional sender ID in the UAE: eleven characters AD- prefix | 3 | Required on promotional sender IDs The brand | 8 | What the prefix leaves for the name ``` ## Saudi Arabia The Communications, Space and Technology Commission (CST, formerly CITC) oversees the sector. - **Licensed providers.** Senders contract with an authorised service provider; traffic does not reach operators any other way. This is the constraint that most often surprises a global platform: coverage is not only a commercial matter. - **Registered sender names**, supported by documents such as a commercial registration or an authorisation letter. Numeric and unregistered international senders are heavily filtered. - **Promotional sender names carry an "-AD" suffix**, per provider guidance, and cannot be reused for service messages. Promotional quiet hours apply; providers quote slightly different windows, so confirm the current one. - **Personal data** falls under the Saudi Personal Data Protection Law. ```diagram:path # The only way a message reaches a Saudi operator Your platform | Sends under a registered sender name | Through a contract with an authorised provider Licensed provider | Authorised under CST rules | Hands the traffic to the operator Operator | Accepts traffic only through that route | Delivers it Handset | The message arrives > Coverage in Saudi Arabia is a licensing question, not only a commercial one. ``` ## The rest of the region Qatar, Kuwait, Bahrain and Oman each have their own operator-level sender ID processes, documents and lead times. They are broadly similar in shape — register the sender, separate promotional from transactional — but not identical. Plan each as its own workstream. ## The three regimes side by side ```diagram:compare | United Arab Emirates | Saudi Arabia | United States (10DLC) Who approves | Each operator, under TDRA rules | Licensed provider, under CST rules | The Campaign Registry, via your provider Sender identity | Registered sender ID per operator | Registered sender name with documents | Registered brand plus a ten-digit number Content declared as | Promotional or transactional sender | Promotional or service sender | A registered campaign with sample messages Promotional marker | AD- prefix | -AD suffix | Separation by campaign type Unregistered traffic | Not delivered | Not delivered | Blocked since early 2025 > Three regulators, no coordination between them, and a strikingly similar answer. That convergence is the thing worth planning around. ``` The same pattern appears in India (DLT registration of headers and templates), Singapore (the SMS Sender ID Registry) and Australia (the SMS Sender ID Register). See [10DLC registration without tears](/en/learn/10dlc-without-tears) for how these compare. ## Sequencing a Gulf launch Order matters more than effort, because several steps cannot start until the previous one has finished. ```diagram:flow # What has to happen before the first message Establish the entity | A trade licence in-market, or documents your provider accepts for a foreign entity. Nothing downstream starts without it. Choose the route | Direct with a licensed provider, or through a global provider that uses one. Ask which, in writing. Register the sender | Per operator in the UAE, per provider in Saudi Arabia. Not one submission, several. Separate the traffic | One sender for promotional, one for transactional. They never share an identity. Evidence the consent | Documented per person and per purpose, before the first send rather than at the first audit. > Weeks, not days, and largely serial. A plan that treats this as configuration will slip. ``` ## A worked example A European online retailer plans to launch order updates and weekly offers in the UAE and Saudi Arabia in one quarter. 1. **Week 1:** confirm the route. Their global provider reaches the UAE directly but Saudi Arabia through a licensed local partner — acceptable, but noted as a separate dependency. 2. **Weeks 1–2:** gather documents: trade licence, letters of authorisation on company letterhead, brand evidence. 3. **Weeks 2–5:** register four sender IDs: transactional and AD- promotional in the UAE (with both operators), service and -AD promotional in Saudi Arabia. 4. **In parallel:** add a separate marketing opt-in at checkout, and set promotional sends to respect local quiet hours in each country's time zone. 5. **Launch:** order updates first on the transactional senders; offers only once the promotional senders are approved. The integration work took a week. The calendar was set by registration. ```diagram:timeline # One quarter, two countries Week 1 | Confirm the route | Direct to the UAE; Saudi Arabia through a licensed local partner, noted as a separate dependency Weeks 1–2 | Gather documents | Trade licence, letters of authorisation, brand evidence Weeks 2–5 | Register four sender IDs | Transactional and AD- in the UAE with both operators; service and -AD in Saudi Arabia In parallel | Consent and quiet hours | A separate marketing opt-in; promotional sends set to local quiet hours Launch | Order updates first | Offers only once the promotional senders are approved > The integration took a week. Registration set the calendar. ``` ## The question that separates providers Ask one question and listen to the shape of the answer: *are you the licensed party in this market, or do you reach it through someone who is?* Both answers can be fine. A provider reaching Saudi Arabia through a licensed partner may deliver very well. But the failure modes differ. A direct licence means the provider owns the regulatory relationship and can escalate. A partner route means a party in the path you have no contract with, whose problems arrive at your desk as unexplained delivery failures. A coverage map is not an answer; a map is not a licence. ```diagram:decision # "Are you the licensed party in this market?" ? | Licensed directly | Through a partner Who owns the regulatory relationship? | The provider does, and can escalate | A party in the path you have no contract with — its problems reach you as unexplained delivery failures > Both can deliver well. The failure modes differ, and a coverage map is not a licence. ``` ## What to ask a provider - Are you licensed in this country, or do you use a partner? Which partner? - Which documents do you need for sender registration, and what is your current lead time per operator? - Do you enforce promotional quiet hours and the AD marker for me, or is that my responsibility? - What happens to my registered sender IDs if I move to another provider? ## Where to go next Next in this track: [telling people they are talking to a machine](/en/learn/disclosing-ai-in-a-conversation). For the wider market structure, read [regional messaging in the Gulf](/en/learn/regional-messaging-in-the-gulf); for language and layout, [Arabic-first is not translation](/en/learn/arabic-first-is-not-translation). ## Sources [^1]: [Telecommunications and Digital Government Regulatory Authority](https://tdra.gov.ae/) — TDRA (United Arab Emirates) [^2]: [Communications, Space and Technology Commission](https://www.cst.gov.sa/) — CST (Saudi Arabia) [^3]: [Enhanced measures against scam SMS](https://imda.gov.sg/Content-and-News/Press-Releases-and-Speeches/Press-Releases/2023/Enhanced-measures-against-scam-SMS) — Infocomm Media Development Authority (Singapore), 2023 --- Published by the company behind five products in this category. Those products appear in this site's directory alongside competitors under the same published criteria and are labelled as its own. Editorial content does not recommend them.