Stay on the free WhatsApp Business app if one or two people answer messages from a phone, you only ever message people who already have your number saved, and you are not in one of Meta's regulated verticals. Move to the WhatsApp Cloud API when you need several people in one shared inbox, automated replies, template messages to customers who have not saved you, or a documented appeal route if Meta acts against your account.
The app costs nothing. The API bills per delivered template message, and in the UAE Meta's published marketing rate is $0.0499 or AED 0.1832 per message.
Every rate, date and policy statement on this page is taken from Meta's own published documentation or its live rate card, checked on Thursday 3rd September 2026. Where two Meta sources currently disagree, this page says so rather than picking one. WhatsApp pricing has moved twice in the past twelve months, so re-check before you budget.
The two products share a name and almost nothing else. Confusing them is the single most expensive mistake a UAE business makes on this decision, because the sales conversation you have with a vendor is shaped by which one you think you are buying.
A free application you install on a phone. It has an inbox, a catalogue, quick replies, labels and broadcast lists. You own it directly, there is no third party in the chain, and there is nothing to integrate.
It is governed by the WhatsApp Business Messaging Policy, the WhatsApp Business Terms of Service and the WhatsApp Messaging Guidelines.
An interface, not an application. It has no inbox of its own, so you also need software to read and reply in, which is why every API deployment involves a Solution Provider, a platform, or a system somebody built for you.
It is governed by the same three documents plus the WhatsApp Business Solution Terms, which were last modified on 6 March 2026 and which carry rules the app is not subject to.
respond.io states the same point plainly on its own product page: "The WhatsApp API doesn't include an inbox to send and receive messages, so you'll need a WhatsApp Business Solution Provider (BSP) like respond.io to unlock its full potential." That is accurate, and it is worth internalising before you compare prices. The Meta rate is never the whole bill.
The extra rulebook on the API side is not a formality. The Business Solution Terms are where the AI clause lives, where the restriction on using conversation data to build user profiles lives, and where Meta reserves the right to terminate an account for breaching either. If a vendor has never mentioned that document to you, they have not read it.
Every row below is sourced to Meta's own documents. Where Meta does not publish an answer, the cell says so instead of guessing. That is the difference between this table and most of the ones you will find.
| WhatsApp Business app | WhatsApp Cloud API | |
|---|---|---|
| Cost from Meta | Free. | Charged per delivered template message. Inbound user messages are not billed by Meta. |
| Software you need | None. The app is the inbox. | An inbox, platform or custom build, because the API has no interface of its own. Most deployments also sit behind a Solution Provider. |
| Outbound reach | Broadcast lists reach only people who have already saved your number in their contacts. | Messaging limits start at 250 unique recipients per rolling 24 hours, rising to 2,000, then 10,000, 100,000 and unlimited. |
| Phone numbers | Not documented in the Meta sources used for this page. | Up to two registered numbers before scaling; up to 20 after. |
| Automation | The consumer rule applies: "Don't bulk message, auto-message, or auto-dial using WhatsApp." | Automation is explicitly permitted inside the 24-hour window, provided you offer prompt, clear and direct escalation paths to a human. |
| Quality visibility | Not exposed to you. | Green, Yellow or Red over a rolling seven days, with the customer block reasons visible in WhatsApp Manager. |
| Enforcement | An in-app ban notice. No documented graduated ladder. | Warning, then a 1 or 3 day template block, then a 5, 7 or 30 day full block, then an account lock, then permanent removal. |
| Appeal | "Request review" in the app. If the option is not shown, the ban is final and cannot be appealed. | Request Review in Business Support Home. Meta's Business Help Centre states all policy violations can be appealed within 90 days. |
| Regulated verticals | Prohibited outright: "You are prohibited from messaging about any Regulated Verticals on the WhatsApp Business App." | Permitted only in named countries, with licence and age gating. The UAE appears on none of those country lists. |
| Voice calling in the UAE | WhatsApp messaging works normally in the UAE. WhatsApp voice and video calling is restricted here under TDRA's VoIP policy, and licensed operators are obliged to block non-compliant VoIP traffic. Meta does not list the UAE among the countries excluded from its Business Calling API, but that is a statement about Meta's platform, not about a carrier-level block. Treat UAE availability as unresolved and do not build a plan on it. | |
| Verification | Meta Verified exists as a paid subscription an app account can hold. Meta's own ban article notes a banned account "automatically loses its Meta Verified subscription", with no refund. | Scaling to the 2,000 tier brings the ability to "display your business name to customers in chats" and "eligibility to apply for a WhatsApp official business account". |
Sources: WhatsApp Business Messaging Policy; WhatsApp Business Solution Terms; Meta's messaging-limits and policy-enforcement developer documentation; Meta Business Help Centre articles on quality rating and appeals; WhatsApp FAQ articles on account bans and restrictions; TDRA's published VoIP policy and FAQ.
Three things about WhatsApp pricing are widely reported and currently wrong. Conversation-based pricing was deprecated on Tuesday 1st July 2025, so "conversations per month" is no longer a billing unit. There is no free monthly allowance any more. And the UAE marketing rate rose on Wednesday 1st October 2025, which is why so many vendor pages still quote a figure that has not been true for eleven months.
| Category | USD per message | AED per message |
|---|---|---|
| Marketing | $0.0499 | AED 0.1832 |
| Utility, first 100,000 a month | $0.0157 | AED 0.0576 |
| Authentication, first 300,000 a month | $0.0157 | AED 0.0576 |
| Service | $0.00 | AED 0.00 |
Pulled from Meta's own live rate card for market AE on Thursday 3rd September 2026. Marketing returns an empty volume-tier list for the UAE, meaning there is a single flat marketing rate here with no volume discount. Utility and authentication are tiered, and the tier boundaries are different for each, so a calculator that reuses one threshold set for both will be wrong.
Meta added AED as a billing currency on Wednesday 1st April 2026 and publishes a separate AED rate card. Those AED figures are not a live conversion of the USD figures. Multiply the dollar rate by a market FX rate and you will produce a number that does not match your client's actual Meta invoice. Use Meta's published AED line, which is what the table above does.
Meta has published that two things which are free today become chargeable on Thursday 1st October 2026: service messages, and utility templates delivered inside an open 24-hour customer service window. For service messages Meta states the charge will be each market's existing utility or authentication rate, with no volume tier discounts. For in-window utility templates Meta says only that they revert to being charged, and has not published a separate rate line, so the ordinary utility rate is a planning assumption rather than a published figure.
| Change | Effective | Detail |
|---|---|---|
| Meta Business Agent messages become chargeable | 1st August 2026 | "One global rate of $2.00 USD per 1M tokens", which Meta estimates at "approximately 4 to 5 cents (USD) per message". |
| Service messages become chargeable | 1st October 2026 | Charged per message at the market's existing utility or authentication rate. No volume tier discounts. |
| Utility messages inside the 24-hour window become chargeable | 1st October 2026 | Free since July 2025, reverting to charged. |
| 72-hour free entry point window | Unchanged | Messages inside it "remain free for message delivery". |
Meta's main pricing page still says non-template messages and in-window utility templates are free, and makes no mention of the October change. Meta's dedicated upcoming-changes page says both become chargeable. Both are Meta primary sources and they contradict each other as of Thursday 3rd September 2026. Nobody selling you a WhatsApp deployment can resolve that for you, and any vendor telling you confidently that "replies are always free" has not looked recently.
Meta has also not yet published a UAE service-message rate line for October. If service is charged at the market utility rate as stated, the UAE figure would be $0.0157 or AED 0.0576, but that is a planning assumption rather than a published rate.
Meta's rate is the floor, never the bill. Providers charge in one of two shapes, and mixing them up is the most common costing error we see.
Widely repeated markup percentages for several other providers appear only in third-party comparison blogs, with no primary source we could retrieve. They are deliberately not on this page. If a number matters to your budget, ask the provider to point at their own published price for it.
Nobody in the room knows what Meta's per-message fee actually is. In one meeting a quoted rate of $0.025 was read aloud as 25 cents and neither side corrected it confidently. That $0.025 was an operator's recollection, not a Meta rate, and nobody present could say so. That is not a criticism of operators, it is a symptom of how badly this is documented in the market. Bring the rate card to the meeting.
These are the two reasons most businesses actually move, and they are the two rows where competitor comparison tables are least reliable.
On the app, the conversation lives on a phone. That is the real constraint, and it is the one operators describe to us: "If I close the WhatsApp, I can't find the data, I have to open chat by chat." The fear is not that automation is bad, it is that automation leaves no institutional record.
On the Cloud API there is no WhatsApp-imposed seat count at all, because there is no WhatsApp interface. How many people can be in the inbox is decided entirely by the software you connect, and it is priced by that vendor, not by Meta. What Meta does document is the number of phone numbers you may register: up to two before scaling, and up to 20 once your business portfolio reaches the 2,000 tier.
Comparison tables routinely give a specific seat limit for the WhatsApp Business app. We could not source that figure to a Meta document, so it is not on this page. If a vendor quotes you one, ask which Meta page it comes from before you plan a rota around it.
The app is governed by the consumer-side guidance, which is blunt: "Don't bulk message, auto-message, or auto-dial using WhatsApp. WhatsApp uses both machine learning technology and reports from users to detect and ban accounts that send unwanted automated messages." Automation is not a supported use of the app.
The API is the opposite. The Business Messaging Policy states you may use automation when responding during the 24-hour window, on one condition: you must have available prompt, clear and direct escalation paths. Meta lists them: in-chat human agent transfer, phone number, email, web support on the business website, in-store visits, or a support form. An AI assistant with no route to a human is the part that breaches policy, not the AI assistant.
The rule that arrived with the Business Solution Terms update bars AI providers from using the WhatsApp Business Solution to distribute their own assistant where that assistant is "the primary (rather than incidental or ancillary) functionality being made available". That is the general-purpose assistant distribution case.
The same clause then says the opposite of what the headlines said: "you may retain an AI Provider as your Third Party Service Provider". A business running an AI assistant to serve its own customers is a customer of an AI provider, not an AI provider. Nothing in the clause caps how capable that assistant is, and the popular framing that "open-ended bots are banned and structured bots are fine" does not appear anywhere in the terms.
There is one real constraint for vendors in that clause. You may fine-tune on conversation data only for a model that is for your exclusive use. Pooling client conversations to train a shared model is prohibited, and Meta states it may terminate the account for it.
One more thing Meta says out loud, and almost nobody quotes: your bot is an input to your number's quality rating. Meta's own guidance on driving high-quality conversations names "the bot functionality and how quickly questions and other enquiries are resolved" among the factors influencing user sentiment and the rating. A bad assistant is not just a bad experience, it is a scoring problem.
This is the row that sells the API more often than any feature, and it is the row where the least is actually documented. Here is what is on the record.
Meta's Business Help Centre lists, among the things a business portfolio gains after scaling from the 250 tier to the 2,000 tier, two items in its own words: "Display your business name to customers in chats" and "Gain eligibility to apply for a WhatsApp official business account".
Read that carefully. Eligibility to apply is not a badge. Scaling is a precondition, not an approval. Meta does not publish the full criteria it applies to the application, and this page will not invent them.
On the app side, Meta Verified exists as a paid subscription that a WhatsApp Business app account can hold. We know that from an unexpected place: Meta's own article on banned Business app accounts, which notes that a banned account "automatically loses its Meta Verified subscription" and that the subscription is cancelled with no refund available.
Meta's term is "official business account". The market calls it the green tick. respond.io's own comparison table calls the same row "Blue tick verification". Three names, one poorly documented process, and a lot of vendors implying that buying their platform delivers it. Buying an API deployment does not buy you a badge. It makes you eligible to ask for one.
Ban fear is the most consistently evidenced anxiety in this market. It is the headline hook in a competitor's Meta ad copy, it sits in the title of a UAE search result we found, and it is a Reddit thread. Almost every prospect assumes the API is the risky surface and the app is the safe one. The documentation says the reverse.
On the app you get one binary outcome, delivered as an in-app notice, and possibly no appeal at all. Meta's own wording: "If you don't see an option to request a review, it means the ban is final and can't be appealed." Only one phone number is reviewed per appeal, and you cannot reach your chat history or backups while the account is banned.
On the Cloud API you get a warning first, a named policy, an itemised violation, a documented ladder, and a 90-day appeal window. The ladder Meta publishes runs: a 1 or 3 day block on sending template messages and adding phone numbers; then a 5, 7 or 30 day block on sending anything; then an account lock, removable only via appeal; then, after multiple warnings without change, permanent removal from the platform.
For any UAE business doing outbound at volume, the API is the lower risk surface, not the higher one. That is the opposite of what most people walk in believing.
Not automation, and not volume in itself. Meta acts on user feedback signals and on policy category violations. Message quality is computed from "blocks, reports, mutes, archives, and reasons users provide when they block you" over the past seven days, weighted by recency. Note that archives and mutes count against you, which is materially stricter than the commonly repeated "only blocks matter".
Templates carry their own separate score. A template can degrade on low read rate alone, with no blocks at all. When one hits Red, Meta pauses it for 3 hours, then 6 hours on the second instance, then disables it on the third. Meta notes that pausing does not initially affect the phone number, but that a business consistently sending low-quality templates may eventually see the number impacted.
Usually template pacing, not a ban. Meta holds messages on a new or previously non-Green template once an unspecified threshold is reached, waits for early customer feedback, then either scales the send to the full audience or drops the held messages. Dropped ones surface as a failed status with error code 132015. Meta's stated goal is that even paced campaigns still deliver within an hour at the 99th percentile. Panicking and re-sending is the wrong response.
There is also a ceiling you cannot see. Meta limits how many marketing template messages any individual user receives across all businesses, based on that person's recent marketing read rate and how full their inbox is. The UAE is not on the exclusion list for that mechanism, so it applies to UAE senders and UAE recipients. Separately, WhatsApp gives users an "Offers and announcements" setting that stops marketing from your business entirely, at which point the API accepts your request and simply does not send, returning code 131050. Your CRM will not know unless you subscribe to the user preferences webhook.
We sell API deployments. This section still belongs on the page, because the fastest way to lose a UAE client is to sell them infrastructure they did not need and then watch them notice.
What you give up by staying on the app is worth naming: no visible quality rating, no graduated warnings, no itemised violation, and an appeal route that may not exist at all when you need it.
Here is the part vendors answer with total confidence and Meta's public documentation answers only partly. We will separate the two.
Messaging limits are calculated and set at the business portfolio level, and are shared by every business phone number in that portfolio. One number can consume the whole portfolio's capacity in a period. That single fact reshapes most migration plans, and it kills the popular idea that adding numbers adds volume.
Getting from 250 to 2,000 has three published paths: verify your business, have your partner verify your business if you were onboarded by one, or send 2,000 delivered messages outside customer service windows to unique recipients within a 30-day moving period using templates with a high quality rating.
The developer documentation says "2,000 delivered messages... within a 30-day moving period". The Business Help Centre article says the quality messaging path "requires a minimum of 1,000 conversations over 30 consecutive days". Both are Meta. We report both rather than picking the one that sounds better.
On timing, Meta states partner-led business verification is faster, with most requests resolved within minutes and some taking up to 24 hours, while Meta business verification can take "as little as 10 minutes and as long as 14 working days". Beyond the 2,000 tier, increases are automatic: send high-quality messages across all numbers and templates, use at least half your current limit in the last 7 days, and the portfolio moves up one level within 6 hours.
Whether your chat history transfers, how WhatsApp coexistence behaves in practice, whether customers notice a difference under coexistence, and whether one number can serve both surfaces at once are all questions the competitor pages answer in a sentence each. We did not verify any of them against Meta's own text for this page, so they are not asserted here.
That is not evasion, it is the test we would apply to any vendor. Ask whoever is quoting you to point at the Meta documentation for the migration promise they just made. If they cannot, the promise is theirs, not Meta's, and it should appear in your contract rather than in a slide.
Three columns, kept strictly apart. The first two are policy. The third is market practice we observe, and it is labelled as practice because no Meta document endorses any of it.
How many reports it takes to get banned. Meta publishes none. Any unban success rate or recovery statistic. Meta publishes none. Any warm-up schedule presented as Meta guidance. There is no such guidance. If you have read one of those figures somewhere, it was made up by whoever needed it in a sentence.
Federal Law No. 2 of 2019 applies to all uses of ICT in health in the UAE, explicitly including the free zones. Its Article 13 prohibits storing, processing, generating or transforming health data relating to health services provided inside the State anywhere outside the State, except where a resolution is issued by the Health Authority in coordination with the Ministry. The penalty attached specifically to Article 13, under Article 24, is not less than AED 500,000 and not more than AED 700,000.
That figure is real and it is frequently misquoted. It is not a general health-data-breach fine, and it is not the penalty for sending a patient a message. It attaches to cross-border storage and processing. HIPAA, meanwhile, is United States law and does not apply in the UAE. The UAE instrument is Federal Law No. 2 of 2019, and a vendor telling a Dubai clinic it must be "HIPAA compliant" as a matter of UAE law is telling you they have not read the local statute. Meta's own Business Messaging Policy also states plainly: don't use WhatsApp for telemedicine, or to send or request health related information where applicable regulations prohibit distributing it to systems without heightened requirements.
Learnmind builds AI customer communication on WhatsApp, Instagram and Facebook for businesses in Dubai and beyond. Two client results are published on our site, and those are the only two we will quote you.
Alcaz Media is a UAE-based performance marketing agency working with brands like Ferrari Middle East, La Vista Development, and Myjooti.
As published on learnmind.ai/results, alongside our work with UK beauty brand Lola's Lashes.
We also work with clients in the healthcare and aesthetics space. Due to the sensitive nature of these engagements, we are unable to publicly disclose their identities. If you are a healthcare provider and would like to learn more about our work in this sector, get in touch and we can share relevant details privately.
The WhatsApp Business app is a free application you install on a phone, with its own inbox, catalogue and broadcast lists. The WhatsApp Cloud API is an interface with no inbox of its own, so it must be connected to separate software and a Solution Provider. The app is free and cannot be automated under Meta's rules. The API bills per delivered template message, permits automation inside the 24-hour customer service window, exposes a quality rating, and is additionally governed by the WhatsApp Business Solution Terms.
No. Since Tuesday 1st July 2025 Meta charges per delivered template message, and there is no free monthly allowance. Inbound user messages are not billed by Meta. On top of Meta's rate you pay your provider, which is charged either as a per-message markup, for example Twilio publishes $0.005 per message on inbound and outbound, or as a flat platform fee, for example 360dialog publishes €49 per number per month with no markup on Meta fees.
On Meta's published UAE rate card, checked on Thursday 3rd September 2026: marketing is $0.0499 or AED 0.1832 per message, with a single flat rate and no volume tiers in this market. Utility is $0.0157 or AED 0.0576 for the first 100,000 messages a month, and authentication is the same rate for the first 300,000. Service messages are free today. Meta publishes AED directly, so do not convert the dollar figure yourself, and note the UAE marketing rate rose on Wednesday 1st October 2025, which is why many vendor pages still quote a stale number.
A newly created business portfolio has a messaging limit of 250 unique WhatsApp user phone numbers per rolling 24 hours, outside customer service windows. It rises to 2,000, then 10,000, 100,000 and unlimited. The commonly quoted "Tier 1 is 1,000 messages a day" is wrong. Limits are set at the business portfolio level and shared across every phone number in the portfolio, so adding numbers does not add capacity.
No. The AI Providers clause in the WhatsApp Business Solution Terms prohibits providers and developers of AI technologies from using the WhatsApp Business Solution to distribute their own assistant where that assistant is the primary functionality being offered. The same clause explicitly permits a business to retain an AI provider as its third party service provider. A business running an AI assistant for its own customers is a customer of an AI provider, not an AI provider. The separate and older rule that does apply is that automation inside the 24-hour window must offer prompt, clear and direct escalation paths to a human.
For a business doing outbound at any volume, the app carries more risk. A banned app account gets an in-app notice and, in Meta's own words, if the request review option is not shown then the ban is final and cannot be appealed. The Cloud API gives you a warning first, a named policy, an itemised violation, a documented ladder of graduated blocks, and a 90-day appeal window. Note also that the Flagged and Restricted phone number statuses were discontinued on Tuesday 7th October 2025, so any guide built around them is out of date.
WhatsApp messaging works normally in the UAE. WhatsApp voice and video calling is restricted here: TDRA regulates voice over internet protocol as a licensed telecommunications service, and licensed operators are obliged to block non-compliant VoIP traffic. Meta does not list the UAE among the countries excluded from the WhatsApp Business Calling API, but that describes Meta's platform availability rather than the carrier-level position in the UAE, and we found no authoritative source confirming that such a call connects to a UAE mobile network. Treat it as unresolved and build on messaging.
No. Meta states the opt-in can be general and not specifically for WhatsApp, provided you comply with all local laws, clearly state that the person is opting in to receive communication, and clearly state the name of the business they are opting in to hear from. Meta names SMS, a website, a phone IVR flow, and in person or on paper as accepted methods. In the UAE, Cabinet Resolution No. 56 of 2024 separately defines telemarketing to include marketing messages through social media applications, and its obligations include a communication channel for consumers who want marketing information and not contacting people on the Do Not Call Registry. Note that the resolution's operative controls are drafted in call language, so how they apply to a WhatsApp template message is not specified in the text.
We are not going to answer that from a vendor's marketing page. Meta's own documentation on chat transfer and on WhatsApp coexistence was not verified for this guide, so no claim is made here. What is documented is the process around it: messaging limits are set at the business portfolio level, you may register up to two phone numbers before scaling and up to 20 after, and scaling to the 2,000 tier requires business verification, partner-led verification, or a qualifying volume of high-quality messages over 30 days. Ask any provider quoting you a transfer promise to point at the Meta page it comes from.
Fifteen minutes, no deck. Tell us how many people answer your WhatsApp, what you send and to whom, and we will tell you honestly whether the Cloud API earns its cost in your business or whether the free app is still the right answer.
Rates and policy statements on this page were checked against Meta's published documentation on Thursday 3rd September 2026. This page is commercial guidance, not legal advice. A clinic or regulated business making a compliance decision should have the primary instruments reviewed by UAE counsel.