When a Vapi, Retell AI or ElevenLabs Pod Is the Better Fit
The cases where a Vapi, Retell AI or ElevenLabs Pod suits a client better than VAW Native today, and how to run both engines side by side.
Written By voiceaiwrapper
Last updated 26 days ago
VAW Native is the built-in voice engine. There are a few things it doesn't do yet, and some clients are better off staying where they already are. This article lists the cases where a Vapi, Retell AI or ElevenLabs Pod (an engine or provider connection) suits a client better today, and shows how to run both engines side by side so you don't have to choose one for everyone.
This compares only what each engine offers inside VoiceAIWrapper. Your provider's own dashboard may offer more. Check your provider's documentation for anything this article says depends on the provider.
Quick check
If a client needs one of these, plan to use a provider Pod for that client or that use case:
When the client already runs on a provider
Even without a missing feature, a provider Pod can be the simpler choice:
The client has a mature setup. Their agents, prompts, tools and knowledge bases are already tuned in Vapi, Retell AI or ElevenLabs. There's no one-click import into VAW Native, so moving means rebuilding each agent and retesting it. If the setup works, connect their account as a Pod and keep it. VoiceAIWrapper reads their agents straight from the provider, so there's nothing to import.
The client wants to pay the provider directly. Calls on a provider Pod are billed by the provider to whoever owns the connected account. Calls on VAW Native use AI credits from your VoiceAIWrapper organization, so you carry that cost and recover it through your client billing. See Billing: One Balance in AI Credits Instead of a Separate Provider Bill.
The client's team works in the provider dashboard. Changes they make there show up in VoiceAIWrapper the next time you open the agents list.
What you give up on a provider Pod
Choosing a provider Pod is a trade-off. Inside VoiceAIWrapper, provider Pods don't get:
Full agent editing. You and your clients can change the greeting and system prompt. Everything else is changed in the provider's dashboard.
Call Data Extractions, which are VAW Native only.
Upkeep-free setup. Provider agents and numbers need their webhooks synced before VoiceAIWrapper can track their calls. See Setup and Upkeep: No Provider Keys or Webhook Syncing.
For the full list, see Features You Only Get on VAW Native.
Run both side by side
You don't have to pick one engine for your whole agency. Every organization has a VAW Native Pod, and you can connect Vapi, Retell AI and ElevenLabs Pods next to it. Your plan decides which providers you can connect. See Use Several Providers and Organizations in One Account.
How the pieces fit together:
Each Pod is separate. Agents, phone numbers, campaigns and call history belong to the Pod they were created in. Use the Pod selector in the header to move between them.
One client can use both engines. A client account can have one workspace per Pod. Give a client a VAW Native workspace and a Vapi workspace, and their users switch between the two in the portal. See Create a Workspace and Assign Assets.
Each number answers on one engine. Connecting a Twilio number to VAW Native changes its voice settings in Twilio, so its incoming calls go to your VAW Native agent instead of wherever they went before. Use separate numbers for each engine.
Split by job, not only by client. For example, run a client's inbound receptionist on VAW Native, and their outbound campaign, where voicemail detection matters, on Vapi.
Frequently asked questions
Can I move a client to VAW Native later?
Can I move a client to VAW Native later?
Yes. It's a manual move: you rebuild the agent, connect the numbers and recreate the campaigns, and the old call history stays on the old Pod. See Move a Client from Vapi, Retell AI or ElevenLabs to VAW Native.
What happens when a VAW Native outbound call reaches voicemail?
What happens when a VAW Native outbound call reaches voicemail?
VAW Native doesn't detect voicemail yet, so the call counts as answered and the campaign doesn't call that lead again. The agent hears the voicemail greeting like any other speech. Outbound agents built with VAW Assistant have a line in their prompt telling them to leave a short message if they reach voicemail, then end the call, but that relies on the agent recognising the recording from what it hears. End call after silence on the agent's Call Settings tab ends calls that go quiet. See Call Settings: Recording, Silence Timeout and Maximum Call Length. If voicemail handling matters for a campaign, run it on a provider Pod with Consider voicemail as answered set the way you want. See Outbound Dialing Rules: Attempts, Redial Wait, Voicemail and Priority.
Does a provider Pod cost extra?
Does a provider Pod cost extra?
Your provider bills you or your client directly for calls at its own rates. Pay-as-you-go uses paid BYOK connection add-ons. Growth includes 1 connection for Vapi, Retell AI or ElevenLabs in total, with extra connections available as add-ons. Scale includes Vapi, Retell AI and ElevenLabs BYOK connections. See Add-Ons: BYOK Connections, Client Accounts and Team Members.
Related articles
Was this helpful?
More in VAW Native vs Vapi, Retell AI and ElevenLabs
Provider Feature ComparisonVAW Native Compared with Vapi, Retell AI and ElevenLabsSetup and Upkeep: No Provider Keys or Webhook SyncingBilling: One Balance in AI Credits Instead of a Separate Provider BillStill need help? Share an idea