Skip to main content
A Telugu voice agent on Bolna is a regular agent whose transcriber (speech-to-text) and voice (text-to-speech) are both set to Telugu, with a prompt written in Telugu script. This page lists the providers whose Bolna docs confirm Telugu support, the language code to send, and a minimal API example. Bolna’s language code for Telugu is te. Telugu is one of the languages Bolna detects automatically mid-call. If you want one agent that handles both English and Telugu on the same call, start here for the Telugu side, then follow Set up multilingual voice AI agents. For every language, see the languages overview.

Choose a Telugu transcriber

The transcriber turns the caller’s Telugu speech into text. Send the plain code te as transcriber.language, not a locale such as te-IN (Create Agent). For callers in India, the Sarvam page calls Sarvam usually the strongest transcriber choice. Compare all transcribers in Choosing a speech-to-text provider.

Choose a Telugu voice

The voice (synthesizer) speaks the agent’s replies. Most providers require language inside provider_config, so set it to te (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 Telugu script and the voice a Telugu voice. A v4 Flash voice id names its language, as <persona>_te_<use case>.

Write the prompt for Telugu

  • Write in Telugu script, not romanized Telugu. నమస్కారం! మీరు ఎలా ఉన్నారు? rather than Namaskaram! Meeru ela unnaru?. 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 keep those words as they are inside Telugu script text instead of forcing a pure Telugu translation.
  • Set politeness explicitly. Ask for the polite plural (మీరు) rather than the informal singular. A generic “be polite” instruction does not reliably produce it.
  • Read alphanumerics character by character, in English. For OTPs, registration numbers and order IDs, this avoids misheard and mispronounced digits.
  • Leave language switching out of the prompt. Bolna switches languages itself.
The full guidance, with examples, is in Writing prompts in non-English languages.

Create a Telugu 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:
The voice is priya, one of the 16 bulbul:v3 voices that work in every Bulbul language. To use one of the 4 Telugu bulbul:v4-flash voices instead, set model to bulbul:v4-flash and take the voice and voice_id pair from List voices. 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 Telugu transcription most often goes wrong. Bolna has two transcriber fields for this:
  • keywords: a comma-separated list of terms callers say.
  • context: a sentence or two describing the call.
Support for Telugu transcribers:
  • Sarvam: keywords on Sarvam needs saaras:v4, and takes up to 50 terms of up to 64 characters each. context works on every Saaras model.
  • Soniox: reads both. context can run to about 10,000 characters.
  • Smallest AI: reads keywords, with an optional weight per term such as Bolna:5, up to 100 terms. It has no context field.
  • Gemini is not in the provider support table for these fields.
Sarvam transcribes English words in the native script of the call’s language. On a Telugu agent, a boosted term such as PhonePe can come back in Telugu script rather than Latin script.
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. Pronunciation lists work on ElevenLabs and on Cartesia sonic-3 and newer; of these, only ElevenLabs is confirmed for Telugu. On other providers the list is ignored. Write how a word should sound in Telugu script, and keep in mind that each language has its own list. See Control how your agent pronounces words for the dashboard steps, the pronunciation_rules API field and limits.

Serve Telugu and English on one agent

Many callers move between Telugu and English. Bolna handles this in two ways:
  • Code-mixing within a sentence. Sarvam and Soniox transcribe callers who mix English into Telugu; on Soniox, pick the multilingual option. A sentence with a few English words is still treated as Telugu.
  • A full language switch. Add both English and Telugu to one agent with multilingual_config, each with its own transcriber, voice and prompt. Telugu is one of the languages Bolna detects automatically, so with the default “requested or auto detected” trigger the agent follows a caller who moves into Telugu. The multilingual quickstart shows the API shape.
On a multilingual agent, you can also:
  • Start a call in Telugu with "agent_data": { "language": "te" } on POST /call, or an agent_language column set to te in a batch CSV. Inbound calls can return agent_language from your caller data source.
  • Let system messages such as the hangup and “are you still there?” checks follow the active language.
  • Read How language switching works for what does and doesn’t trigger a switch.
Tamil, Telugu, Kannada and Malayalam are closely related, so Bolna decides a switch between them from the grammar of the whole sentence, not a single word. A switch inside this group needs a clearer signal than English to Telugu.

Phone numbers for Telugu agents in India


Next steps

Languages overview

Every language with a guide, and its providers

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 voice catalogs per language

Start a call in a language

Pick the opening language per call, batch row or inbound caller

How language switching works

What does and doesn’t trigger a mid-call switch