WhatsApp calling in the UAE: what actually works
WhatsApp is not banned in the UAE. Messaging works normally: text, images, voice notes, documents, groups and the WhatsApp Business Platform all function here every day. What does not work is WhatsApp voice and video calling, which is restricted at network level because voice over the internet is a licensed activity in the UAE and WhatsApp does not hold that licence or an exemption. That is the whole answer. Everything below is the evidence for it, and the part that actually matters commercially: what a UAE business should build its customer communication on instead.
Why this page exists. "Why is WhatsApp banned in Dubai" is a live search in this market, and most of the pages answering it are written by people who have never used a UAE SIM. They quote a monthly VoIP subscription that was abolished in 2025, an app list that has changed, and a dirham fine that traces to no legal text we could find.
We sell WhatsApp messaging automation, so we have an obvious commercial interest in the messaging half of this answer. Read it with that in mind, then check the regulator's own text, which we link at every step.
The short answer, in five lines
- WhatsApp works in Dubai and across the UAE. The app is not blocked and messaging is not restricted.
- Voice and video calls over WhatsApp do not connect on UAE networks. This has been true for years and was still being reported as current by UAE press in 2026.
- The reason is licensing, not censorship of WhatsApp specifically. Voice over Internet Protocol is a Regulated Activity in the UAE. Two licensees hold telecoms licences, and they are obliged to block non-compliant VoIP traffic.
- Some calling apps are permitted, because they are licensed, provided in collaboration with a licensee, or approved by the regulator. WhatsApp is not on that list.
- For a business, the consequence is structural: a voice-first AI strategy is disadvantaged in this market, while WhatsApp messaging automation is not affected at all.
Is WhatsApp blocked in the UAE, or just calling?
Just calling. The distinction is not a technicality, and a UAE resident will spot a page that gets it wrong within one sentence.
WhatsApp messaging is in ordinary daily use across the country. Government entities run WhatsApp customer service channels. UAE press coverage in 2026 treats the app itself as unremarkable while describing calling as unavailable. In May 2026 Khaleej Times ran a piece explaining that private WhatsApp chats and groups are fully subject to UAE cybercrime law, which is a sentence that only makes sense in a market where private WhatsApp chats are normal and widespread.
On calling, the evidence is current rather than historic. In February 2026 WhatsApp Web gained voice and video calling globally. Both Gulf News and Khaleej Times covered it, on the same day, and both reported the same UAE position. Gulf News, 10 February 2026:
"voice and video calls remain unavailable on WhatsApp's mobile and desktop applications in the UAE ... The features' availability is subject to approval by the Telecommunications and Digital Government Regulatory Authority (TDRA)."
Khaleej Times, the same day, put it as availability "subject to approval by the TDRA, with WhatsApp calling features still restricted on mobile and desktop apps". That is the useful currency test. A brand new WhatsApp calling surface launched worldwide, and it did not arrive here. This is not a stale 2018 fact being recycled.
The regulation, in the order it actually applies
Most articles stop at "TDRA bans it". The chain is worth publishing, because it explains why the restriction is stable and why it is unlikely to be lifted by a vendor's product launch.
Layer one: the statute
Federal Law by Decree No. 3 of 2003 regarding the organisation of the telecommunications sector. This is what makes providing a telecommunications service a Regulated Activity requiring a licence. TDRA's own policy documents and FAQ reference it throughout.
Layer two: the VoIP Regulatory Policy
Regulatory Policy, Voice over Internet Protocol, Version 2.0, issued 30 December 2009, replacing version 1.0 of 26 December 2006. It is eight pages, it is public, and it is still the live instrument. Paragraph 3.1, verbatim:
"Subject to paragraph 3.3 below, to the extent that the provision of VoIP Services requires a person to engage in or conduct a Regulated Activity in the State, that person will need to have been issued with a Licence to do so, in accordance with the Law. At present there are two Licensees which are legally entitled to engage in or conduct Regulated Activities in the State. It is not the TRA's present intention to issue any further Licences that would allow the holders of such Licences to provide VoIP Services."
Paragraph 3.2 is the one that produces the blocking:
"Where a Licensee believes that a VoIP Service is being provided by a person not licensed to do so under the Law, over a Public Telecommunication Network operated by that Licensee, that Licensee will be entitled to block that VoIP Service, unless instructed by the TRA to do otherwise."
The policy defines a VoIP Service as "all of the services and technologies that allow the transmitting, receiving, delivering and routing of voice telecommunications by means of Internet Protocol". Text messaging is not voice, is not within that definition, and is not touched by the policy. That is the legal reason the messaging half of WhatsApp is unaffected.
Be precise about the age of this document. The VoIP Policy is a 2009 instrument written by "the TRA", the authority's former name, before it became the TDRA. It has never been withdrawn, and TDRA still links to it as current from a page its own sitemap records as last modified 19 March 2025. So it is live, but it is not recent regulation, and anyone describing it as a new rule has not read it. Section 8 of the policy reserves the right to "revise, revoke, or reissue this Policy from time to time".
Layer three: the closed-group exemption
Paragraphs 3.3 and 3.4 exempt VoIP provided exclusively over a Closed Group Network, meaning a network operated for the users of a single entity or a commonly owned group and not interconnected with a public network. This is the legal basis on which internal corporate voice works while consumer app calling does not, and it is why your company's internal conferencing is a different question from your customer's WhatsApp call.
Layer four: the blocking obligation, stated by TDRA in plain terms
On its internet guidelines page, TDRA writes:
"Voice and video calls are considered Voice over Internet Protocol (VoIP) services that are a regulated activity in the UAE. Such services shall be provided by the licensed service providers or in collaboration with them."
"The licensed service provider in UAE are obliged to block the traffic of VoIP applications that are not in compliance, as it falls under the prohibited content category of Illegal communication services."
Note the mechanism. The obligation sits on e& and du, the two licensees, at carrier level. It is not something Meta can switch on from Menlo Park, and it is not something a messaging vendor can enable with a toggle.
One practical detail if you go looking for that page yourself: the working URL contains /departments/. The shorter variant that several vendor pages cite returns a 404, which is one reason so much secondary writing on this topic is out of date.
Which calling apps are permitted in the UAE?
TDRA publishes a list of VoIP applications currently allowed in the country. Here it is in full, in TDRA's own order, as published on the page last modified 19 March 2025. WhatsApp does not appear on it, in either category.
| Category | Applications named by TDRA |
|---|---|
| General | Microsoft Teams, Skype for Business, Zoom, Blackboard, Google Meet (Meeting only), Cisco Webex, Avaya Spaces, BlueJeans, Slack, BOTIM, GoChat, Voico, Etisalat Cloud Talk Meeting, Matrx, Totok, Empay, Sanad, Comera |
| Telehealth | Mind Mina Telemedicine, NextGenGP Telehealth, vSee, OKADOC, DOXY, GetBEE, Dhani Health, Health Interface, Zoom |
Three things about that list that most articles get wrong:
- Google Meet is qualified. TDRA writes "Google Meet (Meeting only)", not general calling.
- "C'Me" is not on the current list. "Comera" is. C'Me appears on older press round-ups, including a Khaleej Times list from 2022. Anyone naming C'Me on a 2026 page is copying a four-year-old article.
- The list is authoritative on what is permitted, not on what is usable. It still names ToTok, which was widely reported to have been removed from the major app stores in 2019. We have not verified that removal against a primary source, and we mention it only to make the point that the list is a permissions register, not a guide to what you can install today.
There is also a documented route in. TDRA's guidelines say it "may provide a VoIP exemption approval to allow VoIP applications in the UAE, taking into consideration the users and market demands and needs", by official letter to [email protected]. So the door exists and is discretionary. WhatsApp has either not applied or not been granted it. There is no public record either way, and we are not going to guess.
What changed in 2025 and 2026, and what did not
On WhatsApp calling itself: nothing. We enumerated TDRA's press releases and statements for 2025 and 2026 from its own sitemap. Not one concerns VoIP, calling or WhatsApp.
Two adjacent things did change, and both are commercially relevant.
The paid Internet Calling Pack was discontinued
You will still find pages telling UAE readers they must buy a monthly VoIP add-on before approved calling apps will work. That was once true. du's own page now states that "your Internet Calling Pack (ICP) subscription will no longer be available as a service after 18 August 2025", that "the BOTIM app can continue to be freely accessed and used outside of the ICP, although it will require an active data package", and that customers receive a full refund for ICP fees collected from 10 June 2025 onward.
We are deliberately not printing the old monthly subscription prices that circulate on comparison sites. The du product no longer exists, and we could not confirm the e& position from a live e& page, because every Internet Calling Plan URL we tried now redirects and returns a 404. If a page quotes you a dirham figure for a VoIP package in 2026, that is a strong signal it has not been checked.
The two-licensee model was reaffirmed to 2046
On 12 August 2026 the TDRA Board renewed the telecommunications licences of e& and du for twenty years, effective 9 August 2026 to 8 August 2046, replacing the licences originally issued in 2006. Read alongside paragraph 3.1 of the VoIP Policy, which says the authority does not intend to issue further licences permitting VoIP services, that is a market structure that has just been locked in for two decades. Nobody should plan a UAE customer-voice strategy on the assumption that consumer VoIP is about to be liberalised.
Does the WhatsApp Business Calling API work in the UAE?
This is the question that matters if you are being sold a WhatsApp calling product, and the honest answer is: nobody has published an answer, including us. Here is exactly what is known and what is not.
What Meta says
Meta's own Cloud API calling documentation states that "business-initiated calling is available in every location Cloud API is available, except the following countries: United States, Canada, Egypt, Vietnam, Nigeria", and that "user-initiated calling is available in every location Cloud API is available". The UAE is not on Meta's exclusion list. Neither is Saudi Arabia, which also restricts WhatsApp calling, and that omission tells you what kind of list it is.
Why that is not the same as "it works here"
Meta's exclusion list describes Meta's own platform availability. The UAE restriction is a network-level matter sitting with e& and du under the obligation quoted above: licensees "are obliged to block the traffic of VoIP applications that are not in compliance". A WhatsApp business call is WhatsApp voice traffic carried over a UAE network. There is no published TDRA exemption for WhatsApp of any kind, consumer or business.
We searched for a primary or authoritative source confirming that a WhatsApp Business Calling API call connects to a consumer on a UAE mobile network. We did not find one. We also did not find one confirming that it fails. It is genuinely unresolved in public sources, and any vendor telling you it definitely works here has not checked.
The trap we nearly fell into, recorded so you do not. Meta's Calling API pricing documentation lists AED among eight new billing currencies introduced with effect from 1 April 2026. That is a billing currency for the business account, not a market where calls are available. There is no per-destination calling rate card naming the UAE. Do not read AED billing as evidence that UAE calling works, and be careful of any calculator that lets you select the United Arab Emirates and quotes you a per-minute rate. Appearing in a dropdown is not a statement about carrier-level delivery.
What the other vendors actually say, read carefully
We read the two most-cited vendor explanations rather than paraphrasing them.
respond.io's page marketing the feature, last modified 16 January 2026, says the API is "generally available to all WhatsApp API users unless they're in sanctioned countries or those with government restrictions on WhatsApp Calling (e.g., Saudi Arabia)." It names only Saudi Arabia and does not mention the UAE. So it neither claims nor denies UAE availability, and its own carve-out is for countries with government restrictions on WhatsApp calling, which is a fair description of the position here. Wati, another provider, repeats Meta's list verbatim and likewise does not name the UAE.
That is not dishonesty, and we are not going to call it that. It is what happens when a global vendor mirrors Meta's exclusion list and stops. Meta's list answers "where will the API let you dial". It does not answer "where will the call actually connect". Those are different questions, and in this market the second one is the only one that pays your bills.
The other exposure, which is separate from whether it connects
TDRA's FAQ, last modified 30 August 2026, is blunter than most vendor pages about consequences for the user:
"Except where exempted as stated in the Policy or approved by TDRA, any person using VoIP Services which are not provided by a Licensee or in collaboration with them (even if not offering it to others for a fee), may be committing a criminal offence."
"Unless this software/application is provided by a Licensee or in collaboration with them or is approved by TDRA, it is very likely that it is illegal to use this software/application to make Voice and Video calls over the Internet ... you are legally liable for such action, and the Licensees have the right to and most probably will block your illegal traffic."
Our published position: treat WhatsApp calling, consumer or Business API, as unavailable in the UAE. Build on messaging. If your BSP claims otherwise, ask them in writing whether business-initiated calling is enabled for UAE destinations on your account, and keep the email.
What this means for a UAE business
Here is the commercial point, and it is bigger than a compliance footnote. A voice-first AI strategy is structurally disadvantaged in this market, and a messaging-first one is not.
If your plan is "our AI will call customers over WhatsApp", the plan has a regulatory dependency you do not control, in a market whose licence structure was just renewed to 2046. If your plan is "our AI answers customers on WhatsApp in writing, instantly, at three in the morning", nothing on this page applies to you. Different half of the app, different law, no restriction.
There is a second reason, and this one comes from our own sales calls rather than from a regulator. We mine our call notes for patterns, anonymised, and the most consistent one in the Gulf is this: buyers here accept AI on text and reject it on the phone, and they say why, unprompted. One Dubai owner overruled his own team who wanted phone AI with the line "AI can talk logical, but it cannot talk emotional, it cannot get to the customer like that". In our UK conversations the pattern inverts, and buyers there often buy AI voice first. That is an observed pattern from our own conversations, not a survey, and we are not going to dress it up as one. But it points the same way the regulation does.
So the practical stack for a UAE business looks like this.
| What you need | What to use in the UAE | Why |
|---|---|---|
| Customer voice calls | The ordinary licensed network: a landline or mobile number from e& or du, or a licensee-provided VoIP or PBX feature riding on a licensee connectivity service | TDRA's FAQ is explicit that VoIP services must be obtained from a licensee, including for call centres and multi-office corporate voice |
| Customer messaging and automation | WhatsApp, normally and lawfully, including the WhatsApp Business Platform. This is where we work | Text is not a VoIP service and is not within the scope of the policy |
| App-based consumer calling | BOTIM, GoChat, Comera and the rest of the TDRA list, now usable on a plain data package since the Internet Calling Pack was scrapped in August 2025 | These are licensed, provided in collaboration with a licensee, or approved by TDRA |
| Internal and B2B meetings | Microsoft Teams, Zoom, Cisco Webex, Slack, Google Meet for meetings | All named on TDRA's permitted list; internal corporate voice also has the closed-group route at paragraphs 3.3 and 3.4 |
| Video conferencing between your own branches | Obtain it from a licensee | TDRA's FAQ: "Video conferencing is considered to be similar to VoIP, thus it must be obtained from a licensee" |
What WhatsApp messaging actually costs a UAE business
Since messaging is the route that works, here is what Meta charges for it. These rates came from Meta's own live pricing system for market AE on 3 September 2026, queried twice with identical results.
| Message category | USD per message | AED per message | Notes |
|---|---|---|---|
| Marketing | 0.0499 | 0.1832 | One flat rate for the UAE. No volume tiers. Charged in every window |
| Utility (first tier, to 100,000 a month) | 0.0157 | 0.0576 | Free today when delivered inside an open 24-hour service window |
| Authentication (first tier, to 300,000 a month) | 0.0157 | 0.0576 | Note the tier thresholds differ from utility |
| Service | 0 | 0 | Free today. Changing on 1 October 2026, see below |
Four things to know about that table, because they are where competitor pages go wrong.
- The commonly quoted UAE marketing rate of $0.0385 is stale. Meta raised the UAE marketing rate with effect from 1 October 2025. The live rate is $0.0499. We have seen a vendor page stamped "last updated September 2026" still publishing the old figure.
- Do not convert USD to AED yourself. Meta publishes its own AED rate card, added as a billing currency on 1 April 2026, and those AED figures are not a live FX conversion of the USD ones. Multiplying by a rate produces a number that will not match the invoice.
- Conversations are no longer the billing unit. Conversation-based pricing was deprecated on 1 July 2025. You are charged when a template message is delivered. A calculator built on "conversations per month" is modelling a pricing system that no longer exists.
- The free tier is scheduled to change on 1 October 2026. Meta has published that service messages, and utility messages sent inside the 24-hour window, both become chargeable on that date. Today they are free. If you are being sold a service-led WhatsApp deployment on the basis that "replies are free", ask what the model looks like after 1 October 2026.
A contradiction inside Meta's own documentation, reported rather than smoothed over. Meta's main pricing page still says non-template messages and in-window utility templates are free and does not mention the 1 October 2026 change. Meta's dedicated upcoming-changes page does. Both are Meta primary sources and they currently disagree. We checked both on 3 September 2026 and are telling you they disagree rather than picking the one that suits us. Re-check both before you commit to a budget.
The rules that do apply to WhatsApp messaging here
Calling restrictions are not the only UAE-specific thing to know, and the other items catch more businesses in practice.
Meta's own limits, which most people get wrong
A new business portfolio starts at 250 unique recipients per rolling 24 hours outside a customer service window, not the 1,000 a day that vendor content repeats. Limits are set at portfolio level and shared across every number in that portfolio, so splitting sending across more numbers does not buy you volume. You scale to 2,000 by verifying your business, having your onboarding partner verify it, or through a quality-messaging path. Meta's developer doc describes that path as 2,000 delivered messages to unique recipients over a rolling 30 days using high-quality templates, while its Business Help Centre article says a minimum of 1,000 conversations over 30 consecutive days. Those are Meta's own two numbers and we are reporting both rather than choosing.
There is also a per-user marketing limit that most businesses never see coming. Meta throttles how many marketing templates an individual receives based on their own recent read rate and inbox state. It is not active for senders or recipients in the European Economic Area, the United Kingdom, Japan or South Korea. The UAE is not on that exclusion list, so per-user marketing limits apply to UAE senders and UAE recipients. Hit one and the API returns error 131049 and delivery to that person may be unavailable for up to 24 hours.
Telemarketing law reaches social-media marketing messages
Cabinet Resolution No. 56 of 2024, in force 27 August 2024, defines telemarketing to include "marketing text messages and marketing messages through social media applications". It applies to all companies licensed in the State, free zones included, and requires prior approval to practise phone marketing activity, use of local numbers registered under the commercial licence, respect for the Do Not Connect Register, and a communication channel through which interested consumers opt in.
Here is the honest complication. The definition in Article 1 sweeps in social-media marketing messages, but the operative obligations in Articles 4 and 5 are drafted in call language: record the marketing phone call, identify the company at the beginning of the call, call only between 9am and 6pm. How a 9am to 6pm window or a call-recording duty maps onto a WhatsApp template message is not specified in the text. So we will say what is supportable and no more: the definition covers social-media marketing messages, and the operative controls were written for calls. A cautious business treats the opt-in requirement as applying and takes advice on the rest.
Two sector-specific things
Banks and licensed financial institutions. Khaleej Times reported on 22 April 2026, from a notice it says it had seen, that the UAE Central Bank told banks and licensed financial institutions to stop using messaging apps including WhatsApp for customer data, transaction instructions, passwords, PINs, OTPs and documents containing personal or financial information, with a compliance deadline of 30 April 2026. We could not locate that notice on the Central Bank's own site or in its Rulebook, so we flag it as a press report rather than a primary source. If you are a bank, insurer or finance company, do not take a marketing page's word for this, including ours. Get the notice or get counsel.
Clinics and healthcare. The UAE analogue to the American framework people reach for is Federal Law No. 2 of 2019 on the use of ICT in health fields. HIPAA is United States law and does not apply in Dubai, so a vendor telling a Dubai clinic it must be "HIPAA compliant" as a matter of law is telling you something untrue about the jurisdiction you operate in. There is a genuine twist worth knowing, though: the Dubai Health Authority's Standards for Telehealth Services Version 4, effective 26 November 2025, require telehealth platforms to hold HIPAA compliance certification, with HITRUST or SOC 2 alignment available as an alternative at DHA's discretion. So in Dubai HIPAA arrives not as law but as a DHA procurement standard for telehealth platforms, which is a narrower and very different thing. Article 13 of Law 2/2019 restricts storing, processing, generating or transferring health data outside the UAE, and the penalties of AED 500,000 to 700,000 attach specifically to that cross-border obligation, not to health-data breaches generally. Dubai Health Authority policy treats WhatsApp as social media for advertising purposes and prohibits pushing an unsolicited appointment time a patient did not request. If you run a clinic, that is a bigger constraint on your WhatsApp automation than anything about calling.
The grey zone: what is safe, what has a consequence, and what operators actually do
Every honest version of this page needs a section on the edges. We have separated three things that most pages blur together: what is clearly fine, what carries a named consequence, and what real operators do that is neither policy nor prohibited.
Clearly safe
- Messaging customers on WhatsApp, with opt-in. Not a VoIP service, not restricted, and the WhatsApp Business Platform is designed for it. Meta's opt-in requirement can be met with a general consent; it does not have to be WhatsApp-specific.
- Running an AI assistant on your own WhatsApp number. Meta did not ban AI chatbots on WhatsApp. Its clause bars AI providers from distributing their general-purpose assistant as the primary product on the platform, and explicitly permits a business to retain an AI provider as its service provider. Businesses running AI assistants for their own customer service are on the right side of that line.
- Answering an inbound customer inside the 24-hour service window. Free today, chargeable from 1 October 2026, still entirely permitted.
- Using an approved calling app. BOTIM, Teams, Zoom, Webex and the rest of TDRA's list, now on a plain data package.
- Corporate VPN use for internal networks. TDRA stated in July 2016 that there are no regulations preventing companies, institutions and banks from using VPN technology to reach their internal networks over the internet.
Carries a named consequence
- Placing unlicensed VoIP calls, including over a VPN. TDRA's FAQ says the user "may be committing a criminal offence" and that licensees have the right to and most probably will block the traffic. Note what we are not doing here: you will find a specific dirham fine quoted all over the blogs for this. We could not trace it to any published legal text, so we do not repeat it. That does not make the underlying exposure imaginary, and it is a bad idea to build a business process on it.
- Sending marketing templates without opt-in, or misclassifying marketing as utility. Meta names template misclassification as an enforcement trigger. Enforcement escalates from a warning through restrictions to account termination under the Business Terms of Service.
- Ignoring user feedback signals. Meta does not act on "too much automation" as such; it acts on blocks, reports, mutes and low read rates, and on policy-category violations. Meta itself names bot functionality and how quickly enquiries are resolved as inputs to your number's quality rating, which is a straightforward argument for a good assistant rather than a cheap one.
- Sending health data offshore from a UAE clinic. Article 13 of Federal Law No. 2 of 2019, with the AED 500,000 to 700,000 penalty attached to that article.
- A bank or insurer using WhatsApp for customer data or transactions. Per the April 2026 press report above, treated as a compliance matter rather than a marketing choice.
Borderline moves real operators use, labelled as operator practice
The following are things businesses in this market actually do. None of them is Meta policy or UAE regulation. They are practice, and we are labelling them as practice because the risk is real and unquantified.
- Warming up a new number on a gentle ramp. No Meta document prescribes a warm-up schedule. The only documented ramps are the messaging-limit ladder and Meta's own template pacing. Vendor warm-up tables circulate widely and cite nothing. The risk: you are following a number somebody invented, and it may cost you weeks of sending capacity for no measurable protection.
- Seeding a new number with inbound conversations before any outbound. Rational, given that quality is computed from user feedback, but undocumented. The risk: the same, plus it is easy to convince yourself it worked when the real variable was your message quality.
- Staggered batches on a number rated high quality. We hear this from operators, in batches of roughly five hundred, precisely because Meta's enforcement is a black box. The risk: messaging limits are portfolio-wide and shared, so splitting sends across numbers isolates number-level quality but does not buy you volume. Anyone selling it to you as a way to send more is wrong.
- Suppressing a segment after the first non-reply. Sensible against per-user marketing limits and read-rate-driven template quality, but there is no Meta threshold to point at. The risk: you will suppress people who would have converted, and you will not be able to tell.
- Category discipline: never dressing a marketing message as a utility message. This is the one item on the list where practice and policy agree. Meta names template misclassification as an enforcement trigger. Treat it as a rule, not a tactic.
And one item that is not a grey zone at all: we do not sell, build or recommend a VPN workaround for WhatsApp calling. A VPN is not itself illegal here, and TDRA has said so about corporate internal-network use. Using one to place unlicensed VoIP calls runs straight into the FAQ language above. It is a bad foundation for a customer-facing process, and if a vendor offers it to you as a feature, that tells you what their compliance thinking is worth.
If you want the half that actually works, built properly
Learnmind designs, builds and runs WhatsApp messaging automation and AI assistants for businesses in the UAE. Not calling, for all the reasons on this page. Fifteen minutes is usually enough to tell you whether your use case is a messaging problem or a phone-system problem, and we will say so if it is the second one.
Frequently asked questions
Is WhatsApp banned in Dubai?
No. WhatsApp is not banned in Dubai or anywhere in the UAE, and messaging works normally: text, images, voice notes, documents, groups and the WhatsApp Business Platform. What is restricted is WhatsApp voice and video calling, which does not connect on UAE networks because voice over the internet is a licensed activity here and WhatsApp is not on the regulator's list of permitted VoIP applications.
Why can I not make WhatsApp calls in the UAE?
Because voice and video calls over the internet are a Regulated Activity under Federal Law by Decree No. 3 of 2003 and the TDRA VoIP Regulatory Policy version 2.0 of 30 December 2009. The policy states that only licensed providers may offer VoIP services, that the authority does not intend to issue further licences for it, and that a licensee may block a VoIP service provided by an unlicensed person over its network. TDRA's guidelines go further and say licensed providers are obliged to block the traffic of non-compliant VoIP applications. The restriction is applied at carrier level by e& and du, not by WhatsApp.
Does WhatsApp messaging work in Dubai?
Yes, normally. Text messaging is not a VoIP service, so it falls outside the scope of the VoIP policy entirely. Businesses use the WhatsApp Business Platform here lawfully every day, and UAE government entities run official WhatsApp customer service channels. Nothing about the calling restriction affects a business messaging its customers on WhatsApp.
Which calling apps are allowed in the UAE?
TDRA publishes the list. In the general category it names Microsoft Teams, Skype for Business, Zoom, Blackboard, Google Meet (meeting only), Cisco Webex, Avaya Spaces, BlueJeans, Slack, BOTIM, GoChat, Voico, Etisalat Cloud Talk Meeting, Matrx, Totok, Empay, Sanad and Comera. In the telehealth category it names Mind Mina Telemedicine, NextGenGP Telehealth, vSee, OKADOC, DOXY, GetBEE, Dhani Health, Health Interface and Zoom. WhatsApp does not appear in either category. Note that the list records what is permitted, not what is currently usable.
Does the WhatsApp Business Calling API work in the UAE?
This is unresolved and no primary source settles it. Meta's documentation excludes only the United States, Canada, Egypt, Vietnam and Nigeria from business-initiated calling, and the UAE is not on that list. But Meta's list describes Meta's platform availability, not carrier-level delivery, and the UAE restriction is applied by the licensed operators under TDRA's obligation to block non-compliant VoIP traffic. We found no source, primary or secondary, confirming that such a call connects to a UAE consumer, and none confirming it fails. Any vendor telling you definitively that it works in the UAE has not checked. Treat it as unavailable, build on messaging, and if a provider claims otherwise, ask them in writing whether business-initiated calling is enabled for UAE destinations on your account.
Do I still need to buy a VoIP package to use BOTIM in the UAE?
No. du's own page states that the Internet Calling Pack subscription is no longer available as a service after 18 August 2025, that the BOTIM app can continue to be freely accessed and used outside the pack although it requires an active data package, and that customers received a refund for pack fees collected from 10 June 2025 onward. Pages still quoting a monthly dirham VoIP subscription are out of date. We could not confirm the e& position from a live e& page, so we do not state one.
Is it illegal to use a VPN in the UAE?
A VPN is not illegal in itself. TDRA stated in July 2016 that there are no regulations preventing companies, institutions and banks from using VPN technology to access their internal networks over the internet, and that the illegal use is using a false or third-party IP address for the purpose of committing a crime or preventing its discovery. Using a VPN to place unlicensed VoIP calls is a different matter: TDRA's FAQ says a person using VoIP services not provided by or in collaboration with a licensee may be committing a criminal offence. We do not recommend or build VPN workarounds for WhatsApp calling, and we do not repeat the specific fine figure that circulates online, because we could not trace it to any published legal text.
What does WhatsApp messaging cost a business in the UAE?
As at 3 September 2026, from Meta's own live pricing system for the UAE market: marketing messages are $0.0499 or AED 0.1832 each with no volume tiers; utility and authentication messages start at $0.0157 or AED 0.0576 each with volume tiers above that; service messages are free today. Meta publishes its own AED rate card, so do not convert from USD yourself. Two dates matter: the UAE marketing rate rose on 1 October 2025, which is why many vendor pages still show a stale $0.0385, and from 1 October 2026 service messages and in-window utility messages are scheduled to become chargeable.
Can a UAE business run an AI assistant on WhatsApp?
Yes. Meta did not ban AI chatbots on WhatsApp. Its policy bars AI providers from distributing their general-purpose assistant as the primary product on the platform, and it explicitly permits a business to retain an AI provider as its service provider. Meta also names bot functionality and how quickly enquiries are resolved as factors influencing your phone number's quality rating, so the quality of the assistant is a platform-health matter, not just a customer-experience one.
How we checked this, and what we could not settle
Every regulatory statement on this page was taken from TDRA's own published material: the internet guidelines page, the FAQ, the VoIP Regulatory Policy version 2.0 PDF, and TDRA press releases. Every Meta rate and policy statement came from Meta's own documentation or Meta's own live pricing system, queried on 3 September 2026. The two 2026 press confirmations are Gulf News and Khaleej Times, both dated. We did not use visa-service sites, eSIM affiliate pages or SEO round-ups, because they contradict each other on prices and app lists, cite no primary source, and several still assert a VoIP subscription that du abolished in 2025.
Four things we could not settle, stated plainly rather than glossed:
- Whether a WhatsApp Business Calling API call connects to a UAE consumer. No public source states it either way. This is the single open question on the page.
- The e& Internet Calling Plan position. du's discontinuation is confirmed from du's own page. Every e& equivalent URL we tried now redirects and returns a 404.
- The Central Bank notice on messaging apps in financial services. Reported by Khaleej Times from a notice it says it sighted. We could not find it on the Central Bank's site or in its Rulebook.
- Whether TDRA has ever received or refused a WhatsApp VoIP exemption application. No public record either way, so we make no claim.
If something on this page is wrong or has changed, write to [email protected] with the source that shows it and we will correct the line and the date.
Sources
- TDRA internet guidelines and permitted VoIP application list, page last modified 19 March 2025, retrieved Thursday 3rd September 2026
- TDRA Regulatory Policy, Voice over Internet Protocol, Version 2.0, issued 30 December 2009
- TDRA FAQs, page last modified 30 August 2026
- TDRA press release on the renewal of the e& and du telecom licences, 12 August 2026
- TDRA statement on the use of VPN, 31 July 2016
- du, Internet Calling Pack, retrieved Thursday 3rd September 2026
- Gulf News, WhatsApp Web voice and video calls and UAE availability, 10 February 2026
- Khaleej Times, are WhatsApp Web voice and video calls available in the UAE, 10 February 2026
- Khaleej Times, WhatsApp private chats are not exempt from UAE law, 2 May 2026
- Khaleej Times, banks told to stop using WhatsApp for financial services customer data, 22 April 2026
- Meta, WhatsApp Cloud API calling documentation and Meta, Calling API pricing, retrieved Thursday 3rd September 2026
- Meta, WhatsApp Business Platform pricing, updates to pricing and upcoming changes to non-template message pricing, retrieved Thursday 3rd September 2026
- Meta, messaging limits and per-user marketing template limits
- Meta, tips for driving high-quality conversations and improving quality rating on WhatsApp
- respond.io on the WhatsApp Business Calling API, last modified 16 January 2026, and Wati on WhatsApp calling restrictions, last updated 5 March 2026, both treated as vendor claims rather than facts
- Dubai Health Authority, Standards for Telehealth Services, Version 4, effective 26 November 2025
- Cabinet Resolution No. 56 of 2024 on telemarketing, published 28 June 2024 and in force 27 August 2024, read from an English translation mirror; and Federal Law No. 2 of 2019 on the use of ICT in health fields
Written by Edmund Gay, Learnmind.ai, Dubai. This page is commercial information about a market we operate in, not legal advice. Regulation and vendor rates on this page carry the date we checked them, and both change.