Skip to main content
Edits in the builder never reach end users on their own. You work on an unpublished copy, and only publishing promotes that work into the live agent. The published version keeps serving conversations while you build and test at your own pace. For how these states appear in the agent library, see Agents, flows, and deployments.
A draft moving through pre-publish validation to a named release with a rollback path, above a version pinning lane where a conversation stays on the release it started on

​
Where you are: the environment chip

The toolbar always shows which environment the builder is editing. The chip is also a switcher, so selecting it opens a menu that moves you between the live flow and any draft. The switcher menu lists the published version under Published · live and every draft under Drafts, with a New draft button at the bottom. The row you are editing carries an EDITING badge.
The environment chip menu open in the builder toolbar, with the published live version under Published, the Drafts section, and the New draft button with the draft count
While a draft is active, the toolbar publish button reads Make live instead of Publish. An eye icon labeled View draft opens the draft’s chat in a new tab. When the current environment holds nothing new, the publish button is disabled and its hover text reads No changes to publish.

​
Drafts

A draft is a full, separate copy of the flow. The New draft dialog describes it as a safe copy to experiment in, with the live agent running untouched. You give it a Draft name, for example summer-sale-flow, and pick a Start from source: Live, Blank flow, or another existing draft.
The New draft dialog with the Draft name field and the Start from selector set to the live version
Drafts are capped per agent, and the cap depends on your plan. When you reach the cap, the dialog shows a limit warning and you must discard a draft before creating another.
If your organization moves to a plan with a lower cap, a daily cleanup deletes the least recently edited drafts above the new cap.
Every draft appears in the Versions & drafts panel, opened from the history icon in the toolbar. The Drafts tab shows the count against the cap, and each draft card carries its name, who edited it last, and four buttons: Draft conversations run separately from production conversations, and they never count as billable conversation usage.

​
Collaboration

Presence avatars in the toolbar show who else has the builder open. An avatar’s status dot changes when that member is actively editing a gambit, which helps you avoid working over each other in the same environment.

​
Publishing

Selecting Publish opens a dialog titled Publish Agent. From a draft, Make live opens the same dialog titled with the draft’s name, so you can confirm which flow is about to go live. The dialog states the version number the release will get.
The Publish Agent dialog with the Version name field, the change description field, the Pre-publish validation panel, and the Publish button naming the next version
Two optional fields become the release record: A Pre-publish validation panel sits above the publish button, and its state changes the button itself: Errors block the release outright. Warnings and skipped validation do not, but the button label changes so the choice is explicit. After a successful publish, the dialog confirms Published Successfully, shows the new version number and time, and offers View Agent. Promoting from a draft card instead opens its own dialog, titled with the draft’s name. It carries the same Version name and release-notes fields, notes that people already chatting are not interrupted, and confirms with Promote to live. Either way, the promoted draft becomes the new version and leaves the Drafts tab.

​
Versions and rollback

The Versions tab of the same panel lists every release, newest first. Each version card shows the version number, the version name and notes, and who published it when. The live version carries a Live badge.
The Versions tab of the Versions and drafts panel with version cards showing the Live badge, Rollback, Export, and Clone to draft buttons
Rollback changes the live agent immediately. New conversations start on the rolled-back version as soon as you confirm.
Selecting Rollback opens a confirmation dialog, and the release happens when you confirm. Rollback only moves the live release to that version. It does not add a version to the list and it does not change the flow you are editing in the builder. Every version stays in the list, so you can move between releases in either direction.

​
Version pinning

Active production conversations stay pinned to the version on which they started. Publishing a new release, or rolling back, never changes a conversation midway. New conversations start on the current live version.