A bilingual Arabic and English AI voice agent answers calls in whichever language the caller speaks, switches mid-call if they do, and follows up on WhatsApp. For a business in Saudi Arabia or the UAE, the details that decide whether it works are dialect handling, how it says names, numbers and addresses, and how it fits local data protection rules. Test those on your own calls before you roll it out.
Callers in the Gulf don't stick to one language. A customer in Riyadh might open in Najdi Arabic, give a plate number in English letters and ask the price in Arabic numerals. A caller in Dubai might be Emirati, Egyptian, Indian or British. A voice agent that only does one language, or does Modern Standard Arabic in a stiff way, will lose a lot of those callers.
We also have an Arabic-language guide written for oil change centers and fuel stations. This post is for GCC operators more broadly: service chains, clinics, real estate offices, retail and any business that takes bookings or enquiries by phone.
What "bilingual" should mean in practice
Many systems say they support Arabic. Ask what that means in detail.
| Capability | What to check |
|---|---|
| Language detection | Does it pick the caller's language from the first sentence, or ask them to press a button? |
| Mid-call switching | If a caller switches from Arabic to English halfway through, does the agent follow? |
| Mixed sentences | Can it understand "أبغى أحجز appointment بكرة الصبح"? Code-switching like this is normal in the Gulf. |
| Dialect understanding | Does it understand Gulf, Najdi, Hijazi, Levantine and Egyptian callers, not only Modern Standard Arabic? |
| Speaking style | Does it reply in a natural, polite Gulf register, or in formal news-broadcast Arabic? |
| Names and numbers | Can it read back an Arabic name, a phone number and a date correctly in both languages? |
| Summaries | Does it write the call summary in the language your staff read? |
The speaking style matters more than most buyers expect. Formal Arabic sounds polite but distant, a bit like a recorded government line. Many businesses prefer a light Gulf or "white" Arabic register that most Arab callers understand. Pick the register your brand would use at the front desk.
Dialects: how to test them
Speech recognition for Arabic has improved a lot, but quality still varies by dialect and by vendor. Don't trust a demo recorded in a quiet room. Run your own test.
- Gather real calls. Pull 20 to 30 recordings from your own lines, with consent, covering the dialects your customers use.
- Write test scripts. Turn common calls into scripts: booking, price question, location, complaint, reschedule.
- Use different speakers. Ask staff and friends from different backgrounds to call in: Saudi, Emirati, Levantine, Egyptian, South Asian English, Western English.
- Add noise. Call from a car, a street, a busy shop. That's where most real calls come from.
- Score each call. Did the agent understand the request, capture the right details, and give the right answer? Note every misheard name or number.
If the agent struggles with one dialect your customers use often, ask the vendor what they can tune. Sometimes the fix is a custom vocabulary list (your branch names, service names, neighborhood names). Sometimes it's a different speech model.
Numbers, names and addresses
These trip up bilingual systems more than anything else.
- Phone numbers. Callers may say digits in Arabic, in English, or mixed. Have the agent read the number back in groups and confirm.
- Plate numbers. Saudi plates combine Arabic and Latin letters with digits. If your business uses plates, test them specifically.
- Names. "Mohammed" has many spellings in English. Store the name in Arabic script when the caller speaks Arabic, and in Latin script when they spell it in English.
- Addresses. Many callers give a landmark or district name rather than a street address. Send a WhatsApp message asking for a location pin instead of trying to capture an address by voice.
- Dates and times. Confirm whether the caller means today or tomorrow, and morning or evening, before booking. Read the final booking back in full.
WhatsApp as the second half of the call
In Saudi Arabia and the UAE, many customers would rather get a WhatsApp message than an email or SMS. A good setup uses the call to understand the need and WhatsApp to finish the job:
- Booking confirmation with date, time, branch and a map link
- A request for a location pin or a photo
- A price quote or brochure
- A reminder the day before
- A short follow-up asking how the visit went
Sending business messages on WhatsApp requires using WhatsApp's business tools and following its rules on templates and opt-in. Ask your vendor how they handle that.
Data protection: the basics
Both Saudi Arabia and the UAE have personal data protection laws that apply to how businesses collect, store and use customer information. Call recordings, transcripts, names and phone numbers all count as personal data. We aren't lawyers, so treat this as a list of questions to bring to your legal adviser, not legal advice.
Questions to answer before going live:
- Disclosure. How do you tell callers the call is recorded, and that they may be speaking with an automated agent?
- Purpose. What do you use the recordings and transcripts for, and is that stated in your privacy notice?
- Storage location. Where are recordings and transcripts stored? Some sectors and some data types have rules on keeping data inside the country.
- Retention. How long do you keep recordings, and who deletes them?
- Access. Who on your team, and at the vendor, can listen to calls?
- Sector rules. Healthcare, finance and government-related work often have extra requirements on top of the general law.
Get these answers in writing from any vendor, and have your adviser review them against the law in each country where you operate.
Where a bilingual voice agent helps most
- After-hours calls. Evening is busy in the Gulf, and many calls come late. An agent can book or take details when the office is closed.
- Peak periods. Weekends, the days before Eid, and evenings during Ramadan can bring call spikes that staff can't cover.
- Multi-branch routing. A caller asking for "the branch near the airport" can be matched to the right location and booked there.
- Lead capture. Real estate, clinics and service businesses can capture every enquiry with the caller's need and budget, then pass it to the right salesperson.
Example calculation: answering every call across branches
Say a business has 10 branches, each gets 25 calls a day, and 15% go unanswered. That's 10 × 25 × 0.15 = 37.5 missed calls a day across the network. If 1 in 4 of those callers would have booked, and an average booking is worth SAR 300, the network misses about 37.5 × 0.25 × 300 = SAR 2,812 a day in first bookings. Use your own call logs and booking values. The method matters more than these example inputs.
How to run a pilot
- Pick one or two branches with steady call volume and a manager who will give feedback.
- Start with after-hours and overflow. The agent only answers calls your team would have missed.
- Review every transcript for the first two weeks. Note misheard words, wrong answers and missed handoffs.
- Tune the vocabulary and the call rules. Add branch names, service names and any phrases the agent got wrong.
- Expand to answering first, then to more branches, once results hold steady.
Where Trilix fits
Trilix builds bilingual Arabic and English voice agents for businesses in Saudi Arabia, the UAE and Canada. Our AI phone agent answers in the caller's language, books into your system, follows up on WhatsApp and feeds call outcomes into one report across branches. For an overview of how it works for multi-location service operators, see our automotive service page.
Want to hear it in your customers' dialect?
We'll set up a test line with your branch names and services so your team can call it in Arabic and English.