OOctwin Platform WhatsApp AI agents

An Arabic WhatsApp AI agent that never asks which language you want.

Most bilingual agents open with a question: Arabic or English? That question is the first thing a customer has to do for you rather than for themselves, and a good number of them answer it by leaving.

An Octwin agent reads the language from the words that arrive. If someone says «السلام عليكم، صباح الخير» the reply is in Arabic — sentence, menu, buttons and text direction — on the first message, before they have done anything but say hello.

Detected from the message, not chosen from a menu

The language is read from the customer’s own words, on the message that arrives. There is no language menu, no "press 1 for English", and no extra AI call spent working it out.

It can only ever choose a language your agent actually speaks, so a detection it cannot serve falls back rather than answering in a language you never wrote.

The whole reply switches, not just the sentence

This is the part that separates a translated agent from a bilingual one. When the language changes, the agent’s sentence changes — and so does the menu underneath it, both lines of every row, the button labels, and the direction the whole message is laid out in.

That is the platform drawing the same list in a second language, not a model improvising a translation on the way out. Right-to-left is a rendering decision, not a string the model has to remember to make.

Arabic customers get the whole product, not a translated menu

Everything the agent can do in English it does in Arabic: the scrollable product carousel, the option list, the booking form, the catalogue, the cart, the payment request, the handover to a person with the conversation attached.

Your own records come with you too — product names, fields and prices are yours, in the languages you store them in.

A default is a starting point, not a ceiling

A pack can declare its own default language — an agent built for a Gulf wholesaler starts in Arabic. Detection still overrides that default the moment a customer writes in something else, which is what makes one agent serve a mixed customer base without you running two.

What works today, and what does not

Questions people ask

Does the customer have to choose Arabic?
No. That is the point. The language is detected from their first message, and the whole reply — including the menu and the text direction — comes back in it.
What if a customer switches language mid-conversation?
Detection runs on the message that arrives, so the reply follows the customer rather than a setting made earlier in the thread.
Does it understand Egyptian or Gulf dialect?
We do not make that claim. What is measured is detection and correct Arabic rendering. Ask for a demonstration with your own customers’ messages rather than taking a dialect claim on trust — from us or from anyone else.
Can one agent serve Arabic and English customers?
Yes — that is the normal case. One agent, one set of flows; the language is decided per message rather than per customer or per number.
Is right-to-left handled properly?
Yes. Direction is part of how the platform renders a message, not something the model is asked to produce, so lists and buttons lay out correctly rather than nearly correctly.

Keep reading

Say hello in Arabic and see what comes back.

Try it on your own website first — nothing is visible to a customer until you decide it is.

Get started free Browse the marketplace