Skip to main content
A Hindi voice agent on Bolna is a regular agent whose transcriber (speech-to-text) and voice (text-to-speech) are both set to Hindi, with a prompt written in Devanagari. This page lists the providers whose Bolna docs confirm Hindi support, the settings that matter most for Hindi and Hinglish calls, and a minimal API example. If you want one agent that handles both English and Hindi on the same call, start here for the Hindi side, then follow Set up multilingual voice AI agents. For other Indian languages, see the languages overview. For a summary of every Hindi voice and transcriber on Bolna, see Hindi text to speech.

Choose a Hindi transcriber

The transcriber turns the caller’s Hindi speech into text. Send the plain code hi as transcriber.language; hi-IN is rejected (Create Agent). For callers in India, the Sarvam page calls Sarvam usually the strongest transcriber choice, and the Deepgram page points to Sarvam for better accuracy on Indian languages. Compare all transcribers in Choosing a speech-to-text provider.

Choose a Hindi voice

The voice (synthesizer) speaks the agent’s replies. Most providers require language inside provider_config, so set it to hi (Create Agent). Voice catalogs change over time. Confirm a valid model and voice_id pair with List voices, or preview voices in the Languages tab. See Choosing a text-to-speech provider for a wider comparison.
On Sarvam bulbul:v4-flash, the spoken language follows the script of the text, not language. Keep the prompt in Devanagari and the voice a Hindi voice.

Write the prompt for Hindi and Hinglish

  • Write in Devanagari, not romanized Hindi. नमस्ते! आप कैसे हैं? rather than Namaste! Aap kaise ho?. Native script gives more accurate pronunciation and stops the text being treated as English.
  • Keep common English loanwords in Latin script. Callers say “order”, “OTP” and “support ticket” in English, so write आपका order status check करने के लिए मुझे थोड़ा समय दीजिए। instead of forcing a pure Hindi translation.
  • Set gender and politeness explicitly. For a female persona, ask for consistent feminine verb forms in Hindi.
  • Read alphanumerics character by character, in English. For OTPs, registration numbers and order IDs, this avoids misheard and mispronounced digits.
The full guidance, with examples, is in Writing prompts in non-English languages.

Create a Hindi agent over the API

This uses the same body shape as the API quickstart, with Sarvam for both transcription and voice.
1

Write the agent config

Save this as agent.json:
sampling_rate and encoding are left out because Bolna sets them for Sarvam to match the telephony provider.
2

Create the agent

The response contains the new agent_id.
3

Place a test call

Call the agent with POST /call, as in the API quickstart, and check the transcript with GET /executions/{id}.
To use another provider, swap the transcriber or synthesizer block for one from the provider’s page. Every combination is validated when you create the agent: an unsupported transcriber model and language pair returns 400 Provided language: <language> is not available for the model: <model>.

Improve recognition with keywords and context

Brand names, product names and place names are where Hindi transcription most often goes wrong. Bolna has two transcriber fields for this:
  • keywords: a comma-separated list of terms callers say. On Sarvam this needs saaras:v4, and takes up to 50 terms of up to 64 characters each.
  • context: a sentence or two describing the call. Sarvam reads it on every Saaras model.
Sarvam transcribes English words in the native script of the call’s language. On a Hindi agent, a boosted term such as PhonePe can come back in Devanagari rather than Latin script.
Not every transcriber reads both fields. See Keywords and context for the full provider support table and how to write good terms.

Fix pronunciation of numbers and names

A pronunciation list tells the voice how to say a word: an acronym, a brand name, a place name, or a number such as 56. Pronunciation lists work on ElevenLabs and on Cartesia sonic-3 and newer. On other providers the list is ignored.
  • Write how a word should sound in the script the voice speaks. For a Hindi voice, write नो योर कस्टमर rather than know your customer.
  • Each language has its own list, so 56 can be “five six” in English and पाँच छह in Hindi.
  • A rule only matches text the agent actually says. If the LLM writes a number out in words, a rule for the digits won’t apply, so ask the prompt to keep numbers exactly as written.
See Control how your agent pronounces words for the dashboard steps, the pronunciation_rules API field and limits.

Serve Hindi and English on one agent

Many Indian callers move between Hindi and English. Bolna handles this in two ways:
  • Code-mixing within a sentence. Sarvam, Soniox, AssemblyAI and Gladia transcribe code-mixed speech, and Kalpa Labs speaks Hinglish from one model. A sentence with a few English words is still treated as Hindi.
  • A full language switch. Add both English and Hindi to one agent with multilingual_config, each with its own transcriber, voice and prompt. Hindi is one of the languages Bolna detects automatically mid-call. The multilingual quickstart builds an English and Hindi agent over the API.
On a multilingual agent, you can also:

Phone numbers for Hindi agents in India


Next steps

Multilingual setup

Indian language support by provider, and per-language voices and prompts

Sarvam speech-to-text

Saaras models, language codes and biasing limits

Sarvam text-to-speech

Bulbul models and the Hindi voice catalog

SIP trunks

Bring your own carrier, including Indian carriers

Speech-to-text providers

Every transcriber Bolna supports

Text-to-speech providers

Every voice provider Bolna supports