Skip to main content

Overview

If your business requires data residency in India or you want to achieve the lowest possible latency for calls to Indian phone numbers, you can configure your agent to route calls through Bolna’s Indian servers. This guide explains the configuration requirements to ensure your calls are processed entirely on Indian infrastructure.

Requirements

To route calls through Indian servers, your agent configuration must meet all of the following requirements:

1. Telephony Provider

Use Plivo as your telephony provider.
Twilio is not supported for Indian server routing. If you use Twilio, calls will be processed on US servers.

2. Transcriber (Speech-to-Text)

Use one of these transcription providers:
  • Deepgram
  • Azure
  • Sarvam
  • ElevenLabs
  • Smallest
If using Deepgram, additional requirements apply:
RequirementSupported Values
Modelnova-2, nova-3, and their variants (e.g., nova-2-phonecall, nova-3-general)
Languagehi (Hindi), multi-hi (Multilingual Hindi), en-IN (Indian English)

3. Synthesizer (Text-to-Speech)

Use one of these voice synthesis providers:
  • ElevenLabs
  • Sarvam
  • Azure TTS
  • Cartesia
Some ElevenLabs voices may not be available in the India region. If you encounter issues, try selecting a different voice.

4. LLM (Language Model)

Use one of these LLM providers:
  • Azure OpenAI

5. Provider API Keys

Use Bolna’s default provider integrations. Do not connect your own API keys for the transcriber, synthesizer, or LLM providers.
If you connect your own API keys for any provider (transcriber, synthesizer, or LLM), calls will automatically route through US servers regardless of other configuration settings.

Quick Checklist

Before deploying your agent for Indian server routing, verify:
ComponentRequirementStatus
TelephonyPlivoRequired
TranscriberDeepgram, Azure, Sarvam, ElevenLabs, or SmallestRequired
Deepgram Languagehi, multi-hi, or en-IN (if using Deepgram)Required
SynthesizerElevenLabs, Sarvam, Azure TTS, or CartesiaRequired
LLMAzure OpenAIRequired
Custom API KeysNone connectedRequired

Troubleshooting

If your calls are not routing through Indian servers, check the following:
  1. Telephony Provider: Ensure you’re using Plivo, not Twilio
  2. Deepgram Language: If using Deepgram, verify the language is set to hi, multi-hi, or en-IN
  3. Custom API Keys: Check that you haven’t connected your own API keys for any provider in the Providers section
  4. Provider Selection: Verify all providers (transcriber, synthesizer, LLM) are from the supported lists above