Skip to main content
Voice AI Pods and Provider Connections

Bolna and Ultravox Pods (Legacy)

New Bolna and Ultravox Pods can no longer be added. Existing ones keep working. See what each can and can't do, and how to move clients to another engine.

Written By voiceaiwrapper

Last updated 26 days ago

You can no longer add new Bolna or Ultravox Pods. If you connected one earlier, it keeps working: your agents, campaigns, leads and call logs are still there, and calls still run. This article explains what these legacy Pods can and can't do, and how to move clients to another engine when you're ready.

Applies to: Bolna and Ultravox Pods connected before these providers were removed from Add Pod. To connect a new provider, see Connect Vapi, Connect Retell AI or Connect ElevenLabs Agents, or use your built-in VAW Native Pod.

What still works

An existing Bolna or Ultravox Pod still appears in the Pod selector, and you can do everything you could before:

  • Switch to the Pod and use its pages: Pod Dashboard, Phone Number Pools, Campaigns, All Leads, Call Logs, Agents and Knowledge Base, plus Phone Numbers on Bolna and Tools on Ultravox.
  • Edit agent prompts and greetings from the Agents page.
  • Run campaigns and manage their leads.
  • Update the Pod's keys and concurrency. Open the Pod selector and click the pencil (or Edit). Bolna asks for Bolna Account Name, API Key and Bolna Account Concurrency. Ultravox asks for Profile Name, API Key, Webhook ID and Concurrency, and checks the Ultravox webhook again when you save.

If you delete a Bolna or Ultravox Pod, you can't add it back, because these providers are no longer offered in Add Pod. Deleting also removes the Pod's campaigns, phone number pools, calls, analytics and client configurations. This can't be undone.

What each Pod can't do

Bolna and Ultravox never had every feature the other engines have. Here's what's missing:

FeatureBolnaUltravox
Phone Numbers pageYesNo. Outbound campaigns use Telephony & caller number instead.
Outbound phone campaignsYesYes
Inbound phone campaignsYesNo ("Ultravox does not offer Inbound orchestration")
Inbound widget campaigns (web widgets)No ("Not supported for this provider")No ("Ultravox does not support web call/chat")
Tools pageNoYes
Chat LogsNoNo
Create agents with VAW AssistantNoNo

New features are built for VAW Native, Vapi, Retell AI and ElevenLabs. To compare engines feature by feature, see Provider Feature Comparison.

Move a client to another engine

You can't switch an existing Pod, campaign or client workspace to a different engine. Instead, you rebuild on the new engine and switch your client over. Your built-in VAW Native Pod is already set up, so it's often the quickest place to move to.

  1. Choose the new Pod. Use your VAW Native Pod, or connect a new provider with Add Pod.
  2. Rebuild the agent. Copy the prompt and greeting from the old agent's Agents page. On VAW Native, see Create an Agent with the AI Agent Builder.
  3. Set up phone numbers on the new Pod. On VAW Native, connect your Twilio account first, then buy a number or use one you already own in Twilio. See Connect Your Twilio Account to VAW Native and Buy a New Phone Number. Twilio charges your Twilio account for any number you buy. On Vapi, Retell AI or ElevenLabs, you get numbers in the provider. See Phone Numbers on Vapi, Retell, ElevenLabs and Bolna.
  4. Export the leads you still need from the old campaigns. See Export Leads.
  5. Create the campaign on the new Pod and import the leads. See Import Leads from a CSV File.
  6. Give the client a new workspace. A workspace's VoiceAI Pod can't be changed after it's created, so add a workspace on the new Pod to the same client account and assign the new agent, numbers and campaign. See Create a Workspace and Assign Assets.
  7. Test, then pause the old campaign. Place a test call on the new setup before you pause the old campaign, so the client isn't left without calls. Test calls are real calls: on VAW Native they use AI credits, and on a BYOK Pod your provider bills you for them.

Keep the old Pod until you no longer need its call history. Call logs, recordings and analytics stay in that Pod and are deleted with it. To keep a copy of the call logs, export them first. See Export Call and Chat Logs.