How to Set Up a WhatsApp AI Agent in the UAE
A step-by-step guide: choosing the route, registering the number, business verification, a secure webhook, the 24-hour window and the handoff to your team.
In the UAE, the customer's first message usually arrives on WhatsApp. Putting an AI agent behind that number — one that replies in seconds, qualifies the enquiry, and hands it to a person — is one of the most valuable automations a business here can make. It is also one where most of the difficulty has nothing to do with AI. It is in Meta's setup: which route to choose, what happens to the app on your phone, verification, the 24-hour rule, and a handful of steps the dashboards do not explain.
This guide walks through setting up a WhatsApp AI agent in the UAE, step by step, including the parts that cost us time when we connected our own number in October 2026.
It deals with setup. For what Meta's terms allow and what messages cost, see the 2026 WhatsApp rules. For connecting conversations to your CRM, see AI integration for CRM and WhatsApp.
The short answer
An AI agent cannot run on the ordinary WhatsApp Business app; it needs the WhatsApp Business Platform, through Meta's Cloud API directly or through a provider. Decide first whether your team still needs the app on that number, because that decides the route. Then: set up a Meta business portfolio and app, register the number, verify your business, connect a secure webhook, design the conversation and the handoff, test on a real phone, and go live with someone watching. Budget for the setup taking days rather than hours, mostly waiting on Meta.
Step 1: Choose the route
There are three ways to put WhatsApp in front of customers, and only two of them support an AI agent.
| Route | AI agent possible? | Cost of the route itself | Good when |
|---|---|---|---|
| WhatsApp Business app | No | Free | A small team replying by hand from a phone |
| Meta Cloud API, direct | Yes | No platform fee; Meta's message charges apply | You have, or a partner provides, the engineering to connect it |
| Through a Business Solution Provider | Yes | A monthly fee to the provider, plus Meta's charges | You want the provider's tools, support, or to keep using the app alongside the API |
The question that usually decides it: does your team want to keep replying from the WhatsApp Business app on the same number?
- If not, the direct Cloud API is the simplest and cheapest. The number moves to the platform, and staff reply through a dashboard or your CRM instead of the phone app.
- If yes, some providers support "coexistence", where the app and the API share one number. It is convenient, but read the conditions: there are typically requirements such as opening the app regularly to keep the connection alive.
When we connected our own number we evaluated both and chose the direct Cloud API, with the team replying from a review page. It removed a monthly fee and a dependency, at the cost of staff no longer using the phone app for that number.
Step 2: Prepare before you touch the dashboard
- A number you control that can receive a verification SMS or call. A UAE mobile or landline both work.
- If that number is already on a WhatsApp app, decide now. For the direct route without coexistence it must be removed from the app first, and the chat history on the phone does not come with it.
- A Meta business portfolio (formerly Business Manager) with an admin who will be available during setup.
- Your trade licence and company details exactly as registered, for business verification.
- A privacy policy page on your website that covers WhatsApp messages. Meta asks for the URL before your app can go live.
- A display name that matches your business. Meta reviews it against its naming rules.
Step 3: Create the app and register the number
In Meta's developer tools you create an app, add the WhatsApp product, and attach it to a WhatsApp Business Account inside your portfolio. You then add your phone number and verify it by code.
One step catches people out. After the number shows as verified, it may still sit in a pending state. It has to be registered with the API, which includes setting a six-digit two-step verification PIN. In our case the dashboard showed the number as verified with no obvious next action; it only became active once we made the registration call. Keep that PIN safe — you will need it again if the number is ever re-registered.
Step 4: Verify the business, and understand the limits until you do
Business verification is a separate process, completed with your trade licence and company details. Until it is done, Meta applies a low ceiling on how many people your business can start conversations with in 24 hours — 250 for a new unverified account. Replies to people who messaged you first do not count against it, so an inbound-only agent can go live before verification. Anything that sends the first message, such as reminders or follow-ups to people who have not written to you, will hit the ceiling quickly.
Start verification on day one. It is the step most likely to take longest.
Step 5: Connect the webhook — securely
Meta delivers each incoming message to an address on your server, called a webhook. Three things matter:
- Verify every request. Meta signs each delivery with your app secret. Check the signature before acting on a message, or anyone who finds the address can send your agent fake conversations.
- Subscribe to the right events — at minimum, messages. It is easy to verify the webhook and forget to subscribe, and then nothing arrives.
- Reply to Meta quickly and do the work afterwards. Meta retries deliveries it thinks failed, so a slow response produces duplicate messages. Handle duplicates anyway.
Store tokens and secrets in the server's configuration, never in code or a shared document.
Step 6: Design the conversation
This is where the AI work actually is, and where most agents are let down.
- Write down the job. What the agent handles, what it never handles, and what a finished conversation looks like — a booked meeting, a qualified lead, a resolved question. See AI employees in the UAE.
- One question at a time. WhatsApp is a conversation, not a form. Answer what the person asked first, then ask the next thing you need.
- Short messages. Phone-screen length, in plain language.
- Arabic and English, from the person's own message. Detect the language from what they write, not their number, and have native speakers review the Arabic. See Arabic AI customer service.
- Be clear it is an assistant. It can have a friendly name and still say what it is if asked, and it should never claim to be a person.
- Never invent. Prices, timelines and commitments come from your approved knowledge or from a person, not from the model.
Meta's rules also matter here. They distinguish an agent that serves your own customers about your own business from a general-purpose AI assistant, and they set out what Meta permits regarding AI and the use of WhatsApp data. Read the 2026 WhatsApp rules before you design the scope.
Step 7: Design the handoff and the 24-hour window
WhatsApp's customer service window shapes everything. When a customer messages you, you can reply freely for 24 hours. After that, you can only send pre-approved template messages until they write again.
That has three consequences for an AI agent:
- Hand off fast. If the agent passes a conversation to a person, that person must reply inside the window or switch to a template. Alert the team immediately, with a summary, not just a notification.
- Give the team somewhere to reply. On the direct route the phone app is gone for that number, so staff need a dashboard or CRM inbox that sends through the API. Once a person has taken over, the agent should stay quiet in that thread.
- Plan the safety nets. What happens when the customer goes quiet halfway through? When nobody on the team picks up? Ours sends the team a partial lead after a set period of silence rather than letting it disappear.
Templates must be submitted and approved by Meta before use, and marketing templates need the recipient's opt-in. Message charges depend on the category and on whether the window is open; the 1 October 2026 changes are covered in the 2026 WhatsApp rules.
Step 8: Test on real phones
- Test from several numbers, in Arabic and English, including the awkward cases: voice notes, images, documents, someone who asks for a person immediately, someone abusive, someone who writes three messages in a row.
- Expect stale caches. If the number was recently moved off the WhatsApp app, phones that chatted with it before may claim it is "no longer on WhatsApp" for a while. Opening a wa.me link to the number, or WhatsApp Web, usually works when the phone app does not.
- Check the whole path, not just the reply: does the lead reach the team, with the right details, in time to act inside the window?
Step 9: Go live, and watch it
Switch the app to live mode, put the number on your website, ads and email signature, and have someone read every conversation for the first week. Real customers will ask things nobody predicted. Fix the knowledge, not just the wording. Then move to reviewing a sample weekly.
In our own case, the first genuine inbound message arrived before our test had finished — a reminder that the moment a number is live, it is live.
What to measure
- Time to first reply, especially outside working hours.
- Share of conversations that reach the intended outcome — booked, qualified or resolved.
- Handoffs, and how quickly a person replied after each one.
- Conversations that went quiet, and at which question.
- Errors found in the weekly review, traced to their cause.
Common mistakes
- Choosing the route without asking the team whether they rely on the phone app.
- Leaving business verification until later, then discovering the daily limit when a campaign starts.
- An unsigned webhook, open to anyone who finds the address.
- No reply path for humans once the app is gone from the number.
- A form disguised as a chat — ten questions before answering the customer's one.
- Ignoring the 24-hour window in the handoff design.
- No one reading the first week's conversations.
How Nexus Labs AI sets up WhatsApp agents
Nexus Labs AI, also known as Nexus Labs UAE, is an AI company in Dubai. We build WhatsApp agents for businesses across the UAE and the GCC — answering, qualifying and following up in Arabic and English, writing to your CRM, and handing off to your team — and we run one on our own number. We handle the Meta setup, the secure connection, the conversation design and the handoff, on the direct Cloud API or through a provider if you need to keep the app. Our AI services page describes the customer response and CRM layers, and you can see it working on a real WhatsApp conversation.
Where to Go Next
Before you start, read the 2026 WhatsApp rules. For what happens after the conversation, AI integration for CRM and WhatsApp. For the sales use case, AI sales agents in the UAE; for support, automating customer service with AI agents. For budgeting, what an AI agent costs. Or talk to us about your number.
Frequently Asked Questions
Can I put an AI chatbot on the WhatsApp Business app?
No. The free WhatsApp Business app is designed for people replying by hand and does not offer an interface for an AI agent. An AI agent needs the WhatsApp Business Platform, accessed through Meta's Cloud API directly or through a Business Solution Provider.
Can I keep using the WhatsApp Business app on the same number?
Only through a coexistence arrangement, which some providers offer, where the app and the API share the number. It usually comes with a monthly fee and conditions such as opening the app regularly. Without coexistence, the number must be removed from the app before it is registered on the API, and staff reply through a dashboard or CRM instead.
Do I need a Business Solution Provider in the UAE?
No. Meta's Cloud API can be used directly with no platform fee, provided someone builds and maintains the connection. A provider adds tools, support and options such as coexistence, for a monthly fee. Meta's own message charges apply either way.
Why does my number show verified but pending?
Verifying the number by code is not the final step. The number must also be registered with the API, which includes setting a six-digit two-step verification PIN. Until that registration is done, the number can remain pending even though it shows as verified.
What is the WhatsApp messaging limit for a new business?
A new, unverified business can start conversations with up to 250 people in 24 hours. Replies to customers who messaged first do not count against this. Completing Meta's business verification raises the limit, so start it as early as possible.
What is the 24-hour rule on WhatsApp?
When a customer messages your business, you can reply freely for 24 hours. After that, you can only send messages using templates that Meta has approved, until the customer writes again. An AI agent's handoff to a person must be designed so the person replies inside that window.
Does a WhatsApp AI agent need a privacy policy?
Yes. Meta asks for a privacy policy URL before an app can go live, and your customers' data is covered by data protection law in any case. The policy should explain what you collect through WhatsApp, why, how long you keep it and who processes it.
How long does it take to set up a WhatsApp AI agent?
The technical connection can be done in a day. Business verification, display name review and template approvals depend on Meta and can take longer, which is why verification should start first. Designing and testing the conversation properly usually takes more time than the setup itself.