WhatsApp Business API providers in the UAE: a buyer's guide

A WhatsApp Business API provider, which Meta calls a Solution Provider and the market calls a BSP, sells you access to the WhatsApp Business Platform and the software wrapped around it: an inbox, automation, integrations and support. It does not set the price of a message. Meta does. For the UAE, Meta charges a flat USD 0.0499 (AED 0.1832) per delivered marketing template and USD 0.0157 (AED 0.0576) per utility or authentication template at the first volume tier, taken from Meta's own live rate card on Thursday 3rd September 2026. Every fee a provider quotes you sits on top of that.

The short answer

• You want the cheapest official access and will configure it yourself: a flat-fee provider that passes Meta's rates through untouched. 360dialog publishes EUR 49 per number per month and states "no markup on Meta fees".
• You send low volume and want no monthly commitment: a per-message provider. Twilio publishes USD 0.005 per message with Meta's fees passed through, but it charges that USD 0.005 on inbound messages too, which Meta does not charge for at all.
• You want a full inbox, workflows and AI agents as a product: respond.io publishes USD 79, 159 and 279 a month, and states plainly that "WhatsApp fees are not included in any respond.io subscription".
• You want the conversations designed, built and run for you, in Arabic and English, by someone in your time zone: that is an agency engagement rather than a plan. It is the wrong answer if what you wanted was a self-serve tool on a monthly plan.
• You are a bank, insurer or other licensed financial institution: stop and take advice before you buy anything. Khaleej Times reported on 22 April 2026 that the UAE Central Bank had told licensed financial institutions to stop using messaging apps for customer data and transactions, with a 30 April 2026 compliance deadline. We could not locate that notice on centralbank.ae, so treat it as reported rather than verified, and get it checked.

What a WhatsApp Business API provider actually is

Three different words get used for the same thing and they are not interchangeable. Meta's own Business Messaging Policy uses "Solution Provider (formerly known as Business Service Provider)", which is where the market abbreviation BSP comes from. Vendors also describe themselves with other Meta partner labels. Those labels are not the same word Meta uses here, so the question worth asking is a plain one: will you be the Solution Provider on my WhatsApp Business Account, and will you say so in writing?

What you are buying is not the API. The API is Meta's. What a provider adds is the part Meta does not ship: a shared inbox, template management, automation, CRM and calendar integrations, reporting, and a human to shout at when a template gets rejected the day before a campaign. respond.io puts the commercial argument for its own category bluntly on its WhatsApp API 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."

Two structural facts worth knowing before you talk to anyone. First, Meta requires government entities to access the platform through a Solution Provider, which tells you the role is a real one in Meta's architecture, not a reseller invention. Second, Meta's own scaling documentation contains the phrase "Have your partner verify your business (if you were onboarded by one)", which is Meta acknowledging that some businesses arrive without a partner at all.

Direct to Meta, or through a provider?

The honest framing is not "direct is cheaper". Meta's per-message rate is the same either way, and it is charged on delivery of a template message regardless of who set the account up. The difference is what surrounds it, and one of those differences is measurable.

Business verification speed. Meta publishes two timings for the same step. Partner-led business verification: "Most requests are resolved within minutes, but some can take up to 24 hours." Meta business verification: "a verification decision can be made in as little as 10 minutes and as long as 14 working days." That gap is the single clearest argument for going through a provider, and it is Meta's own number rather than a vendor's.

What direct actually costs you. You take on template drafting and appeals, quality monitoring, the messaging-limit ladder, webhook plumbing, and building or buying an inbox. For a business sending a few hundred templates a month with a developer already on staff, that is a reasonable trade. For a clinic or a car dealership whose front desk is the bottleneck, it is a second job.

The trap in the middle. The riskiest option is neither of these. It is an unofficial gateway, one of the tools that automate the consumer WhatsApp app rather than the official platform. On the WhatsApp Business App, Meta's consumer-side rules apply, and they say: "Don't bulk message, auto-message, or auto-dial using WhatsApp." Appeals there are a single in-app "Request review" button and, in Meta's words, "If you don't see an option to request a review, it means the ban is final and can't be appealed."

That asymmetry is the opposite of what most buyers assume. On the official platform you get a warning naming the policy, a documented ladder of graduated blocks, an itemised violation in Business Support Home, and a 90-day appeal window. For any UAE business sending outbound at volume, the official API is the lower ban-risk surface, not the higher one.

What it really costs in the UAE

Since 1 July 2025 Meta has charged per delivered template message. Conversation-based pricing, the old model of 24-hour conversation windows with 1,000 free a month, is gone. Any provider still quoting you "per conversation" is either using its own unit or modelling a pricing system Meta retired more than a year ago.

Meta added AED as a billing currency on 1 April 2026 and publishes a separate AED rate card. Those AED figures are not a live currency conversion of the USD ones, so do not let anyone multiply a USD rate by an exchange rate for you. The number that appears on the invoice is Meta's published AED line.

Meta's UAE rate card, taken from Meta's own pricing system on 3 September 2026

Source: Meta's own public rate data for market AE, queried twice on Thursday 3rd September 2026 with identical results. Meta's marketing rate for the UAE rose on 1 October 2025, which is why so many vendor pages still show USD 0.0385.

Ignore the authentication-international rate. It applies only when a business sends more than 750,000 messages outside customer service windows in a rolling 30-day period and is based in a different country from the recipient. Meta states it directly: "you will not be billed the authentication-international rate since you are based in the same country as the user." A Dubai business sending OTPs to UAE numbers pays the ordinary UAE authentication rate of USD 0.0157 (AED 0.0576). We have deliberately kept the higher international rate off the table above, because it is not your rate. If a provider's calculator quotes you a materially higher authentication figure, it has not been configured for this market.

The volume tiers, which almost nobody publishes correctly

Utility and authentication share the same six rates, but they do not share the same thresholds. A calculator that applies one threshold set to both will be wrong.

Marketing has no tiers at all in the UAE. If someone offers you a volume discount on marketing messages, that discount is coming out of their margin, not Meta's, which is a perfectly good deal to accept as long as you know which one it is.

The provider layer, from each vendor's own published price

There are only two commercial models, and the most common error in provider comparisons is mixing them up.

Each figure is that vendor's own published price as fetched on Thursday 3rd September 2026. We have deliberately left out the widely repeated claims that Wati adds a flat 20% markup, that Gupshup adds about USD 0.001 and that Telnyx adds about USD 0.004. Those numbers appear only in third-party comparison blogs; the primary pages either could not be retrieved or no longer exist, so we will not publish them.

What that adds up to, as arithmetic rather than a quote

The figures below are our own calculation on the verified Meta rates above. Meta publishes no example bills. They cover Meta's charge only, before any provider fee.

Read the first row again, because it is the commercial fact that decides which model suits you. A clinic or a salon that only answers inbound enquiries currently pays Meta nothing. Its entire WhatsApp bill is the provider's platform fee. That is true today and, as the next section explains, it is scheduled to stop being true.

What changes on 1 October 2026, and why it hits the UAE service use case hardest

Meta has published that from 1 October 2026 two things that are free today become chargeable: service messages, and utility templates delivered inside the 24-hour customer service window. The 72-hour free entry point window, opened when someone messages you from a click-to-WhatsApp ad or a Facebook Page button and you reply within 24 hours, is stated as remaining free.

Meta says service messages will be charged at each market's existing utility and authentication rates, with no volume tier discounts, but it has not yet published a UAE service rate line. If that means the UAE utility rate, service messages would cost USD 0.0157 (AED 0.0576) each. Treat that as a planning assumption, not a quotable rate. On that assumption, and assuming three messages per inbound conversation, a service-led account paying Meta nothing today would pay roughly USD 23.55 at 500 customers a month, USD 94.20 at 2,000 and USD 471.00 at 10,000.

One more thing to say out loud, because no vendor page we read says it: Meta's own two pricing pages currently contradict each other on this. The main pricing documentation still describes non-template messages and in-window utility templates as free and does not mention the change. The dedicated upcoming-changes page describes the change. Both are Meta. Anyone quoting you a 2027 budget should be re-checking both pages, and so should we before this page's next update.

Separately, Meta has published that messages from its Meta Business Agent Platform became chargeable on 1 August 2026 at one global rate of USD 2.00 per one million tokens, with Meta estimating a typical message at 20,000 to 25,000 tokens, or roughly 4 to 5 US cents per message. That is a different product from the templates above, but it is the direction of travel: the free parts of this platform are being priced.

How long onboarding actually takes, and what holds it up

The step that varies is business verification, and Meta publishes both timings, quoted in the section above: minutes to 24 hours partner-led, ten minutes to fourteen working days through Meta. Ask a provider which route it will use for you before you sign, and ask for it in writing.

The step people forget is the messaging limit. A newly created business portfolio starts at 250 unique recipients per rolling 24 hours, outside open customer service windows. Not 1,000. The "Tier 1 equals 1,000 messages a day" line that circulates through vendor content is stale, and a provider still repeating it is telling you something about how current its playbook is. The limit is calculated at the business portfolio level and shared across every number in that portfolio, so adding numbers does not add capacity.

Getting from 250 to 2,000 has three routes, in Meta's words: verify your business, have your partner verify your business, or send delivered messages to unique recipients outside customer service windows using high-quality templates. Meta's own documents disagree on the volume for that third route. The developer documentation says "2,000 delivered messages ... within a 30-day moving period"; the Business Help Centre says "a minimum of 1,000 conversations over 30 consecutive days". We report both because Meta publishes both.

Above 2,000 the ladder runs 10,000, 100,000, then unlimited, and Meta moves you automatically when two things are true: you are sending high-quality messages across all numbers and templates, and in the last seven days you have used at least half of your current limit. When those are met, "your portfolio's limit increases by one level within 6 hours".

Reaching 2,000 also unlocks the practical stuff: up to 20 registered phone numbers instead of two, your business name displayed to customers in chats, and eligibility to apply for an official business account.

The green tick, and what it does not get you

The green tick, properly the official business account, is the badge every provider dangles and none of them controls. Here is what Meta's own documentation supports, and nothing beyond it: after scaling from 250 to 2,000, a business gains "eligibility to apply for a WhatsApp official business account". Eligibility to apply. Not the badge.

We could not source published approval criteria for the badge itself from Meta's primary documentation, so we are not going to invent any. What that means commercially is simple: a provider that promises you a green tick is promising something it cannot deliver. A provider that says "we will get you to the tier where you can apply, and we will file the application" is describing the real process.

Displaying your verified business name in chats, which is a separate thing, does come with the 2,000 tier, and for most customers that is the trust signal they actually notice.

Can a UAE provider give you WhatsApp voice calling?

Be careful here, because this is where international vendor pages fall over in this market.

WhatsApp messaging works normally in the UAE. WhatsApp voice and video calling does not. Both halves of that sentence matter. The TDRA publishes a list of VoIP applications permitted in the UAE and WhatsApp is not on it, in either the general or the telehealth category. The governing instrument is the Regulatory Policy on Voice over Internet Protocol, version 2.0, issued 30 December 2009 under Federal Law by Decree No. 3 of 2003, which says a licensee "will be entitled to block that VoIP Service" where it is provided by an unlicensed person. Gulf News and Khaleej Times both reported on 10 February 2026, when WhatsApp Web gained calling globally, that calling remained unavailable in the UAE pending TDRA approval.

Now the part that requires precision. Meta's documentation for the WhatsApp Business Calling API says business-initiated calling is available everywhere Cloud API is available "except the following countries: United States, Canada, Egypt, Vietnam, Nigeria". The UAE is not on that exclusion list. That is a statement about Meta's platform, not about UAE carrier-level blocking, and the two are not the same thing. The UAE restriction sits downstream of Meta entirely, with the licensed operators. We found no primary source confirming that a WhatsApp Business Calling API call connects to a UAE consumer, and none confirming it fails. It is genuinely unresolved in public sources, and we are not going to resolve it with a marketing claim.

The practical position: build your UAE customer messaging on WhatsApp, and build your customer voice on the ordinary licensed telephone network. If a provider's pricing calculator quotes you a UAE per-minute WhatsApp calling rate, ask it in writing whether business-initiated calling is enabled for UAE destinations on your account, and keep the answer.

If you leave: your number, your data and your prompts

This is the question buyers ask last and should ask first. We will be straight about the limits of what we can source.

What is documented. Your messaging limit belongs to the business portfolio, not to the provider. Your quality rating attaches to the phone number, is computed over a rolling seven days, and is driven by user feedback. And Meta's Business Solution Terms restrict what anyone may do with your conversation data: a provider must not "share, transfer, sell, license, or distribute Business Solution Data" to third parties outside the permitted service-provider relationship, and Meta says it "may terminate your account and revoke your access" for breaching that.

The same terms contain a clause that matters if your provider is an AI vendor: it may fine-tune a model on your conversation data only where that model is "for your exclusive use". Pooling client conversations to train a shared model is prohibited. That is a fair question to put to any provider selling you an AI assistant.

What we could not source. We could not find a published Meta procedure for moving a WhatsApp Business Account and its phone number between providers in the primary documentation we read for this page. So treat any provider's account of that process as its account, and put it in the contract instead of the sales call.

What operators actually do about it. On our own sales calls we have had a client ask for exit rights over the assistant's configuration before signing, treating the prompt copy as a transferable asset. It is the sharpest question anyone has asked us. We have also repeatedly heard the fear underneath it, in an operator's own words: "If I close the WhatsApp, I can't find the data, I have to open chat by chat." Any system that leaves no institutional record behind is a system you cannot leave.

Twelve questions to ask before you sign

• Which model are you? A flat platform fee with Meta's rates passed through, or a per-message fee on top of them. Both are legitimate. Vagueness is not.
• Do you bill inbound messages? Meta does not. Some providers do.
• Do you bill me at Meta's published rate card, or your own? One vendor's own pricing page says messages are billed "based on WATI rate card", which is not the same sentence as Meta's rate card.
• Show me the UAE line in AED. If they convert from USD with an exchange rate, the number will not match the invoice.
• What happens to my bill on 1 October 2026? A provider that has not read Meta's upcoming-changes page is going to surprise you.
• Whose Meta Business portfolio holds the WhatsApp Business Account and the number: mine or yours?
• Will you verify my business as a partner, or do I go through Meta business verification? Minutes versus up to fourteen working days.
• Which messaging-limit tier do I start on? The correct answer is 250 unique recipients per 24 hours.
• What is the escalation path to a human, and where does it sit in the conversation? Meta's policy requires "prompt, clear, and direct escalation paths" alongside automation in the 24-hour window.
• Walk me through your last template rejection. Meta says appeals must include a sample and are reviewed within 24 hours, and that all policy violations can be appealed within 90 days. A provider that has never appealed one has not run a real campaign.
• If I leave, what do I get back? Chat history, templates, the assistant's configuration, and in what format.
• What happened on 7 October 2025, and what is the starting messaging limit? This one is a test. If the answer involves "Flagged" or "Restricted" statuses, or "1,000 messages a day", their playbook is describing a system that no longer exists.

Safe, risky and grey: how accounts really get restricted

Meta does not restrict accounts for "using automation" or "sending too many messages". It acts on user feedback signals and on policy category violations. Everything else in circulation is either operator practice or out of date. Here is the line, drawn where Meta draws it.

Safe, in Meta's own words

• Automation inside the 24-hour window. "You may use automation when responding during the 24-hour window, but must also have available prompt, clear, and direct escalation paths", listing in-chat human transfer, phone, email, web support, in-store visits or a support form.
• A general opt-in. Meta states opt-in "can be general and not specifically for WhatsApp, as long as businesses comply with all local laws". It must clearly state that the person is opting in to receive communication, and name your business. Accepted methods include SMS, a website, an IVR flow, and paper.
• Running an AI assistant for your own business. The clause everyone misquotes is headed "AI Providers" and sits in the WhatsApp Business Solution Terms. It bars providers of AI technologies from using the platform to distribute their assistant where such technologies are "the primary (rather than incidental or ancillary) functionality being made available for use". It then says explicitly: "you may retain an AI Provider as your Third Party Service Provider". Meta did not ban AI chatbots on WhatsApp. It barred AI companies from using WhatsApp as a distribution channel for their own assistant. The widely repeated framing of "open-ended bots banned, structured bots fine" does not appear anywhere in the terms.

Risky, with the consequence named

• Sending a marketing message under a utility or authentication category. Meta names "template misclassifications" as an enforcement trigger in its own policy-enforcement documentation. It is also the most common deliberate cost-saving trick in this market, because the rate gap in the UAE is USD 0.0499 against USD 0.0157. The published ladder runs: a warning naming the policy, then a 1 or 3 day block on sending templates, then a 5, 7 or 30 day block on sending anything, then an indefinite account lock removable only by appeal, then permanent removal from the platform.
• Letting a template's quality slide. Templates carry their own rating separate from the number's. At the lowest rating a template is paused for 3 hours, then 6 hours on the second instance, then disabled on the third. Low read rate alone can degrade a template. No blocks required.
• Regulated verticals. Meta's prohibited list includes medical and healthcare products, dating services, multi-level marketing, alcohol and tobacco, real money gambling, and payday and peer-to-peer lending. The sentence that catches UAE businesses out is Meta's own: "These prohibitions apply irrespective of the global or local licenses, registrations, or other approvals your business may hold." The country-gated exception lists for gambling, over-the-counter drugs and alcohol do not include the UAE.
• Assuming only blocks count. Message quality is "determined by a combination of user feedback signals like blocks, reports, mutes, archives, and reasons users provide when they block you". Archives and mutes count against you, which is stricter than the common advice. Meta also names your bot's functionality and how quickly enquiries are resolved as inputs to the rating, which is a good argument for a well-built assistant rather than against one.
• Ignoring the invisible ceilings. Meta caps how many marketing templates any one user receives, based partly on their recent read rate. The UAE is not excluded from those per-user limits. Hitting one returns error 131049 and delivery to that user may be unavailable for up to 24 hours. Separately, a user can switch off marketing from your business entirely through WhatsApp's "Offers and announcements" setting, which the API honours with error 131050 whether or not your CRM knows about it.

Grey: what operators actually do, labelled as practice not policy

These are things we see UAE businesses do. None of them is Meta policy, and we are not presenting them as rules.

• Warming a new number up on a ramp. No Meta document prescribes a warm-up schedule. The ramps circulating in vendor content, typically 10 to 20 messages a day in week one rising to 80 to 100 by week three, are not sourced to Meta by the pages that publish them. The only ramps Meta actually documents are the messaging-limit ladder and template pacing.
• Sending in staggered batches on a green-rated number. One pattern we hear repeatedly on sales calls is batches of around 500, staggered, on a number rated high quality, explicitly because operators find Meta's enforcement to be a black box. Rational, undocumented, and not a guarantee of anything.
• Splitting sending across several numbers to spread risk. This isolates number-level quality, but it does not buy you volume: messaging limits are portfolio-wide and shared. Anyone selling extra numbers as extra capacity is wrong.
• Suppressing unengaged contacts after the first no-reply. Sensible against read-rate-driven template quality and per-user marketing limits. Meta publishes no threshold, so nobody can tell you the right number.

And the honest answer to "why did my blast only half send?" Usually template pacing, not a ban. Meta holds messages on new or non-green templates until it has a quality signal, then either scales the send to the full audience or drops the held messages with a failed status and error code 132015. Its stated goal is that even paced campaigns deliver within an hour at the 99th percentile.

The UAE layer your provider should be able to discuss

Cabinet Resolution No. 56 of 2024, in force since 27 August 2024, defines telemarketing to include "marketing text messages and marketing messages through social media applications". That definition reaches WhatsApp marketing. It applies to companies licensed in the UAE including those in free zones, and it requires prior approval to conduct phone marketing from the competent authority, a dedicated channel for consumers who want marketing information, screening against the Do Not Call Registry, and record-keeping.

Report the tension rather than papering over it, because this is where vendor content overreaches: the definition in that resolution sweeps in social-media messages, but the operative obligations are drafted in call language, including recording marketing phone calls, identifying yourself at the start of the call, and a 9am to 6pm window. How those map onto a WhatsApp template message is not specified in the text. A cautious business treats the opt-in channel and the permitted hours as applying. Nobody should tell you the law definitively imposes a 9am to 6pm window on WhatsApp messages, because the text does not say that.

If you are a clinic, one more correction worth having. HIPAA is United States law and does not apply in the UAE; the instrument that governs your patient data is Federal Law No. 2 of 2019 on the use of ICT in health fields. Its headline penalty of AED 500,000 to 700,000 attaches specifically to Article 13, the prohibition on storing, processing or transferring UAE health data outside the country. It is not a general fine for sending a patient a message. Meta's own Business Messaging Policy also tells businesses not to use WhatsApp "for telemedicine or to send or request any health related information" where the applicable regulation demands heightened handling. Appointment logistics and clinical content are materially different categories, and a provider selling to Dubai clinics should be able to explain the difference without being prompted.

Frequently asked questions

What is a WhatsApp Business API provider?

It is a company that gives you access to the WhatsApp Business Platform and supplies the software Meta does not: an inbox, template management, automation, integrations and support. Meta's own term is Solution Provider, formerly Business Service Provider, which is where the market abbreviation BSP comes from. Other Meta partner labels are not the same thing, so ask a candidate in writing whether it will be the Solution Provider on your account.

How much does the WhatsApp Business API cost in the UAE?

Two layers. Meta charges per delivered template message: in the UAE that is USD 0.0499 (AED 0.1832) for marketing, and USD 0.0157 (AED 0.0576) for utility or authentication at the first volume tier, checked against Meta's own rate card on 3 September 2026. Marketing has no volume discount in the UAE. On top of that a provider charges either a flat platform fee, such as 360dialog's EUR 49 per number per month with no markup on Meta's fees, or a per-message fee, such as Twilio's USD 0.005 per message, which Twilio applies to inbound messages as well as outbound.

Can I use the WhatsApp Business API without a provider?

Meta's own scaling documentation refers to businesses that were not onboarded by a partner, so the platform contemplates both routes. The measurable difference is verification speed: Meta states that partner-led business verification is usually resolved within minutes and at most 24 hours, while Meta business verification takes "as little as 10 minutes and as long as 14 working days". Going direct also means you own template drafting, appeals, quality monitoring and building or buying an inbox. What you should not do is use an unofficial gateway that automates the consumer app, because that is the surface where a ban can be final and unappealable.

How many messages can I send on day one?

A newly created business portfolio can start conversations with 250 unique WhatsApp users per rolling 24 hours, outside open customer service windows. Replies to customer-initiated conversations are unlimited. The limit is set at the portfolio level and shared by every number in it, so registering more numbers does not increase it. The ladder above 250 runs 2,000, then 10,000, 100,000 and unlimited. Anyone telling you the starting tier is 1,000 messages a day is quoting a stale figure.

How long does WhatsApp Business API approval take in the UAE?

The variable step is business verification, and Meta publishes both timings: minutes to 24 hours if a partner verifies you, ten minutes to fourteen working days through Meta directly. After that, moving from the 250 tier to 2,000 takes either verification or sustained high-quality sending, and Meta's own documents give two different volumes for that path: the developer docs say 2,000 delivered messages within a rolling 30 days, the Business Help Centre says a minimum of 1,000 conversations over 30 consecutive days.

Does the WhatsApp Business API support voice calls in the UAE?

Treat it as unavailable and do not build on it. WhatsApp messaging works normally in the UAE; WhatsApp voice and video calling is restricted, and WhatsApp does not appear on the TDRA's published list of permitted VoIP applications. Meta's Business Calling API documentation excludes only the United States, Canada, Egypt, Vietnam and Nigeria, which is a statement about Meta's platform rather than about carrier-level blocking in the UAE. No primary source we found confirms that such a call connects to a UAE consumer, and none confirms it fails. The honest position is that it is unresolved, so a UAE business should build its voice strategy on the licensed telephone network.

Will using an AI chatbot get my WhatsApp account banned?

No. Meta explicitly permits automation when responding inside the 24-hour customer service window, provided you also offer prompt, clear and direct escalation paths to a human. The clause people are thinking of is headed "AI Providers" in the WhatsApp Business Solution Terms, and it bars providers of AI technologies from using WhatsApp to distribute their assistant where the AI is the primary functionality being offered. The same clause states that a business "may retain an AI Provider as your Third Party Service Provider". Meta also names bot functionality and resolution speed as inputs to your number's quality rating, so a well-built assistant helps the score rather than harming it.

How do I get the green tick on WhatsApp?

The green tick is the official business account badge, and no provider controls it. What Meta's documentation supports is that scaling from the 250 messaging tier to the 2,000 tier gives you eligibility to apply for an official business account, along with up to 20 registered numbers and your business name displayed to customers in chats. We could not source published approval criteria for the badge itself, so any provider promising to deliver it is promising something outside its control.

What happens to my number if I switch providers?

Three things are documented and one is not. Your messaging limit belongs to your business portfolio rather than to the provider; your quality rating attaches to the phone number and is recalculated over a rolling seven days; and Meta's Business Solution Terms bar a provider from sharing, selling or distributing your conversation data outside the permitted service-provider relationship, and bar it from training a shared AI model on that data. What we could not find in Meta's primary documentation is a published procedure for moving an account and number between providers. So put the exit terms in the contract: who holds the Meta Business portfolio, what you get back, and in what format.

What we could not verify

Sources

• Meta, WhatsApp Business Platform pricing and updates to pricing, retrieved Thursday 3rd September 2026
• Meta's public rate calculator and the pricing data behind it, market AE, queried twice on Thursday 3rd September 2026
• Meta, upcoming changes to non-template message pricing (the 1 October 2026 change)
• Meta, authentication-international rates
• WhatsApp Business Messaging Policy and WhatsApp Business Solution Terms (last modified 6 March 2026, the AI Providers clause)
• Meta, WhatsApp Business Platform policy and spam enforcement
• Meta, messaging limits and phone number quality rating (which records that Flagged and Restricted were discontinued on 7 October 2025)
• Meta, template pausing, template pacing and per-user marketing limits
• Meta, getting opt-in
• Meta, WhatsApp Business Calling API
• Twilio WhatsApp pricing, 360dialog pricing, respond.io pricing, Wati pricing and AiSensy pricing, each retrieved Thursday 3rd September 2026
• respond.io, WhatsApp API for business, quoted for its own claim about BSPs
• TDRA internet guidelines and permitted VoIP applications, VoIP Regulatory Policy version 2.0 (30 December 2009) and TDRA FAQs
• Gulf News, 10 February 2026 and Khaleej Times, 10 February 2026, on WhatsApp calling in the UAE
• Khaleej Times, 22 April 2026, on the reported Central Bank position for licensed financial institutions
• Cabinet Resolution No. 56 of 2024 on telemarketing (in force 27 August 2024) and Federal Law No. 2 of 2019 on the use of ICT in health fields, read from mirrors of the official English translations; the official UAE legislation portal blocks automated retrieval