Saving & Publishing
How drafts, publishing, and version history work across all channels.
Last updated
How drafts, publishing, and version history work across all channels.
Every Spara channel has two states at any given time: a draft and a published version. They work independently: your team edits and tests the draft while leads only ever interact with the published version.

Any change you make in the editor (to the instructions, abilities, or configuration) is saved to the draft. Drafts are private. They do not affect live conversations until you explicitly publish.
To save changes to your draft, click Save draft in the editor header. You can save as often as you like. The draft persists between sessions, so you can make changes over multiple sittings before publishing.
Testing always uses the draft. The built-in Testing interface and Simulations always run against the current draft, so you can validate changes before going live.
When you're satisfied with your draft, click Publish in the editor header. Publishing makes the draft the new live version, and all new conversations immediately use the updated channel.
Each channel has exactly one published version at a time. The previously published version is retained in Version History.
Chat channels require at least one activation trigger on any non-default channel before publishing. If a non-default channel has no triggers, the publish button will show an error.
Click Version History in the editor header to see a list of all previously published versions, newest first. Each entry shows who published it and when.
Select any version to preview its instructions. Click Restore to create a new draft from that version. Restoring does not publish; it gives you a draft to review and test before going live again.
To pause a live channel without deleting it, click Unpublish. Unpublished channels are not shown to leads. If the one you're unpublishing is the default for its channel, Spara will prompt you to confirm, since incoming traffic will have no channel to handle it until you publish a replacement.
No. Saving a draft never affects live conversations. Only publishing changes what leads see.
Open Version History, select the previous version, and click Restore. This creates a draft from the old version. Publish it to roll back immediately.
Yes, but changes are not merged; the last save wins. Coordinate with your team to avoid overwriting each other's edits.
Last updated