By Digitize Bird
To send compliant SMS in the UAE, you need a registered sender ID, documented opt-in consent, and messages sent only between 7 AM and 9 PM. Promotional and transactional SMS follow different rules. The TDRA enforces all of this through the mobile operators, not just on paper. Get any piece wrong, and your messages simply stop delivering.
We’ve registered sender IDs for retail, healthcare, and logistics clients across the UAE. Almost every compliance issue we see traces back to one thing: businesses assume SMS rules work the way email rules do. They don’t. Here’s what actually matters.
What Is the TDRA, and Why Does It Regulate SMS So Closely?
The TDRA is the UAE’s Telecommunications and Digital Government Regulatory Authority. It oversees every licensed telecom operator in the country, including Etisalat and du. Because SMS runs through those operators’ networks, the TDRA effectively controls what can be sent, to whom, and when.
This matters more than in most markets. SMS in the UAE is treated as a high-trust channel. People still act on text messages here in a way they’ve stopped doing with email. The TDRA protects that trust aggressively, because losing it hurts everyone who relies on SMS to run a business.
Who Actually Needs to Register a Sender ID?
Any business sending SMS under its own brand name needs a registered sender ID. This applies whether you’re sending promotional offers or appointment reminders. The sender ID is the name your customer sees instead of a random number.
Registration goes through your SMS provider, who submits it to the relevant operator on your behalf. We handle this step for every new client, because an unregistered or expired sender ID gets blocked without warning. There’s no grace period. Your campaign simply fails mid-send, and you often don’t find out until customers start asking why they never got your message.
What Actually Counts as Valid Consent?
This is where we see the most confusion. The TDRA requires explicit consent before you send promotional SMS. That consent has to be written or electronic, and it has to be storable. A verbal agreement at checkout doesn’t count. Neither does a pre-checked box buried in your terms and conditions.
Practically, this means keeping a real record: a timestamped form submission, an app permission toggle, a signed physical form. If a customer disputes ever opting in, you need to produce that record. We build this into onboarding now, because retrofitting consent records after a complaint is far harder than collecting them properly from day one.
When Can You Actually Send a Marketing Message?
Promotional SMS in the UAE can only go out between 7 AM and 9 PM, UAE time. Anything outside that window is a violation, even if the content itself is fully compliant. This rule catches out businesses running global campaigns on autopilot, where a scheduled send doesn’t account for local time zones.
Transactional messages aren’t bound by this window in the same way. An OTP or a delivery alert can go out at 3 AM if that’s when the transaction happens. The distinction between promotional and transactional content is doing a lot of work here, which brings us to the next question.
Promotional vs Transactional: Where the Line Really Sits
The TDRA doesn’t judge a message by how polite or informational it sounds. It judges it by intent. If the message is meant to market, advertise, or drive a purchase, it’s promotional, no matter how the copy is worded.
A “your order has shipped” message is transactional. A “your order has shipped, and here’s 10% off your next one” message is promotional, because that second sentence changes the message’s purpose. We’ve had clients try to soften promotional content by making it sound like a service update. The TDRA and the operators see through this pattern quickly, and repeated attempts tend to draw more scrutiny, not less.
Can a Business Outside the UAE Send SMS to UAE Numbers?
International senders face a stricter rule. They can send transactional messages, like OTPs or account notifications, to UAE numbers. They generally cannot send promotional SMS directly to UAE recipients without working through a locally compliant route.
This is one reason global platforms sometimes struggle to deliver reliably here. Their default routing isn’t built around TDRA rules. For a business based outside the UAE but selling into it, working with a provider that already handles local registration removes this problem entirely, rather than discovering it mid-campaign.
What Happens If You Get This Wrong?
Consequences scale with the violation. Sender ID misuse can get that ID suspended, sometimes instantly, since operators can act without waiting for a formal complaint to escalate. Repeated consent violations put your ability to send SMS in the UAE at risk altogether.
Customers also have a direct way to fight back. They can text “BALL” to 7726 to block all promotional SMS, or a specific sender ID followed by “B” to block just that sender. Once a customer does this, that channel is closed to you, often for good. We treat this as the real cost of non-compliance. It’s not just a fine risk. It’s losing a customer’s attention permanently.
How We Approach This With Our Clients
We don’t treat compliance as a checkbox before launch. We build it into how a campaign gets set up in the first place. That means verifying sender ID status before a send, not after a failure. It means asking clients where their consent records actually live, not assuming they exist.
This slows down a first campaign by a day or two. It saves weeks of cleanup later, when an unregistered sender ID gets flagged mid-campaign. We’d rather have that conversation upfront than explain a blocked send to a client who’s already told their team the SMS is going out.
If you’re setting up SMS-based verification or two-factor authentication specifically, the compliance considerations shift again, since OTP delivery has its own reliability and timing expectations. We cover that in more depth on our SMS authentication solutions page.
A Practical Checklist Before You Hit Send
- Sender ID is registered and currently active, not expired
- Consent records exist for every recipient on your send list, in a storable format
- Send window falls between 7 AM and 9 PM UAE time, for promotional content
- Message content matches its stated classification, promotional or transactional
- Unsubscribe or opt-out method is included and actually works
- Bilingual content is ready if your audience includes Arabic-speaking recipients
Frequently Asked Questions
Is bulk SMS legal in the UAE? Yes. Bulk SMS is legal when sent through a registered sender ID, with documented consent, within the 7 AM to 9 PM window for promotional content, and with a working opt-out option included in every message.
Do I need separate consent for transactional and promotional SMS? Yes, in practice. Transactional messages tied to a service a customer already uses don’t need the same opt-in as promotional content. Any message designed to market or upsell needs its own explicit, storable consent record.
Can I send SMS in English only, or does it need Arabic too? English-only promotional SMS is common, but businesses targeting a broad UAE audience often see stronger response rates with bilingual content. There’s no blanket ban on English-only, but audience fit matters more than compliance risk here.
What happens if a customer blocks my sender ID? Once a customer texts a block request to 7726, your sender ID is restricted for that number. There’s no override. Your only path back is a customer opting back in directly through your own channel, not through the operator.
How long does sender ID registration take in the UAE? Timelines vary by provider and operator, but it typically takes a few business days once documentation is submitted correctly. Incomplete submissions are the most common cause of delay, more than any actual approval bottleneck.
Do these rules apply to WhatsApp Business messages too? No. TDRA’s SMS-specific rules govern SMS traffic through mobile operators. WhatsApp Business messaging falls under separate platform policies set by Meta, plus its own opt-in requirements, which differ from TDRA’s SMS framework.
Need help getting a sender ID registered or auditing your current SMS compliance setup? Talk to our team about your specific use case.
Sources & References
Etisalat & du business/enterprise SMS policies (per respective operator terms)
Telecommunications and Digital Government Regulatory Authority (TDRA) — tdra.gov.ae
TDRA FAQs — tdra.gov.ae/en/FAQs
UAE Government Portal — u.ae
