Most guides on this subject are two years stale. They still describe conversation pricing that Meta retired on 1 July 2025, still weigh the Cloud API against an On-Premises product that stopped delivering messages on 23 October 2025, and still call the badge a green tick when Meta's own documentation calls it blue.
This page is written for a business in the UAE that is trying to work out whether to buy this at all. It tells you what the Platform is, whether you need it, what it really costs once the provider fee and the build are in the number, what you can build on it, and what actually gets a number taken away. It also tells you when the free app is the right answer and you should keep your money.
Three separate products carry the WhatsApp name. Two of them are free. One of them bills you per message. Vendors blur the three constantly, so start here.
The consumer app is personal messaging, built for talking privately to friends, family and businesses. The WhatsApp Business app is a free download aimed at a small business owner. It adds a product catalogue that works as a small mobile storefront, along with automated greetings and canned replies, and it runs on a single phone number. Someone holds that phone.
The WhatsApp Business Platform is the third thing, and Meta is unusually blunt about it: it is not an app at all. It is a collection of APIs, an interface that other software talks to. There is nothing to install and no inbox to open. Your booking system, your CRM or your chatbot sends a request to Meta, and Meta delivers the message. Because the Platform gives you no inbox of its own, most businesses buy one, and that is where a provider's monthly fee comes from.
Put plainly: the Business app is a phone in one person's hand. The Platform is a socket your other systems plug into. Everything else follows from that. The Platform supports multiple numbers, thousands of agents and bots on the same number, pre-approved message templates, and integration with a CRM or marketing platform. It also needs either developer resources or a Meta-approved partner to run. The app needs neither.
| Consumer WhatsApp | WhatsApp Business app | WhatsApp Business Platform | |
|---|---|---|---|
| What it is | A personal messaging app | A free app for small business owners | A collection of APIs. Meta states it is not an app |
| Who holds it | A person | One owner or a small team sharing one phone | Your software, with staff working through a separate inbox product |
| Phone numbers | One | One | Multiple |
| People replying at once | One | One phone at a time | Thousands of agents and bots |
| Automation | None | Greetings, away messages, quick replies, catalogue | Approved templates, chatbots, CRM and marketing platform integration |
| What Meta charges | Nothing | Nothing | Per delivered template message, since 1 July 2025 |
| What it takes to set up | A phone number | A phone number | Developer resources or a Meta-approved partner |
Plenty of guides still weigh the Cloud API against the On-Premises API. Treat that section as proof the page is stale. Meta stopped feature updates to On-Premises on 9 January 2024, restricted new number registration to the Cloud API from 1 July 2024, and the final version expired on 23 October 2025. Meta's wording is flat: messages sent to or from business numbers still registered for On-Premises will not be delivered. Cloud API is the only supported route in 2026. Meta's own case for it is up to 1,000 messages per second, 99.9% uptime and sub-five-second p99 latency, with some partners reporting infrastructure cost reductions of 90% or more. Those are Meta's figures, published to justify the migration, not independent measurements.
You genuinely need the Platform when at least one of these is true:
The free Business app is the right answer, and paying for the Platform is a waste, when:
Two things to weigh before you switch. Meta has billed per delivered template message since 1 July 2025, so cost now tracks how many templates you send, not how busy your inbox is: the UAE rates sit on our WhatsApp Business API pricing page. And a new business portfolio starts capped at 250 unique recipients outside a service window in a rolling 24 hours, shared across every number in that portfolio, so the Platform does not hand you scale on day one.
Migration is the other trap. A number already in use with WhatsApp cannot be registered on the Platform unless it is deleted first, and that destroys the chat history. The exception is Coexistence, which keeps the Business app running on the number and carries up to six months of history across, and Meta requires a Solution Partner or Tech Provider to do it. The app versus Cloud API comparison covers the migration in detail, and choosing a provider covers who should do it for you. One thing the Platform will not fix for a UAE business is WhatsApp calling, which is a separate regulatory question.
Two routes exist. You build against Meta's Cloud API yourself, or you go through a Meta-approved partner. Meta names two partner types, Solution Partner and Tech Provider, not one generic "BSP". The difference that matters is who bills you and what you may do with your existing number.
| Dimension | Direct Cloud API | Tech Provider | Solution Partner |
|---|---|---|---|
| Who bills you for Meta usage | Meta, on your own payment method | Meta, once you attach your own payment method | The partner, which can extend credit and invoice you |
| Keep your number and chat history | No | Yes, via Coexistence | Yes, via Coexistence |
Choosing between providers is its own subject, covered on choosing a WhatsApp Business API provider in the UAE. If one person answers every chat on one number and you never message a list, do not start any of this. Stay on the free app: see WhatsApp Business app vs the Cloud API.
The rule depends on which WhatsApp your number is on today. Meta's phone number page still carries the flat sentence that numbers already in use with WhatsApp cannot be registered unless they are deleted first, and for a number on the consumer app that holds: delete the account, lose the history. For a number on the WhatsApp Business app it no longer holds as a blanket rule, because Coexistence exists. A number that has been banned has to be unbanned through the appeal process before either route will work.
The exception is Coexistence. The Business app keeps running on the same number, messages mirror both ways, and with your consent up to six months of history syncs into the API along with your WhatsApp contacts. Group chats do not come across, and view-once and disappearing messages are switched off. You get 24 hours to finish the sync or you start over. Meta states you must use a Solution Partner or Tech Provider for it, so a salon with two years of threads on its main number cannot go direct and keep them. That constraint, not technical skill, decides the route for most UAE SMEs.
Verification is not required to finish partner-led Embedded Signup, and Meta's direct get-started flow does not list it either. Do it early anyway. It is one of the three ways off the 250-contact starting limit, and it lifts your portfolio's number cap from 2 to 20.
Meta accepts five document categories: certificate or articles of incorporation, a business registration or licence, a government-issued business tax document (self-filed returns are not accepted), a business bank statement, and a utility bill. For the UAE, Meta's country matrix accepts a certificate of formation, the commercial licence (رخصة تجارية), the VAT registration certificate, a telecoms or electricity bill, and a bank statement. Arabic documents are accepted as they are.
One rule breaks more applications than anything else: the name on the document must match exactly what appears in your Meta Business Portfolio. A DEWA bill proves your address, not your legal name, so the commercial licence carries the weight. Set the portfolio name to the exact string on the licence, entity suffix included, FZ-LLC, FZCO or L.L.C. Free-zone trade names that differ from the registered entity are the usual culprit, though that diagnosis comes from partner material, not a Meta page.
This has changed. Review is no longer an upfront blocker: Meta now runs it automatically when you reach a higher messaging limit. You get 10 name changes per 30-day period, and once a change is approved you have 14 days to re-register the number or the approval lapses. Meta does publish display name guidelines, in the Business Help Centre, and the automatic review runs against them. That page resists automated reading, so the list below separates what is documented from what is partner-reported. Documented: the name has to relate to your business, appear on your official website, and not be a generic term or a bare geographic location on its own. Partner-reported, and worth avoiding regardless: URLs, phone numbers, emoji and decorative punctuation, personal names with no visible link to the business, and the words WhatsApp or Meta.
It is not green any more. Meta's documentation calls the Official Business Account badge a blue checkmark, so anyone selling a "green tick service" in 2026 is quoting retired marketing. You can apply yourself, in WhatsApp Manager. Meta lists five criteria: policy compliance, 30 days on the platform, a verified business portfolio, two-step verification enabled, and an approved display name. Brand fame is not one of them. Meta Verified is a separate paid subscription and is not the same thing. More sits on getting the WhatsApp green tick in the UAE.
On timing, be sceptical of everyone. Meta publishes no end-to-end onboarding SLA, so every "live in 24 hours" figure comes from a vendor page. The only timings Meta commits to near this flow are limit upgrades applying within six hours once you qualify, and appeals decided in 24 to 48 hours. Setup is the fast part. Verification is the part you cannot schedule, and a name mismatch is what turns days into weeks. One thing you can stop worrying about: there is no UAE government or TDRA approval process for the API. TDRA blocks WhatsApp voice and video calling, not messaging, which is covered on WhatsApp calling in the UAE.
Two things need to be straight before you look at a single rate. Meta bills you per delivered message, not per conversation. And Meta's bill is usually the smallest line in what you actually pay.
Meta's wording is flat: "Effective July 1, 2025, Meta charges on a per-message basis." Conversation-based pricing is marked deprecated. The allowance everyone remembers, the first 1,000 service conversations free each month, is gone, and service conversations became free for everyone on 1 November 2024 in any case.
Be careful who you read. Meta's own marketing site still describes those 1,000 free conversations. Its developer documentation contradicts it. Treat any page repeating the old model as proof nobody has updated it in two years.
You are charged when a template message is delivered. Not when it is read, and not when it earns a reply. A 5,000-contact broadcast that nobody opens costs exactly what one that fills your diary costs.
There are exactly three template categories: marketing, utility and authentication. "Service" is not a template category, it is a billing label for free-form messages sent inside the 24-hour window. Anything selling you four categories is out of date.
The rate then varies by the recipient's country calling code. Utility and authentication carry volume tiers, so higher monthly volume automatically unlocks a lower rate. Marketing has no tiers.
The nasty part is miscategorisation, and it is quiet rather than loud. A utility template that reads as promotional is automatically recategorised to marketing and its status stays approved. It keeps sending. It just starts costing the marketing rate, after one day's notice, and repeat offenders lose even that notice. The rejection rule runs the other way round from what most guides say: it is a template you filed as marketing or utility, whose content Meta decides is really authentication, that gets killed. Even then it is not instant. You get notice, and the status flips to rejected on the first day of the following month.
One hard limit: marketing templates are not delivered to United States numbers at all. Utility and authentication to US numbers are unaffected.
The exception to free free-form messaging: from 16 February 2026 Meta charges businesses it classifies as AI Providers for non-template messages in the markets that policy covers. It dropped those charges in most European markets on 13 May 2026. A business running an assistant for its own customers is not an AI Provider under that policy.
Answering fast is a pricing decision, not just a service one. Let the window lapse and your next contact is a paid template.
The platform fee. Almost nobody uses the Cloud API raw. You go through a Solution Partner, who invoices you and carries the credit line, or a Tech Provider, where Meta bills you directly for usage and the provider bills for everything else. Either way there is a subscription. Published examples: 360dialog lists EUR 49 a month for its entry tier, Twilio charges from USD 0.005 per message on top of Meta's fee. Most Gulf providers publish nothing. Choosing between them is covered in our provider buyer's guide and the Dubai vendor comparison.
The build. Templates written and approved, flows designed, your CRM or booking system connected, Arabic and English variants doubling the approval work. One-off, usually the largest number in the project, and no honest figure exists in the abstract.
The management. Template rejections and resubmissions, quality-rating monitoring, recategorisation drift, someone actually answering. Budget for it monthly or it comes out of your own evenings.
Assumptions, all labelled and all yours to change: a Dubai property agency, 3,000 marketing templates delivered a month, 800 utility templates delivered outside the window, every other reply landing inside an open window, all recipients on UAE numbers, at Meta's published UAE rates read on 3 September 2026.
| Line | Working | Monthly |
|---|---|---|
| Marketing templates | 3,000 at AED 0.1832 | AED 549.60 |
| Utility, outside window | 800 at AED 0.0576 | AED 46.08 |
| Utility, inside window | free today | AED 0.00 |
| Meta subtotal | AED 595.68 | |
| Platform fee | provider dependent | from EUR 49 |
| Build and management | quoted per project | not modelled |
Read that honestly. Meta's share is under AED 600. The platform fee, the build and the person running it are the real bill, and a rate card never shows them.
For the live UAE rate card in dirhams, both volume-tier tables and the change Meta has published for 1 October 2026, see WhatsApp Business API pricing in the UAE. To run your own volumes, use the UAE pricing calculator. Do not convert a USD rate into dirhams yourself: Meta publishes a separate AED card and the two do not match.
The platform has two modes, and nearly every design decision follows from which one you are in. Inside an open customer service window you can send almost anything, free-form and instantly. Outside it you can send one thing only: a message template that Meta approved in advance.
The window opens when a WhatsApp user messages you or calls you, and the timer resets to 24 hours on each new inbound contact. Inside it, Meta documents 16 service message types that need no pre-approval: text, images, video, audio, documents, stickers, contact cards, location, location requests, reactions, interactive reply buttons, list messages, call-to-action URL buttons, address messages, interactive voice call messages and WhatsApp Flows. Outside it, Meta is blunt.
You can only send pre-approved template messages.
The calling trigger matters less here than elsewhere. WhatsApp voice and video calling is restricted on UAE networks, so build for messaging and read what actually works with WhatsApp calling in the UAE before a vendor sells you a voice feature.
One exception widens the window. If someone reaches you through a Click to WhatsApp ad or a Facebook Page call-to-action button and you reply within 24 hours, a 72-hour free entry point window opens in which every message, templates included, costs nothing. That is the cheapest lane on the platform, and it is covered on capturing leads from Instagram ads.
| Category | What it covers | When you pay |
|---|---|---|
| Utility | Order confirmations, delivery and tracking updates, payment reminders, appointment and account alerts, feedback tied to a specific transaction. Zero persuasive intent, and specific to that customer. | Charged outside a customer service window, free inside one. |
| Marketing | Offers, promotions, coupons, product recommendations, abandoned cart nudges, retargeting. Also the bin for anything vague or mixed. | Always charged. |
| Authentication | One-time passcodes only. No URLs, no media, no emojis, parameters capped at 15 characters. | Always charged. The in-window exemption covers utility only. |
"Service" is not a template category. It is the label for free-form messages inside the window, and those are free. The categorisation trap is quiet rather than loud: a utility template Meta judges to be promotional gets recategorised to marketing and stays approved, so it keeps sending and quietly starts costing the marketing rate. The rejection runs the other way. A template you filed as marketing or utility, whose content Meta reads as authentication, is the one that gets killed, and it dies on the first day of the following month rather than on the spot. Actual rates live on the UAE pricing page.
Because free-form replies inside the window need no approval, an AI can answer what the customer actually asked, in Arabic or English, read a photo, and hand over to a human. Two things to know. Meta introduced pricing for businesses classified as AI Providers, effective 16 February 2026, charging for non-template messages in specific markets, and discontinued those charges in most European markets on 13 May 2026. Meta also has a policy position on AI in these threads: see what actually gets an account banned.
If everything on your list happens inside the window, replies to people who messaged you first, greetings, quick replies, a catalogue, the free Business app already does most of it. That comparison is on app versus the Cloud API. Note too that product catalogues appear in Meta's description of the Business app, and a catalogue message is not among the 16 documented service message types, so if catalogue selling is the reason you are buying, make your vendor demonstrate it before you sign.
Two separate systems can take your number away, and people confuse them. The quality rating measures how customers react to you. Policy enforcement judges what you sent. A number can hold a perfect rating and still be blocked for a breach, and it can slide to red without breaking a rule.
Meta's bar is lower than most vendors imply. Its opt-in documentation accepts a general opt-in that need not name WhatsApp, provided you comply with all local laws. That final clause is where a UAE business actually lives, because local law is stricter than Meta.
The working test: for any number on your list, can you show when and where that person agreed to hear from you? A walk-in who gave a mobile number to confirm a booking has not consented to your Eid promotion, and a bought list is not consent in any form. Customers can also switch you off silently through WhatsApp's "Offers and announcements" setting, after which your marketing templates fail with error 131050. The exact wording sits on our page on what actually triggers a WhatsApp Business ban.
It is not your delivery rate or your open rate. Meta computes it from the last seven days of recipient feedback, weighting recent messages more heavily. The signals it names are blocks, reports, mutes, archives, and the reasons people give when they block a business. Mutes and archives are the two that matter most and the two you will never see, because a muted thread looks identical to a read one in your own numbers. Anyone claiming reply rates or send volume feed the score is guessing. Green is high, yellow medium, red low, and a number with too little history reads as unknown. All of it sits in WhatsApp Manager, under Account tools and then the phone numbers panel.
| Status | Means | Consequence |
|---|---|---|
| Connected | Normal | You send within your messaging limit |
| Flagged | Quality is low | If it does not recover in seven days the limit drops one tier. Since 7 October 2025 that limit is set per business portfolio, so one bad number drags every number you own down with it |
| Restricted | You hit your 24-hour limit | You can still reply to inbound messages. Sending resumes next period |
| Rate limited | You are sending faster than Meta will accept | Messages start failing. This is the one that stops a campaign mid-send |
| Banned | Policy enforcement, not quality | The number is gone unless the appeal succeeds |
Red is not a ban. It is a seven-day warning with a demotion at the end, and Meta emails you when it starts. Templates run the same mechanic: one that reaches low quality is paused three hours, then six, then disabled on the third instance. Policy enforcement is harsher and runs independently, escalating from a one or three day block on templates, to a five, seven or thirty day block on all messages, to permanent disablement. Appeals usually take 24 to 48 hours, and Meta says not all spam violations may be appealed.
The limit counts unique customer numbers you message outside an open customer service window in a moving 24 hours. Replying to people who contacted you first does not count. Tiers run 250, then 2,000, 10,000, 100,000, then unlimited.
Getting off 250 takes one of three routes: complete Meta business verification, have a partner verify you, or deliver 2,000 outside-window messages to unique numbers in 30 days on high-quality templates. The third is circular at 250 a day, so verification is the real answer, covered on the green tick and verification page. Above 2,000, scaling is automatic within six hours if quality stays high and you used at least half your current limit in the past seven days.
One trap catches multi-branch businesses. Since 7 October 2025 limits are set per business portfolio and shared by every number in it, so buying more numbers does not buy more capacity. A separate per-customer marketing cap exists, but Meta publishes no figure because it adapts to each person's recent engagement.
Meta's terms bar AI providers from using the platform to distribute their assistants as the product, while explicitly permitting a business to retain an AI provider as its service provider. A clinic running an assistant for its own patients is the second thing, not the first. The clause is quoted in full on our ban triggers page. Separately, from 16 February 2026 Meta charges businesses it classifies as AI Providers for non-template messages in certain markets, breaking the rule that free-form replies are free. It dropped those charges in most European markets on 13 May 2026.
This is where most guides overstate the risk, so here is the honest version. The mainland PDPL, Federal Decree-Law 45 of 2021, requires consent you can prove, given clearly and for a stated purpose, and withdrawable at any time. It does not require consent to be channel-specific, and it is not true that nothing can be processed without consent: the law lists ten grounds that need none, including performing a contract the customer is party to. Its Implementing Regulations still have not been issued, so there is no federal penalty regime and no enforcement record to point at. Treat it as the direction of travel, not a deadline.
DIFC and ADGM are different. They run their own data protection laws with real regulators and real fines, so if your licence sits in either zone, that is the regime that binds you, not the federal one.
On sending hours, the number everybody quotes needs a caveat. TDRA's policy on unsolicited electronic communications does prohibit marketing between 21:00 and 07:00 and does require an opt-out on every marketing text. But it defines its scope as messages sent over a UAE telecom licensee's network, SMS and MMS. WhatsApp traffic is data through Meta's Cloud API, so on the policy's own wording it does not bind a WhatsApp sender. Keep to daylight hours anyway, because a 22:00 promotion earns blocks, and blocks are what actually cost you the number.
One practical win: Cloud API supports data localisation and the UAE is on the list, so message content can be pinned at rest inside the country. Health data has its own stricter regime, covered for clinics in Dubai.
It is not an app. Meta calls it the WhatsApp Business Platform, and it is a set of APIs that your own software talks to. There is nothing to install and no inbox to open, which is why almost every business that adopts it also buys an inbox product from a partner. That partner subscription, not Meta's per-message fee, is usually the larger bill.
You need the Platform if more than one person has to answer the same number at once, if software has to send or reply for you, if you need to send approved templates to a list rather than only replying to people who message first, or if conversations have to land in another system. If one person answers and keeps up, the free Business app does the job and paying for the Platform is a waste.
Meta has billed per delivered message, not per conversation, since 1 July 2025. Read on 3 September 2026, the UAE rates were AED 0.1832 for a marketing template and AED 0.0576 for utility and authentication, with service messages free. On top of Meta's fee sit a provider subscription, the one-off build, and ongoing management. In a worked example of 3,000 marketing and 800 utility templates a month, Meta's share was under AED 600, which was the smallest line in the total.
It depends which WhatsApp the number is on. A number on the consumer app has to be deleted before it can be registered, and deleting it destroys the history. A number on the WhatsApp Business app can move across through Coexistence, which keeps the app running on the same number and syncs up to six months of history. Meta requires a Solution Partner or Tech Provider to do Coexistence, so you cannot go direct and keep your history.
Meta publishes no end-to-end onboarding time, so every "live in 24 hours" figure comes from a vendor's own page. The technical setup is the fast part. Meta business verification is the part you cannot schedule, and the single thing that turns days into weeks is a mismatch between your trade licence name and your Meta Business Portfolio name. There is no TDRA or UAE government approval process for the API itself.
Two separate systems can take a number away. The quality rating measures how customers react, using blocks, reports, mutes, archives and the reasons people give when they block you. Policy enforcement judges what you sent. In practice the ranked causes are messaging people who never opted in, filing marketing as utility, blasting a cold list on day one, and ignoring the email that tells you your number has been flagged.
No. Meta's documentation calls it the Official Business Account badge and it is a blue checkmark, so anyone selling a green tick service in 2026 is quoting retired marketing. You apply for it yourself in WhatsApp Manager against five published criteria, and brand fame is not one of them. Meta Verified is a separate paid subscription and is not the same thing.
Not directly, and this is widely misreported. The TDRA policy that bans marketing between 21:00 and 07:00 defines its scope as messages carried over a UAE telecom licensee's network, meaning SMS and MMS. WhatsApp traffic is data through Meta's Cloud API, so on that policy's own wording it does not bind a WhatsApp sender. Keep to daylight hours anyway, because a late promotion earns blocks, and blocks are what cost you the number.
Fifteen minutes on a call. We will tell you honestly whether the API is worth it for your volume, or whether the free app already covers you. We would rather say no than sell you a platform fee you do not need.
Dubai based. We answer on WhatsApp, which is the whole point.