Skip to main content

Voice AI Agent - Create, test, compare and publish

Manage your Voice AI agent versions in ZipLeads. Create and test drafts, compare changes, publish approved updates and restore past versions while calls stay live.

M
Written by Matt Phillips

Voice AI Agent Versioning in ZipLeads lets you create drafts, test changes, compare versions and publish updates without interrupting live calls.

Version history helps you track previous configurations, see what changed and restore an earlier version when needed. Because draft and live versions are kept separate, you can improve your Voice AI agents while callers keep getting a consistent experience.


What is Voice AI Agent Versioning?

Voice AI Agent Versioning is a version control feature. It lets you manage changes to your agent without immediately affecting the configuration used for live calls. Instead of editing the active version directly, you create a draft, make your changes and test them before publishing.

Each saved version is an agent configuration. It can include the agent's prompt, voice, model, actions, MCP integrations, Knowledge Base connections and post-call settings.

Version history also lets you compare configurations, review previous changes and restore an earlier version when necessary.

For example, if you want to update your agent's greeting or change how it answers customer questions, you can make those changes in a draft, test the new behaviour and publish only when you're happy with the results.

Important: Agent Versioning is available through Labs → Agent Versioning. It supports prompt-based Standard and Realtime Voice AI agents. It does not support agents created with the Flow-Based Builder.


Understanding Agent Version History

Version history shows how your agent's configuration has changed over time. Each saved version includes identifying details, so you can review previous configurations, see which version is currently live and pick an earlier version to compare or restore.

The Version history panel shows your agent's saved versions and any current draft.

Each entry can include:

  • Version Number: A numbered identifier such as v0, v1, v2 or v3.

  • Author: The user associated with the version.

  • Timestamp: The date and time associated with the version.

  • Change Tags: Labels showing relevant changes, such as prompt updates.

  • Live Badge: Shows the version currently handling live calls.

  • Draft Status: Shows the editable configuration that hasn't been published yet.

For example, your agent might have v1 marked as Live while v3 is the newest saved version. This means v1 is still the active configuration, even though a newer numbered version exists.

The live version is read-only. To change it, you need to create a draft.

Version Limit: Each Voice AI agent supports up to 20 versions. You can delete older versions to free up space.


Creating and Managing Draft Versions

Drafts give you a separate workspace for changing your agent without touching its active configuration. You can adjust prompts, voice settings, actions and other supported settings while callers keep talking to the live version.

You can create a draft from:

  • The Live Version: Start with the configuration currently used for live calls.

  • A Previous Version: Use an earlier saved configuration as the starting point for new changes.

Each Voice AI agent supports one draft at a time.

When a draft exists, it appears separately in version history, so you can tell the editable configuration apart from saved versions.

Draft and Live Versions

Knowing the difference between draft and live versions helps you avoid accidental changes to live customer conversations.

Feature

Draft Version

Live Version

Purpose

Prepare and test changes

Handle live calls

Editable

Yes

No

Testing

Can be tested before publishing

Can be tested as the active version

Customer Calls

Does not replace the live configuration

Handles live calls

Publishing

Can be published as a new version

Requires a new draft to make changes

Important: Creating a draft doesn't automatically make it live. Your existing live version stays active until a different version is published or made live.


Testing Draft and Live Agent Versions

Testing lets you confirm your agent behaves as expected before customers hear the changes. Voice AI Agent Versioning lets you test draft configurations separately from the version currently handling live calls.

When testing, check which version is selected and any information shown in the Test Audio panel.

  • Draft Testing: Test calls use the draft configuration, so you can check changes before publishing.

  • Live Version Testing: Test calls use the live version, not automatically the newest saved version.

For example, if v1 is live and v3 is the newest saved version, the Test Audio panel may show that test calls run v1 rather than v3.

This helps you avoid testing the wrong configuration.

Available Testing Methods

ZipLeads gives you two main ways to test Voice AI agents.

Web Call

Web Call lets you talk to your agent directly through your browser's microphone.

Use Web Call to check:

  • Welcome messages and greetings.

  • Prompt instructions.

  • Conversation flow.

  • Knowledge Base responses.

  • Supported agent actions.

Web Call doesn't support testing Call Transfer.

Phone Call

Phone Call testing lets you check your agent over a real phone connection.

Use Phone Call when you need to check:

  • Phone-based conversations.

  • The caller experience over a phone connection.

  • Call transfer behaviour.

  • Telephony-dependent settings.

For detailed testing requirements and call logs, see How to Test Voice AI Agents.


Comparing Agent Versions

Version comparison shows you what changed between two configurations before you publish or restore. Instead of checking each setting by hand, you can look at highlighted differences or view the full configuration of a selected version.

The Compare versions window has two views:

Changes

The Changes view highlights the differences between two selected agent versions.

Choose the versions you want to compare using the version dropdown menus.

For system prompt changes:

  • Red Highlighting: Shows content removed from the compared configuration.

  • Green Highlighting: Shows content added to the compared configuration.

  • Change Count: Shows the number of changes found in the comparison.

For example, if a sentence in the agent's system prompt is changed, the comparison highlights the removed and added text.

This makes it easier to spot unintended prompt changes before making a version live.

Full Configuration

The Full configuration view shows the settings stored in a selected version.

Depending on how your agent is set up, this can include:

  • Agent name.

  • Voice.

  • AI model.

  • Billing configuration.

  • Language.

  • Timezone.

  • System prompt.

  • Other supported agent settings and integrations.

Use this view when you want to look at the overall configuration of an earlier version, rather than just the differences between two versions.


Publishing and Restoring Agent Versions

Publishing and restoring let you control which configuration handles live conversations. Publishing puts a new configuration live from a draft. Restoring makes an earlier saved version active again.

1. Publishing a Draft

When you publish an edited draft, ZipLeads creates a new saved version and makes that configuration live.

Publish when you've finished testing a change and want your agent to start using the updated configuration for live calls.

Before publishing, review the changes and make sure the draft behaves as expected during test calls.

2. Restoring an Earlier Version

Restoring lets you go back to a previous supported configuration without rebuilding its settings by hand.

Use the Make live option to activate the selected supported version.

For example, if a recently published configuration isn't giving the results you expected, you can select an earlier version from version history and make it live again.

Once an older version is made live, it becomes read-only. To make more changes, create a draft from that version.

Important: The newest numbered version isn't always the live version. Always check the Live badge to see which configuration is currently active.


Managing Version Limits and Retired Models

Version limits and model availability affect which configurations you can keep and reuse. Understanding these limits helps you manage version history and keep older configurations available when you need them.

1. Version Limits

Each Voice AI agent can keep up to 20 versions.

When you reach the limit, you can delete older versions to make room for new ones.

Review older versions from time to time and keep any that may be useful for comparing or restoring.

2. Retired AI Models

A previously saved agent version may use a model that's no longer supported.

If a model has been retired:

  • The original saved version stays unchanged.

  • You need to select a supported replacement model in an editable draft.

  • The model isn't replaced silently.

  • The replacement needs your consent and must be published.

This makes sure any change to the underlying AI model is intentional.

Tip: Test the replacement model before publishing, as different models may respond differently to the same instructions.


Frequently Asked Questions

Q: Can I create multiple drafts for the same Voice AI agent?

No. Each Voice AI agent supports one draft at a time.

Q: Can I make changes directly to a live version?

No. Live versions are read-only. Create a draft from the live version to make changes.

Q: What happens if the model used by an older version is retired?

You need to select a supported replacement in a draft. The saved version stays unchanged, and the replacement needs your consent and must be published.

Q: Can I compare versions that aren't currently live?

Yes. The comparison window lets you select any saved versions to review.

Q: Why does my agent show a newer version number than the live version?

The newest saved version and the live version aren't always the same. The Live badge shows which configuration is currently active.

Q: Does Agent Versioning support Flow-Based Builder agents?

No. Agent Versioning currently supports prompt-based Standard and Realtime agents, not Flow-Based Builder agents.

Q: What happens when I reach the version limit?

Voice AI agents support up to 20 versions. You can delete older versions to free up space.

Q: Does restoring an older version make it editable?

No. Restoring a version makes it live and read-only. Create a draft from that version to make further changes.

Did this answer your question?