Gulf and African A2P traffic rarely fails on content first. It fails on identity. A sender string your customer recognizes gets filtered, rewritten, or hard-held at the border because the registration behind it was never filed, was filed against the wrong regulator, or was filed for the wrong channel. The MENA and Latin America messaging channels playbook names the regional shape of that problem at altitude. This post is the filing-level companion for the markets buyers ask about most: Saudi Arabia, the UAE, Kenya, Nigeria, Morocco, and Egypt, with regulator names as the surfaces expect them, the regime each market runs, where operator practice diverges from the regulator's rule, WhatsApp posture, quiet-hour windows, and the evidence set each filing carries.
Everything below is a tenant-owned registration playbook, not legal advice and not a delivery guarantee. Approvals are granted by the regulator or the operator in each market, lead times move, and coverage is enabled per tenant: a market listed here is not necessarily enabled on your account.
The regulators, as the surfaces name them
Registration forms, operator portals, and error catalogs each expect one specific name per regulator. The six this post covers:
- Saudi Arabia — CST. The Communications, Space and Technology Commission, the successor to CITC (the Communications and Information Technology Commission). Older checklists and 2024-era blog posts still say CITC; the 2026 filing surface says CST. Same registry lineage, renamed mandate.
- UAE — TDRA. The Telecommunications and Digital Government Regulatory Authority. Alphanumeric sender IDs answer to it, and the two consumer operators, Etisalat and du, enforce its registrations at the network edge with their own thresholds.
- Kenya — CA. The Communications Authority of Kenya. A2P sender IDs run through its submission posture, with operator-side filtering layered on top.
- Nigeria — NCC. The Nigerian Communications Commission. Registered alphanumeric sender IDs on the major operators; unregistered traffic gets rewritten or falls to long codes.
- Morocco — ANRT. The Agence Nationale de Réglementation des Télécommunications. Alphanumeric senders are tolerated subject to operator vetting, with promotional traffic policed.
- Egypt — NTRA. The National Telecommunications Regulatory Authority. A tightened registration posture, with reserved namespaces (government, banking) filtered at the operator level.
Each market's row in the country-rules reference carries the same structured fields (sender_types, registration, sender_rules, content_restrictions) the country requirements surface documents, and the formal filing walk-throughs live on the docs site under each regulator's page.
The regime map: who registers what, and how long it takes
| Market | Regulator | Alphanumeric sender ID | Registration | Lead time to plan |
|---|---|---|---|---|
| Saudi Arabia | CST (successor to CITC) | Allowed, pre-registered | Required | 2–6 weeks, empirically |
| UAE | TDRA | Allowed, pre-registered | Required | 2–4 weeks |
| Kenya | CA | Allowed, submitted per sender | Required for sustained A2P | 1–3 weeks |
| Nigeria | NCC | Allowed on major operators once approved | Required | 2–4 weeks |
| Morocco | ANRT | Tolerated, operator-vetted | Recommended | 1–2 weeks |
| Egypt | NTRA | Allowed, pre-registered | Required | 1–3 weeks |
Two reading notes before the per-market sections:
- Lead times are planning numbers, not promises. The KSA figure assumes evidence complete on first submission; missing documents add a round-trip each. The UAE figure assumes the license and use-case note match the sender string on first pass.
- Numeric senders skip most of this. Long codes and short codes provisioned at purchase carry their own identity everywhere above; the registrations in this table are the price of the brand string, not the price of sending.
Saudi Arabia: CST registration and the operator layer
The CST regime is the strictest in the corridor. An alphanumeric sender without an approved country-registration entry is held or rewritten at the border, and the send gate names the market when it holds traffic. The filing itself is one entry; the operator layer under it is where the day-to-day behavior shows up:
| Layer | What it controls | Lead time |
|---|---|---|
| CST alphanumeric registration | The brand string on MT traffic; unregistered alphanumerics held or rewritten | 2–6 weeks, empirically |
| Numeric sender provisioned at purchase | OTP and transactional traffic while the alphanumeric filing pends | Days |
| Use-case note on the filing | Promotional versus transactional scrutiny; financial and government-adjacent brands face deeper vetting | Filed with the registration |
The operator layer is where KSA surprises people. STC, Mobily, and Zain enforce the same CST rule with different latency and rewrite behavior: a sender that delivers cleanly on one operator can surface rewritten on another in the same hour. That asymmetry is operator-level, and it is why the answer to "my ID works sometimes" is to finish the registration, not to shop operators. While the filing pends, route OTP and time-critical traffic over the numeric sender the gate does not hold.
The UAE: TDRA entries and the Etisalat-du split
The UAE reads like Saudi Arabia with a two-operator enforcement layer. The TDRA entry is the regulatory artifact; Etisalat and du each apply it at their edge:
| Operator | Unregistered alphanumeric behavior |
|---|---|
| Etisalat | Filtered or rewritten to a generic route; rewriting is the common outcome on consumer traffic |
| du | Same regime, different thresholds; rewrites surface at different volumes than on Etisalat |
Two practical consequences. First, a test matrix that sends through one operator proves nothing about the other; the acceptance check for a new sender is delivery on both, and a rewrite on either means the entry is missing or mismatched, not that the operator is broken. Second, the entry and the operator layer move on separate clocks, so a freshly approved entry can deliver on one operator hours before the other. Plan against the slower of the two and keep the numeric sender as the fall-back identity.
Kenya and Nigeria: CA submission, NCC entry
Kenya runs a submission posture that reads like a light DLT equivalent: the CA expects A2P senders lodged with use case and sample traffic, and operators filter spam-shaped traffic carrying an unregistered brand string. The evidence set that clears first pass is the boring one: business registration, the use case, and representative samples. Promotional traffic without the lodging degrades first; OTP on a numeric sender does not wait on it.
Nigeria pairs an NCC registration with operator consent. Registered alphanumeric sender IDs deliver on the major operators (MTN, Airtel, Glo, 9mobile); unregistered strings are rewritten or dropped to a long code, and a registered ID still answers to the national do-not-disturb registry on promotional traffic.
| Market | Regulator | Alphanumeric posture | Evidence the filing carries |
|---|---|---|---|
| Kenya | CA | Lodged sender with operator-layer filtering; treat as pre-launch work | Business registration, use case, sample templates |
| Nigeria | NCC | Approved on major operators; unregistered traffic rewritten | Business registration, authorization letter, use case |
Morocco and Egypt: the corridor rows
The two North-African rows are lighter than the Gulf regimes but not free. Morocco's ANRT tolerates alphanumeric senders subject to operator vetting; the risk is not a hard hold but progressive filtering of unvetted promotional traffic, so the registration is a stability step a sustained program does in week one. Egypt's NTRA runs a tighter posture: reserved namespaces for government and banking are filtered at the operator level, and alphanumeric senders outside those namespaces still clear a registration before they carry sustained volume.
| Market | Regulator | Sender-ID posture |
|---|---|---|
| Morocco | ANRT | Alphanumeric tolerated, operator-vetted; promotional traffic policed |
| Egypt | NTRA | Registration before sustained volume; reserved namespaces filtered at operator level |
WhatsApp posture per market
WhatsApp to these markets answers to Meta's WABA rules, not to the telecom regulator, and the two review tracks do not recognize each other: a CST-approved sender ID does not satisfy Meta's display-name review, and a WABA-approved display name does not satisfy the CST. Plan them as parallel calendar items.
| Market | WABA display-name review | Review latency to plan |
|---|---|---|
| Saudi Arabia | Standard display-name approval; financial and government-adjacent names draw extra review | Add a week over the baseline |
| UAE | Standard approval; brand trademarks verified against the license | Baseline plus a few days |
| Kenya | Standard approval; fewer escalation paths, so rejections cycle slower | Baseline |
| Nigeria | Standard approval; high template volume means queue variance | Baseline plus a few days |
| Morocco | Standard approval; French and Arabic display names reviewed in their own queues | Baseline |
| Egypt | Standard approval; Arabic script verification on government-adjacent names | Add a week over the baseline |
The template discipline from the regional playbook carries over: anything outside the customer-initiated window goes through pre-approved templates, so template design belongs in onboarding with the same lead-time thinking as the sender registrations above.
Quiet hours and calendar windows
| Market | Window | Source |
|---|---|---|
| Saudi Arabia | Friday prayer window; Ramadan shifts evening traffic patterns | Convention, operator-enforced in practice |
| UAE | Religious holidays; Ramadan daytime caution for promotional traffic | Convention |
| Morocco, Egypt | Promotional windows policed per campaign type | Regulator-adjacent, check per campaign |
| Kenya, Nigeria | No general statutory A2P window | Set your own policy |
None of the six markets runs a statutory after-hours ban on the shape France does (20:00–08:00, Sundays and holidays), but the Gulf calendars behave like one in practice: traffic into KSA during the Friday prayer window and into both Gulf markets on religious holidays draws complaints and operator attention that a quiet-hours policy would have avoided. Quiet hours on Devotel Orbit are a tenant-configured control: set the window per market, per campaign type, and the platform holds the send to the window you chose. The calendar judgment is yours; the control is there to make it enforceable.
What the required-vs-recommended playbook already carries, and which Gulf rows it does not
Read Sender-ID Registration: Required vs Recommended vs Absent — Which Market to Launch First for launch sequencing. It ranks Saudi Arabia fourth and the UAE fifth among the ten markets customers launch into most, with the per-market send-gate code and the single highest-yield first action, and its effort-times-impact ranking is the right ordering tool. What it does not carry, and what this post owns until those rows are folded in:
- Operator-level divergence. The STC-Mobily-Zain enforcement split and the Etisalat-du rewrite thresholds appear nowhere in its KSA and UAE rows, which stop at the regulator layer.
- Lead-time numbers. Its Saudi row names the registration but not the empirical weeks a filing takes; this post's regime map does.
- Quiet-hour and calendar windows. Absent for KSA and UAE in that post; the France and Germany rows carry timing rules that the Gulf rows do not yet.
- WABA review latency per market. The post states the SMS-versus-WABA separation as a principle (Brazil row) but carries no per-market WhatsApp review latency, Gulf or otherwise.
- Kenya and the North-African rows. Nigeria appears only in the regional routing matrix of the MENA and Latin America playbook; Kenya, Morocco, and Egypt have no row in either ranking, and the formal NTRA walk-through lives on the docs site, not in the launch-order comparison.
Use the sequencing post to order the work and this post to file it; where the two disagree on a detail, the live GET /compliance/country-rules row is the answer at send time.
Frequently asked questions
Is it CITC or CST on a 2026 filing?
CST. The Communications, Space and Technology Commission succeeded CITC, and current filing surfaces use the CST name. Older checklists, operator letters, and blog posts that say CITC point at the same registry lineage; do not let the older name on a template delay a filing.
Can we send to Saudi Arabia on a numeric sender while the alphanumeric registration pends?
Yes. The registration gate holds alphanumeric traffic; numeric senders provisioned at purchase are exempt and deliver. The common launch shape is numeric sender for OTP and time-critical traffic from day one, alphanumeric brand string switched on per use case as entries approve.
Does one TDRA entry cover both Etisalat and du?
The regulatory entry is one; enforcement is two operator layers with separate sync clocks and thresholds. Approve the entry, then verify delivery on both operators before calling the sender live, and expect a window where the sender delivers on one and rewrites on the other.
Who owns the registration evidence and the approval?
Your team. The tenant configures the compliance posture, files the registrations, and owns the evidence set: business registration, authorization letters, use-case notes, and sample traffic. Devotel Orbit carries the documents and settings you attach and routes traffic per the posture you set; the approval itself is granted by the regulator or operator in each market, never by the platform.
Source and further reading
- MENA and Latin America messaging channels playbook: the regional channel-order and gray-route companion this post drills into.
- Sender-ID Registration: Required vs Recommended vs Absent: the launch-order ranking across the ten most-launched markets.
- Saudi Arabia CST sender rules: the formal filing walk-through for the KSA row.
- UAE TDRA sender rules: the formal TDRA entry reference.
- Egypt NTRA sender rules: the NTRA posture in full.
- Country-rules directory: request curation for a market whose row is missing or stale.
- Sender-ID registration workflow: the tenant-side registration surface on Devotel Orbit.
Published 15 October 2026.