Save Deployment Configuration Drafts for Customer Agent
Friday, July 17, 2026
What it is
You can now save draft changes to a Customer Agent deployment configuration before publishing, keeping your edits separate from the live deployment until you are ready to go live. Previously every configuration change deployed immediately, which made it hard to control when updates became visible.
Why it matters
Managing a live Customer Agent means frequent updates and testing, but deploying every change immediately made it hard to review and prepare before customers saw it. A draft state lets you review and prepare updates first, which reduces deployment risk and raises confidence in testing before going live.
The Take
Casey Hawkins + Chris Carolan
When editing a live agent feels dangerous, people stop editing it, and the agent stops getting better.
The frustration this solves is familiar to anyone who has built conversational flows. Testing them has historically felt nothing like testing a workflow. You had to click into each piece, you could not see the whole thing at once, and any change you made was live. Being able to tinker with the configuration without touching the version customers are actually talking to is the kind of safety net that makes people willing to improve it at all.
Reducing deployment risk is really about confidence. When editing a live agent feels dangerous, people stop editing it, and the agent stops getting better. A draft state lowers the stakes of iteration.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
FAQ
Is this for me?
If you run a live Customer Agent and have been hesitant to adjust its configuration because changes went live instantly, this is the safety net you were missing.
Produced by Value-First Media