Skip to main content
VAW Native vs Vapi, Retell AI and ElevenLabs

Setup and Upkeep: No Provider Keys or Webhook Syncing

What it takes to start and keep running on VAW Native compared with a Vapi, Retell AI or ElevenLabs Pod: keys, concurrency, webhook sync and provider-side changes.

Written By voiceaiwrapper

Last updated 26 days ago

A Vapi, Retell AI or ElevenLabs Pod (an engine or provider connection) runs on an account you manage elsewhere, so it needs keys, matching settings and a webhook sync before VoiceAIWrapper can track its calls. VAW Native runs inside VoiceAIWrapper, so most of that work isn't needed. This article compares what each engine asks of you on day one and every week after, and what goes wrong when someone changes the provider account outside VoiceAIWrapper.

Side by side

TaskVAW NativeVapi, Retell AI and ElevenLabs Pods
Create the PodAlready done. Every organization gets one, named VAW Native Pod.Add it yourself with Add Pod in the Pod selector.
API keysNone.Your provider's keys, checked when you connect. You update them in VoiceAIWrapper whenever you roll them in the provider.
Setup in the providerNone.ElevenLabs needs a webhook created in ElevenLabs first. Vapi and Retell AI need nothing extra before you connect.
ConcurrencySet by VoiceAIWrapper for your plan. You only choose the inbound and outbound split.The total must match your provider's own limit. Vapi: you type it. Retell AI: read from your account. ElevenLabs: set from your subscription when you connect.
Webhook syncNone. Calls run on VoiceAIWrapper, so it already sees every call.Each agent, and each Vapi and Retell AI number, must be synced before campaigns can use it.
Phone numbersConnect a Twilio account once. VoiceAIWrapper then sets up each number for you.Bought and set up in the provider. Vapi and Retell AI numbers are then synced.
Changes made elsewhereAgents, knowledge bases and tools only change in VoiceAIWrapper.Anyone with access to the provider dashboard can change agents, webhooks or numbers. Some changes break call tracking until you sync again.

Getting started on VAW Native

Your VAW Native Pod exists from the moment your organization is created, on every plan, and it can't be deleted. There's nothing to connect, and you can open Agents and start building straight away.

To see what the Pod asks for, open the Pod selector in the header and click the pencil (Edit) on your VAW Native Pod. The Update VoiceAI Pod drawer opens on Update Credentials, but there are no credentials on it. It holds the Pod's name and its settings: how long recordings and transcripts are kept, what callers hear on a number with no agent yet, and Knowledge bases on calls. The note at the bottom reads "VAW Native is the built-in voice engine - no API keys or credentials needed. Your Pod's total concurrency is managed by the platform."

Header Pod selector β†’ pencil (Edit) on the VAW Native Pod β†’ Update VoiceAI Pod drawer on the Update Credentials step: Pod Name, Keep recordings for, Keep transcripts for, When a number has no assistant yet, Knowledge bases on calls, the Webhook signing secret section (secret hidden), and the line 'VAW Native is the built-in voice engine - no API keys or credentials needed.' at the bottom.

The Webhook signing secret on the same drawer is for your own systems. VoiceAIWrapper signs the webhooks this Pod sends you with it, so your server can check they're genuine. You only need it if you receive webhooks from this Pod: agent webhooks, a phone number's inbound webhook, or campaign webhooks. See Verify Webhook Signatures.

The one thing you do connect: Twilio

VAW Native places and answers phone calls through your own Twilio account. Web calls, test calls in the browser and website widgets work without it.

You connect Twilio once with your Account SID and Auth Token. After that, VoiceAIWrapper points each number you add at your agent, and sets up the outbound connection in your Twilio account the first time an agent calls out. See Connect Your Twilio Account to VAW Native.

Getting started on a provider Pod

Each provider takes a few steps more:

  • Vapi: your organization name and ID, private and public keys, and your Vapi Concurrency Limit. See Connect Vapi.
  • Retell AI: your Retell API Key. The concurrency is read from your Retell AI account. See Connect Retell AI.
  • ElevenLabs: create a webhook in ElevenLabs with the URL VoiceAIWrapper gives you, then enter an unrestricted API key and the webhook's ID and secret. See Connect ElevenLabs Agents.

Then sync each agent you'll use, and on Vapi and Retell AI each number too. Syncing points the agent's or number's webhook at VoiceAIWrapper, so calls show up in Call Logs and campaigns can track leads.

Keeping a provider Pod running

On a provider Pod, the Assistants (Vapi) or Agents (Retell AI, ElevenLabs) page shows each agent's state in the Webhook column: Synced, or Sync required with a Sync now button. The Phone Numbers page has the same column for Vapi and Retell AI numbers. Campaign setup also stops you until the agent and number you choose are synced.

A Vapi Pod β†’ Assistants page with one synced and one unsynced assistant: the Webhook URL column shows another address on the unsynced row, and the Webhook column shows the green Synced badge on one row and the amber Sync required link with the Sync now button on the other. Blur any customer webhook domain.

For every detail of what syncing changes in your provider account, see Sync Webhooks So VoiceAIWrapper Can Track Calls.

What breaks when provider settings drift

VoiceAIWrapper reads agents and numbers from your provider account each time you open their pages. Changes made in the provider dashboard show up there, and some of them stop call tracking:

Change made in the providerWhat you'll notice in VoiceAIWrapperFix
An agent's webhook or Server URL is changedThe agent shows Sync required. Its calls stop appearing in Call Logs and campaigns stop tracking them.Click Sync now.
An agent is attached to a synced Vapi or Retell AI numberThe number goes back to Sync required.Click Sync now on the number.
An agent is deletedIt disappears from the agents list. Campaigns that used it need another agent.Choose a new agent in the campaign's Settings.
An API key is rolled or deletedAgent and number pages can't load, and syncing fails.Update the Pod's keys. See Manage Pods: Rename, Update Keys, Switch and Delete.
The ElevenLabs workspace webhook is deleted, disabled or pointed elsewhereCall results stop reaching VoiceAIWrapper, even on agents that show Synced.Restore the webhook in ElevenLabs, or create a new one and update the Pod.
Vapi server messages are turned offVoiceAIWrapper tracks calls with status-update, hang and end-of-call-report. Without them, call progress and results go missing.Turn those messages back on in the assistant's settings in Vapi.
Your provider's concurrency limit changesVoiceAIWrapper keeps using the Pod's old total, so it no longer matches your provider account.Match the Pod's total again. See Split Concurrency Between Inbound and Outbound Calls.

If clients or their developers also have access to the provider account, agree who changes what. A single webhook edit in the provider dashboard can stop a campaign from tracking calls until someone notices Sync required.

Upkeep on VAW Native

There's less to watch, but a few things still matter:

  • Rotating your Twilio Auth Token. Update it in Phone Numbers β†’ Connected telephony accounts straight away. Calls on numbers that use that connection stop working until VoiceAIWrapper has the current token. Re-check tests a connection on demand.
  • The SIP trunk named VAW Native in your Twilio account. VoiceAIWrapper creates it for outbound calls, so don't delete it. Twilio bills you directly for numbers and phone minutes.
  • AI credits. New VAW Native calls and chats pause when your balance runs out. See What Happens When You Run Out of Credits.
  • Total concurrency follows your plan. To change the total, contact support. You can move lines between inbound and outbound yourself.

Frequently asked questions

No. VAW Native agents live in VoiceAIWrapper, so a saved change applies to the next call or chat. There's no webhook to keep in step.

No. Prompt, voice and model changes don't touch the webhook. You only sync again when the webhook or Server URL changes, or when an agent is re-attached to a synced number.

Yes, for web calls, test calls in the browser and website widgets. You need a Twilio account for phone numbers.