Key takeaways
- English, Hindi and Hinglish, plus Tamil, Telugu, Marathi, Bengali, Gujarati, Punjabi, Kannada, Malayalam and Odia.
- The agent replies in the prospect's language and keeps product terms as your UI shows them.
- Indian speech-to-text and text-to-speech run on Sarvam, an India-based provider.
- Prospects can interrupt in any of these languages and the agent stops to listen.
Why a Hinglish voice demo matters
Plenty of Indian buyers read English documentation and still think out loud in Hinglish: "Yeh report weekly export ho sakti hai?" (an illustrative example). An English-only agent that stumbles on that sentence feels like a bad call centre. One that answers in the same register feels like a colleague.
Code-mixing is not an edge case to handle later. It is how many demo calls in India actually sound, so it was built in from the start.
How the language switch works
- The agent greets in the language you set and then follows the prospect. If they switch mid-sentence, it follows the switch.
- Product names, menu labels and button text stay as your product shows them, so what the agent says matches the screen.
- Your talk track and qualification questions can be written once in English; the agent asks them naturally in the prospect's language.
- Live captions and a transcript panel help buyers in noisy rooms or on weak connections.
Voices and providers
Speech for English (India) and Indian languages runs on Sarvam's speech-to-text and text-to-speech models. English (US, UK and Australia), Spanish, French, German and more run on Deepgram and ElevenLabs, listed on our sub-processors page, and used only on calls in those languages; see every language the agent speaks. The conversation itself runs on Anthropic's Claude in the United States, which our security page explains.
The design target is a reply in about one second after the prospect stops speaking. That is a PRD target, not a measured result.