TL;DR: When choosing a WhatsApp Business API provider in the UAE, what matters is whether the account and number are in your name, whether Meta's charges are itemised separately from the provider's fee, whether the API and webhooks are complete enough to run an AI assistant, whether the inbox lets a person take over cleanly, where your messages are stored, and how you would leave. The brand of the provider matters less than the answers to those questions.
What is a WhatsApp Business API provider?
A WhatsApp Business API provider, or Business Solution Provider (BSP), is a company that connects your business to the WhatsApp Business Platform. It typically handles the onboarding and verification of your WhatsApp Business Account, provides an inbox where your team reads and replies, manages message templates, exposes an API so your own software can send and receive messages, and passes Meta's messaging charges through with its own fee added. The alternative is connecting directly to Meta's Cloud API, where your engineering team or agency does the provider's work and you pay Meta's charges alone.
This is written for the owner or operations lead of a UAE business that has decided it needs the Business API, usually because it wants an AI assistant or automation on the number customers already use, and is now facing a list of providers that all look the same. If you have not yet decided between the app and the API, read the Business API versus the app first.
Do you need a BSP at all?
Not always. Meta's Cloud API lets a business connect directly, and an engineering team can build the integration, host it, and use or build an inbox. The trade-off is straightforward: going direct means no provider markup and full control, in return for having someone competent to run the integration and keep up with Meta's changes. Using a BSP means paying for that someone, and for their inbox and team tools, in return for not having to run it yourself.
A business with an engineering partner already building its AI assistant often does not need a BSP's platform, because the assistant is the platform. A business that wants an inbox, agents, tags and reports without any engineering usually does. Many businesses end up with a hybrid: a direct or lightly-wrapped API connection for the assistant, and a simple inbox for the humans.
Who owns the account and the number?
This is the question that determines whether every other question matters. Your WhatsApp Business Account should be created inside your company's Meta Business account, with your staff as administrators, and the number should be one your company controls. The provider is granted access; it does not own.
Some providers, to make onboarding easier, create the account under their own business. It works until you want to leave, at which point the number your customers have saved, the templates you had approved and your verification status are all the provider's. Ask before setup: whose Meta Business account will this live in, and who will be the administrators? If the answer is not "yours", stop.
What does the pricing consist of?
WhatsApp Business API costs have two layers. The first is Meta's own messaging charges, which depend on the category of conversation (marketing, utility, authentication, service) and the country of the customer. The second is the provider's fee: a platform charge, per-seat charges for the inbox, sometimes a per-message markup on top of Meta's rates, setup fees and support tiers.
What matters is that the two layers are itemised separately so you can see what is Meta's and what is the provider's, and that you understand what happens when volume grows. A provider that quotes a single blended figure per message is hiding its margin inside Meta's rate. Meta's pricing model, conversation categories and free tiers change; check the current documentation rather than relying on a provider's summary or on this article.
Does the provider support what an AI assistant needs?
An AI assistant is software that receives every incoming message, decides what to do, and sends replies, media, buttons and templates. For that it needs the provider to expose the platform fully, not through a limited "chatbot builder". The checklist:
- Webhooks that deliver every incoming message, including media and location, to your system promptly and reliably, with retries when your system is down.
- A sending API that covers text, images, documents, audio, interactive buttons and lists, and approved templates, with no artificial limits below Meta's own.
- Template management through the API, so new templates in Arabic and English can be submitted and tracked without a support ticket.
- Message status (sent, delivered, read, failed) back to your system, so the assistant knows what happened.
- Human takeover: a way for a person to step into a conversation the assistant was handling, and for the assistant to know it has been taken over.
- Conversation history export, so your data is not trapped in the provider's inbox.
Some providers offer a visual bot builder in place of an API. That is fine for a menu, and limiting for an assistant that reads documents, looks up a CRM and hands off to a person with context. Ask whether you get the raw API, and ask an engineer to look at the documentation before you sign.
What about the inbox and team features?
If people will work in the provider's inbox, the questions are ordinary: can conversations be assigned and tagged, can teams and branches be separated, can Arabic and English be handled without the interface breaking, is there a mobile app for staff, can a manager see what was said, and can conversations be searched and exported. The best test is to give the inbox to the person who will use it most for an afternoon.
Where are your messages stored?
Every message passes through the provider's systems and is usually stored there. Ask where, in which country or region, for how long, who at the provider can read it, and whether it is used for anything beyond delivering your service. For healthcare, finance, legal or government-facing businesses, ask whether an in-region option exists. Check the current UAE data protection guidance for your sector alongside whatever the provider says, and read our note on data residency for the questions that apply to the AI side as well.
How would you leave?
Ask this before signing. If the account is in your name, migrating the number to a different provider or to a direct connection is possible, but the process has steps, conditions and timing that change. Ask the provider to describe exactly what leaving involves, what happens to approved templates and conversation history, and whether any fee applies. Check Meta's current migration guidance. A provider that answers this clearly is one you can trust with the rest.
The questions on one page
| Question | Why it matters | Good answer sounds like |
|---|---|---|
| Whose Meta Business account will the WABA live in? | Decides whether you can ever leave | Yours, with your admins |
| Are Meta's charges and your fee itemised separately? | Shows the real margin and how it scales | Two lines, with volume behaviour explained |
| Do we get the full API and webhooks? | Determines what an assistant can do | Yes, with documentation an engineer can read |
| How does a human take over from the assistant? | Handoff is where trust is kept | A clear mechanism, visible to both sides |
| Where are messages stored and for how long? | Compliance and confidentiality | Named region, retention you set, export on request |
| Can templates be managed through the API in both languages? | Speed of change | Yes, without tickets |
| How do we leave? | Everything else depends on it | A described process, no surprises |
What to ask a vendor
Bring the table above and ask each question in writing. Add: who onboards and verifies the business, and what they need from you; what the support process is when messages stop arriving; and whether the provider has UAE clients in your sector who can describe leaving as well as joining. Do not accept "it's all included" as an answer to the pricing question, or "it's secure" as an answer to the storage question.
How Soluvide handles this
We are an engineering studio, not a BSP, and we do not resell any provider. When we build a WhatsApp assistant for a client, the WhatsApp Business Account is created in the client's Meta Business account from the first day, with the client's staff as administrators. We connect the assistant either directly to Meta's Cloud API or through a provider the client chooses, based on whether the client needs an inbox and team tools beyond what the assistant provides. Meta's charges and any provider fee are passed through and itemised; our own work is a fixed price agreed after a free scoping call. The code, the templates, the prompts and the conversation data are the client's, and leaving us does not involve losing the number.
What we build on top of the API is described on the AI chatbots and agents page.
If you are comparing providers and want an engineer's read on the documentation before you sign, message us on WhatsApp and we will tell you what we see.
Questions
Frequently asked.
A company approved by Meta to help businesses get onto the WhatsApp Business Platform. A BSP typically handles onboarding and verification, provides an inbox and template management, passes Meta's messaging charges through with its own fee on top, and exposes an API so software such as an AI assistant can send and receive messages. Some businesses instead connect directly to Meta's Cloud API without a BSP.
Where this applies
What we build for this.
- SolutionWhatsApp lead qualificationLeads you paid for go cold because nobody answered at 9pm.
- ServiceAI chatbots & agentsWhatsApp, web, Instagram and voice — English and Arabic.
- SolutionArabic & English support agentsYour chatbot falls apart the moment a customer writes in Gulf Arabic.
- ServiceAI integration & consultingFind where AI pays off, then wire it into what you already run.