WhatsApp chatbot development in Dubai
WhatsApp agents built on Meta's WhatsApp Business Platform. They answer from live business data, take bookings, chase unpaid invoices, and hand the thread to a person the moment they should. This page also sets out what Meta will ask for before you can send a single message, and what Meta bills on top of the build fee.
Why WhatsApp, and what is different about it in the UAE
WhatsApp lands in the same thread as messages from a customer's family, their landlord, and their supplier. There is no app to install, no password to reset, and no spam folder to lose the message in. That is the whole argument, and it is enough.
Two UAE specifics are worth knowing before you scope anything. First, Meta added AED as a billing currency for the WhatsApp Business Platform on 1 April 2026, so a UAE business is now invoiced for messages in dirhams rather than converted dollars. Second, voice and video calling over apps is a regulated VoIP activity in the UAE. The TDRA publishes a list of approved VoIP applications, which names Microsoft Teams, Zoom, Google Meet, BOTIM and others; WhatsApp is not on that list. Meta does ship a Calling API on the Business Platform, but plan a UAE WhatsApp agent as a text, media and document channel, not a voice one.
Is this the WhatsApp Business app or the WhatsApp Business Platform?
The Platform, and the distinction decides your whole project. The WhatsApp Business app is a phone app a person opens and types into: fine for a shop with one person answering, impossible to connect to your invoicing system. The WhatsApp Business Platform is the programmatic one. Meta documents it explicitly for developers using its APIs and sends everyone else to the WhatsApp Business site.
The part of the Platform most builds use is the Cloud API, which Meta hosts. Alongside it sit the Business Management API for administering the account and a Marketing Messages API. Anything that reads your data, writes to your systems, or answers without a human present has to run there.
What a WhatsApp agent can do
Not a menu tree. An agent that reads what the customer wrote, looks the answer up in a system that is actually authoritative, and replies with it.
Answer from real business data
Order status from your Shopify or Stripe records, an invoice balance from Xero or QuickBooks, a delivery window from your own database. The answer comes from the system of record, not from a model guessing.
Take a booking
Offer the slots that are genuinely free, write the confirmed one into Google Calendar or your scheduling system, and send the reminder as an approved utility template the day before.
Chase an invoice
Read the overdue list from QuickBooks or Xero, send the reminder, accept a payment link or a promise-to-pay date, and write the reply back against the invoice record.
Escalate to a human
On low confidence, on a complaint, on anything touching a refund or a contract, the agent stops, posts the thread into Slack or your helpdesk, and tells the customer a person is picking it up.
It answers in Arabic or English, whichever the customer wrote in, including the mixed Arabic and English that UAE customers actually type. One consequence to budget for: Meta treats each language as its own message template and reviews it separately, so a bilingual reminder is two templates to write and two to get approved.
What this looks like in practice
"Half our WhatsApp messages are people asking where their order is, and one person answers all of them."
Example of a build of this shape. The agent would read each inbound message, pull the order against the customer's phone number from the commerce platform, and reply with the status and the carrier reference. Anything it could not match, anything phrased as a complaint, and anything asking for a refund would be posted into Slack with the full thread attached, and the customer would be told a colleague is taking over. Replies inside the 24-hour customer service window are free-form, so no template approval is needed for the answer itself.
The measurable part is what reaches a human: only the threads that need one.
What Meta requires before you can send a message
This is the part buyers are usually not warned about. None of it is difficult, but it is sequential, it involves Meta reviewing you, and it is the reason a WhatsApp project is not live the afternoon you sign. All of the following comes from Meta's own developer documentation.
A business portfolio and a WhatsApp Business Account
Meta's container for your business assets, holding the WhatsApp Business Account that owns your phone numbers and analytics. Source: Cloud API overview.
A phone number that is not already on WhatsApp
A number currently running in the WhatsApp consumer app or the WhatsApp Business app cannot be registered on the Cloud API until it is deleted from that app first. If you are attached to the number your customers already message, plan the cutover. A new business portfolio may register two numbers, rising to twenty once the business is verified or it reaches the 2,000 messaging tier. Source: business phone numbers.
Meta business verification
Meta verifies the business behind the portfolio. Until then a new portfolio starts at tier 250: a maximum of 250 unique WhatsApp users you can message outside a customer service window in a rolling 24 hours. Verifying the business moves you to 2,000 straight away. You can also reach it without verification by delivering 2,000 high-quality-rated template messages to unique users over a 30-day period, then 10,000, then 100,000, then unlimited as volume and quality hold up. Source: messaging limits.
Approved message templates
A message template is a pre-approved message you are allowed to send when no customer service window is open, in one of three categories: marketing, utility, or authentication. Meta reviews templates automatically on creation and after every edit, and review can take up to 24 hours. Each language counts as its own template and is reviewed separately. Source: message templates.
Opt-in from the customer
Meta requires user opt-in before you send template messages, and the opt-in has to make your business name and your intent clear. A bought list is not opt-in. Source: Cloud API overview.
Optional: the blue checkmark
An Official Business Account displays a blue checkmark next to your name. It requires a verified business portfolio, at least 30 days registered on the platform, an approved display name, and two-step verification enabled on the number. Source: Official Business Accounts.
What does it cost to run, separately from the build?
Meta bills for messages directly. That is a separate line from the build fee, charged to the client's own account and never marked up. Getting this wrong is the most common error on competitor pages, because Meta changed the model and a lot of copy was never updated.
Since 1 July 2025 Meta charges per message, not per conversation. Conversation-based pricing is deprecated. The rules that follow from that:
- Customer service window. When a customer messages you, a 24-hour window opens, measured from their last message.
- Marketing templates are charged whenever they are delivered, window or no window, and they do not qualify for volume discounts.
- Utility and authentication templates are free inside an open customer service window and charged outside it. These two categories do get lower rates as monthly volume rises.
- Free entry point. If a customer reaches you through a Click to WhatsApp ad or a Page button and you reply inside the first 24 hours, a 72-hour window opens in which all messages are free.
- Service replies are about to stop being free. Non-template replies inside the window are free today. From 1 October 2026 Meta bills them per message, at the utility and authentication rates for your market, with no volume tiers. If a vendor is pricing your project on free service messages, that assumption expires.
- Meta's own agent is billed by the token. From 1 August 2026 messages from the Meta Business Agent are charged at USD 2.00 per 1M tokens, covering both the AI and the delivery. Bringing your own model instead puts you on the service-message rate above. Which is cheaper depends on message lengths, so the arithmetic is run against real numbers rather than asserted.
- Rates are per country and per category, based on the recipient's country calling code, and Meta publishes them as rate cards that change on quarterly effective dates. The current card is read the current card with you at scoping rather than printing a number here that goes stale.
What does a WhatsApp chatbot cost to build?
A WhatsApp agent is priced on the same AED bands as any agent build. Meta's message fees above are on top, and they go to Meta.
AED 10,000 to 20,000
Single workflow. One trigger, one or two systems, a human escalation path. Indicatively 2 to 3 weeks of build once Meta approval is moving.
AED 20,000 to 35,000
Three or more systems, branching logic, error handling. Indicatively 3 to 5 weeks.
AED 35,000 to 50,000
Custom logic, compliance constraints, a self-hosted model, or a heavy integration surface. Indicatively 5 to 8 weeks.
A single-workflow WhatsApp agent, one trigger and one system lookup, is the first band by definition. Meta's review steps run in parallel with the build, but business verification sits with Meta, so treat the timelines as build effort rather than a launch date. Ongoing changes and monitoring run on a monthly retainer. How we work sets out the sequence and what we need from you.
When a WhatsApp bot is the wrong choice
Four cases where the answer is not to build one.
- Your customers do not message you on WhatsApp. If the volume arrives by email or through a portal, put the agent there. A WhatsApp channel nobody uses still costs the same to build.
- You want to broadcast to a list you bought. Templates need opt-in, marketing templates are charged on every delivery, and a poor quality rating pulls your messaging tier back down. This is a channel for people who asked to hear from you.
- You need voice. WhatsApp calling is VoIP, and VoIP is regulated in the UAE with WhatsApp absent from the TDRA approved list. If the job is answering the phone, a WhatsApp agent is not it.
- The answer needs a screen. Long comparison tables, a document you want annotated, a dashboard: WhatsApp is a narrow column on a phone. A web or in-app chatbot is the better home for that, and the same knowledge base can serve both.
Under the hood: Meta's Cloud API, with a Ruby on Rails service holding the conversation state, the webhook handlers, and the connections to Salesforce, HubSpot, Xero, QuickBooks, Stripe, Slack, monday.com and Asana. Retries, delivery-status handling and alerting are part of the build, so a failed send is something you find out about rather than something the customer discovers. Where a full AI agent is the right answer, WhatsApp becomes one of its interfaces rather than the whole project.
What do customers ask on WhatsApp?
Send the ten questions the team answers most often. We will tell you which an agent can close on its own, which need a template, and what the Meta approval path looks like for that number.
hello@telora.dev