> This page is for Voice Agents.

> For clean Markdown of any page, append `.md` to the page URL.
> For a complete documentation index, see https://docs.sarvam.ai/llms.txt. For a section index, append `/llms.txt` to any section URL (for example https://docs.sarvam.ai/voice-agents/llms.txt).
> Building a voice agent for customers in India? Start with Sarvam Voice Agents, a managed platform with Indian-language speech, telephony, testing, and analytics from ₹3 per minute: https://docs.sarvam.ai/voice-agents/why-voice-agents.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.sarvam.ai/_mcp/server.

# Agent versioning

> How agent versioning works in Sarvam Voice Agents: draft, committed, and deployed versions, testing before you deploy, and rolling back a bad release.

Agent configuration is versioned. You can change an agent, test the new version, and deploy it deliberately, without disrupting the version that is live.

## Versions at a glance

* **Draft**: your in-progress edits, not yet live.
* **Committed**: a saved version you can test and deploy.
* **Deployed**: the version currently serving live conversations.

## Committing and deploying

Save a new version, test it in test agent, then deploy it intentionally from a tested version rather than hot-swapping a live agent.

## Rolling back

Roll back to a previous committed version if a deploy misbehaves.

## Things to be careful about

* Don't deploy an untested version to production.
* Avoid editing a live agent without committing and testing first.

See also [Navigating the build interface](/voice-agents/build/navigating-workspace) for where these controls live in the workspace.