A change to your AI phone agent went wrong? Go back to the version that worked.
This free guide is for owners running several AI phone agents. It shows what each platform saves, how to go back to a version that worked, and the few things that cannot be undone.
Book a free review of your phone agentsOr read how a safe rollout works
Page updated .
In short
- All three platforms keep older versions of an agent, so going back is usually possible.
- Going back usually means pointing the phone number or the traffic at the earlier version.
- A deleted Retell setup cannot be brought back, and going back does not undo an edit to a shared tool.
Does my platform keep old versions?
Yes. Vapi, Retell and ElevenLabs all keep saved versions of an agent. What differs is the wording and how you go back to one.
- Vapi versions assistants and tools. The docs date the feature to the week of 17 August 2026.
- Retell keeps numbered versions, with drafts you can edit and published versions that cannot be changed.
- ElevenLabs saves a version each time you save to a branch, and a saved version cannot be modified afterwards.
How do I go back?
Point the phone number, the tag or the traffic back at the last version that worked. On Vapi you restore the earlier version, on Retell you move the tag back or make a new draft from the old version, and on ElevenLabs you send all traffic back to the Main branch.
Native version history covers one agent at a time. For several agents, four habits make going back quick.
- Before every change, save a copy of each agent's settings and the version each phone number points at.
- Write the way back as short steps before the change, not during the problem: what to move, who may move it and how you check the result.
- Go back on shared parts separately. Tools, building blocks and shared setups are not undone by going back on an agent, so keep their own copies.
- After going back, check that each agent and phone number points where the steps say, and check the version on a fresh call.
What cannot be undone?
A deleted Retell setup cannot be brought back, according to Retell staff on the Retell community forum. Going back to an older agent version also does not undo an edit to a shared tool.
- Retell staff say a deleted Retell setup cannot be recovered and that no backup or export is kept. Keep your own copy of each script.
- On ElevenLabs, rolling an agent back does not undo an edit to a shared tool, because the earlier version uses the same tool.
- For Retell shared building blocks, the docs we read describe no version history, so an edit has no documented way back. Keep a copy before you change one.
For your developer: the details on each platform
Technical notes for whoever manages your voice agents on Vapi, Retell and ElevenLabs. Every statement comes from the official docs or forum pages in the Sources list.
On Vapi
- Restoring an assistant version takes effect immediately.
- Drafts are per user and do not affect live calls. Publishing creates a numbered version that becomes current. Restoring creates a new version from the old configuration and makes it current. For example, restoring v1 while v2 is current creates v3. Restoring replaces any current draft. Tools restore into a draft and need a publish.
- Rollback steps: restore the earlier assistant version in the dashboard. For a canary, set the bad version to 0 percent in the traffic split. Squads keep version history, but the docs say the dashboard has no control to make an earlier squad version current. The way back is to update the squad with the old member list.
- Script it: save the JSON of every assistant before a fleet change. The docs describe export in the dashboard but no API route for restore, so a scripted rollback means reading the saved configuration and updating the assistant with it. The docs do not spell that out, so test it on one assistant first.
- Vapi GitOps saves a snapshot on every deploy and has list and restore-to-timestamp commands. The docs do not say whether a rollback creates new Vapi versions or overwrites the live configuration.
On Retell
- Retell rolls back by version: create a draft from any past version, or move a tag or number binding back.
- Numbered versions start at V0, drafts can be edited, and published versions are read-only. Each agent starts with prod and staging tags and can have up to 10 tags, according to the docs. A page for comparing agent versions side by side exists.
- The docs example moves the prod tag to V3 and back to V2 to return to the previous configuration. Or create a draft from the earlier version and publish it. If a version has phone numbers or tags attached, remove those assignments before you delete it.
- Script it: keep your own copy of prompts and LLM config. Retell staff on the Retell community forum recommend keeping prompts and configs in your own version control and using the update call instead of creating and deleting.
- The deleted LLM trap: Retell staff on the Retell community forum say a deleted Retell LLM configuration cannot be recovered and that no backup or export is kept. The delete call refuses by default if an agent still uses the LLM, but with force set it deletes anyway and leaves those agents pointing at an LLM that no longer exists.
- The docs we read describe no version history for library subflows, so an edit to one has no documented way back. Keep a copy before you change it.
On ElevenLabs
- ElevenLabs keeps full version history on branches. The versioning page has no revert command, so the practical rollback is to send traffic back to Main or read an older version.
- Versions are created when you save to a branch and cannot be modified afterwards. Branches work like git branches, with an undeletable Main. Deployments split conversations across branches by percentage, and the percentages must total exactly 100. The experiments page says full version history is preserved, enabling rollbacks.
- Rollback steps: deploy 100 percent of traffic back to Main, or retrieve the agent at an earlier version or branch tip by its ID. The versioning page does not mention restore or revert, so confirm the exact step on one agent first.
- Script it: record the version each number and deployment used before a change. Rolling an agent back does not undo an edit to a shared tool, because the earlier version references the same tool ID.
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.
- Vapi docs: assistant versions, restore and export
- Vapi docs: tool versions
- Vapi docs: versioning with squads
- Vapi docs: traffic splitting
- Vapi docs: config as code
- Retell docs: agent versions and tags
- Retell API reference: delete Retell LLM
- Retell docs: conversation flow subflows
- Retell community forum: deleted LLM configuration (topic 2349)
- ElevenLabs docs: agent versioning
- ElevenLabs docs: experiments
- ElevenLabs docs: editing tools
Checked against the Vapi, Retell and ElevenLabs docs on 18 November 2026.