Skip to main content

​
Agent Versioning

Agent versioning lets you capture the full configuration of an agent at a point in time, creating an immutable snapshot you can deploy, compare, or restore later. This is essential for production deployments where you need reproducibility and safe rollbacks.

​
Concepts

The draft is always your working copy. Publishing a version does not affect the draft — you can continue editing freely after publishing.

​
What Is Included in a Version

A published version captures the complete agent state:

​
Publishing a Version

1

Open the agent

Navigate to Build > Agents and select the agent you want to version.
2

Click Save Version

In the agent editor header, click the Save Version button.
3

Name and describe

Enter a version name (e.g. “Production v1”, “Post-holiday update”) and an optional description explaining what changed.
4

Publish

Click Save. The version is created with the next available version number.
Published versions are immutable. You cannot edit a published version. To make changes, edit the draft and publish a new version.

​
Version History

Click the version history button in the agent editor header to open the version history panel. It shows:
  • The current Draft at the top
  • All published versions in reverse chronological order
  • For each version: version number, name, description, author, and publication date

​
Restoring a Version

If you need to revert the draft to a previous configuration:
1

Open version history

Click the version history button in the agent editor.
2

Select a version

Find the version you want to restore.
3

Click Restore

Click the Restore button on the version. The agent’s draft configuration is overwritten with the snapshot data.
Restoring a version overwrites the current draft. If you want to preserve the current draft, publish it as a new version before restoring.

​
Version Pinning (Channels)

By default, phone numbers use the agent’s draft configuration. For production stability, you can pin a phone number to a specific published version.
  1. Navigate to Deploy > Channels
  2. On the phone number, select an agent
  3. Use the version dropdown next to the agent selector to choose a published version (or leave it on “Draft”)
  4. Save the configuration
When a version is pinned, incoming calls on that number use the frozen snapshot — even if you continue editing the draft.
Use version pinning for production numbers and keep the draft for development and testing. This lets you iterate safely without affecting live calls.

​
Version Pinning with A/B Testing

When running an A/B test, each variant can be pinned to a different version independently. For example:

​
Filtering by Version

Published versions integrate with monitoring and analytics:
  • Monitor > Calls: filter the call list by version number to see only calls handled by a specific version
  • Monitor > Analytics: version filter available on dashboards to compare performance across versions
This makes it easy to measure the impact of configuration changes on real call data.

​
Best Practices

Always publish a version and pin it to your production number before going live. This ensures calls are not affected by subsequent edits to the draft.
Names like “V1” are less useful than “Added appointment booking tool” or “French prompt rewrite”. A good name tells you what changed without opening the snapshot.
After deploying a new version, use the version filter in Analytics to compare metrics (call duration, sentiment, automation rate) between the old and new versions.