o send A2P SMS to UAE mobile numbers you must register the alphanumeric sender ID with the TDRA through a licensed local aggregator. UAE-based brands are typically approved in about 5-7 business days, and applications from entities without a UAE trade licence can take longer; promotional IDs require an 'AD-' prefix, and a No-Objection Certificate from both Etisalat (e&) and du is needed.
Who has to register, and how
The UAE Telecommunications and Digital Government Regulatory Authority (TDRA) governs A2P messaging into the country. Any brand sending application-to-person SMS — OTPs, alerts, reminders, or marketing — must pre-register its sender ID; unregistered IDs are blocked at the network layer. Registration is not done directly with the regulator but through a licensed local aggregator that submits the application and holds the operator relationships.
Timelines and the documents you need
| Applicant type | Typical approval time | Core documents |
|---|---|---|
| UAE-based entity | ~5–7 business days | Trade licence, Emirates ID of signatory, sender-ID request, NOCs |
| International entity | Can take longer; depends on documentation | Company registration, authorisation letter, sender-ID request, NOCs |
The single most under-appreciated requirement is the dual NOC: a No-Objection Certificate is needed from both UAE operators — Etisalat (e&) and du. An application that clears one operator but not the other does not go live. A licensed aggregator coordinates both in parallel, which is part of why going through one is mandatory rather than optional.
The AD- prefix rule
Content category drives the sender-ID format. Promotional messages — marketing offers, campaigns, loyalty promotions — must carry an 'AD-' prefix on the sender ID so recipients can identify advertising at a glance. Transactional and service messages — OTPs, banking alerts, delivery and appointment notifications — do not take the prefix. Getting the category wrong is both a compliance failure and a deliverability problem, because promotional content sent on a non-AD ID can be blocked.
The refreshed consent rules (October 2025)
The TDRA refreshed its Marketing SMS policy in October 2025, tightening the consent regime. Senders of promotional traffic must hold and be able to produce opt-in proof, logged in the Consent Management System, before messaging a recipient. In practice this means your marketing sender IDs are only as safe as your consent records — the registry approval gets you the ID, but the opt-in evidence is what keeps it compliant in operation.
Registration and the ongoing consent posture are two different jobs. BroadNet's sender-ID registry service handles the TDRA submission and dual-operator NOCs, and the platform enforces category rules and opt-in status on every outbound message.
Why applications get rejected
Most rejections are avoidable. The recurring reasons we see across UAE submissions:
- Trade-licence mismatch — the sender ID or use case does not match the activity listed on the applicant's trade licence.
- English-only documentation — supporting documents that should be provided in Arabic (or bilingually) are submitted in English only.
- Brand conflict — the requested ID collides with an existing registered brand or trademark.
- Length — the alphanumeric sender ID exceeds 11 characters.
- Restricted terms — the ID contains reserved, regulated, or prohibited words.
- Wrong category — promotional content requested without the 'AD-' prefix, or a marketing use case declared as transactional.
The wider regulatory clock
Sender-ID registration does not sit in isolation. The Central Bank of the UAE set a timeline to phase out SMS OTP for banking authentication by 31 March 2026, which changes how financial-sector senders should think about verification traffic even as they keep transactional sender IDs registered. Plan sender-ID and authentication strategy together. For UAE coverage specifics see our UAE coverage page, the step-by-step in our answer on sender-ID registration with the TDRA, and the cross-market view on our regulations hub.
Frequently asked questions
How long does TDRA sender-ID approval take?
For a UAE-based entity, approval typically takes about 5-7 business days. An entity without a UAE trade licence can take longer, because the documentation and operator verification take longer. Either way, the timeline assumes complete, correctly categorised paperwork and the required No-Objection Certificates from both Etisalat (e&) and du.
When do I need the AD- prefix on a UAE sender ID?
The 'AD-' prefix is required for promotional content — marketing offers, campaigns, and loyalty promotions. Transactional and service messages such as OTPs, banking alerts, and delivery notifications do not use it. Sending promotional content on a non-AD sender ID is a compliance failure and can be blocked at the network layer.
Why do I need a NOC from both Etisalat and du?
Because both operators terminate A2P traffic in the UAE, a sender ID must be cleared on both networks to reach all subscribers. An application approved by only one operator will not deliver reliably. A licensed local aggregator obtains both No-Objection Certificates in parallel as part of the registration.
What is the most common reason a UAE sender ID is rejected?
A mismatch between the requested sender ID or use case and the activity on the applicant's trade licence is among the most common. Others include English-only documentation, brand or trademark conflicts, IDs longer than 11 characters, restricted terms, and requesting promotional traffic without the 'AD-' prefix.
References
- TDRA — UAE Telecommunications and Digital Government Regulatory Authority: tdra.gov.ae
- Central Bank of the UAE — consumer protection and authentication: centralbank.ae
- GSMA — A2P SMS and sender-ID governance resources: gsma.com