Skip to content

Compliance

The UAE Do-Not-Call Registry (DNCR): Complete Guide for Businesses

Anam Jalal

Founder & CEO, MAJ Leads

Updated 27 Jul 2026 · 10 min read

Quick answer

The DNCR (Do Not Call/Connect Register) is the TDRA-supervised registry set up under Cabinet Resolution 56 of 2024 to protect consumers from unwanted marketing calls, active since September 2022. Businesses must not call listed numbers; violations carry fines of AED 50,000 to 150,000. Consumers register via SMS to short code 1012; businesses screen dial lists through telco portals or APIs.

What is the UAE Do-Not-Call Registry (DNCR)?

Cabinet Resolution No. 56 of 2024 defines it in Article 1, verbatim:

“Do Not Connect Register (DNCR): The unified national registry supervised by TDRA to protect Consumers from unwanted Marketing Phone Calls.”
Cabinet Resolution No. 56 of 2024, Article 1 (official text, moet.gov.ae)

TDRA is the Telecommunications and Digital Government Regulatory Authority, the body that supervises the registry and, together with the Ministry of Economy and the sector regulators named in Article 9, enforces the wider telemarketing framework.

There is a genuine quirk in the official English text worth knowing about, because it explains why you will see the registry referred to two different ways. Article 1 names it the “Do Not Connect Register,” but Article 4(2) elsewhere in the same resolution calls it the “Do Not Call Registry.” Same acronym, same registry, two different English expansions in the same official translation. This isn't a drafting error to resolve: both names point to the same TDRA-supervised list. It is why “DNCR” is the safer shorthand to use rather than spelling it out one way and being told you got the name wrong.

The operative obligation sits in Article 4(5), and it is stated plainly:

“Do not call for marketing products or services to Consumers whose numbers are listed on the DNCR.”
Cabinet Resolution No. 56 of 2024, Article 4(5) (official text, moet.gov.ae)

This is not a soft guideline. Cabinet Resolution No. 57 of 2024, the companion penalty instrument, sets a specific, escalating fine for calling a DNCR-listed number:

DNCR violation penalty (Cabinet Resolution 57 of 2024, Table 1, Row 4; verify current amounts against the official text)
Violation1st offence2nd offence3rd offence
Calling a consumer whose number is on the DNCR (Art. 4(5))AED 50,000AED 75,000AED 150,000

That is per violation, not per campaign: a dial list with ten DNCR-listed numbers on it is ten separate first-offence exposures. For the full 18-row penalty schedule covering every telemarketing violation, see our complete TDRA fines and penalty table.

How long has the DNCR been active?

The registry itself predates the 2024 resolutions that now enforce it. According to Virgin Mobile UAE's own DNCR page, the registry has been active since September 2022. Cabinet Resolution 56 of 2024, which came into force on 27 August 2024, gave the existing registry its current statutory teeth: the legal duty not to call listed numbers, and the fine schedule for breaching that duty.

How do consumers register a number on the DNCR?

Per Virgin Mobile UAE's DNCR page, a consumer registers by sending an SMS from their own phone number to short code 1012. The exact mechanics of that SMS can vary by operator, so if you're registering your own number, check your carrier's current instructions rather than assuming a fixed keyword applies across all networks.

Once a number is registered, Article 6(5) confirms the consumer's standing: they may use the DNCR both to suspend marketing calls and to file complaints about calls that continue to arrive.

How do businesses screen a dial list against the DNCR?

This is the part most compliance write-ups skip, and it's worth being honest about: there is no single public TDRA lookup tool where a business can paste in a phone number and get a clean/listed answer back. Screening happens at the telco layer instead, through operator-run portals and APIs built for exactly this purpose. du, for example, offers an enterprise “My Account” DNCR portal for business customers, and Etisalat provides a DNCR API intended for integration into a company's own PBX or CRM systems.

In practice, this means DNCR compliance is an integration problem as much as a legal one. A business running outbound campaigns needs its dialling system, whether that's a human call centre's CRM or an AI voice platform's pre-call workflow, wired into one of these operator channels, checking every number before it is dialled, not after.

What can a consumer do if marketing calls continue after registering?

Article 6(1) sets out the complaint path: a consumer may file a complaint with the Competent Authority, supplying the complainant's and the defendant's name and number along with any supporting documents. That complaint is what feeds the enforcement side of the framework: the fines in Table 1 are not self-executing; they follow from a complaint or an audit finding a violation.

How does MAJ Leads build DNCR screening into outbound AI agents?

DNCR screening sits in the pre-call layer of an outbound deployment, before the AI voice agent ever dials. Every contact entering an outbound queue is checked against the DNCR through the relevant telco channel first. If a number is listed, it is automatically suppressed: no call is placed, and the contact is flagged rather than silently dropped, so the client's CRM record reflects why that lead wasn't called.

The same pre-call layer that handles DNCR suppression also enforces the 09:00–18:00 calling window, because both controls are really the same kind of problem: a call should be structurally prevented from happening when it isn't allowed to, rather than left to an operator's judgment in the moment. There is production evidence this works: across 1,094 timestamped outbound dials placed during a live UAE outbound campaign running 2 June to 12 July 2026 (six active weeks), 100.0% fell inside the permitted weekday, daytime window, with zero calls before 09:00, zero at or after 18:00, and zero on Friday, Saturday, or Sunday. Built correctly, the scheduler simply refuses the call rather than relying on a human to remember the rule.

Legal caveat

Legal note: This guide describes the DNCR provisions of Cabinet Resolution 56 of 2024 and the penalty schedule in Cabinet Resolution 57 of 2024 as published. It is informational, not legal advice. Penalty amounts can be amended by Cabinet decision; verify current figures against the official text and take independent legal advice before relying on any figure here for a compliance decision. MAJ Leads builds TDRA-aware calling systems. It does not act as a licensed TDRA authority and does not warrant regulatory outcomes.

Does the DNCR apply to inbound calls or AI receptionists?

No. The DNCR obligation in Article 4(5) is about calls the business initiates: outbound telemarketing. An AI receptionist answering calls that customers place to the business is not covered by the DNCR at all; there is nothing to screen because the business isn't the one dialling. This is why inbound deployments (answering the phone, booking appointments, handling FAQs) carry none of the DNCR, calling-window, or prior-approval overhead that outbound campaigns do. See our related guide on running outbound AI calls without getting fined for the full outbound compliance checklist.

Which businesses need DNCR compliance?

Article 3 applies the resolution to “all companies licensed in the State, including those located in free zones, that market products or services through telemarketing.” That covers clinics running re-engagement campaigns, real-estate brokerages following up on portal leads, and any SME running outbound sales or marketing calls, regardless of whether a human agent or an AI voice agent is placing the call. The technology doesn't change the legal duty; the direction of the call does.

If your business is weighing whether to build DNCR screening in-house or deploy it as part of a managed outbound system, our services overview covers how compliance screening, calling-window enforcement, and call recording are bundled into a single pre-call workflow rather than three separate projects.

Sources

Frequently asked questions

What does DNCR stand for in the UAE?
DNCR stands for Do Not Call Registry, though the official English translation of Cabinet Resolution 56 of 2024 is not fully consistent about the name. Article 1 defines it as the "Do Not Connect Register," describing it as the unified national registry supervised by the Telecommunications and Digital Government Regulatory Authority (TDRA) to protect consumers from unwanted marketing phone calls. Article 4(2), elsewhere in the same resolution, refers to it instead as the "Do Not Call Registry." Both phrases describe the exact same registry; this is a drafting inconsistency in the official translation, not two separate systems. Because of this, "DNCR" is the safer shorthand to use in practice, since it sidesteps the question of which full name is technically correct and simply refers to the underlying registry both articles are describing.
What happens if my business calls a number on the DNCR?
Under Table 1, Row 4 of Cabinet Resolution 57 of 2024, calling a number listed on the DNCR carries a fine of AED 50,000 for a first offence, AED 75,000 for a second, and AED 150,000 for a third, tied to Article 4(5)'s obligation not to call DNCR-listed consumers. These fines apply per violation, not per campaign: a single outbound run that dials ten separate DNCR-listed numbers can generate ten separate first-offence exposures rather than one fine for the whole campaign. This is why screening the full dial list against the DNCR before every campaign run, not just when the list is first built, matters more than the individual fine amount suggests. Penalty amounts can be revised by Cabinet decision, so always verify the current figures against the official text before relying on them for a compliance decision.
How does a consumer register their number on the DNCR?
Per Virgin Mobile UAE's own DNCR page, a consumer registers by sending an SMS from their own phone number to short code 1012. The registry itself has been active since September 2022, predating the statutory duty that Cabinet Resolution 56 of 2024 later placed on businesses not to call listed numbers. The exact mechanics of that SMS, such as whether a specific keyword needs to be included in the message body, can vary slightly from one mobile operator to another and are not uniformly documented across every UAE telecom provider. Because of that, the safest approach for anyone registering their own number is to check their own carrier's current published instructions directly rather than assuming a single fixed process applies identically across du, Etisalat, and any virtual network operators.
Is there a public tool businesses can use to check the DNCR?
No single public TDRA lookup tool exists where a business can enter a phone number and get a straightforward listed-or-clear answer back. Screening instead happens through channels operated by the telecom companies themselves. du, for example, offers an enterprise "My Account" DNCR portal aimed at business customers, while Etisalat provides a DNCR API intended for integration directly into a company's own CRM or PBX system rather than for manual, one-off lookups. In practice, this makes DNCR compliance as much an integration task as a legal one: a business running outbound campaigns, whether through a human call centre or an AI voice platform, needs one of these operator channels wired into its dialling workflow so every number is checked automatically before a call is placed, not looked up manually after the fact.
Does the DNCR apply to AI voice agents that make outbound calls?
Yes. The DNCR obligation in Article 4(5) attaches to the call itself, not to the technology used to place it, so an AI outbound caller is bound by exactly the same duty as a human sales agent would be. That means every number in an AI voice agent's outbound dial list must be screened against the current DNCR before the call is placed, using the same telco-operated portals or APIs a human-staffed call centre would use. Inbound AI receptionists sit on the opposite side of this line entirely: because the business isn't the one initiating the call, an AI system that only answers calls customers place to it falls outside the DNCR, the calling-hours window, and the prior-approval requirement altogether. The distinction that matters for compliance purposes is always who placed the call, not whether a human or an AI agent is on the line.

Anam Jalal

Founder & CEO, MAJ Leads

Anam Jalal is the founder of MAJ Leads, a Dubai-based AI voice agent company deploying TDRA-compliant AI receptionists and callers for UAE clinics, brokerages and SMEs — working hands-on across UAE telephony and CRM integrations, from SIP provisioning to TDRA compliance configuration.

Read more about Anam

Related articles

Explore our services