Drafts, publishing and versions
Know which settings are live, release a reviewed configuration and restore a previous version safely.
An assistant has a mutable draft and immutable published versions. Saving and publishing are separate actions.
Which configuration is used?
| Surface | Configuration |
|---|---|
| Voice preview | Current voice editor values, including unsaved changes. |
| Flow designer and template preview | Current editor flow or selected template; previewing or editing does not save or publish it. |
| Saved draft → Test draft | Saved assistant draft. |
| Live version → Test live | Published voice configuration, using dashboard test permissions. |
| Knowledge preview | Draft settings and permitted preview sources. |
| Evaluations | Saved draft or published version explicitly selected for the run. |
| Phone, API and customer voice | Published version. |
| Website widget | Published widget and assistant snapshot pinned for that session. |
| WhatsApp text | Chat publication selected for the channel. |
Publish a voice assistant
- Select Save draft and complete your test scenarios with Saved draft → Test draft.
- Open Review & publish in the assistant header.
- Review the saved revision, changed settings and assigned channels, then confirm Publish v….
- Use Advanced → Versions and publishing to inspect versions or configure an allocation, and check each assigned channel.
- Start a new customer session and confirm its version in Logs.
Publishing freezes configuration and selected contracts. Changed MCP schemas require review and republishing. Credentials and current execution permissions remain authoritative; a published version cannot keep using a revoked key or tool.
The Flow editor follows this same process. Applying a template, moving stages or changing routes edits the draft; Test draft and Review & publish require you to save first. Stage layout is saved and versioned with the flow. Publishing from the header replaces any current split traffic allocation with the reviewed version; the review dialog flags this before confirmation.
Widgets have their own draft/publish workflow. WhatsApp's Publish for chat supports a text configuration without requiring the complete voice stack; publish voice separately in the assistant editor when offering calls.
Roll out or restore
If using version allocations, they must total 100%. A visitor receives a stable allocation. Existing conversations keep their configuration; start a new session when checking a release.
Restore as draft copies a previous version into a new draft. It does not immediately roll back live traffic. Review, test and publish that restored draft, then confirm the resulting channel version.
Document review expiry, public disclosure revocation and tool disablement still take effect. Restoring configuration does not restore permissions or make expired evidence usable.
Keep a short record of the release's purpose and passing tests so a future correction has a clear baseline.