GoHighLevel Voice AI Agent Versioning: Drafts, Testing and Rollback Explained

Short answer: GoHighLevel Voice AI agent versioning (Official, in Labs) lets you change an AI phone agent in a separate draft while the live version keeps answering calls. You test the draft with a web call or a real phone call, compare it with earlier versions, then publish it. If something goes wrong, you pick an earlier version and click Make live. Turn it on under Labs, Agent Versioning. It works for prompt-based Standard and Realtime agents, not Flow-Based Builder agents, and keeps up to 20 versions per agent.

Why this matters if an AI agent answers your phone

Before versioning, editing a Voice AI agent meant editing the agent that was taking calls right now. A small prompt change, a new action or a different voice went straight to real callers. If the change made the agent book the wrong calendar or transfer calls to the wrong number, you found out from a customer.

HighLevel listed agent versioning in its LevelUp Day 2026 roundup and published a help article for it. The idea is the same one software teams use: keep a stable live version, work on a copy, test the copy, and only then switch. For a med spa, a home services company or a law office that relies on an AI front desk, that removes most of the risk from routine changes.

What a version includes

According to HighLevel's help article, each saved version holds the full agent setup, not just the prompt:

• The system prompt and agent name
• Voice, model, language and timezone
• Actions, such as booking or call transfer
• MCP integrations and Knowledge Base connections
• Post-call settings

The version history shows version numbers (v0, v1 and so on), who made each one, when, change tags, a Live badge and whether a draft is open. One detail to watch: the highest version number is not always the live one. Always check the Live badge.

How to set up Voice AI agent versioning

1. Turn it on in Labs. Open Labs in the sub-account and enable Agent Versioning. Labs features can change, so try it in one sub-account first.
2. Create a draft. Start from the live version or from any earlier saved version. Creating a draft does not change what callers hear.
3. Make your edits in the draft. Change the prompt, actions, voice or knowledge base. Only one draft can exist per agent at a time.
4. Test the draft. A web call uses your browser microphone and is quick, but it cannot test call transfer. A phone call tests the full path, including transfers.
5. Compare versions. The Changes tab shows removed text in red and added text in green, mainly for prompt edits. The Full configuration tab shows every setting in a version.
6. Publish. Publishing saves the draft as a new version and makes it live.
7. Roll back if needed. Select an earlier version and choose Make live. That version becomes read only, so create a new draft from it for further edits.

Limits and things to know

• 20 versions per agent. Delete old versions when you reach the cap.
• One draft at a time. Two people cannot work on separate drafts of the same agent.
• No Flow-Based Builder support. Agents built with the flow builder are not covered by this feature yet.
• Retired models. Saved versions keep the model they were built with. If a model is retired, you choose a replacement in a draft, accept the change and publish. Test first, because a new model can answer the same prompt differently. This matters right now because Google is retiring a Gemini Live preview model used for realtime voice; see our guide on the Gemini 3.8 Live switch.
• Cost. No separate price has been announced. Test calls still use normal Voice AI minutes.

A simple change routine for service businesses

Versioning only helps if you use it the same way every time. A routine we recommend:

1. Write down what you are changing and why before you open the draft.
2. Keep a short test script: a booking request, a pricing question, an after-hours call and a call that must be transferred.
3. Run the script against the draft with a real phone call, not only a web call.
4. Publish outside your busiest hours and listen to the first few live calls afterward.
5. If bookings or transfers drop, roll back first and investigate second.

Agencies managing several clients should add one more step: note the live version number in the client's records after each publish, so anyone on the team can roll back quickly.

What to do now

• Turn on Agent Versioning in one sub-account and create a draft from your current live agent as a baseline.
• Build your test script and save it where your team can find it.
• If your agent was built with the Flow-Based Builder, keep making careful manual backups until versioning supports it.
• See every other release from the event on our LevelUp 2026 live hub.

Want an AI phone agent that books calls and is set up with a safe change process from day one? See our AI front desk voice agent package, or book a free discovery call.

Yaakov (Koby) Oranski, Founder and CEO of Yotomations

Certified GoHighLevel Admin and Partner. Koby designs CRM migrations, two-way integrations, billing systems and AI agents for service businesses, and writes from the engagements described on this site.

Published 2026-10-29