Skip to content
Voice Agent FleetRequest a free fleet review

Published a new prompt but live calls still use the old one? A five-step check for Vapi, Retell and ElevenLabs

This free guide is for teams running voice agents on Vapi, Retell or ElevenLabs. It shows how each platform decides which version answers a call, then gives a five-step check you can run in minutes.

Checked against the Vapi, Retell and ElevenLabs docs on 18 November 2026.

Request a free fleet reviewOr read how a safe rollout works

Retell: the phone number points at a version

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.

The docs we read do not say what happens to a call that is already in progress when a binding changes.

Vapi: the number picks an assistant, not a version

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.
  • 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.

ElevenLabs: the number points at an agent and a branch

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.
  • The docs do not say what a running call does after an edit.

The five-step check

Read what the live call actually used, read what the number points at, compare the two, then fix the pointer instead of the prompt.

  1. Find a call that sounded wrong and read its version

    Retell calls carry agent_version and agent_tag. Vapi calls record the assistant version, and exports include it. ElevenLabs conversations can be listed by agent, branch and version.

  2. Read what the number points at

    Retell: the version reference on the number. Vapi: the assistant, plus any saved traffic split. ElevenLabs: the branch on the number and any traffic deployment.

  3. Compare it with the version you published

    If they differ, the prompt is fine and the pointer is stale. Do not edit the prompt again yet.

  4. Check the shared parts

    Vapi tools carry their own versions, and Retell library subflows are shared between agents. A pinned tool can keep old behavior inside a new assistant version, and a subflow edit can change an agent without a new version.

  5. Fix the pointer and prove it with a call

    Set the Retell number to latest published or a tag, remove or update the Vapi split, or deploy or merge the ElevenLabs branch. Then place a test call and read the version on that call.

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.

Want someone to review how your fleet ships changes?

The free 30-minute fleet review call covers how your agents are versioned, how a change reaches live calls and how you would roll it back. We ask for no data and no access before the call.

Request a free fleet reviewOr read how a safe rollout works