Type your monthly message volumes below and this tool returns your Meta bill in dirhams. In the United Arab Emirates, Meta charges AED 0.1832 (USD 0.0499) per delivered marketing template, AED 0.0576 (USD 0.0157) per utility template and AED 0.0576 (USD 0.0157) per authentication template. Service messages are free today. Billing is per delivered message, not per conversation. Inbound messages from your customers are not billed by Meta at all.
Three things this calculator does that the popular ones do not: it applies Meta's volume tiers, which have different thresholds for utility and authentication; it prints dirhams from Meta's own AED rate card rather than converting dollars; and it shows you both today's bill and your bill from 1 October 2026, when part of the free tier is withdrawn.
Enter delivered messages per month. Everything is priced from Meta's published United Arab Emirates rate card, read 3 September 2026.
Meta publishes the band rates but does not state on its rate card which method it applies. Below 100,000 utility or 300,000 authentication messages a month the two give the identical answer.
| Line | Messages | Rate | Today | 1 Oct 2026 |
|---|---|---|---|---|
| Meta total | 0 | 0.00 | 0.00 |
| Per-message model, at Twilio's published USD 0.005 on inbound and outbound | USD 0.00 |
| Flat platform-fee model, at 360dialog's published Regular plan | EUR 49 per number, per month |
Neither line is added to the Meta total and neither is converted into dirhams. Each is the vendor's own published price in the vendor's own currency. Your actual provider may price differently.
Every figure below came from Meta's own published United Arab Emirates rate card on Thursday 3rd September 2026. It is not a vendor's copy, not a blog's transcription, and not a currency conversion. We queried it twice and got identical values on both calls.
| Category | AED | USD | Volume tiers |
|---|---|---|---|
| Marketing | 0.1832 | 0.0499 | None. One flat rate at any volume. |
| Utility, first band | 0.0576 | 0.0157 | Six bands, first runs to 100,000 a month |
| Authentication, first band | 0.0576 | 0.0157 | Six bands, first runs to 300,000 a month |
| Service | 0.0000 | 0.0000 | Free today. Chargeable from 1 October 2026. |
Meta's UAE marketing rate returns an empty tier list, which is why the marketing line has no volume discount. That is not an oversight in this calculator, it is the rate card.
| Monthly volume | AED | USD |
|---|---|---|
| 0 to 100,000 | 0.0576 | 0.0157 |
| 100,001 to 1,000,000 | 0.0547 | 0.0149 |
| 1,000,001 to 4,500,000 | 0.0518 | 0.0141 |
| 4,500,001 to 40,000,000 | 0.0490 | 0.0133 |
| 40,000,001 to 80,000,000 | 0.0461 | 0.0126 |
| 80,000,001 and above | 0.0432 | 0.0118 |
| Monthly volume | AED | USD |
|---|---|---|
| 0 to 300,000 | 0.0576 | 0.0157 |
| 300,001 to 2,000,000 | 0.0547 | 0.0149 |
| 2,000,001 to 10,000,000 | 0.0518 | 0.0141 |
| 10,000,001 to 20,000,000 | 0.0490 | 0.0133 |
| 20,000,001 to 40,000,000 | 0.0461 | 0.0126 |
| 40,000,001 and above | 0.0432 | 0.0118 |
The band rates are identical between the two categories. The thresholds are not. Utility drops to its second band at 100,001 messages a month, authentication at 300,001. A business sending 200,000 utility templates and 200,000 authentication templates gets a discount on the utility volume and no discount at all on the authentication volume. Any tool that runs both categories through one threshold set will hand you the wrong number in that range.
For context, on the same Meta system on the same day, the marketing rate was USD 0.0501 for Saudi Arabia, USD 0.0635 for the United Kingdom and USD 0.0118 for India, against USD 0.0499 for the UAE. We read those three in dollars only. Meta publishes a dirham card for the UAE, which is the one this calculator uses.
Some calculators carry a second tab for the WhatsApp Business Calling API. This one does not, and the reason is specific to the UAE. Text messaging on WhatsApp works normally here. Voice and video calling over WhatsApp is restricted. The TDRA treats voice and video calls as a regulated VoIP activity that "shall be provided by the licensed service providers or in collaboration with them", and licensed providers "are obliged to block the traffic of VoIP applications that are not in compliance". WhatsApp does not appear on the TDRA's published list of permitted VoIP applications, and UAE press confirmed in February 2026 that voice and video calls remain unavailable on WhatsApp in the UAE.
Meta's own documentation does not list the UAE among the countries excluded from business-initiated calling. That is a statement about Meta's platform availability, not about a carrier-level block sitting downstream of Meta. We could find no source, primary or otherwise, confirming that a WhatsApp Business Calling API call connects to a consumer on a UAE mobile network, and none confirming that it fails. It is genuinely unresolved. So we will not put a UAE call rate in a calculator, and you should treat any vendor who quotes you one as having skipped the same check.
One trap worth naming, because it is easy to fall into. Meta's calling pricing page lists AED among the billing currencies it added on 1 April 2026. That is a currency your account can be billed in. It is not evidence that UAE calling works.
Meta charges on a per-message basis, and has done since 1 July 2025. Conversation-based pricing, the model where a 24-hour window was the billable unit, was deprecated on that date. The old allowance of 1,000 free conversations a month went with it. There is no free monthly allowance today.
This matters more than it sounds. A calculator that asks you for "conversations per month" is modelling a pricing system that no longer exists, and it cannot tell you the one thing that actually drives your bill, which is the mix of message types you send. Five hundred customers who each get one marketing broadcast and five hundred customers who each get one order confirmation produce bills that differ by more than a factor of three, and no conversation count can see that difference.
The billing trigger is delivery. You are charged when a template message you send is delivered, not when it is sent, not when it is read, and not when the customer replies. Messages your customers send to you are not billed by Meta at all, which is why the inbound field in this tool adds nothing to the Meta total.
The practical consequence for forecasting: model your volumes as delivered templates by category. If your CRM reports conversations, break each conversation into the template messages it will actually contain. A booking flow that sends a confirmation, a day-before reminder and a follow-up is three delivered utility templates, not one conversation.
Four things cost you nothing from Meta as this page is written.
The free entry point carries three conditions that marketing copy usually omits, and this calculator states them next to the field. The customer must have arrived from a Click-to-WhatsApp ad or a Facebook Page call-to-action button, so organic inbound does not qualify. The customer must be on the Android or iOS app, because Meta explicitly excludes desktop and web. And the 72 hours runs from when you replied, not from when the customer messaged, and you have to reply within the first 24 hours to open the window at all.
Meta has published that from 1 October 2026, service messages become chargeable per message at each market's existing utility and authentication rate, with no volume tier discounts, and that utility messages sent inside the 24-hour customer service window revert to being charged. Messages inside the 72-hour free entry point window are stated to remain free.
That is four weeks from the day this page was written. A calculator built only on today's rules would be wrong before most people found it, which is why this one shows both columns at once and will keep doing so.
Flag one. Meta has not published a separate UAE service rate line. Our second column prices service at the UAE utility rate, which is what Meta says it will match, but that is our arithmetic and not Meta's quoted figure. Treat it as a planning assumption.
Flag two. Meta's main pricing page still describes service messages and in-window utility templates as free and does not mention the change. The dedicated upcoming-changes page does. Both are Meta primary sources and they currently disagree with each other. Re-check both before you sign anything.
Flag three. Meta has not said whether in-window utility messages will count towards the utility volume tiers once they are charged. This calculator pools them with your out-of-window utility volume. If Meta prices them separately, the answer changes only above 100,000 utility messages a month.
There is a separate line item worth knowing about even though it is not in this calculator. Meta's Business Agent Platform launched on 1 July 2026 and its messages became chargeable on 1 August 2026 at one global rate of USD 2.00 per one million tokens, which Meta estimates at approximately four to five US cents per message on a typical message consuming 20,000 to 25,000 tokens. That is Meta's own agent product, not a charge on running your own assistant, and it is not part of the template rate card above.
Run the service-led preset in the calculator and watch what happens. A business whose whole use case is answering inbound enquiries pays Meta nothing today and a real monthly figure from 1 October. A business that mostly sends marketing broadcasts sees no change at all, because marketing was never free. If you are buying an AI assistant to answer WhatsApp enquiries, the honest way to compare vendors this month is on the October number, not the September one.
Meta added AED as a billing currency effective 1 April 2026, one of eight currencies added at the same time alongside ARS, CLP, COP, MYR, PEN, SAR and SGD. It publishes a separate dirham rate card. That card is not a live conversion of the dollar card, and you can prove it with the published numbers alone.
Divide Meta's UAE marketing pair and you get 0.1832 over 0.0499, which is 3.6713. Divide the utility pair and you get 0.0576 over 0.0157, which is 3.6688. Two different ratios from the same rate card on the same day. The dirham figures are set and rounded independently, which means that if you take Meta's dollar rate and multiply it by any single exchange rate, your forecast will not match the invoice.
So this tool holds two rate cards and never crosses between them. The AED total is computed entirely from Meta's AED figures. The USD total is computed entirely from Meta's USD figures. Switch the currency control and you are switching rate cards, not applying a conversion.
One thing we could not verify and will not guess at: which currency a specific UAE account is billed in. It depends on the currency set on that WhatsApp Business Account, and we found nothing in Meta's public documentation that settles it. Check it in WhatsApp Manager rather than assuming, then use the matching column here.
Everything above is what Meta charges. You reach Meta through a Business Solution Provider, and every provider adds something. There are two models, and confusing them is the most common budgeting error we see.
Twilio publishes USD 0.005 per message, inbound and outbound, with Meta's fees passed through and no monthly subscription. There is an optional Messaging Engagement Suite add-on at USD 0.015 per message with the first 1,000 a month free. Note the sting in that model: Twilio's fee applies to inbound messages, which Meta does not charge for at all. A service-led clinic whose Meta bill is currently zero does not have a zero bill on a per-message provider.
360dialog publishes EUR 49 per number per month on Regular, EUR 99 on Premium and EUR 249 on Advanced, and states there is no markup on Meta's fees. respond.io publishes USD 79, 159 and 279 a month on monthly billing, or USD 948, 1,908 and 3,348 a year, and states that WhatsApp fees are not included in any subscription because Meta charges those based on your usage.
The crossover between the two models sits around EUR 49 divided by USD 0.005, which is roughly ten thousand chargeable messages a month, ignoring the currency mismatch. The flat model wins above it and the per-message model wins below it. For a service-heavy account the true crossover is lower, because the per-message provider is billing your inbound traffic too.
You will find comparison blogs quoting a flat twenty per cent markup for one popular provider, and per-message markups of around USD 0.001 and USD 0.004 for two others. We could not retrieve a primary source for any of those numbers. One vendor's pricing page returned a 404 after redirect and another's rate-card article is gone. Rather than launder third-hand figures into a calculator, we left them out and named only the two providers who publish their own fee in plain sight.
The best-known general WhatsApp pricing calculator is respond.io's, one of only three tools in its own top-nav and internally linked from every page on its site. We read it on 3 September 2026. It is a competent global tool. It is not a UAE tool, and the difference costs money. Four problems, in order of how much.
The figure that circulates across UAE pricing content is USD 0.0385 per marketing message. Meta raised the UAE marketing rate effective 1 October 2025 and records the change in its own update log as a higher marketing message rate for the United Arab Emirates. The rate we read on Meta's own system on 3 September 2026 is USD 0.0499, about thirty per cent higher. We found the old figure still live on a UAE pricing page stamped Last Updated 2 September 2026, one day before we looked, and that same page still describes the rate as a 24-hour conversation price. Conversations stopped being the billing unit on 1 July 2025. Two errors, one page, both invisible unless you check Meta yourself.
respond.io's calculator page tells you that "the more messages a business sends, the lower the cost per message" and that "tiered discounts reset at the start of each month". That is true in general and false for the UAE line that costs the most. Meta's UAE rate card returns no marketing tiers at all. Marketing is one flat rate at 1,000 messages and at 10,000,000. A UAE business reading a generic volume-discount promise will budget for a broadcast discount that never arrives, and the tiers that do exist, on utility and authentication, change nothing until 100,000 and 300,000 messages a month respectively.
respond.io's copy anchors on "As of July 1, 2025". Across the eleven respond.io pages examined on 3 September 2026, none carried a visible last-updated date, only a server-rendered timestamp. That is the hole this page exists to fill. Meta changed the UAE position twice in the twelve months to September 2026: the marketing rate rise on 1 October 2025 and the addition of AED as a billing currency on 1 April 2026. A rate card without a read date is unfalsifiable. You cannot tell whether it is current or eleven months behind, and neither can the person quoting it to their finance director.
There is no business-location input, which is the input that decides whether international authentication rates could ever apply. There is no dirham output and no currency switch, so a UAE business gets dollars and has to convert, which is exactly the thing that makes a forecast miss the invoice. Volumes are set with four sliders of 117 steps rather than a number field, so you cannot type 4,300. There is no free entry point modelling. And the result cannot leave the page: no share link, no export, no copy.
The UAE is one of nine markets with a separate international authentication rate, alongside Egypt, India, Indonesia, Malaysia, Nigeria, Pakistan, Saudi Arabia and South Africa. At AED 0.1872 (USD 0.0510) in its first band, it is more than three times the standard authentication rate. It is also the single easiest way to make a UAE calculator produce a frightening and wrong number, which is why this one keeps it off unless all of Meta's conditions are met.
Meta applies it only when all three of the following hold. The business sends more than 750,000 messages outside customer service windows in a rolling 30-day period. The business is based in a different country from the recipient. And the message is delivered on or after the start time Meta assigns, which is set 30 days after eligibility so you get 30 days' notice.
Meta's own wording is unambiguous on the middle condition: you will not be billed the international authentication rate if you are based in the same country as the user. A UAE business messaging UAE customers pays the standard authentication rate, whatever its volume. Set the location control to "Outside the UAE" and push your non-window volume past 750,000 and the calculator will switch bands and tell you it has, with the conditions restated.
| Monthly volume | AED | USD |
|---|---|---|
| 0 to 300,000 | 0.1872 | 0.0510 |
| 300,001 to 2,000,000 | 0.1778 | 0.0485 |
| 2,000,001 to 10,000,000 | 0.1685 | 0.0459 |
| 10,000,001 to 20,000,000 | 0.1591 | 0.0434 |
| 20,000,001 to 40,000,000 | 0.1498 | 0.0408 |
| 40,000,001 and above | 0.1404 | 0.0383 |
If you are a UAE business messaging UAE customers, ignore this table entirely. It is here so you can see what we excluded and why, not because you are likely to pay it.
Cost and capacity are two different ceilings and the second one catches people out. Meta defines a messaging limit as the maximum number of unique WhatsApp user phone numbers you can deliver messages to, outside a customer service window, within a moving 24-hour period.
A newly created business portfolio starts at 250 unique customers per 24 hours. That is the documented starting figure, not the 1,000 that circulates in vendor content. From there it can be raised to 2,000 by completing a scaling path, and then to 10,000, to 100,000 and to unlimited through automatic scaling.
The three routes to 2,000, in Meta's own words, are: verify your business, have your partner verify your business if you were onboarded by one, or send 2,000 delivered messages outside customer service windows to unique WhatsApp user phone numbers within a 30-day moving period using templates with a high quality rating. Meta's Business Help Centre describes that last route slightly differently, as a minimum of 1,000 conversations over 30 consecutive days. Both wordings are Meta's and they do not agree, so we report both rather than picking one.
Two consequences for anyone modelling a launch. First, limits are calculated and set at portfolio level and shared by every business phone number in the portfolio, so registering more numbers does not buy you more capacity. One number can consume the whole portfolio's allowance. Second, Meta applies a separate per-user marketing limit, capping how many marketing templates an individual receives from any business based on factors including their recent marketing read rate and how full their inbox already is. Those per-user limits are switched off for senders and recipients in the European Economic Area, the United Kingdom, Japan and South Korea. The UAE is not on that exemption list. If a user has hit their limit, further attempts may be unavailable for up to 24 hours and the API returns error code 131049.
There is also a user-level switch that bypasses your CRM entirely. WhatsApp gives users an "Offers and announcements" setting to stop marketing messages from your business. If a user has stopped them, the API processes the request and does not send the message, returning a failed status with code 131050. You can watch for this on the user preferences webhook, but the point stands: some of the volume you budget for is unreachable at any price.
Cutting a WhatsApp bill is easy if you are willing to break something. Here is what is genuinely safe, what carries a named consequence, and what real operators do that is neither endorsed nor forbidden. The third column is operator practice, not Meta policy, and we have labelled it that way because nobody else does.
The Flagged and Restricted phone-number statuses were discontinued on 7 October 2025. Any guide built around "your number went Flagged and dropped a tier after seven days" is describing a system that no longer exists. Since that retirement, Meta's current published documentation no longer states a mechanism, threshold or duration for a messaging-limit downgrade. We cannot source a current downgrade rule, so we do not publish one.
Meta did not ban AI assistants on WhatsApp. The AI Providers clause bars providers of AI technologies from using the platform to distribute their own assistant where that assistant is the primary functionality being offered. It explicitly permits a business to retain an AI provider as its third-party service provider. The rule that actually constrains a business assistant is the older and separate escalation-path requirement in the Business Messaging Policy.
Learnmind is a Dubai business building AI customer communication for UAE companies, so a WhatsApp bill is not an abstraction to us: it is a line in a proposal we have to defend. One pattern comes up again and again on our sales calls, and it is not a question about the technology. It is that nobody in the room knows what Meta actually charges. We have sat in a meeting where a figure of USD 0.025 per message was read aloud as twenty-five cents and neither side corrected it confidently. That is a pattern we observe first-hand, not a survey, and it is the reason this page carries a read date instead of asking you to take our word for it.
Two of our clients are named publicly with their outcomes. Alcaz Media is a UAE-based performance marketing agency working with brands like Ferrari Middle East, La Vista Development and Myjooti, where the published result is a response within seconds, 24/7, and every qualified lead landing in the CRM with full conversation history. Lola's Lashes is a UK beauty brand co-founded by Fraser Angus and Daniel Morris, where the system covers comments across every ad, post and reel around the clock. Both stories are on our results page with the detail. We also work with clients in the healthcare and aesthetics space, and due to the sensitive nature of those engagements we are unable to publicly disclose their identities. If you are a healthcare provider and would like to learn more about our work in that sector, get in touch and we can share relevant details privately.
If you want the same rigour applied to your own account rather than a generic model, send us your message mix. We will build the UAE cost model in dirhams at today's rates and at the 1 October 2026 rates, name the provider fee on top, and tell you which of the two provider models is cheaper at your volume.
Meta's published United Arab Emirates rate card charges AED 0.1832 (USD 0.0499) for every delivered marketing template, AED 0.0576 (USD 0.0157) for a utility template and AED 0.0576 (USD 0.0157) for an authentication template. Service messages cost nothing today. Those four figures were read from Meta's own pricing system on 3 September 2026.
Utility and authentication get cheaper at volume. Marketing does not, because Meta's UAE rate card returns no marketing tiers at all.
It multiplies the number of delivered template messages in each category by Meta's published UAE rate for that category, applying the volume tiers for utility and authentication with their own separate thresholds.
It bills per delivered template message, which is how Meta has charged since 1 July 2025, not per conversation, which was deprecated on that date. Inbound messages from customers are counted but charged at zero by Meta. Nothing is converted between currencies: the dirham total uses Meta's AED rate card and the dollar total uses Meta's USD rate card.
Yes for utility and authentication, no for marketing. Volume tiers were introduced on 1 July 2025 for utility and authentication only, and Meta's UAE rate card returns an empty tier list for marketing, so marketing is one flat rate at every volume.
The utility and authentication thresholds are not the same: the first utility band runs to 100,000 messages a month and the first authentication band runs to 300,000. A calculator that uses one threshold set for both is wrong. Below 100,000 messages a month the tiers make no difference at all.
Because the answer changes on 1 October 2026. Meta's upcoming-changes documentation states that from that date service messages become chargeable per message at each market's existing utility and authentication rate with no volume tier discounts, and that utility messages sent inside the 24-hour customer service window, free since July 2025, revert to being charged.
A tool that showed only today's number would be wrong within weeks of publication, so this one shows today's bill and the announced bill side by side. Meta has not yet published a separate UAE service rate line, so the service figure in the second column is a planning assumption, not a quoted rate.
Meta does not. Billing is triggered when a template message you send is delivered, and inbound user messages are not billed by Meta at all.
Your Business Solution Provider may still bill them. Twilio publishes a fee of USD 0.005 per message on inbound as well as outbound, on top of Meta's fees, so a service-led use case that costs nothing from Meta is not necessarily free once the provider layer is added. That is why this calculator has a separate inbound field that adds zero to the Meta total and is shown separately in the provider estimate.
Because their rate card is stale. Meta raised the UAE marketing rate effective 1 October 2025 and its own update log records the change as a higher marketing message rate for the United Arab Emirates. The live rate we read on 3 September 2026 is USD 0.0499. The older USD 0.0385 figure is still republished widely, including on a UAE pricing page stamped Last Updated 2 September 2026 that also still describes the rate as a 24-hour conversation price, a billing unit Meta retired on 1 July 2025.
The live rate is about thirty per cent higher than the stale one, so a broadcast budget built on 0.0385 lands well short. Almost none of those pages prints the date its rates were read, which is why the staleness is invisible to the person using them.
Meta added AED as a billing currency effective 1 April 2026 and publishes a separate AED rate card, so a UAE account can be billed in dirhams. Which currency a specific account is billed in depends on the currency set on that WhatsApp Business Account, which we could not find documented publicly, so check it in WhatsApp Manager rather than assuming.
Do not convert Meta's USD rate yourself. Meta's AED figures are not a live conversion of its USD figures: the marketing pair implies a ratio of 3.6713 and the utility pair implies 3.6688, so a converted number will not match the invoice.
There are two models and they behave very differently. Twilio publishes a per-message fee of USD 0.005 on inbound and outbound, with Meta's fees passed through and no monthly subscription, plus an optional Messaging Engagement Suite at USD 0.015 per message with the first 1,000 a month free.
360dialog publishes a flat platform fee of EUR 49 per number per month for its Regular plan, EUR 99 for Premium and EUR 249 for Advanced, and states there is no markup on Meta fees. respond.io publishes subscription tiers of USD 79, 159 and 279 a month billed monthly and states that WhatsApp fees are not included.
Widely quoted per-message markups for other providers could not be traced to a primary source, so they are not on this page.
Not necessarily, because cost and capacity are separate limits. Meta caps the number of unique WhatsApp users you can message outside a customer service window in a moving 24-hour period. A newly created business portfolio starts at 250 unique customers, which can be raised to 2,000 by completing a scaling path and then to 10,000, 100,000 and unlimited through automatic scaling.
Limits are set at portfolio level and shared across every number in the portfolio, so adding numbers does not add capacity. Separately, Meta applies per-user marketing limits that are active for UAE senders and recipients, so an individual customer may simply not receive your marketing template no matter what your budget says.
UAE rates, categories, volume tiers, the free tier and the free entry point conditions: Meta's WhatsApp Business Platform pricing documentation and Meta's published UAE rate card, both read on Thursday 3rd September 2026, at developers.facebook.com/docs/whatsapp/pricing and whatsappbusiness.com/products/platform-pricing.
Per-message billing from 1 July 2025, the UAE marketing rate increase on 1 October 2025, AED added as a billing currency on 1 April 2026: Meta's updates-to-pricing log. Service messages and in-window utility templates becoming chargeable on 1 October 2026, and the Meta Business Agent rate from 1 August 2026: Meta's non-template-messages documentation. The 750,000-message threshold and the same-country exemption for international authentication: Meta's authentication-international rates documentation.
Messaging limits, the 250 starting limit, the scaling paths, per-user marketing limits, the Offers and announcements setting and error codes 131049 and 131050: Meta's messaging-limits and marketing-template documentation and the WhatsApp Business Messaging Policy at whatsappbusiness.com/policy. The retirement of Flagged and Restricted on 7 October 2025: Meta's own help article. The AI Providers clause: WhatsApp Business Solution Terms, last modified 6 March 2026.
WhatsApp calling in the UAE: the TDRA's own internet guidelines page listing the VoIP applications currently allowed in the UAE, which does not include WhatsApp, together with Gulf News reporting dated 10 February 2026 that voice and video calls remain unavailable on WhatsApp in the UAE. Meta's position on business-initiated calling availability: Meta's WhatsApp calling documentation and its calling pricing page. We report the two as unresolved against each other rather than picking the answer that suits us.
Provider fees: each vendor's own published pricing page for Twilio, 360dialog and respond.io. The competitor comparison describes the published structure and copy of respond.io/whatsapp-pricing-calculator and ten other respond.io pages as they stood on 3 September 2026. Where we say a figure is stale we mean it against Meta, and we name the date we read Meta.
Not tax, legal or regulatory advice. Rates change, and Meta has changed the UAE card twice in the last twelve months. Check Meta's live rate card before you commit a budget, and re-check the 1 October 2026 position in particular, because Meta's own two pricing pages currently disagree about it.
Rates read and this page written on Thursday 3rd September 2026
Send us your message mix and we will build the UAE cost model in dirhams, at today's rates and at the 1 October 2026 rates, with the provider fee named, so you see both numbers before you commit to a platform.
Dubai based. We answer on WhatsApp, which is the whole point.