Skip to main content
Every change you make to an agent happens in a version. Editing never affects the agent your customers are talking to — you edit a draft, publish it when you are happy, and decide separately when callers should get it. That separation is the point. You can experiment mid-morning on a busy agent, leave a draft half-finished over the weekend, and put it live on Monday with one click. If it turns out to be wrong, you go back to the version that worked.

​
Three actions, in order

Save

Stores your work in the draft you have open. Nothing reaches customers.

Publish

Freezes the draft as a numbered version — a permanent record. Still not live.

Make live

Points your customers at a published version. This is the only action they feel.
Publishing does not put a version live. That is deliberate: it lets you prepare a change in advance and choose the moment it takes effect.

​
Versions and drafts

Versions are numbered from V0 — the version your agent started with. Drafts and published versions share one numbering line, so a number is never reused. Gaps in the numbers are normal. If you discard draft V12, the next version is V13 — a spent number is never handed out again, so numbers always mean the same thing in your history.

​
The version panel

Open it from the version chip in the Studio header — it shows the version you are currently looking at, and turns to the accent colour when that is not the live one. Selecting a version loads it into the editor, so every tab — prompt, voice, tools, knowledge bases, Deploy — shows that version’s configuration. From the 3-dot menu on any row you can:
  • Open a draft for editing, or Preview a published version read-only
  • Make live a published version
  • New version from this — start a fresh draft based on any version, including an old one
  • Delete a draft or an unused published version
Live history at the bottom of the panel records who made which version live, and when.

​
Editing a published version

Published versions cannot be changed — that is what makes them a reliable record. You can still open one, read every setting, and click around freely. The moment you actually change something, Vocily offers to create a new draft from that version, and carries your change into it, so you never retype anything.
This is usually the fastest way to make a small fix: open the live version, start typing, and accept the draft when prompted.

​
Naming a version

When you publish, you can give the version a name and a description — “Faster greeting”, “Removed the upsell line”. Both are optional, but they are what turns a list of numbers into something you can read six weeks later. The name is shown next to the number wherever the version appears, including in conversation history. Continue in a new draft is on by default: publishing freezes what you were working on, so Vocily opens a fresh draft from it and you can keep going.

​
Testing a specific version

The test widget always exercises the version you have open, not the live one — the chip in the widget names it, so Draft V3 means you are testing an unpublished draft. This works for all three: Chat, Talk, and Call. A test call is an outbound call, so it can run any version. Switch versions while the widget is open and it follows you.
Inbound calls are the exception. When a customer dials your number, that call always reaches the live version — there is nowhere in an incoming call for a version to be specified. To try a draft over the phone, use the Call test.

​
Phone numbers and versions

The numbers in Deploy → Routing belong to the version, like every other setting. Choosing a number records it on the version you are editing; it starts ringing that agent when you make that version live. This means:
  • Changing a number in a draft changes nothing for customers until you publish and make it live.
  • Rolling back to an older version also restores the number that version recorded.
  • If the number you chose is already answering for a different agent, Vocily tells you at make-live and names that agent. It is never taken away from them silently — release it there first, or point your version at another number.

​
Rolling back

Making an older version live is the rollback. Open the version panel, find the version that worked, and Make live. It takes effect for the next call. Calls already in progress finish on the version they started with, so a rollback never changes a conversation mid-sentence.

​
What each version records

A published version is a complete picture of the agent: prompt and greeting, language, voice and model settings, tools and API tools, knowledge bases, transfer numbers, runtime variables, outcome and analysis settings, widget appearance, and the phone and WhatsApp numbers it answers on. Two things deliberately sit outside versions, because they belong to the agent rather than to a configuration: its name, and its widget public key and allowed domains — a rollback must never re-open a domain you removed or reissue a key you rotated.

​
Which version handled a call

Every conversation records the version that ran it. Open a conversation from Conversation history and the Version field names it — V4, or V4 — Faster greeting if you named it. Draft V4 means the conversation came from testing an unpublished draft, so you can tell your own trials apart from real customer traffic at a glance.

​
Deleting versions

Drafts can be deleted whenever you like. A published version can be deleted once it is no longer live and no unfinished batch is using it. Two versions can never be deleted:
  • The live version. Make another version live first.
  • V0, the version your agent was created with. Every later version descends from it. If you want the agent gone, delete the agent.

​
Permissions

Making a version live is the one action customers feel, so it is gated separately from ordinary editing. See Roles and permissions.