Every team has two versions: the live version callers hear, and the draft that is safe to change. Nothing moves from one to the other until Go live is pressed.
Edits go into a draft
Every change, whether it starts in Builder chat or in the agent editor, autosaves into the draft within seconds. There is no Save button, and no way to publish by accident: publishing is always the explicit Go live press. Versions cover the whole team, so going live publishes all its agents together.
The draft pill
The Builder's command bar shows draft status at a glance. With a draft open, a pulsing amber DRAFT pill shows how many edits exist and when it last autosaved. Click it for the detail: what the draft is based on, a chip for every field that changed, and the reassurance that callers keep hearing the live version. With no draft the pill turns green: LIVE · v3, who published it and when. History, Discard and Go live sit beside it, in the same bar.
Going live
Go live opens a confirm showing the version transition and an AI-written summary of what changed, editable before it is saved onto the version. Calls in progress are never interrupted; new calls use the new version the moment it is live. A toast confirms it: v3 is now live; v2 saved to history.
Rolling back
History lists every version, newest first, with its summary, author and changed-field chips; the live row is marked taking calls now. Restore as draft on any other version makes it the new draft to check, test and publish. Restoring never touches callers. Restoring over a draft with unsaved edits warns first.
Discarding a draft
Discard removes the draft and returns to the live version, untouched. If any endpoints were connected to the draft, the confirm lists them under will be disconnected. Discarding disconnects them.
Numbers, drafts and real callers
Numbers route to the live version, so drafts never answer real callers. One deliberate exception: an endpoint chosen to connect while drafting answers the draft immediately. It is marked connected to draft on the graph and stays connected when the team goes live.
Test buttons always use the draft while one exists. That is the workflow in one line: edit freely, test the draft, go live when it works as intended.