Do I need to register with the TDRA before sending WhatsApp campaigns?

There is no WhatsApp-specific registration with the TDRA; the sender-ID registration that Etisalat and du require is for SMS. What you need is the licence Meta verifies, consent you can prove, and an opt-out that works. If your business also sends SMS, register the sender ID for that channel separately.

Does a customer messaging us first count as consent to marketing?

It opens a 24-hour window in which you can reply freely, and it establishes a relationship — but it is consent to a conversation, not to campaigns. Ask inside that window, with a button, and record the answer. A customer who asked about opening hours in March has not agreed to a Black Friday broadcast in November.

TDRA rules for WhatsApp marketing in the UAE: what a business must do

Two bodies govern a marketing message to a UAE number: the TDRA, which regulates unsolicited commercial communication, and the Personal Data Protection Law (Federal Decree-Law 45 of 2021), which governs the consent behind it. Meta's rules sit on top. A template that satisfies all three is short, opted-in, and easy to leave.

The Zanii platform team · 14/09/2026 · 8 min read

What the TDRA regulates

The TDRA's unsolicited-communications framework was written for SMS and calls, and it applies by analogy to any commercial message to a UAE subscriber: the sender must be identifiable, the recipient must have agreed to receive marketing, a working opt-out must be provided and honoured promptly, and marketing must not be sent at hours a reasonable person would find intrusive. Etisalat and du enforce the SMS side through sender-ID registration; WhatsApp has no equivalent registry, which is why the burden of proof sits with the business.

The PDPL adds the consent standard: freely given, specific, informed, and withdrawable as easily as it was given. A number harvested from a business card, a WhatsApp group, or a delivery address is not consent to marketing. A tick-box at checkout that says what you will send and how often is. The regulator that acts on a complaint in practice is the UAE Data Office for consent and the TDRA for the sending — and a complaint is usually one screenshot forwarded to either.

How each rule maps onto a template

Sender identity is the display name, which passed Meta's review and shows on every message. Consent is a record per contact, captured before the first marketing template and kept — Zanii writes it as a signed receipt when the customer ticks the box or replies YES, and the campaign screen refuses a marketing send to a contact without one. Opt-out is a quick-reply button on every marketing template ("Stop these messages"), whose tap Zanii records as a receipt and applies before the next campaign is counted. Timing is a send window per number — the platform's default is 09:00 to 21:00 Gulf time and never Friday morning — that an API caller cannot bypass.

Utility messages are outside all of this. A booking confirmation, a delivery update or a payment reminder about a transaction the customer is party to is not unsolicited commercial communication, needs no marketing consent, and reaches a customer who opted out of marketing. The line is content, not intent: the moment a utility template carries an offer, it is marketing in Meta's classification and in the regulator's.

What a complaint looks like, and what answers it

A customer forwards a screenshot to the TDRA's complaints channel or, increasingly, posts it. The question that comes back to the business is not "why did you send this" but "show me the consent". A CRM note saying "opted in" is not evidence; a timestamped record of what the customer was shown and what they did is. That is what the consent receipt is for, and it is why Zanii records opt-ins, opt-outs and every marketing send on a ledger the business does not control — so the record is believed because it cannot have been edited.

What goes wrong

Importing a spreadsheet of past customers and sending an offer to all of them.: Send them a utility message first — an account update, a receipt they are owed — with an opt-in button, and market only to the ones who tap it.
Honouring the opt-out in the CRM but not in the campaign tool.: One list, one record. The opt-out has to be applied where the send happens, automatically, before the count is shown.
Sending a Ramadan offer at 3am because that is when people are awake.: They are, and they still report it. Ramadan shifts the window later — 20:00 to 01:00 is defensible — but the window still exists and should be set per number, not per campaign.

Common questions

Do I need to register with the TDRA before sending WhatsApp campaigns?: There is no WhatsApp-specific registration with the TDRA; the sender-ID registration that Etisalat and du require is for SMS. What you need is the licence Meta verifies, consent you can prove, and an opt-out that works. If your business also sends SMS, register the sender ID for that channel separately.
Does a customer messaging us first count as consent to marketing?: It opens a 24-hour window in which you can reply freely, and it establishes a relationship — but it is consent to a conversation, not to campaigns. Ask inside that window, with a button, and record the answer. A customer who asked about opening hours in March has not agreed to a Black Friday broadcast in November.