Every store we build in Dubai asks for the same thing eventually. Not a chat bubble in the corner, which is free and mostly ignored, but the real thing: order confirmations that arrive on WhatsApp, a COD verification message before the courier is dispatched, a delivery update the customer does not have to chase. That is the WhatsApp Business API, and it is the one integration where clients consistently guess the running cost wrong in both directions.
The confusion is not really their fault. Meta changed how it bills in the middle of 2025 and a lot of the advice in this market never caught up. So before the platform comparison and the feature list, here is the part that actually shows up on a card statement.
Why do WhatsApp quotes vary so much?
Because a WhatsApp quote is three separate bills stapled together and most quotes only show one of them.
| Layer | Paid to | Shape of the cost |
|---|---|---|
| Message charges | Meta | Per template message delivered, priced by category and by where the customer is |
| Platform fee | Your BSP, such as WATI, Respond.io or BotSpace | Monthly subscription, usually banded by contacts or seats |
| Build and integration | Your agency | One-off. Verification, the connection to your store and CRM, the flows themselves |
A quote that gives you a single monthly figure has either buried the message charges in a markup or left them out entirely. Both happen. The first question to ask any provider is whether the rate they quoted includes Meta's fee or sits on top of it.
What changed in Meta's pricing?
Until 1 July 2025, Meta charged for a 24 hour conversation window. You opened a window, sent what you liked inside it, and paid once. Utility templates moved to the new model earlier, on 1 April 2025.
Now it is per template message delivered. Every template that lands is a line on the bill.
For a store this is mostly good news and slightly bad news. Good, because answering a customer who messaged you first is close to free. Slightly bad, because a broadcast to ten thousand contacts is now ten thousand billable events rather than ten thousand windows, and the arithmetic no longer forgives a lazy campaign.
What does it actually cost per message in the UAE?
Meta prices by message category, and the categories are not interchangeable.
| Category | Rate per message (UAE) | In dirhams | What it covers |
|---|---|---|---|
| Marketing | $0.0499 | about AED 0.183 | Promotions, abandoned cart nudges, new arrivals, anything selling |
| Utility | $0.0157 | about AED 0.058 | Order confirmed, payment received, shipped, out for delivery |
| Authentication | $0.0157 | about AED 0.058 | One-time passcodes and login verification |
| Service | Free | Free | Your replies inside a window the customer opened |
Two things follow from that table and both matter more than the numbers themselves.
The first is that a marketing template costs roughly three times a utility one. A store that pushes its entire lifecycle through marketing templates because nobody categorised them properly is paying three times over for messages that would have qualified as utility.
The second is that rates fall at volume. Utility and authentication drop as you send more, to roughly $0.0149 above 300,000 messages a month in the UAE and lower again far beyond that. If you are sending a few thousand a month, ignore this. It is not your lever.
Does a UAE number make it cheaper?
No, and this is the misconception that costs people real money when they plan for it.
Meta bills on where the recipient is, not where your number is registered. A Dubai-registered number messaging a customer in Germany is billed at the German rate, which is several times the UAE one. If you ship internationally, your message bill tracks your customer geography, not your trade licence.
The practical version: model your messaging cost against your actual order mix by country, not against the UAE row alone.
What does the platform layer cost?
This is the monthly subscription for the software that sits between your store and Meta, and providers handle Meta's fee very differently.
- BotSpace passes Meta's per-message cost straight through with no markup and makes its money on the subscription. Tiers run from a free single-seat plan up to around $3,500 a month at a million contacts.
- WATI lists Growth at roughly $119 a month billed annually, capped at three users, and Pro at about $179 a month annually for five, with additional seats around $49 each.
- Twilio adds a flat $0.005 per message on top of Meta's rate, which is predictable but is a markup all the same.
Across the market, markups run from nothing to somewhere around 15 to 20 percent, or a flat per-message fee instead. For most UAE SMEs the platform line lands between AED 150 and 600 a month. It is rarely the number that decides anything.
What does the build cost?
The one-off. Meta Business verification, connecting the platform to your store and CRM, designing the templates, getting them approved, and wiring the events that trigger them.
| Scope | Typical range | What it looks like |
|---|---|---|
| Simple | AED 2,600 to 5,200 | Order and shipping notifications from the store, basic auto-replies, one inbox |
| Moderate | AED 5,200 to 13,000 | COD verification, abandoned cart flow, qualification and routing, CRM sync both ways |
| Complex | AED 13,000+ | AI handling of first-line questions, multiple departments, custom logic against your own systems |
The variable is almost never WhatsApp. It is what WhatsApp has to talk to. A Shopify store firing standard order events is a small job. A WooCommerce build with a custom COD flow, a delivery partner API and an ERP that owns stock is a different project, and the same drivers apply that move any website quote in Dubai.
What a realistic store setup costs
A UAE store doing a few hundred orders a month, mostly transactional messaging with an occasional campaign:
- Platform subscription: AED 150 to 600 a month
- Meta messages: a few hundred dirhams a month if it is utility-led, considerably more the moment marketing broadcasts become the habit
- Build: AED 2,600 to 13,000 once, depending on the integration list
Which is to say the running cost is not the decision. The build is, and the discipline afterwards is.
How do you keep the bill down?
Four things, in order of how much they actually save you.
- Categorise properly. Order updates are utility. If they are going out as marketing templates you are paying triple for no benefit. This is the single biggest saving available and it is a configuration issue, not a negotiation.
- Let customers open the window. Click-to-WhatsApp entry points on product and checkout pages start customer-initiated conversations, and your replies inside those are free.
- Segment before you broadcast. Per-message billing means an untargeted blast to your whole list is now a real number. Send to the segment that might convert.
- Right-size the plan. Platform tiers are banded by contacts and seats. Paying for a million-contact tier on a ten thousand contact list is the easiest money to give back.
Is it worth it?
For a store, usually yes, and the reason is not the messaging cost. It is that WhatsApp is where UAE customers already answer. A delivery update sent by email in this market is a delivery update nobody reads, and every unread update is a support call you pay for in staff time instead.
Priced end to end, a serious setup lands under what one full-time support hire costs in a year.
If you want the numbers in more depth, including the volume bands and a fuller breakdown of BSP markups, the parent agency keeps a maintained version of the rate card in WhatsApp Business API pricing in the UAE. The automation side of this work, the flows, the CRM wiring and the AI qualification, is built by the team at GoDesign, and we handle the store and the integration end of it here.
If you are scoping a build, the API integration page sets out how we connect stores to systems like this, and the questions to ask a web agency apply just as well to whoever quotes you for the WhatsApp piece.
