How much does an AI chatbot cost in the UAE?
A straight answer on what an AI chatbot actually costs to build and run for a UAE business — the build fee, the monthly running costs, and the hidden line items most vendors leave out of the quote.
“How much does an AI chatbot cost?” is a fair question with an annoying answer: it depends. But it depends on a small number of things you can actually reason about, so this piece gives you the real ranges and the levers that move them — for a UAE business specifically.
This piece is about chat — text agents on your website, WhatsApp and social. If it is a voice agent you are pricing — one that answers the phone — the economics are different, and we break those down separately in what a bilingual voice agent actually costs to run.
The short version
For a custom AI chatbot built around your business, expect a build fee from around AED 45,000, plus running costs charged per conversation that scale with how much you use it.
That range covers a lot of ground, though, so it is worth understanding what sits at each end:
- A simple FAQ bot — answering common questions from your own information, no integrations — sits at the lower end.
- An agent that takes action — checks availability, books, looks up an order, qualifies a lead, writes to your CRM — sits higher, because the value and the effort are both higher.
Off-the-shelf chatbot subscriptions exist for a few hundred dirhams a month, and for a very simple use case they are worth considering. But they answer questions; they rarely do the job, and they are hard to make sound like your business. This article is about the custom kind that actually moves the needle.
What actually drives the price
Five things, in roughly the order they matter.
1. How many of your systems it has to touch. This is the single biggest driver, and it has nothing to do with the AI. A bot that answers from a fixed set of information is straightforward. A bot that has to read your live inventory, your booking calendar and your CRM — and write back to them — is a real integration project. If your systems have clean, documented APIs it is quicker; if they are legacy or closed, it is slower and costs more.
2. Whether it needs Arabic. For most UAE businesses, a bilingual English/Arabic bot is not optional — a large share of your customers expect to be served in Arabic. Handling both properly, including customers who switch between them mid-sentence, adds to both the build and the running cost. It is usually worth it; it is not free.
3. How clean your data is. A chatbot that confidently quotes stock you do not have, or a price that is wrong, is worse than no chatbot. If the data behind it is unreliable, fixing that comes first — and that work is part of the real cost, even though it is not “the bot”.
4. How many channels. A bot on your website is one thing. The same bot live on WhatsApp, Instagram and your phone line from day one is more. For most UAE businesses WhatsApp is the channel that matters most, so we often start there.
5. What happens after launch. In the first month you will review conversations and adjust. That tuning is real, whether it is your team’s time or a retainer. It tapers, but it does not go to zero — your prices and services change, and the bot has to change with them.
The running cost most quotes leave out
Vendors love to quote the build fee and go quiet on what it costs to run. Over two years, the running cost usually exceeds the build. It is charged per conversation and scales directly with volume, so the honest way to think about it is cost per conversation, not a flat monthly figure.
There are also line items that rarely appear in a proposal: conversations where the customer immediately asks for a human (you still pay for those), and the cost of the human escalations themselves. A bot that handles 60% of enquiries is not saving you 60% of your support cost — it is saving you rather less, because the other 40% now costs slightly more than before.
None of this means a chatbot is a bad investment. It means the number you should be comparing against is your current fully-loaded cost per handled enquiry — not the vendor’s headline price.
How to work out whether it pays back
Do this simple sum before you commit to anything:
- Work out what it costs you today to handle one customer enquiry — the person’s time, plus their share of supervision and overhead, divided by how many enquiries they actually handle.
- Compare that against the bot’s cost per resolved conversation — cost per conversation divided by the share it handles without a human.
- Multiply the difference by your monthly enquiry volume.
If the saving comfortably repays the build inside a sensible period, build it. If your volume is low, it may not yet — and it is far cheaper to learn that from a spreadsheet than from a deployment.
There is one important exception: if the enquiries you are currently missing are high-value — a lost sale, a lost booking — the calculation is not about cost saving at all. It is about recovered revenue, and a handful of recovered deals a month can justify the whole thing at volumes well below the cost-saving threshold.
Why we do not publish a fixed price
Because a number without a scope is misleading. Two chatbots that sound identical in a brief can differ several-fold once you look at the systems behind them. We would rather spend thirty minutes understanding your operation and give you a real figure than publish a bracket you would have to unlearn.
If you want that figure for your business, a 30-minute scoping call is free, and we will model the running cost against your current cost per enquiry so the comparison is honest. More on how we scope and quote is on our how we work page, and the detail of what we build is under Agentic AI & Automation.