Which Arabic does it speak, and what happens when the caller switches to English?

Gulf Arabic for UAE callers, with Modern Standard behind it, and the choice is written into the scope rather than left to a dropdown. Switching mid-sentence is the harder half: dialectal speech is thin in the corpora these models were trained on, and a mixed sentence raises the error rate further. So we measure it on your own recorded calls before launch instead of claiming it. Where an engagement cannot fund that work, we say the agent runs in English and the Arabic calls route to a person.

Can it answer on our existing number, or does it need a new one?

Your existing number, in almost every case. The agent sits behind a trunk from the operator that issued the line, so the number on your licence, your listings and your signage is the one it picks up. A vendor-issued number is quicker to switch on and it is the wrong default, because you cannot take it with you and your customers have never seen it. We use one only for a pilot line nobody has been asked to ring.

Our customers message us on WhatsApp. Can the agent take those calls?

No, and no supplier in this market can. Voice and video calling over the internet requires a TDRA licence, so WhatsApp calling is blocked in the UAE while its messaging is not. That is exactly why the phone line still matters here, and why the thread and the line are two separate builds rather than one. What happens to a message after it arrives is a workflow question, and the join it crosses is set out here.

Do we have to tell the caller it is not a person?

No UAE statute requires it today, and we build the agent to say so anyway in its first line. The disclosure that does carry weight is the recording one: where a call is recorded and processed, the caller is told at the start, because consent is the primary basis for that processing under the PDPL. The AI disclosure also improves the call. A caller who knows they are talking to a machine asks shorter questions and gets a better answer for it.

What happens when it cannot answer, and does the caller have to repeat themselves?

It hands over, and no. The handover conditions are agreed before the build, and when one fires the call transfers with the transcript, the number and whatever the agent already collected on the screen of the person taking it. The failure worth designing against is not an agent that is wrong. It is an agent that holds on: a caller trapped in a loop costs more than the call it could not take.

Is recording the call a problem under the PDPL?

Recording is not the problem. Where the audio goes is. A recording is personal data, and sending it to a hosted speech model is a cross-border transfer under Articles 22 and 23 of Federal Decree-Law No. 45 of 2021, for which the federal data protection regulator has published no adequacy list. So it is answered on safeguards: what is processed, where, for how long, and what the caller is told at the start. If you are registered in DIFC or ADGM the federal law is not your regime at all, and mainland UAE is not an adequate destination for either.

When would you tell us to hire a person instead?

When the calls are few, varied, and each worth real money. An agent earns its place on repetition: the same question, at the same hour, several times a day. A brokerage taking 12 calls a day that each turn on judgement should hire, and we will say so on the first call. The split that usually holds is a person for the calls that convert and an agent for the ones that would otherwise reach voicemail. Whether a process is worth automating at all is a separate test we publish.

AI voice agents · UAE

AI voice agents answering calls in Arabic and English.

WhatsApp carries this market’s messages but not its calls, so the phone line does the work. Webzenia builds the agent that answers it on your own number, in Arabic and English.

Tell us which calls are getting lost

What it has to get right

What an AI voice agent must get right.

Three decisions settle whether it works, and none of them is the model: whose number it answers on, which Arabic it hears, and where it stops.

The number it answers on.

A UAE-licensed operator issues the line and a SIP trunk carries the call, so the agent answers the number your listings and your signage already point at. Nothing changes on the caller’s side, and nothing has to be re-published if the supplier does.

The Arabic it hears.

Gulf Arabic and Modern Standard are not one setting with two labels. The variety is decided before the build, on the input side and the output side, then written into the scope or declined in writing rather than implied by a chip.

Where it hands over.

The agent is built to hand over rather than to hold on. A caller who asks for a person gets one, with the call already on screen, so nothing is repeated back from the start and nobody is trapped proving they already explained it.

Where the line is losing calls

The calls it can take.

Not a menu tree with a better voice. The six calls a small team here actually drops, each answered on the first ring.

The call after hours, or in Arabic.

Answered at 21:00, and answered in Arabic when the caller opens in it, with the enquiry logged before anyone reads it in the morning

Output

no enquiry waits on the rota

Any hourArabic or English

The enquiry before anyone qualifies it.

Requirement, timing and budget captured while the caller is still on the line, then routed to the person who should ring back

Output

reps call people who are ready

Captured liveRouted

The booking, and the confirmation.

Slots offered, one taken and the confirmation sent before the call ends, into the calendar your team already keeps

Output

a diary that fills without a call-back

Booked on callCalendar

The call back somebody asked for.

A return call to a customer who requested it, opening on what they asked about. Cold outbound is a licensed activity here under Cabinet Resolution 56 of 2024 and is a separate engagement.

Output

the callback happens the same day

RequestedSame day

The invoice somebody has to chase.

A reminder call to your own customer about an invoice already due, with the payment link sent during the call and the promise logged against the account

Output

fewer invoices chased by a person

Your customersLink sent

The same four questions, all day.

Status, hours, documents and eligibility answered from the record rather than from memory, with anything that needs judgement handed on

Output

the team keeps the calls worth their time

From the recordHanded on

Whose number it answers on

Your own number, or the platform's.

Every platform in this market will give you a number today. What none of them can give you is the number your customers already have.

	The platform’s numberIssued by the voice vendor	Your own numberIssued by a UAE-licensed operator
What the caller sees	A number nobody recognises, with no history behind it.	The number on your licence, your listings and your signage.
Who holds the number	The vendor does. Leaving means telling every customer a new one.	You do. Point the trunk elsewhere and the line keeps working.
Who owns the recording	Shared with a processor whose retention period you did not choose.	You do, with the retention you set and the disclosure in your greeting.
What it costs to move	A number migration, where the vendor permits one at all.	A trunk reconfiguration. The agent is repointed, not rebuilt.
When each is right	A pilot or an internal line nobody has been asked to ring.	When the line is published and has to outlive any one supplier.

Which number to use.

Your own, in almost every case, because the line is the one thing in this build your customers already know by heart. A platform number earns its place on a pilot nobody has been asked to ring, and nowhere else. We settle it on the first call, alongside which systems the call has to write into once it ends, which is the same join a workflow crosses. The line sits inside the wider AI and automation programme, and automation work in Dubai sets out how it runs here.

The UAE context

What is true of a UAE phone line.

Webzenia has worked with Gulf clients since 2018. These three come up on every voice engagement, and not one of them is about the model.

01of 03
The line is still the channelMessages cross, calls do not
WhatsApp here cannot carry a voice call.
Voice and video over the internet need a TDRA licence, so WhatsApp calling is blocked here while its messaging is not. A JLT freight forwarder under DMCC keeps a phone number doing work it has stopped doing in most markets, answered by whoever is nearest, in whichever language the caller opens with.
Our methodThe channel scope is agreed before the build: the line, not the app.
02of 03
A line is harder than a chatGulf dialect, one pass, noisy audio
Gulf Arabic is a different language setting.
A Dubai Silicon Oasis distributor on a free zone licence hears Gulf dialect on the line. Dialectal Arabic diverges from Modern Standard in vocabulary, sound and grammar, and Gulf speech is thin in the corpora these models trained on. A chat gives a second look at the text; a noisy call gives one pass.
Our methodThe variety is fixed in scope, on the input side and the output side.
03of 03
A recording is personal dataPDPL, and two regimes beside it
The recording is the compliance question.
For a Business Bay property-management firm on a mainland DET licence, consent under the PDPL is the primary basis, and sending call audio to a hosted speech model is a cross-border transfer. There is no adequacy list to look it up in. A DIFC or ADGM entity sits under its own regime entirely.
Our methodProcessing location, disclosure and retention settled before the first call.

What the engagement covers

Inside a voice agent build.

Not an API key and a demo number. The six pieces of work between the first flow diagram and a customer being answered.

Designing the call flow.

Every path a caller can take, mapped with you before anything is built: what the agent answers, what it asks for, and where it stops

Output

a flow you sign off

PathsStopping points

The voice, and the Arabic decision.

The agent built and given a voice, with the Arabic variety written into the scope instead of implied by a chip that says the language is supported

Output

a claim you can check

Named in scopeChecked, not claimed

The number and the operator.

A trunk from your own licensed operator into the agent, so the line you already publish is the line it picks up

Output

nothing changes for the caller

SIP trunkYour operator

Where the call is recorded.

The booking, the enquiry and the outcome landing in the systems your team already opens, rather than in a vendor dashboard nobody logs into

Output

the call lands where the work is

CRMCalendar

Tuned on your own calls.

The agent runs against real recordings in Arabic and English until it holds the conversation, and every stumble is listened to rather than counted

Output

it works before a customer hears it

Both languagesReal calls

Reported on calls handled.

What was answered, what escalated and what the agent got wrong, every month, against calls rather than metered minutes

Output

a number you can hold it to

AnsweredEscalated

Our stack

Inside a live call, layer by layer.

A live call is four things happening inside a second, and one more after it. Select one to see where we would use something else.

Twilio

Why Twilio

Elastic SIP trunking lets a voice agent answer a number somebody else issued, which is the only arrangement under which the line survives a change of supplier.

How we excel

We bring your own operator’s trunk to the agent rather than the agent’s number to your customers, so the line on your licence stays the line that rings.

Bring your own trunkClean transferNumber

TwilioYours

VapiTheirs

PlivoMixed

Platform numberTheirs

How the build runs

From the call flow to a live line.

A voice agent is judged in the first ten seconds. The decisions that settle those seconds are taken in week one, not week six.

01Weeks 1 to 2Scoped

Choosing the number and the languages.

We agree which number the agent answers on and who issues it, which Arabic it hears and answers in, and the exact conditions under which it stops and puts a person on. The call flow is then drawn against those three answers rather than against a template, and you sign it off before anything is built.

Numberdecided, with the operator
Arabicvariety named in the scope
Handoverconditions written down

02Weeks 3 to 6Building

Wiring the line and tuning it.

The agent is built, connected to the trunk and wired into the systems the call has to write into. Then it runs against your real recorded calls in Arabic and English, and every place it stumbles is listened to rather than counted, because a word error rate does not tell you which word cost the call.

Trunkconnected on your line
Callstuned in both languages
Systemswired, and read back

03OngoingHeld

Going live, and keeping it sharp.

We watch the first weeks of real calls, because the questions callers actually ask are never quite the ones a flow anticipates. What the agent gets wrong is fixed on a retainer, and what it cannot answer goes back into the flow rather than into a longer prompt.

Callswatched from day one
Fixesheld on a retainer
Escalationsread, not just counted

Reported against calls answered, resolved and escalated, never against minutes billed.

Reported on calls resolved

AnsweredResolvedEscalated

Our commitment

Four promises about the line.

A voice agent fails three ways: callers hang up, the Arabic was never really there, or the recordings end up somebody else’s. We commit against all three.

Tuned on real calls before launch.
The agent runs against your own recordings in both languages and is signed off against the flow before it answers a live line. A demo call proves nothing about a caller in a car park.
A person is always one sentence away.
Every flow has a path to a human, and the call arrives with the transcript and the caller’s details already on screen. Nobody is asked to start again, and nobody is held in a loop to prove the agent tried.
We put the Arabic scope in writing.
Which variety it hears, which it answers in, and what happens when it does not follow, all named in the scope. Where an engagement cannot fund that work we write it down rather than ship a chip that says Arabic is supported.
The number and the recordings stay yours.
The trunk, the number and the call recordings sit in accounts you hold, with the retention you set. Ending the engagement does not take your line with it, and does not strand a recording somewhere you cannot reach.

If the first ten seconds do not hold the caller, it is not finished.

Common questions

AI voice agents, answered.

Gulf Arabic for UAE callers, with Modern Standard behind it, and the choice is written into the scope rather than left to a dropdown. Switching mid-sentence is the harder half: dialectal speech is thin in the corpora these models were trained on, and a mixed sentence raises the error rate further. So we measure it on your own recorded calls before launch instead of claiming it. Where an engagement cannot fund that work, we say the agent runs in English and the Arabic calls route to a person.
FAQ · 01
Your existing number, in almost every case. The agent sits behind a trunk from the operator that issued the line, so the number on your licence, your listings and your signage is the one it picks up. A vendor-issued number is quicker to switch on and it is the wrong default, because you cannot take it with you and your customers have never seen it. We use one only for a pilot line nobody has been asked to ring.
FAQ · 02
No, and no supplier in this market can. Voice and video calling over the internet requires a TDRA licence, so WhatsApp calling is blocked in the UAE while its messaging is not. That is exactly why the phone line still matters here, and why the thread and the line are two separate builds rather than one. What happens to a message after it arrives is a workflow question, and the join it crosses is set out here.
FAQ · 03
No UAE statute requires it today, and we build the agent to say so anyway in its first line. The disclosure that does carry weight is the recording one: where a call is recorded and processed, the caller is told at the start, because consent is the primary basis for that processing under the PDPL. The AI disclosure also improves the call. A caller who knows they are talking to a machine asks shorter questions and gets a better answer for it.
FAQ · 04
It hands over, and no. The handover conditions are agreed before the build, and when one fires the call transfers with the transcript, the number and whatever the agent already collected on the screen of the person taking it. The failure worth designing against is not an agent that is wrong. It is an agent that holds on: a caller trapped in a loop costs more than the call it could not take.
FAQ · 05
Recording is not the problem. Where the audio goes is. A recording is personal data, and sending it to a hosted speech model is a cross-border transfer under Articles 22 and 23 of Federal Decree-Law No. 45 of 2021, for which the federal data protection regulator has published no adequacy list. So it is answered on safeguards: what is processed, where, for how long, and what the caller is told at the start. If you are registered in DIFC or ADGM the federal law is not your regime at all, and mainland UAE is not an adequate destination for either.
FAQ · 06
When the calls are few, varied, and each worth real money. An agent earns its place on repetition: the same question, at the same hour, several times a day. A brokerage taking 12 calls a day that each turn on judgement should hire, and we will say so on the first call. The split that usually holds is a person for the calls that convert and an agent for the ones that would otherwise reach voicemail. Whether a process is worth automating at all is a separate test we publish.
FAQ · 07

Keep exploring

Explore AI and Automation Services

Part ofAI and Automation Services

AI Consulting

What your licence and data regime allow, ranked and costed.

Custom AI Development

Built where your own data beats a hosted model.

AI Chatbot Development

Answers from your documents, in the Arabic customers write.

AI Dialers

Outbound calling built inside the telemarketing rules.

WhatsApp Automation

Threads that finish in writing, in Arabic and English.

Business Process Automation

Rewrite the process for this market, then automate it.

Workflow Automation

Wire the two systems either side of the hand-off.

CRM Development

A CRM that knows which of your companies is selling.

Zoho Implementation

The suite configured around where data sits and how invoices leave.

Next step

Tell us which calls nobody is picking up.

We will tell you which of them an agent should take, which Arabic it would need, and which ones should stay with your team.

Tell us what you need.

What an AI voice agent must get right.

The number it answers on.

The Arabic it hears.

Where it hands over.

The calls it can take.

The call after hours, or in Arabic.

The enquiry before anyone qualifies it.

The booking, and the confirmation.

The call back somebody asked for.

The invoice somebody has to chase.

The same four questions, all day.

Your own number, or the platform's.

What is true of a UAE phone line.

WhatsApp here cannot carry a voice call.

Gulf Arabic is a different language setting.

The recording is the compliance question.

Inside a voice agent build.

Designing the call flow.

The voice, and the Arabic decision.

The number and the operator.

Where the call is recorded.

Tuned on your own calls.

Reported on calls handled.

Inside a live call, layer by layer.

From the call flow to a live line.

Choosing the number and the languages.

Wiring the line and tuning it.

Going live, and keeping it sharp.

Four promises about the line.

AI voice agents, answered.

Explore AI and Automation Services

AI Consulting

Custom AI Development

AI Chatbot Development

AI Dialers

WhatsApp Automation

Business Process Automation

Workflow Automation

CRM Development

Zoho Implementation

Tell us which calls nobody is picking up.