Terminology mapping
Differences worth knowing before you port anything
Wait for completed, not the disconnect event
call-disconnected fires the moment the line drops, before duration, cost, recording and extracted data are populated. The completed status arrives a few seconds later with everything filled in. See Call statuses.Keys are per workspace, not per agent
Provider credentials are added once under Connect provider credentials and reused across agents.
Telephony is a choice, not a default
You can buy a number from Bolna, connect Twilio, Plivo, Exotel or Vobiz, or register your own SIP trunk. India-specific paths (140/160-series numbers, DLT) are documented separately.
Indian languages are first-class
Per-language transcription and voice providers are configurable on one agent — see Set up a multilingual agent.
Porting an agent
1
Recreate the agent
Paste your existing system prompt into the Agent tab, or send it to
POST /v2/agent. Start with the preferred models rather than matching your old provider exactly — swap later if quality demands it.2
Re-declare your tools
Tools are declared per agent on the Tools tab. Call transfer and calendar actions are built in; anything else is a custom API call.
3
Point your number at Bolna
Either buy a number or connect the account or trunk your number already lives on.
4
Re-point your webhook
Set the webhook URL on the Extractions tab and whitelist Bolna’s three source IPs — see Get results with webhooks.
5
Compare on real calls
Run the same 20 calls through both systems before switching traffic. Test before you call real customers covers what to check.