WhatsApp automation · UAE
WhatsApp carries this market’s messages but not its calls, so a flow cannot hand anyone to a phone. Webzenia builds the thread that completes in writing, in Arabic and English.
Tell us what the thread should doWhat the thread can carry
Three jobs, and the third one is the reason this market is different. Sending, answering, and finishing something that has nowhere else to go.
An Al Quoz F&B producer on a DET mainland licence sends delivery windows to trade buyers who agreed to receive them. Every outbound message is a template that was approved before the campaign existed, and the list is a consent record rather than a contact export.
Where is my order, what are your hours, send me the invoice again. These do not need a human and should never wait for one, so the flow answers them and passes anything with a decision in it to a named person rather than to a queue.
The thread cannot become a call here, so a confirmation, a document or an agreement has to complete inside it. That is a design constraint, not a preference, and it is why a flow copied from another market stops halfway and waits for a phone to ring.
What the work includes
Six pieces of work, each producing something you keep. The first one is the reason the rest can exist at all.
The Business API on your own number, business verification through Meta, and a library of approved templates in Arabic and English, each written to the category it will actually be approved under
a verified sender and templates you can send today
Sequences that fire from something real happening: an order placed, a basket left, a renewal approaching, a document still missing. Each step reads its state from your system rather than from a schedule, so a customer who already paid stops being chased
journeys with a source of truth
The consent is taken at the point the person is already answering questions, with the wording, the timestamp and the source recorded against the contact
a consent record you can produce, rather than an assumption you inherited
Confirmations, reminders and the documents that come back the other way. A Dubai Marina physiotherapy clinic on a DHA facility licence collects an insurance card and confirms an appointment without either side reaching for a phone
a completed exchange, in the thread
One number, several people, and an assignment rule that says who owns a conversation rather than leaving it to whoever looks first. The Arabic thread goes to someone who reads Arabic
a channel that survives an absence
A qualification flow that asks the two questions worth asking, plus the deliverability work behind it: quality rating watched, opt-outs honoured on the spot, sends paced. What else this stack automates is on AI automation in Dubai
a flow and a rating
The app, or the platform
Most of this market is sold the API before anyone asks whether the free app was failing. Sometimes it was not.
| The Business appOne phone, one person | The Business APIA channel, built and run | |
|---|---|---|
| Who can answer | Whoever is holding the phone, and only one of them at a time. | A team on one number, each conversation assigned to a named owner. |
| What is automated | A greeting, an away message and a few saved replies. | Flows that read your systems and act on what is actually true. |
| Messaging first | A broadcast list, capped, and only to people who saved your number. | Approved templates to a consented list, at whatever size it reaches. |
| The template rules | None to speak of, which is why so little may be sent. | Every outbound message reviewed, and the category is not yours to set. |
| If the number is hit | The number goes, and the history goes with it. | A rating you can watch fall, and a pace you can change before it does. |
When one person answers everything, the volume is not beating them, and nothing has to be sent unprompted. That is a real business, and the API buys it very little in exchange for a setup, a verification and a monthly cost. We say so rather than quoting. It earns its place where two people need the same number, or where something has to go out first: a noon and Amazon.ae seller on a DET Trader licence answering where-is-my-order at volume crosses both lines in one week. What tips it is rarely message count. It is whether a conversation now has to be owned.
The UAE context
Webzenia has worked with Gulf clients since 2018. Each of these is a build decision here and a footnote almost anywhere else.
Voice and video over the internet need a licence from the authority, so WhatsApp calling is blocked while its messaging is not. Whatever the flow starts, it finishes in writing. What the phone line does instead is argued on AI voice agents.
Meta reclassifies a utility template it judges to be marketing, and the reclassification changes what the message costs and what consent it needs. A flow designed around the lower-priced category can be repriced by a review, which is why the wording is written to the category from the start.
A Sharjah SAIF Zone manufacturer on a free zone licence does not translate a template, it submits a second one and waits for it. Two languages is two queues, and the register it answers in is a decision of its own, argued on AI chatbot development.
What the engagement covers
Six modules. The first produces no automation at all, and the fifth is the one that decides whether any of it may be sent.
The messages already arriving, sorted by what they actually ask for. Most of what a team calls support turns out to be four questions, and knowing which four decides how much of this is worth building.
Each flow is drawn to a finish rather than to a hand-off, because there is no call to hand off to. Templates are written to the category they will be judged under, in both languages, before either is submitted.
The thread reads order state, booking state and payment state from the systems that own them. Where two systems disagree, the seam is named and settled before a message quotes either of them.
Sent is not delivered and delivered is not read. The quality rating, the delivery rate and the opt-out rate are watched together, because the first one falls after the other two have already told you why.
Who agreed to what, when, and through which form, stored against the contact. Opt-outs are honoured immediately and permanently, and how long a thread is kept is decided rather than defaulted.
Your team runs the inbox, edits the templates and reads the ratings, with a written runbook for the three things that go wrong: a rejection, a rating drop and a flow that stopped firing.
Our stack
Six layers between a message arriving and something happening because of it. Select one to see why it earns its place, and where we argue against it.
The official platform is the only one where a number is genuinely yours, several people can answer it, and a message sent outside the customer-initiated window is permitted rather than tolerated.
We open it on your own number and in your own account, so removing us is a permissions change. A provider who owns the number owns the history attached to it.
How the build runs
The category advertises ten minutes. Verification and a sending ramp are weeks, and the difference is worth knowing before you plan a launch around it.
The account is opened in your name, the number is migrated or provisioned, and business verification goes through Meta with the trade licence and the details that have to match it. Where a number is already in use on the Business app, the migration is planned rather than attempted on a Thursday. Nothing is promised on a date the verification queue controls.
Flows are drawn to a finish, templates are written to the category they will be judged under, and Arabic and English go into the queue together rather than one after the other. A rejection is read as information about the category rather than resubmitted with softer wording. The opt-in capture is built in the same phase, because a flow with nobody consented to receive it is a demo.
Sending starts small and climbs as the quality rating holds, because a new number sending at full volume is the fastest way to lose one. Delivery, reads and opt-outs are watched together, flows are corrected where people are dropping out of them, and the inbox is handed to your team with a runbook. What is automated next across the rest of the business is a separate conversation.
The number, the templates and the consent record are in accounts you hold.
Our commitment
This channel is easy to set up in a way that ends it. These are the four things we hold ourselves to.
Consent is recorded under the PDPL
Consent is the primary lawful basis for most commercial processing here, so an opt-in is a legal record rather than a platform setting. The wording, the timestamp and the source sit on the contact, and an unevidenced list is not messaged.
We protect your delivery rating
Volume climbs as the rating holds and stops when it does not. If a campaign would put the number at risk, it does not run, and you hear the reason rather than a rescheduled date.
Opt-out works immediately
A person who asks to stop is stopped in the thread, in the CRM and in every flow that could have reached them, in both languages, without anybody having to process it by hand.
A named person owns each chat
Every thread has an owner rather than a queue, and the number, the templates, the flows and the consent record sit in accounts you hold with Webzenia added as a user. Leaving costs you a handover, never a rebuild.
Recorded consent, paced sending, accounts you hold.
Common questions
Keep exploring
What your licence and data regime allow, ranked and costed.
Built where your own data beats a hosted model.
Answers from your documents, in the Arabic customers write.
Agents that answer your published line, in Arabic and English.
Outbound calling built inside the telemarketing rules.
Rewrite the process for this market, then automate it.
Wire the two systems either side of the hand-off.
A CRM that knows which of your companies is selling.
The suite configured around where data sits and how invoices leave.
Next step
Tell us what you want WhatsApp to do. We will say what needs the Business API, what the Arabic adds to the timeline, and what has to happen somewhere else.
Tell us what you need.