Changed your AI phone agent but callers still hear the old version?
This free guide is for owners running several AI phone agents. It explains why callers can keep hearing an old version and gives a five-step check you can run in minutes.
Book a free review of your phone agentsOr read how a safe rollout works
Page updated .
In short
- The phone number, not your latest edit, decides which saved version answers calls.
- Check what the number points at before you change the script again.
- On Retell, a test in the dashboard can sound right while the real phone line still runs an older version.
Why do callers still hear the old version?
Because the phone number, or a saved traffic split, decides which saved version answers, and it may still point at an older one. Your newest edit is saved, but the number has not been moved to it.
Each platform does this a little differently.
- On Retell, a phone number can be tied to one version, and then it keeps answering with that version, not the newer one.
- On Vapi, a saved traffic split keeps the versions it names. Making a new version live does not move any calls to it.
- On ElevenLabs, calls go to the Main branch unless a traffic deployment says otherwise. An edit saved on another branch does not reach callers by itself.
How can I tell which version a phone number uses?
Look at what the number points at, then at which version answered a real call. Retell, Vapi and ElevenLabs all record the version on the call, so you can compare the two.
- Retell: the version setting on the phone number.
- Vapi: the assistant, plus any saved traffic split.
- ElevenLabs: the branch on the phone number, plus any traffic deployment.
What should I check, in order?
Five steps: read the version on a call that sounded wrong, read what the number points at, compare it with the version you meant to make live, check the shared parts, then fix the pointer and prove it with a test call.
- Find a call that sounded wrong and read which version answered it.
- Read what the phone number points at.
- Compare it with the version you meant to make live. If they differ, the script is fine and the pointer is out of date, so do not edit the script again yet.
- Check the shared parts. A tool or building block shared with other agents can keep old behaviour inside a new version, or change an agent without a new version.
- Fix the pointer, then place a test call and read the version on that call.
For your developer: the details on each platform
Technical notes for whoever manages your voice agents on Retell, Vapi and ElevenLabs. Every statement comes from the official docs or forum pages in the Sources list.
On Retell
- A Retell phone number is bound to an agent plus a version reference, so a number pinned to an older version keeps answering with the older prompt.
- Retell agents have numbered versions starting at V0. A new version starts as a draft, and publishing makes it read-only with the same number.
- The version reference on a number can be a version number, "latest", "latest_published" or a tag such as prod. The docs say numbers assigned directly to a version stay on that version.
- Retell staff on the Retell community forum explain the old prompt after publishing as a number pinned to a specific version, and suggest choosing the latest published option.
- Users reported that the dashboard publish dialog stopped attaching the phone number to the new version around May 2026. Retell staff did not confirm it as a deliberate change.
- A staff reply on the Retell community forum also says Test Audio resolves the latest published version directly and bypasses the number binding. A test can sound right while the phone line still runs an older version.
- Outbound calls can be pinned too. In one forum thread, staff describe an outbound agent pinned to version 81 that loaded that version however often it was republished.
- Retell calls carry agent_version and agent_tag.
- Library subflows are shared between agents, so a subflow edit can change an agent without a new version.
- To fix the pointer, set the number to latest published or to a tag.
- The docs we read do not say what happens to a call that is already in progress when a binding changes.
On Vapi
- Vapi inbound calls use the assistant's current published version, or its traffic split if one is saved. A saved split pins the versions it names.
- The Vapi docs say drafts do not affect live calls, and that inbound calls use the current published version. The docs name no per-number version setting.
- With an explicit traffic split saved, the docs say publishing a new version does not move traffic to it. A split can name up to 5 versions.
- Outbound and web calls can pin a version with assistantVersion next to assistantId.
- Squad members either pin a version or follow Latest, which is the default. Tools inside an assistant version are pinned or follow Latest too, so a tool publish can change behavior without a new assistant version.
- Versioning arrived in the week of 17 August 2026. The API reference says the latestVersion field is null while an organization is not yet onboarded to versioning.
- Vapi calls record the assistant version, and exports include it.
- To fix the pointer, remove or update the traffic split.
- The docs do not say whether a plain API update of an assistant writes to a draft or publishes. Test that on one assistant before you script it.
On ElevenLabs
- An ElevenLabs phone number carries an agent, a branch and an environment, and traffic goes to the Main branch unless a deployment says otherwise.
- Versions are immutable snapshots created when you save to a branch. The docs list no separate publish step.
- The phone number API has agent_id, branch_id and environment fields. The environment field resolves environment variables on calls to that number.
- The docs say traffic deployments are not copied, so all traffic goes to the main branch until you deploy traffic to other branches. An edit saved on another branch does not reach callers by itself.
- Conversations can be listed by agent, branch and version.
- To fix the pointer, deploy or merge the branch.
- The docs do not say what a running call does after an edit.
Sources
Official documentation and forum pages this guide relies on, as read on 18 November 2026. Platforms change fast, so check the page before you act.
- Retell docs: agent versions and tags
- Retell API reference: update phone number
- Retell API reference: list calls
- Retell community forum: phone number pinned to a version (topic 3037)
- Retell community forum: outbound agent pinned to an old version (topic 3185)
- Retell community forum: publish dialog and phone numbers (topic 2967)
- Vapi docs: assistant versioning
- Vapi docs: traffic splitting
- Vapi docs: versioning with squads
- Vapi docs: path to production
- ElevenLabs docs: agent versioning
- ElevenLabs API reference: update phone number
- ElevenLabs API reference: list conversations
Checked against the Vapi, Retell and ElevenLabs docs on 18 November 2026.