pa. Punjabi is one of the languages Bolna detects automatically mid-call.
If you want one agent that handles both English and Punjabi on the same call, start here for the Punjabi side, then follow Set up multilingual voice AI agents. For every language, see the languages overview.
Choose a Punjabi transcriber
The transcriber turns the caller’s Punjabi speech into text. Send the plain codepa as transcriber.language, not a locale such as pa-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 Punjabi voice
The voice (synthesizer) speaks the agent’s replies. Most providers requirelanguage inside provider_config, so set it to pa (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 Gurmukhi and the voice a Punjabi voice. A v4 Flash voice id names its language, as <persona>_pa_<use case>.Write the prompt for Punjabi
- Write in Gurmukhi, not romanized Punjabi.
ਸਤ ਸ੍ਰੀ ਅਕਾਲ! ਤੁਸੀਂ ਕਿਵੇਂ ਹੋ?rather thanSat Sri Akal! Tusi kiven 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 keep those words as they are inside Gurmukhi text instead of forcing a pure Punjabi translation.
- Set gender and politeness explicitly. These are often carried by verb forms, so name the forms you want for the agent’s persona rather than writing “be polite”.
- 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.
Create a Punjabi 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 The voice is
agent.json:priya, one of the 16 bulbul:v3 voices that work in every Bulbul language. To use one of the 4 Punjabi 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
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}.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 Punjabi 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.
- Sarvam:
keywordson Sarvam needssaaras:v4, and takes up to 50 terms of up to 64 characters each.contextworks on every Saaras model. - Soniox: reads both.
contextcan run to about 10,000 characters.
Sarvam transcribes English words in the native script of the call’s language. On a Punjabi agent, a boosted term such as
PhonePe can come back in Gurmukhi rather than Latin script.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 Cartesiasonic-3 and newer; of these, only ElevenLabs is confirmed for Punjabi. On other providers the list is ignored.
Write how a word should sound in Gurmukhi, 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 Punjabi and English on one agent
Many callers move between Punjabi and English. Bolna handles this in two ways:- Code-mixing within a sentence. Sarvam and Soniox transcribe callers who mix English into Punjabi; on Soniox, pick the multilingual option. A sentence with a few English words is still treated as Punjabi.
- A full language switch. Add both English and Punjabi to one agent with
multilingual_config, each with its own transcriber, voice and prompt. Punjabi 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 Punjabi. The multilingual quickstart shows the API shape.
- Start a call in Punjabi with
"agent_data": { "language": "pa" }onPOST /call, or anagent_languagecolumn set topain a batch CSV. Inbound calls can returnagent_languagefrom 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.
Phone numbers for Punjabi agents in India
- Buy an Indian number in the dashboard through Plivo or Vobiz.
- For commercial or telemarketing calls in India, read How to get 140 & 160-series phone numbers in India for the TRAI and DLT requirements.
- To use numbers from your own carrier, connect it with a SIP trunk.
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

