A customer who speaks Spanish, Hindi or Arabic usually reaches a business several ways: a phone call, a website chat, a booking link, a reminder email. Many tools handle one of those in the customer's language and the rest in English, so the customer hits a wall halfway through.
Aiva Chat covers each of those channels in the customer's language, from one setup. The coverage isn't the same everywhere, though, and it's worth knowing exactly where it stops before you promise customers anything.
Here is each channel in turn, followed by a table of what's covered and what to test. For the full language list, see the languages page.
Phone calls: 13 languages
Calls have the widest coverage: English, Hindi, Gujarati, Spanish, French, German, Italian, Portuguese, Dutch, Arabic, Mandarin, Japanese and Korean.
You choose how the assistant picks a language on the Voice & Speech page:
- Follow the caller: it greets in the language of your opening line. If the caller's first reply is clearly a full sentence in another language, it switches and stays in that language for the call.
- Two languages: it greets in your first language and moves to the second if the caller speaks full sentences in it. This suits a business with two main customer groups, such as English and Spanish, or Gujarati and Hindi.
- Always one language: every call is in the language you pick.
In every mode, a caller can ask for another language and the assistant switches. It won't switch on its own because of one foreign word, a name or a noisy line. That matters more than it sounds: people mix languages constantly, and a call that flips language on every borrowed word is harder to follow than one that never switches. Our piece on code-switching on a call explains why.
On a call, the assistant answers questions, books appointments, takes messages and transfers to staff, all in the caller's language. You write your business information once, and it's used for every language.
Website chat: the visitor's language
The chat widget on your website replies in the language the visitor writes or speaks. Its own buttons and labels, the parts that aren't the conversation, can be set to English, Spanish, Hindi, Gujarati, Polish or German.
Chat uses the same information and booking rules as calls, so a visitor can book in their own language without leaving the page.
Booking pages and your website: six languages
Booking pages and the one-page website Aiva Chat builds for you come in six languages: English, Spanish, Hindi, Gujarati, Polish and German.
- You choose the page language. Left on default, a page follows its assistant's language when that's one of the six, and is in English otherwise.
- Visitors can switch. A booking page has a language picker under the business name, and the choice carries through every step.
- Dates and times are local. They're shown in the format each language uses.
- Your own text isn't translated. Service names, the intro and any questions you added appear as you wrote them. If you serve two language groups, write those parts in both, or in the one most customers read.
Confirmations and reminders
When someone books, the confirmation and the reminders before the appointment use the booking page's language. Each one has a link where the customer can confirm, move or cancel, and that page is in the same language.
Texting is paused in Aiva Chat while US carrier registration is completed, so these go by email for now.
What's covered, channel by channel
| Channel | Languages | How the language is chosen | Translated for you |
|---|---|---|---|
| Phone calls | 13 | Follow the caller, two languages, or one fixed language | Yes: answers come from your information in the caller's language |
| Website chat | The visitor's language | The language the visitor writes or speaks | Yes, as on calls |
| Chat widget labels | 6 | Set by you | Fixed labels only |
| Booking pages | 6 | Set by you; visitors can switch | Fixed wording only, not your own text |
| Website | 6 | Set by you | Fixed wording only, not your own text |
| Confirmation and reminder emails | 6 | The booking page's language | Fixed wording only |
The pattern is simple. Anything the AI says is in the customer's language. Anything you typed onto a page stays as you typed it.
Anything the AI says comes in the customer's language. Anything you typed onto a page stays exactly as you typed it.
Setting it up for two or more language groups
- List your customers' languages and roughly how many calls each brings. Two main languages point to the Two languages setting, and more than two point to Follow the caller.
- Write the greeting in the language most callers expect. A short greeting with no long sentence is easiest for every caller to answer in their own language.
- Teach the assistant once. Include the words each group uses for your services.
- Set each booking page's language. A business with two groups can run two booking pages, one in each language, and link each where that group will see it.
- Write your own page text in the language of the page.
- Test each language with a real booking, as below.
What to test in each language
- Numbers, prices and times: check the booking it made, not just what it said.
- A switch: start in one language and ask for another.
- A borrowed word: use an English brand name in a sentence in another language. The call should stay put.
- Your service names: say them the way each group says them.
- The whole journey: book on the page in that language, then open the confirmation email and the manage link.
Our list of what to test in a free trial has the rest. If you're comparing this with a phone menu that asks callers to press a number for their language, our piece on why "press 1" fails sets out the difference.
Language pages
Cost
Languages cost nothing extra. Every plan has every language and every feature: $49, $99 or $199 a month in US dollars. Call and AI usage is billed to your own Twilio and OpenAI accounts with no Aiva Chat markup.
Try it
Call +1 (970) 972-0974 in any of the 13 languages and try to book. Then start a 14-day free trial, no card required, and test each language your customers use.
See how it works: the Aiva Chat AI receptionist
Written by
Shyamsinh Parmar
AI Solutions Architect
Shyamsinh designs production AI systems at Woyce AI, the team that builds Aiva Chat, including the real-time voice architecture behind it. Shyamsinh works from the business process down: where AI should act, what needs a person, which models to use, and what each call costs to run.
More posts


