From bilingual to multilingual
From day one, every voice.aai.dev line has answered in natural English and Spanish — not a translated script, but a real conversation held entirely in the caller's language. That covers the two languages most U.S. small businesses hear daily, and for many of our setups it's exactly right.
Some businesses hear more. A firm serving immigrant communities, a shop in a neighborhood where the first language varies house to house — their callers don't all fit two boxes. So voice.aai.dev setups can now be configured for additional languages beyond English and Spanish, using the same natural-voice approach. Which languages, and how they're handled, is part of the hands-on setup conversation, like everything else about your line.
What it sounds like on a call
The mechanics don't change: there's no “press 2” gate and no menu. The caller speaks, voice.aai.dev detects the language, and the whole conversation happens in it — the greeting, the questions, the message-taking. Your post-call email still arrives written for you, in your language, with the recording attached. The full mechanics are in the languages doc.
Why it matters
A caller who isn't comfortable in your greeting's language rarely pushes through it — they hang up and dial a competitor, and the loss never shows up anywhere. We've written up the reasoning, and how to test your own line for it, in the bilingual answering guide. If your callers span more languages than your staff does, call the line and tell voice.aai.dev about your business — language needs are part of every scoping conversation.