Product update · Studio
Settings and asset changes now wait in your draft until you publish
Changing a chatbot's settings or assets no longer touches the live chatbot. Every edit goes into a draft, so visitors see nothing new until you publish.
· 2 min read
- Shipped
- Area
- Studio
- Available on
- Every plan
Studio works on a simple promise: you edit a draft, test it, and publish when you're happy. Visitors only ever see the published version. We found two places where that promise didn't hold. On a chatbot with no open draft, saving its settings or its assets wrote the change straight to the live chatbot. That meant a half-finished change could reach your visitors before you'd tested it. Both are fixed.
What's new
- Settings changes go to a draft. When you save settings on a published chatbot, Studio now creates a draft from the live version first and saves your change there. The live chatbot stays exactly as it was.
- Asset changes go to a draft too. Adding, editing or removing assets, such as photos, documents and videos your chatbot can share, follows the same rule.
- Publish sends what you see. If you edit the prompt and click Publish without saving first, Studio now publishes what's on your screen. Before, it could publish the last saved draft instead, so a fresh edit to the prompt seemed to disappear.
- Contact details save properly. Changes to contact fields such as the phone number in your chatbot's content now save to the draft reliably.
How to use it
Nothing changes in how you work:
- Open your chatbot and make your changes in any tab.
- Click Save Draft to keep them without going live.
- Try the changes in the test chat.
- Click Publish when you're ready. That's the moment visitors see them.
Good to know
- Draft, test, publish, everywhere. Settings, assets, behaviour, design and content all follow the same flow now.
- Some things take effect straight away. Webhook subscriptions are created or disconnected immediately, and Studio says so where you set them up. Changes to the content of a knowledge base your chatbot already uses, such as adding a page or a document, are also available to the live chatbot right away.
- Going back is easy. Every published version is kept. If a change doesn't work out, restore an earlier version from version history.
- Plan your publish. Because nothing goes live until you publish, you can prepare several changes over a few days and release them together.