How to get the WhatsApp Business API in the UAE
The connection takes ten minutes. The decisions you make before it — which number, which Facebook account, which legal name — are what actually determine how this goes.
Most guides to this are a screenshot tour of a settings page. That is the easy part, and it is not where UAE businesses get stuck. They get stuck because they connected the number the shop runs on and lost the app, or because the name on the trade licence didn't match what they typed into Meta, or because they planned a launch broadcast for a number that was only allowed to message 250 people that day. This is the version with those decisions in it.
The technical part of getting the WhatsApp Business API is genuinely short. You click a button, log in with Facebook, pick a number, and you are live. Ten minutes, maybe fifteen if the OTP is slow. Everything that makes this feel hard happens around that — choosing the right number, having your trade licence in the right state, and understanding what Meta will and won't let you do on day one.
You need three things: a phone number that can receive one verification code, a Facebook account that will own the Business Manager, and — for higher limits and the blue tick — a UAE trade licence whose details match the business name you register. Connection takes minutes. Business Verification takes days.
Decide the number first — everything else follows
This is where people lose a week, and it is always the same mistake: connecting the number the business already runs on, and discovering afterwards that the WhatsApp app they were using every day has stopped working.
You have three real options.
A fresh number. Cleanest path. Buy an Etisalat or du SIM, keep it in a desk phone, use it only for verification. Nothing to migrate, nothing to break. The downside is that you start with a number your customers do not recognise, so you will need to publish it — WhatsApp links, a QR on the packaging, the chat button on your site.
Your existing WhatsApp Business App number, migrated. You keep the number your customers already know, and your chat history can come across. But the app stops working on that number once the API takes over — the API and the app cannot both own a number. If that phone is currently sitting on your counter and three people answer it, plan the switch for a quiet day.
Coexistence. Newer, and the option most UAE businesses actually want once they hear about it. Your number stays on the WhatsApp Business App and connects to the API. Your team keeps replying on the phone; the platform adds automation, a shared inbox and broadcasts on top. You scan a QR from the Business App during setup, and the number has to have been active on the app for at least seven days.
One hard rule regardless of route: the number must not be in use on regular consumer WhatsApp. If it is, you'll need to delete that account first — and you lose those chats.
A +971 number is worth the trouble. UAE customers do notice, and a foreign number on a business claiming to be local reads as exactly what it is. You can technically run the API on any country's number, but if you sell to people in Dubai, get a UAE line.
What Meta needs from a UAE business
There are two different checks and people conflate them constantly.
Connecting a number needs almost nothing — a Facebook login and a number that can receive a code. You can be sending messages the same afternoon.
Business Verification is Meta confirming your company exists. This is what unlocks higher messaging limits and is a prerequisite for the verified badge. For a UAE company you'll want:
- A valid trade licence from your emirate's economic department or free zone authority — DED, DMCC, JAFZA, IFZA, ADGM, whichever applies.
- The legal name on the licence matching the business name you enter in Meta Business Manager. Not the trading name, not the shortened version. This is the single most common rejection.
- A business address and phone number that appear on a document Meta can verify.
- A website or domain associated with the business, ideally with an email address on that domain.
Verification is reviewed by humans and takes days rather than minutes. Start it early, but do not treat it as a blocker — you can connect, build your templates and start messaging while it runs.
The actual sequence
Assuming you're going through a platform with Embedded Signup — the "Login with Facebook" flow — this is what the day looks like.
1. Create the account and pick your region. Sign up, and make sure the account is set to the UAE so you are billed in dirhams and get the right plans. If you arrive through a UAE landing page this is usually handled for you.
2. Start the connection. Settings → WhatsApp → Login with Facebook. A Meta popup opens. Use the personal Facebook account that will administer the business — not a staff member's account they'll take with them when they leave. This is worth thinking about for thirty seconds now rather than fixing in a year.
3. Choose or create the Business Manager. If your company already has one — most do, if you've ever run a Facebook ad — select it. If not, Meta creates one in the flow. Enter the legal business name exactly as it appears on the trade licence.
4. Attach the number and verify. Enter the number, choose SMS or voice call, type in the code. If you're doing coexistence you'll scan a QR from the WhatsApp Business App instead.
5. Set the display name. This is what customers see at the top of the chat, and Meta reviews it. It should be your actual business name. A display name that looks nothing like your registered business is a rejection.
6. You're live. The inbox connects, incoming messages start arriving, and you can reply freely to anyone who writes to you.
Connect your number in about ten minutes
QuickWA runs the official Embedded Signup flow — Login with Facebook, pick your number, done. Coexistence supported if your number is already on the WhatsApp Business App. Billed in AED, 7-day free trial, no card.
Start free trial →Day one is quieter than you expect
New numbers do not get to broadcast to everyone immediately, and this surprises people who were planning a launch campaign.
You start on a limited messaging tier — a cap on how many unique customers you can send template messages to in a rolling 24 hours. Behave well and the cap rises automatically as you send quality traffic and get verified. Behave badly and it does not.
Two consequences worth planning around. First, do not build a launch that depends on messaging twenty thousand people in week one; it will not work. Second, replies to inbound messages are not capped at all — someone messages you, you can talk to them as much as you like. Starting with inbound-driven traffic is both cheaper and faster to scale.
Templates: start them on day one
Any message you send to someone who has not written to you in the last 24 hours has to be a pre-approved template. Approval is usually fast — often minutes — but rejections cost you a cycle, so it is worth getting the categories right the first time.
- Utility — order confirmations, delivery updates, appointment reminders, receipts. Cheap. Keep them strictly transactional; a discount tacked onto the end turns the whole template into marketing.
- Marketing — offers, new arrivals, re-engagement. More expensive and more heavily reviewed.
- Authentication — one-time passcodes only.
If you serve Arabic-speaking customers, submit Arabic versions of the same templates at the same time. Meta treats each language as a separate template, and you do not want to discover the gap the day you need it. Write the Arabic properly — a machine translation of a marketing message reads exactly like a machine translation of a marketing message.
What to do in the first week
Getting connected is not the same as getting value, and the businesses that stall are usually the ones that stop at "the number works".
- Publish the number properly. A wa.me link on the website, a QR on receipts and packaging, the number in your Instagram bio and Google Business Profile. Inbound conversations are free and they lift your limits.
- Set a welcome and an away message. Two minutes of work, and it stops the most common complaint about WhatsApp businesses — silence outside office hours.
- Get the whole team on one inbox. The point of the API is that the business owns the conversation, not whoever's phone it landed on.
- Automate the boring, high-volume messages first. Order updates and appointment reminders are cheap, useful and generate almost no complaints. That is what builds your quality rating.
- Then, and only then, broadcast. Once you have a list that opted in and a number with a healthy rating.
Things that commonly go wrong
Business name mismatch. Meta compares what you typed against the trade licence. "Al Noor Trading LLC" on the licence and "Al Noor" in Business Manager is enough to fail.
The number was on consumer WhatsApp. You must delete that account before the number can be used on the API. People forget it was ever on a personal phone.
The Facebook account belongs to an ex-employee. Fixable, but painful. Decide the owner before you start.
Free-zone licence details that don't match the address. Common with IFZA and similar setups where the registered address is a service address. Make sure the document you upload actually shows what Meta is asking for.
A launch broadcast on day one. Blocked by your messaging tier, and if you push it, damaging to your quality rating before you have built any.
The bottom line
Connecting takes ten minutes; being ready takes a week. Choose the number deliberately, get the legal name exactly right, start Business Verification early and let it run in the background, and spend your first week driving inbound conversations rather than outbound blasts. Do that and by the time your messaging limits lift you'll have a list worth sending to.