The short answer: which route fits which Dubai business
There are three practical ways to put a WhatsApp Business API number to work in Dubai, and the money gap between them is narrower than most provider landing pages imply. Meta's Cloud API costs nothing beyond Meta's own per-message charges: no licence, no seat fee, no minimum. 360dialog charges a fixed monthly licence per hosted number, listed at EUR 49 on its Regular plan (roughly AED 200 at current rates), and passes Meta's message charges through without adding a cent. Twilio charges no monthly platform fee on pay-as-you-go and adds around $0.005 per message (about AED 0.018) on top of whatever Meta bills.
Run those numbers against each other and the crossover sits near 11,000 billable messages a month. Below that, Twilio's per-message fee costs less than 360dialog's fixed licence. Above it, the fixed licence wins, and the gap widens fast as volume climbs.
Price is rarely the deciding factor for a business under 20,000 messages a month, though. The difference that matters is what breaks when you connect the number to a CRM, a booking calendar and a payment link, and who picks up when it does. That part is worth more attention than the rate card.
What a BSP is, and what you get from Meta directly
A WhatsApp Business Solution Provider (BSP) is a Meta-approved company that hosts your WhatsApp Business API number, submits your message templates, gives you a dashboard and a support channel, and bills you for Meta's message charges alongside its own fee. 360dialog and Twilio are both BSPs. Meta's Cloud API is the same underlying platform without the intermediary: Meta hosts the number, you talk to the endpoint, and the only invoice is Meta's.
Going direct removes a layer of cost and a layer of opinion. It also hands you the work. With Cloud API you set up a Meta Business Manager, add a payment method, register the number, handle webhook delivery and retries yourself, submit every template through the API or Business Manager UI, and monitor your own error codes. Support is documentation and a bug report form. There is no inbox, no agent seats, no phone number to call at 9pm when template delivery starts failing.
That trade is fine for a business whose WhatsApp traffic is machine-to-machine: order confirmations, appointment reminders, payment links fired by software. It stops being fine when a team of five needs to see conversations, take over from the bot and leave notes.
One detail that catches people out: whichever route you take, the number is consumed. Once a +971 number is registered on the API it cannot also live in the WhatsApp Business app on a phone. Plan for a spare SIM before you start rather than migrating the line your front desk uses all day.
The July 2025 billing change, and what lands on 1 October 2026
Until mid-2025 Meta billed WhatsApp in 24-hour conversation windows. You opened a conversation in one of four categories and paid a single charge that covered every message inside that window. On 1 July 2025 Meta switched to per-message billing: each delivered template message is charged individually, and the category of that template sets the price.
For a small Dubai business this was mostly good news. A clinic sending 400 appointment reminders used to pay a conversation charge each time it opened a window; now it pays a utility rate per delivered message, which is a smaller number. Free-form replies to a customer inside the 24-hour service window stayed free, and utility templates sent inside that same window became free as well. Businesses that answer inbound leads and send confirmations saw their Meta bill shrink. Businesses blasting cold marketing lists saw it rise, since every marketing template now meters on its own.
The next change is already announced and worth budgeting for. Meta has published pricing updates for service and utility messages landing on 1 August 2026 and 1 October 2026, with the October change ending the free status of service messages inside the 24-hour window and removing the in-window exemption utility templates have held since July 2025. Confirm the exact rates with your provider before you model 2027, because published rate cards move and country bands move with them. If your current WhatsApp bill is close to zero because everything you send is a reply, that line stops being free.
What each message category costs in the UAE
Four categories, four price behaviours. Marketing is promotional and re-engagement traffic and it is the expensive one. Utility covers order updates, receipts, booking confirmations and reminders tied to something the customer already did. Authentication covers one-time codes. Service is any free-form reply inside the 24-hour window opened by the customer.
Working UAE market bands for 2026, useful for budgeting rather than as a copy of Meta's official rate card:
- Marketing template: roughly AED 0.13 to 0.20 per delivered message
- Utility template: roughly AED 0.03 to 0.06
- Authentication template: roughly AED 0.03 to 0.05
- Service reply inside the 24-hour window: free under the current model, billable from 1 October 2026
Meta has been rolling out local-currency billing, so a UAE account increasingly sees AED on the invoice instead of USD. That removes the currency conversion spread a card issuer used to take on every monthly charge, which is small per transaction and annoying at scale.
The practical consequence is that your provider choice barely moves your Meta bill. Message mix moves it. A business at 4,000 messages a month, split 3,000 utility and 1,000 marketing, pays Meta somewhere around AED 220 to 380 regardless of who hosts the number.
Price comparison with real arithmetic
Take that same 4,000-message business and add the provider layer.
Meta Cloud API direct: AED 220 to 380 a month, full stop. Nothing sits on top.
360dialog Regular: AED 220 to 380 plus the EUR 49 licence, so roughly AED 420 to 580. The published plan ladder runs EUR 49 for Regular, EUR 99 for Premium and EUR 249 for high-throughput sending, per hosted number, with Meta's charges passed through untouched.
Twilio pay-as-you-go: AED 220 to 380 plus 4,000 multiplied by AED 0.018, so about AED 73 in markup, landing near AED 295 to 455.
At 4,000 messages Twilio is cheaper than 360dialog by roughly AED 125 a month. Push the same business to 15,000 messages and Twilio's markup becomes about AED 275 while 360dialog's licence stays at AED 200. At 40,000 messages Twilio's markup is around AED 734 against the same AED 200. Twilio's published rate steps down at volume tiers and contract pricing exists, so treat the high end as a negotiation, not a fixed sentence.
Other BSPs in the region price differently again, commonly a hosting fee of $10 to $20 per number per month (about AED 40 to 75) plus a per-message markup. That combination is the one to inspect hardest, because it charges you twice for the same service.
For a full breakdown of what a Dubai WhatsApp setup costs once the automation layer is included, our WhatsApp AI sales agent page lays out what the software above the API does and what it costs.
Where they differ once you connect a CRM
Rate cards are the easy part. The three routes actually diverge once a bot, a CRM and a human handoff enter the picture.
On dashboard and inbox, Twilio gives you a console built for developers: logs, debugger, message insights, and an inbox only if you add Twilio Flex or build one. 360dialog ships a client hub for numbers, templates and billing, and expects you to bring your own inbox or partner platform. Meta direct gives you Business Manager, which shows account health and templates and nothing resembling a team inbox.
Integration with a bot and a CRM looks similar on paper: all three expose the same webhook shape, since it is all Meta's Cloud API underneath. Twilio's SDKs are the most complete if your team writes code and wants one library covering WhatsApp, SMS and voice. 360dialog sits closest to raw Cloud API, which is convenient when your automation was written against Meta's own documentation and you want to move providers later without rewriting handlers.
Support is where the gap is widest. Twilio has paid support tiers and a large public knowledge base. 360dialog runs partner and direct support out of Europe. Meta direct has no support line for a small advertiser, which is the honest reason most Dubai SMBs use a BSP at all.
Time to a live number matters too: with documents in order, a BSP can have a number sending within a day or two of verification clearing, while direct Cloud API depends entirely on your developer's calendar.
Data residency is the last thing worth checking before signing. 360dialog is a German company hosting in the EU, which matters if your legal team asks where the data sits. Twilio is US-headquartered with regional data options depending on product. Meta's Cloud API hosts in Meta's own regions, and local data hosting is available in a limited list of countries, so check the current list rather than assuming the UAE is on it.
Who should pick what
Twilio suits a business with developers already inside it, especially one running SMS, voice and WhatsApp from the same stack. If a WhatsApp thread needs to fall back to SMS when a customer has no data, or escalate to a voice call, one vendor and one library is a real saving in engineering time. That fallback logic pairs well with an AI voice receptionist on the phone side of the same number pool.
360dialog suits a business where WhatsApp is the main sales channel and volume is real. Fixed cost per number, no markup, predictable invoices. A Dubai clinic group sending 30,000 reminders a month knows its provider line will be AED 200 whether it sends 30,000 or 60,000.
Meta Cloud API direct suits low volume and simple automation: a booking confirmation, a payment link, a reminder, all fired by software with nobody watching an inbox. It also suits anyone testing whether WhatsApp automation moves their numbers at all before committing to a monthly line item.
The wrong reason to pick any of them is a comparison table on a provider's own blog. The right reason is which one your automation layer already speaks to and which one answers your ticket.
Verification in the UAE: documents and the 250 ceiling
The provider does not change what Meta asks for. A UAE business needs a valid trade licence (mainland DED or free zone, both work), the Emirates ID of the authorised signatory, a registered address matching the licence, and a Meta Business Manager where the legal name is entered exactly as printed on the licence, legal suffix included.
Meta Business Verification in the UAE has cleared in a matter of days for applicants with a clean trade licence and matching documents, though Meta's own guidance allows for a longer review, so treat any specific day count as an estimate and confirm current turnaround with your provider before you commit to a launch date. Display name approval runs as a separate, usually faster queue. Name mismatch against the trade licence is the most common rejection we see, followed by an expired licence.
The number that decides whether you can operate: an unverified business account is capped at 250 unique business-initiated conversations per rolling 24 hours. Inbound conversations do not count against it. That ceiling is invisible to a support-led business and lethal to anyone running outbound campaigns, which is why verification is the first task rather than a badge to chase later. Completing verification lifts you toward the 1,000 tier, and Meta raises it further based on delivered volume and a clean quality rating.
Whichever provider you sign with, ask who submits the verification and who owns the Business Manager. You want the asset in your own Business Manager with the provider granted access, not the reverse.
Spotting a hidden markup on your invoice
Every provider says its pricing is transparent. Four checks confirm or kill that claim in about ten minutes.
- Ask for one month of usage exported and split by category: marketing, utility, authentication, service. If the provider cannot produce that split, the markup is being blended into a credit balance and you will never see it.
- Compare the per-message line for each category against Meta's published rate for the UAE in that same month. The difference is the markup, expressed as a number rather than a promise.
- Read the invoice for fees that are not messages: per agent seat, per template submitted, per additional number, per API call above a quota, minimum monthly spend. These add up faster than the message markup on a small account.
- Check the billing currency. If the invoice is in USD or EUR while your revenue is AED, your card or bank takes a conversion spread on every charge, typically a couple of percent. On AED 500 a month it is noise; on AED 5,000 it is a line worth negotiating.
Moving between providers later
Migration is possible and it is not free. The WhatsApp number and the WhatsApp Business Account can move between solution partners, and Meta supports the process, but a few things carry a real cost.
Message templates generally need resubmission when the number lands under a different WhatsApp Business Account, so plan for approval time before the switch rather than after. Conversation history living in the old provider's inbox usually stays there, since that is their database and not Meta's. You will need the two-step verification PIN for the number, and the outgoing provider has to release it, which is where an unhappy vendor can cost you days.
Budget a short outage. Messages sent during the handover window fail rather than queue, so run it at 3am on a quiet day and have the automation paused. The engineering cost of repointing webhooks and re-testing flows is typically half a day to two days depending on how many integrations touch the number.
The way to keep that cheap is to write your automation against Meta's Cloud API shape rather than a provider-specific SDK. Then the provider becomes a swappable line item instead of a rebuild.
What we run, and where the provider stops mattering
Our own studio number in Dubai sits behind the API with an AI agent on it. It answers in under 60 seconds at any hour, quotes, qualifies, sends the payment link and writes the deal into the CRM without a person touching it. We run it on ourselves before we sell it to anyone.
The lesson from doing that has nothing to do with which BSP is on the invoice. The provider moves bytes. It has no idea who the customer is, whether they paid, or what to say next. The layer above it decides all of that, and the layer above it is where things quietly break. Two sync bugs in our own stack once left about AED 15,000 of paid bookings sitting in the CRM marked unpaid for weeks. No BSP dashboard would have shown that, because as far as WhatsApp was concerned every message delivered fine.
So pick the provider on cost and support fit, then spend the real attention on the automation. If you want that layer built and monitored, process automation starts at AED 6,000 to set up and AED 1,200 a month to keep running, with the full breakdown on our pricing page. A Growth Audit from AED 3,000 maps where your current WhatsApp path loses leads before anyone connects anything.
Artur Gall, founder of slgo.ai, Dubai.
