Most WhatsApp problems in the UAE come down to four causes. On the free Business app, broadcasts only reach people who saved your number. On the official API, Meta often accepts a message and then drops it, usually with error 131049, its cap on marketing per person. Free text fails outside the 24-hour window, and a new account can only start chats with 250 people a day. Messaging itself works normally in the UAE. Voice and video calls were restricted for years and started connecting in our tests on 25 September 2026, with no official announcement.
Start here: the free app or the official API?
There are two kinds of WhatsApp for business, and they fail in different ways. The WhatsApp Business app is the free app on a phone. The WhatsApp Business Platform, usually called "the API", is Meta's system for sending from software through its Cloud API, most often through a provider. Find out which one you are on before you change anything.
| Free Business app | Official API (Cloud API) | |
|---|---|---|
| Broadcast size | Up to 256 contacts per list | No list cap, but a daily limit on how many people you can start chats with |
| Who receives a broadcast | Only people who saved your number | Anyone who opted in, sent as an approved template |
| What you can send first | Anything | An approved template, unless the customer wrote in the last 24 hours |
| How you see failures | You don't. It looks sent. | Status webhooks with an error code |
| Cost | Free | Meta charges per delivered message |
| Most common reason messages "don't arrive" | The saved-contact rule | Error 131049, the marketing cap |
On the app, a broadcast to 250 customers looks the same whether 250 people got it or 12 did. There is no error and no warning. Most customers never save a business number, so a list of one-time buyers often reaches a small share of the list. We see this on almost every account that moves to us from the app. There is no fix inside the app, because the rule is how the product works. The API has no saved-contact rule, which is the main reason businesses move to it.
The order to check, fastest first
- App or API? If you are on the app, the saved-contact rule is almost always the answer.
- Are you storing status webhooks? A webhook is the message Meta sends back to your system to say what happened: sent, delivered, read or failed. If nobody stores them, every failure on this page is invisible to you.
- Read the error code. 131049 is the marketing cap. 131050 is an opt-out. 131026 means the number cannot receive. 131047 means you are outside the 24-hour window. The full table is below.
- Send a utility control. Send a simple utility template (Meta's sample
hello_worldworks) to the same number. If it lands and your campaign did not, the problem is the category, not the number. - Check your limit. If sends stop after a few hundred people, or fail with 131048, you have hit your daily messaging limit or the number is restricted.
- Check the template. Paused, rejected or wrong-language templates fail with 132015, 132016 or 132001.
Why "sent" does not mean delivered
When your system sends a message, Meta's API answers straight away with a success code and a message ID (a "wamid"). That answer only means Meta accepted the request. Delivery is decided later. If Meta drops the message, the failure arrives minutes later as a status webhook. Code that only checks the first answer records a success, and the dashboard shows a campaign as sent when part of it never arrived.
This is the most expensive mistake we see. The drop itself is normal and often unavoidable. The silence is the damage, because nobody follows up with the people who missed the message. Store every status event against its message ID, and report delivered and read counts, never "sent".
One upside: Meta charges only for messages that are delivered. A dropped marketing message costs nothing. A send to a paused template costs nothing either, and the attempt does not count against your limit.
The error codes UAE senders actually hit
Meta's error guide lists dozens of codes. These are the ones that matter for delivery, with Meta's meaning in plain words and what to do about each.
| Code | What Meta says it means | What to do |
|---|---|---|
| 131049 | Not delivered "to maintain healthy ecosystem engagement": the per-person marketing cap | Do not resend at once. See the next section. |
| 131026 | Unable to deliver: not a WhatsApp user, has not accepted WhatsApp's terms, or an old app version | Fix or remove the number. This is normal list decay. |
| 131050 | The person stopped marketing messages from your business | Do not retry. Mark them as opted out. |
| 130472 | Not sent because the person is in a Meta marketing experiment | Nothing to fix. Meta holds back a small group to measure results. |
| 131047 | More than 24 hours since the person last wrote to you | Send an approved template, not free text. |
| 131048 | Restricted because of limits on how many messages this number can send | Check quality and your limit in WhatsApp Manager. |
| 131056 | Too many messages to the same person in a short time | Slow down to that person. |
| 130429 | Cloud API sending speed reached | Send more slowly. |
| 131053 | The media in the message could not be uploaded | Check the file type and size. |
| 132000, 132012 | Template variables missing, or in the wrong format | Fix the fields your system fills in. |
| 132001 | The template does not exist in that language, or is not approved | Check the template name and language code. |
| 132015, 132016 | Template paused for low quality, or disabled after too many pauses | Edit it, or create a new template with different content. |
| 131042 | A problem with your payment method | Fix billing in your Meta business settings. |
| 368, 131031 | The account is restricted or disabled for a policy breach | Read the notice in WhatsApp Manager before sending anything else. |
What the codes looked like on one UAE account
Here is the failure breakdown from Hype UAE, a retail store we run WhatsApp for: 14,899 messages to 3,293 contacts between 18 June and 22 August 2026. 1,557 messages failed, about 10.5%.
| Code | Failures | Share of failures |
|---|---|---|
| 131049, marketing cap | 1,388 | 89.1% |
| 131026, cannot receive | 111 | 7.1% |
| 130472, experiment group | 51 | 3.3% |
| 131050, opted out | 6 | 0.4% |
| 131053, media upload | 2 | 0.1% |
This is one account in one market with one sending pattern, so your mix will differ. But nearly nine in ten failures were one code, and opt-outs were almost nothing. If your delivery is broken, a wave of opt-outs is very unlikely to be the reason. Of the marketing messages Meta billed on that account, 79.2% were read (5,415 of 6,834), and 11.7% of contacts replied. People in the UAE do read WhatsApp. The cap is what stands between a campaign and that read rate.
The same pattern shows up on small sends. When we sent a seasonal waiting-list message for The Setup Collective to 55 past families in September 2026, 45 received it on the first evening. Six were held back with 131049 and four numbers were no longer on WhatsApp. Our system retried the six with growing gaps (20 minutes, then 2, 6 and 12 hours), and all six were delivered within two days.
Error 131049: sent, accepted, never delivered
131049 is Meta's per-person limit on marketing messages. Meta accepts your send, then declines to deliver it because that person has recently had a lot of marketing from businesses in general, not only from you. It is not a ban, not a block and not a bug in your code. Your quality rating can be green while it happens all day. No provider can switch it off, and anyone who says they can bypass it is not telling you the truth.
The test that shows it is the category
On another UAE account we run, an events business, a marketing invite with a video and buttons failed with 131049 twice to one number on 8 August 2026. In the same minutes, Meta's utility sample template reached that number and was read. We then submitted the same invite, with the same copy, video and buttons, as a utility template. Meta approved it in Arabic and English, it was delivered to the same number, and it was billed as utility, which is cheaper. That is one controlled observation, not a study. It shows the cause on that number. It does not prove utility templates are never held back.
The fix, if the message is really transactional
Utility means a message about something the customer already did or asked for: an order update, a booking confirmation, an appointment reminder, a ticket, an RSVP. If your message is that, send it as a utility template. Two catches. Since 9 April 2025, when Meta decides a template submitted as utility is really marketing, it approves it as marketing instead of rejecting it, so check the category Meta approved, not the one you picked. You can ask for a review within 60 days. Meta can also move an approved utility template to marketing later, usually with one day's notice. Subscribe to the template_category_update webhook so a change does not surprise you.
The fix, if the message is really promotional
- Do not relabel it as utility. Meta reviews categories, and misuse puts the template and the account at risk.
- Wait before you retry. Meta's error guide suggests waiting at least 24 hours. On the send described above, all six held-back messages went through on spaced-out retries within two days.
- Send less, to fewer and better-chosen people. The cap exists because people are being over-messaged.
- Track who did not get it, and reach them another way instead of reporting the campaign as landed.
- Let the customer start the chat. A Click-to-WhatsApp ad, a QR code or a website button makes them write first, so your replies go out inside an open window.
Plan for the Marketing Messages API
Meta now runs a separate Marketing Messages API, which it says optimises delivery towards the people most likely to find a message relevant. Meta's documentation says the Cloud API will stop supporting marketing messages on 13 October 2027. If you send marketing at volume, ask your provider now how and when they will move you. The switch means accepting Meta's new terms and pointing your integration at the new endpoint.
Messaging limits and tiers in 2026
A messaging limit is the number of different people your business can start conversations with in a rolling 24 hours, using templates outside the service window. Replies inside an open window do not count. Messaging the same person twice in a day counts once.
| Limit (different people per 24 hours) | How you reach it |
|---|---|
| 250 | Where every new business portfolio starts |
| 2,000 | Verify your business with Meta, have a partner verify it, or deliver 2,000 templates to different people within 30 days using high-quality templates |
| 10,000 | Automatic |
| 100,000 | Automatic |
| Unlimited | Automatic |
Above 2,000, Meta upgrades you on its own, within about six hours, when your messages are high quality and you used at least half your current limit in the last seven days. You cannot request it and you cannot buy it. Since 7 October 2025 the limit belongs to your whole business portfolio (the Meta account that holds your numbers), not to each phone number. If you run three numbers, one busy number can use up the limit for all three.
What that means in practice:
- Plan the limit before the launch. If you need to invite 4,000 people and you sit at 2,000, half your invites wait a day. Climbing needs a week of real sending at more than half your limit.
- Verify the business early. Business verification, usually with your UAE trade licence, is the quickest way off 250.
- Speed is a separate limit. Each number sends up to 80 messages a second by default. Go faster and you see error 130429. Few UAE businesses ever reach it.
- The free app has no tiers. It has the 256-per-list cap and the saved-contact rule instead.
Quality rating and paused templates
Meta rates your phone number and each template on how people react to them. The main signals are blocks, spam reports and how many people read what you send. Templates are rated green (high), yellow (medium) or red (low).
A template that drops to red is paused: for three hours the first time, six hours the second time, and it is disabled the third time. Sends to a paused template fail with 132015 and cost nothing. A disabled template (132016) cannot come back, so you need a new one with different content. Low quality can also restrict how much a number can send, which shows up as 131048.
What keeps quality up is boring, and it works:
- Only message people who opted in. Bought or scraped lists bring blocks fast.
- Make leaving easy. A person who can reply "stop" leaves quietly. A person who cannot taps "report".
- Send less often than you think. Once or twice a month is welcome for most brands. Weekly blasts teach people to block you.
- Keep it relevant. Segment by what people bought or asked about.
- Warm up a new number. Grow into your limit over days, not with one big send on day one.
Template problems that look like delivery problems
- Wrong language code. Templates are approved per language. Sending an Arabic template with the English language code fails with 132001.
- Variables that don't match. If the template has three blanks and your system fills two, it fails with 132000. Empty fields in your store or CRM are the usual cause.
- Emoji in buttons. In our own submissions, Meta rejected quick-reply buttons that contained emoji. Emoji in the message body was fine.
- Media size. Images can be up to 5 MB, videos and audio 16 MB, documents 100 MB. A failed upload is 131053.
What failures and fixes cost in 2026
Meta changed its UAE prices on 1 October 2026. These are Meta's list rates per delivered message.
- Messages customers send you are free.
- From 1 October 2026, free-form replies inside the 24-hour window (service messages, after the free 1,000) and utility templates sent inside that window are charged. Both used to be free.
- When a customer writes to you from a Click-to-WhatsApp ad, a free entry point window opens. Meta now says it can stay open for up to 7 days, up from 72 hours, and messages inside it are free.
So moving a genuinely transactional message from marketing to utility cuts its Meta price by about 73% and takes it out of the marketing cap at the same time. Our WhatsApp cost guide has worked monthly budgets, and the pricing calculator runs your own numbers.
Is WhatsApp blocked in Dubai?
No. WhatsApp installs and works across all seven emirates. Text, photos, videos, voice notes, documents, groups, Status and WhatsApp Web all work on mobile data and Wi-Fi. Business messaging through Meta's official platform is legal and very widely used. Since 27 August 2024, the UAE's telemarketing rules also cover marketing messages sent through social media apps, so treat WhatsApp marketing with the same care on consent as calls and SMS.
When people say WhatsApp is blocked, they mean calls. Internet calling is called VoIP (voice over internet protocol). TDRA, the UAE's telecoms regulator, says only e& (Etisalat) and du are licensed to provide VoIP, and anyone else can only offer it through them or with TDRA's approval. TDRA also says using unlicensed VoIP apps breaks UAE telecoms law. For years that meant WhatsApp voice and video calls did not connect on UAE networks while messages did. Licensed apps such as Botim, usually with an internet calling plan from e& or du, and work tools such as Zoom and Microsoft Teams filled the gap.
| When | What happened | What officials said |
|---|---|---|
| Nov 2018 | WhatsApp calls suddenly worked for UAE users after an app update | The then TRA said the UAE's VoIP policy had not changed. Calls were blocked again. |
| Feb 2020 | Gulf News found calls worked on some Wi-Fi networks, not on mobile data | No change announced. It faded out. |
| Sep 2021 | During Expo 2020 Dubai, calls connected for many users | Officials described it as a limited test. Calls went back to blocked. |
| Feb 2026 | WhatsApp Web added voice and video calling | Khaleej Times reported that UAE availability still depended on TDRA approval. |
| 25 Sep 2026 | Voice and video calls between UAE numbers connected in our tests, no VPN | No announcement from Meta, TDRA, du or e& when we checked. |
Do not use a VPN to force calls through. TDRA's position on unlicensed internet calling is clear, and the legal risk is yours. If calls do not connect for you, use a licensed app or a normal phone line.
WhatsApp calls in the UAE: what to do as a business
On 25 September 2026 we placed WhatsApp voice and video calls between UAE numbers without a VPN, and they connected. It came as a gradual rollout, so some people had it days before others. Our advice is the same as on the day we tested: use it and test it, but do not rebuild a process on it until someone official confirms the change. Calls started working quietly three times before, and were blocked again each time.
To check on your own phone, update WhatsApp, turn off any VPN, and call a UAE number on mobile data and then on home Wi-Fi. Then try a video call and a group call. In 2020, calls worked on some connections and not others, so test both.
- On the Business app, customers can call your business number when calls connect on their network. Decide who answers, and put your hours on your profile so people are not calling at midnight.
- On the API, calls work differently. Meta's Calling API lets customers call your business for free. To call a customer, you need their permission first, and Meta bills per minute, counted in six-second pulses. Meta lists business-initiated calls to UAE numbers at USD 0.0127 a minute. Calls only ring if calling is switched on and something is connected to answer them: a contact centre, a softphone or a voice agent.
- Keep a normal call button. A plain phone number works on every network, whatever happens to WhatsApp calling next month.
- Keep Botim or your call centre line for now. Calls that started without an announcement can stop the same way.
- Messages are still where the money is. Order updates, quotes, reminders, broadcasts and support never depended on calls.
What we'd do for you, and what we can't promise
When a business tells us its WhatsApp is not working, we run the checks on this page in this order. We confirm app or API, switch on status logging, read the codes, run a utility control, check the limit and template status, and fix categories. Then we report delivered and read numbers, never "sent". We run WhatsApp on Meta's official API, on your own number and your own WhatsApp Business Account, and Meta's message fees pass through with no markup. Pricing is on our WhatsApp page.
What we can't promise is that every message arrives. Nobody can lift Meta's marketing cap, raise your limit on request, or guarantee the category Meta gives a template. Meta decides all three. What we can promise is that you will see every failure while there is still time to reach those people another way.
