Skip to content

Arabic test

How we test our Arabic

Customers in Lebanon mix Lebanese dialect, Arabizi, French and English, often in one message. We tested the WhatsApp Assistant on 300 such messages: 299 passed every check.

Latest run:

The result

299 of 300

messages passed every check

0

invented answers

0

wrong hand-overs to a person

2,125 of 2,126 individual checks passed, and the median reply took 2.2 seconds.

Our own test, not an independent audit. We wrote the messages and the checks ourselves, and none was removed or edited after we saw the results.

The result
Kind of messageMessagesPassed every check
Lebanese dialect110110
Arabizi5554
Modern Standard Arabic1010
French4545
English4545
Mixed languages3030
Spanish55

How we tested

  • A fictional café. Demo Café has a fact sheet with a menu, prices, hours, an address, delivery areas and a short FAQ. No real customer or café is involved.
  • 300 fixed messages, written the way people write to a café on WhatsApp in Lebanon: 110 Lebanese dialect, 55 Arabizi, 10 formal Arabic, 45 French, 45 English, 30 mixed and 5 Spanish.
  • The real AI the assistant runs on, not a simulation. Each message went in a fresh chat, on a fixed clock (Thursday 15 October 2026, 11:00 in Beirut). Nothing was sent to WhatsApp.
The topics, and the ways people write

Topics. Prices and totals, opening hours and closed days, holidays, vegan and allergy questions, delivery, address and parking, bookings (dates, group sizes, impossible times), complaints, discounts, events, cancelling or changing a booking, asking for a person, greetings, off-topic questions and attempts to trick the assistant.

Four ways of writing, often in one chat:

  • Lebanese dialect in Arabic letters, such as “شو عندكم نباتي بالمنيو؟”.
  • Arabizi: Arabic written in Latin letters and numbers, such as “2addesh” or “3andkon”. The reply must come back in Arabic letters.
  • Formal Modern Standard Arabic, French and English.
  • Messages that switch language in the middle of a sentence.

A few messages are long run-on texts, the way people dictate. For bookings, the customer then taps Confirm.

What we check in every reply

Code that does not trust the assistant checks each reply on up to seven points:

  • Right language, in Arabic letters for Arabic or Arabizi messages.
  • Correct facts: the prices, hours or answers the customer needed.
  • Nothing invented: no price, discount or promise outside the fact sheet, and never “your booking is confirmed”.
  • Handover when needed, and only then: a discount, an event, today’s free tables, a complaint.
  • Bookings captured exactly as asked (date, time, people, name) after the customer taps Confirm, or not at all.
  • Owner alert for complaints and big requests.
  • Style and speed: one reply per message, at most one emoji, an AI note under the first reply, each reply within 10 seconds.

Six messages and the assistant’s actual replies

Demo café, fictional

Six of the 300, with the replies copied exactly as the assistant wrote them. All six passed every check.

What this test covers

  • A fictional café and 300 messages we wrote, tested on 11 October 2026.
  • Text messages. Voice notes, photos and stickers are passed to a person.

We re-run the same test after changes to the assistant and update the date at the top. Before any assistant goes live, we also test it with you, on your own questions.

Want to see it with your own messages?

Send us ten messages your customers really write, in any mix of languages. We reply within one working day.

Talk to usTalk to the founderWhatsApp: coming soon