Versions and publishing
The assistant configuration is kept in blocks: runtime, conversation, greeting, turn, inactivity, kb, tools, record, hangup, compliance, telephony, order. Each change to a block saves a new block version; this does not affect calls.
Publishing
Section titled “Publishing”Publish takes a snapshot of all current blocks, validates the whole configuration and freezes it as a version with an increasing number (v1, v2, …). Calls that start after that use this version. If the configuration is invalid, nothing is published.
What publishes a version:
- The setup wizard’s Publish the assistant step (the first version).
- Publishing the draft in the Settings tab (greeting, store policies, extra instructions, call length, interruptions). Prompt and policies →
- Publishing the draft in the Voice tab.
- Publishing the dictionary in the Pronunciation tab. If nothing changed, the version stays the same.
- Rolling back to an earlier version in the Versions tab.
- Configuration changes made by the setup team.
If the assistant has another unpublished draft (e.g. a pronunciation draft), publishing is refused; publish or discard that draft first. This way no change goes live unnoticed.
The console shows the Published version number in the assistant header. For an assistant without a version, the Flow tab says “No published release” and it is not listed for test calls.
Tracking
Section titled “Tracking”Every publish is written to the Change History as agent.publish, with who did it and the version number. Settings and voice drafts (agent.settings.*, agent.voice.*) and rollbacks (agent.rollback) are recorded too. Every call record shows which assistant handled it. Change history →
Rolling back to an earlier version
Section titled “Rolling back to an earlier version”Assistants → assistant → Versions lists every version with its date, who published it and the sections that changed. A version’s Roll back to this version button first shows what will change: sections, voice, pronunciation dictionary, settings and the ready phrases that will be regenerated.
- Rolling back doesn’t rewrite history: the old version’s values are copied and published as a new version.
- Only admins can roll back.
- A rollback by your company restores only the fields your company can edit: greeting, store policies, extra instructions, maximum call length (capped at your plan’s limit), interruptions, voice and the pronunciation dictionary. Core instructions, tools, compliance, telephony and knowledge base settings stay as they are.
- If there are unpublished drafts, the rollback discards them; you confirm this separately to continue.
- If the voice or pronunciation changed, ready phrases are regenerated in the background.
© 2026 Erusoft