Publishing a Bot

Publishing creates an immutable, versioned snapshot of your bot that can be deployed to channels. This separates development changes from what end users experience.

Version Lifecycle

Every bot exists in one of the following states:

State	Description	Editable?
Draft	Work in progress, only visible in the builder	Yes
Published	Active version serving live traffic	No
Archived	Previous version retained for rollback	No

TIP

Only one version can be Published at a time per bot. Publishing a new version automatically archives the previous one.

How to Publish

1. Open your bot in the Flow Builder
2. Click Publish in the top toolbar
3. Enter a version label (e.g., v1.2 - Added billing flow)
4. Optionally add release notes describing the changes
5. Click Confirm Publish

The new version is immediately live on all channels where the bot is deployed.

imagePublish dialog in Flow Builder showing version label input field, release notes textarea, and Confirm Publish button

Publishing a new bot version

Version History

Navigate to Bot Settings > Versions to view the full publication history. Each entry shows:

• Version number and label
• Published date and time
• Who published it
• Release notes

v3  Published   2026-02-07 14:30   jane@company.com   "Added IVR menu for billing"
v2  Archived    2026-02-05 09:15   john@company.com   "Knowledge base updates"
v1  Archived    2026-02-01 11:00   jane@company.com   "Initial release"

imageVersion history table in Bot Settings showing version number, status badge, publish date, author, and release notes for each version

Bot version history

Rolling Back

To revert to a previous version:

1. Go to Bot Settings > Versions
2. Find the archived version you want to restore
3. Click Rollback to this version
4. Confirm the rollback

WARNING

Rolling back replaces the live version immediately. The current published version is archived, and the selected version becomes active.

Draft vs Published Behavior

While editing a bot that is already published:

• All edits are saved to the Draft automatically
• The Published version continues serving traffic unchanged
• Use the Preview panel to test draft changes before publishing
• Discard the draft at any time to revert to the published state

TIP

Enable Change Tracking in bot settings to see a diff between the current draft and the published version before publishing.