WhatsApp Business API in the UAE: access, templates, pricing, rules and integration
By Dr. Hani Elimam Manager & CEO, SmartTech Studio
In the UAE, customers already expect to reach a business on WhatsApp. Most companies start with the free WhatsApp Business app on one phone, and for a while that works. Then the problems arrive together: three staff members share one handset, nobody knows who answered which customer, order confirmations are typed by hand, and the chat history that should sit in the CRM lives in someone’s pocket.
The WhatsApp Business API (Meta now calls it the WhatsApp Business Platform, and its hosted version the Cloud API) is how you move WhatsApp out of the phone and into your systems. This guide explains what it is, how a UAE business gets access, how message templates and pricing work, which rules apply to marketing on WhatsApp here, and how to connect it to a CRM, ERP, POS or website without the usual mistakes.
SmartTech Studio builds these integrations from Abu Dhabi as part of our custom software work. If you are thinking about putting an AI assistant on the channel, read this first and then our guide to AI agents for customer service; the platform rules below decide what such an agent is allowed to do. Platform terms and prices change, so we point to Meta’s own pages rather than freezing figures that will be out of date next quarter. The policy points were checked in November 2026.
WhatsApp Business app or the API: what is the difference?
The WhatsApp Business app is a phone app. It gives you a business profile, quick replies, labels, a catalogue and an away message, and it is free. It is built for one person or a very small team answering by hand, and it can be linked to a handful of extra devices. It does not connect to your software in any reliable way.
The API has no app at all. It is an interface your systems call: your CRM sends an order confirmation, your website receives a customer’s reply, your booking system sends a reminder. People answer through a shared inbox (one you buy or one built for you) where many agents can work the same number, conversations are assigned and every message is stored against the customer record.
The practical test is simple. If WhatsApp is a conversation one person has with customers, the app is enough. If WhatsApp has become a process (orders, bookings, delivery updates, payment links, support tickets with more than two people answering), you need the API.
| WhatsApp Business app | WhatsApp Business API (Cloud API) | |
|---|---|---|
| Who answers | One person, a few linked devices | Many agents on one number, through an inbox |
| Connects to CRM, ERP, POS | No | Yes, through the API and webhooks |
| Messages you start | Typed by hand | Pre-approved templates, sent automatically |
| Cost | Free app | Per delivered template under Meta’s rate card; service replies free |
| Setup | Minutes | Business verification, number registration, templates, integration |
How a UAE business gets access to the WhatsApp Business API
There are two routes. You can use Meta’s Cloud API directly, which Meta hosts and documents on its developer site, and have your own developers or a studio build the integration. Or you can go through a Business Solution Provider (BSP): a company Meta has approved to resell access, usually bundled with an inbox, a chatbot builder and campaign tools for a monthly fee on top of Meta’s charges. Both use the same underlying platform. The choice is about who owns the integration, not about which WhatsApp you get.
Either way, the steps are much the same. First, a Meta business portfolio (formerly Business Manager) in your company’s legal name. Second, business verification: Meta checks that the business is real, typically against your trade licence and a website or domain that matches it. Use the exact licensed name, and make sure the website shows the same name and contact details, because mismatches are the most common reason verification stalls.
Third, a phone number. It must be able to receive a verification code by SMS or voice call, and it must not be active on the WhatsApp or WhatsApp Business app at the same time; a number already on the app has to be migrated or deleted from it first. Many businesses use a landline or a new mobile number so that the main line stays untouched during testing.
Fourth, a display name, which Meta reviews against its guidelines; it should match your brand and your website. Fifth, the templates you plan to send, submitted for approval. After that, your number starts with a limit on how many new customers it can message in a day, and the limit rises as you send volume with good quality ratings. Blocks and reports from customers push your quality down and can freeze a number, so the way you collect opt-in matters from day one.
Templates and the 24-hour customer service window
WhatsApp separates messages the customer starts from messages you start. When a customer messages you, a 24-hour customer service window opens. Inside it you can reply freely with any text, images, documents or buttons, without a template. Each new message from the customer restarts the 24 hours.
Outside that window, the only thing you can send is a pre-approved template: a fixed message with placeholders for the customer’s name, order number, date or link. Meta sorts templates into three categories. Marketing covers promotions, offers, new products and anything meant to sell. Utility covers messages tied to something the customer already did: an order confirmation, a delivery update, an appointment reminder, a payment receipt. Authentication covers one-time passwords.
Categorise honestly. Meta reviews every template and can move one into a different category, and a “delivery update” that ends with a discount code is marketing, whatever you label it. Write templates in both Arabic and English as separate language versions of the same template, so the system can send each customer the version that matches the language they use with you.
A good starting set for most businesses is small: an order or booking confirmation, a reminder, a status update, a payment link, a “we tried to reach you” follow-up, and a one-time password if you have logins. Marketing templates come later, once opt-in is in place.
What it costs: Meta’s per-message pricing
Since 1 July 2025, Meta charges for the WhatsApp Business Platform per delivered template message, replacing the older model that charged per 24-hour conversation. The price depends on the template category and on the country code of the recipient’s number, so a marketing template to a UAE number costs a different amount from a utility template to the same number, and both differ from a message to an Omani or Egyptian number.
Two things are free under the current model. Service messages (your free-form replies inside the 24-hour customer service window) are not charged. Utility templates sent while a customer service window is open are also free. That rewards a design in which confirmations and updates go out while the customer is already talking to you, and it makes marketing templates the main cost line.
Meta also offers volume tiers for utility and authentication templates, and conversations that start from a click-to-WhatsApp ad or a Facebook page call-to-action can open a longer free window. Rates and tiers are published on Meta’s pricing page and rate card, and they are revised; check the current card for the UAE before you budget, and recheck it each quarter.
On top of Meta’s charges, budget for the layer around it: a BSP or inbox subscription if you buy one, or the build and hosting of your own integration. For a custom integration tied into your CRM or ERP, our custom software work starts from AED 25,000, excluding VAT, and is quoted per scope; a straightforward inbox with a few templates often does not need custom work at all.
Opt-in, opt-out and the UAE rules on marketing messages
WhatsApp’s Business Messaging Policy requires opt-in before you message someone first: the customer must have agreed to receive messages from your business on WhatsApp, and the request must name your business. A phone number typed into an invoice or a purchased list is not opt-in. Collect it where the customer can see what they are agreeing to (a checkbox on the website form, a line at checkout, a reply to a QR code at the counter), and store when and where it was given.
Honour opt-outs at once. Give every marketing template a clear way to stop, such as a “Stop” button, and make sure a stop request reaches every system that sends messages, not only the inbox. A customer who opts out of offers can still receive utility messages about an order they placed.
UAE law points in the same direction. The Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) treats phone numbers and chat content as personal data, expects a lawful basis such as consent for processing it, and gives people the right to object to their data being used for direct marketing. Keep chat logs only as long as you need them, restrict who can export them, and know where your provider stores them. Our guide to data protection and breach prevention in the UAE covers the controls in more detail.
Separately, Cabinet Resolution No. 56 of 2024 on regulating telemarketing, in force since mid-2024, sets strict rules for marketing calls: calls only between 9 am and 6 pm, no calls to numbers on the Do Not Call Register, no repeat calls after a customer declines, and fines that can reach AED 150,000. It is written around marketing by phone, and legal commentary differs on how far it reaches into messaging apps. Do not build a WhatsApp campaign that relies on the gap: send marketing only to people who opted in, inside reasonable hours, and ask your lawyer if a campaign targets people who have not dealt with you before.
AI on WhatsApp: what Meta’s 2026 policy allows
In October 2025 Meta changed the WhatsApp Business Solution terms, effective 15 January 2026, to bar providers of general-purpose AI assistants and chatbots from using the Business API when that AI is the main thing they offer. That is why several consumer AI assistants left WhatsApp in early 2026.
The change is aimed at AI companies distributing their assistant through WhatsApp, not at businesses using AI to serve their own customers. A clinic bot that books appointments, a retailer’s assistant that answers questions about stock and delivery, or a support flow that drafts replies for a human agent remain within the rules, because the AI supports the business’s own service rather than being the product.
Design it accordingly. Keep the assistant inside your business: your products, your policies, your bookings. Give it a clear hand-off to a person, log what it says, and do not let it promise refunds, prices or medical advice that a person has not approved. How to scope, test and supervise such an assistant is covered in our guide to AI agents for customer service in the UAE.
Connecting WhatsApp to your CRM, ERP, POS and website
The value of the API is not WhatsApp itself; it is what WhatsApp is connected to. The integration has two directions. Outbound, your systems call the API to send a template when something happens: an order is paid, a booking is made, a shipment leaves, an invoice is overdue. Inbound, WhatsApp sends every customer message and every delivery and read status to a webhook on your server, which files it against the right customer and routes it to the right person.
CRM. Every conversation should land on the customer’s record, matched by phone number, with the agent, the outcome and any follow-up task. Leads from click-to-WhatsApp ads should arrive as leads with their source, so marketing can see which campaigns produce customers rather than chats. If you are still choosing the CRM, our comparison of custom and off-the-shelf CRMs explains which ones handle WhatsApp well.
ERP and POS. Order confirmations, delivery updates, payment links and digital receipts are the messages customers value most, and they come from the ERP or the till. The same pattern we describe for connecting a POS to a CRM applies: one customer ID across systems, events rather than nightly exports, and a log of every message sent.
Website. A WhatsApp button on the site should open a chat with a prefilled message that says which page the visitor came from, and the form on the same page should offer WhatsApp as the reply channel with an explicit opt-in. If your site gets visitors but few enquiries, our guide to sites that do not produce leads covers the wider fixes.
Common mistakes we see
Moving the main number without a plan. Registering your best-known number on the API removes it from the app. Test on a second number, prepare the templates and the inbox, then migrate on a quiet day and tell staff in advance.
Broadcasting to the whole contact list. Sending marketing templates to people who never opted in is the fastest way to collect blocks, lose quality rating and have your sending limit cut. It also invites complaints under the rules above.
Labelling marketing as utility. Meta reviews and recategorises templates; trying to save money by mislabelling only delays approval.
An inbox nobody owns. Automated messages invite replies. If nobody answers within the hours you advertise, the channel damages the brand faster than having no WhatsApp at all. Set working hours, an away template and a clear owner for each queue.
Data in one more silo. A BSP inbox that does not write back to your CRM recreates the phone problem in the cloud. Ask before you sign how conversations, contacts and opt-ins get into your own systems, and how you take them with you if you leave.
Arabic as an afterthought. Templates, buttons, the chatbot and the inbox all need proper Arabic, written for the reader rather than machine-translated, and the right-to-left layout must hold in the agent screens too.
Buy an inbox or build the integration?
For many businesses a BSP inbox is the right answer: a few agents, a few templates, a simple chatbot menu, and a CRM the provider already connects to. It is quick to start, and you should not pay for custom work you do not need.
A custom integration on the Cloud API makes sense when WhatsApp has to work with systems a packaged tool does not know: your own ERP, a POS, a booking engine, a delivery platform, or a CRM with your own fields and rules. It also makes sense when you want the conversation data in your own database rather than a provider’s, or when monthly per-agent fees have outgrown the cost of owning the integration.
Our approach is to start with the messages that matter (the confirmations and updates customers actually want), make sure each one is triggered by a real event in your system, then add the inbox, routing and marketing once the basics run cleanly. If you want to see whether your case needs a build or just a subscription, tell us what WhatsApp has to do for you and we will say which, even when the answer is not us. For campaigns on top of it, our digital marketing team can plan the opt-in and the offers.
FAQ
Can I use my existing WhatsApp number for the API?
Yes, but it cannot stay on the WhatsApp or WhatsApp Business app at the same time. The number has to be migrated or removed from the app, and it must be able to receive a verification code by SMS or call. Many businesses test on a second number first and move the main one once templates and the inbox are ready.
How much does the WhatsApp Business API cost in the UAE?
Since 1 July 2025 Meta charges per delivered template message, priced by category (marketing, utility, authentication) and by the recipient’s country. Replies inside the 24-hour customer service window are free, and so are utility templates sent while that window is open. Check Meta’s current rate card, then add any BSP subscription or integration cost.
Do I need a BSP, or can I connect directly?
You can connect directly to Meta’s Cloud API if you have developers to build and run the integration. A BSP adds a ready inbox, chatbot builder and support for a monthly fee. Both run on the same platform; the question is whether a packaged tool fits your systems or you need the integration built around them.
Can I send WhatsApp marketing messages to any customer number I have?
No. WhatsApp requires opt-in naming your business before you message someone first, and the UAE’s data protection law gives people the right to object to direct marketing. Send marketing templates only to customers who agreed, give every message a way to stop, and record when and where consent was given.
Is an AI chatbot on WhatsApp still allowed after January 2026?
For your own customer service, yes. Meta’s terms, effective 15 January 2026, bar general-purpose AI assistants whose main purpose is the AI itself. A bot that books appointments, answers questions about your products or helps your agents remains allowed, provided it stays within your business and hands off to a person.
How long does a WhatsApp API integration take?
Business verification and template approval depend on Meta and on how clean your documents are, so start them first. A packaged inbox can then be live quickly. A custom integration with your CRM, ERP or POS takes longer and depends on how many events and systems are involved; we give a dated plan with the written quote.