Why changing a rule feels risky
The scariest moment in support automation is changing a rule. Will the new returns window break exchanges? Will the holiday policy leak into January? Most teams find out from customers, after the change is already live and the wrong answer has gone out more than once.
- One policy touches several playbooks
- Old rules linger after a change
- Mistakes surface in real conversations
How Yuma tests and rolls out changes
In Yuma 2.0, every playbook carries its own tests: example situations with the outcome you expect. Ask Yuma writes most of them, and you can turn any real conversation into a test. When you change a policy, Yuma rewrites the pages it touches and reruns the suite as simulated conversations. No real customer is involved.
A failing test shows exactly which page is unclear, and Yuma fixes it and reruns until everything passes. Then you roll out to a share of matching conversations, with the rest handled as drafts your team reviews in the helpdesk, and raise the share as trust grows.
Holiday returns without the January surprise
A brand extends its returns window for the holidays. Yuma updates the returns playbook and the related pages, then reruns the tests. One fails on exchanges, so Yuma flags the unclear line and fixes it. The change goes live to a small share of conversations first, then to all of them a few days later.
Benefits
01Control
No surprises
Changes are proven in simulated conversations, then rolled out to a share of traffic you control.
02Coverage
Real cases become tests
Turn real conversations into tests, so your suite grows from the questions customers actually ask.
03Ownership
Gaps go to a person
Where the Handbook is silent, Yuma hands the conversation to a person and logs the gap as an open question.
04Consistency
One change, every channel
When your returns playbook changes, it changes on email, chat, SMS and the phone too.
Yuma
Step by step
- 01
Change the policy
Describe the change in plain words, or ask Ask Yuma to make it. - 02
Review the draft
Check the draft and every page the change touches. - 03
Rerun the tests
Yuma reruns the suite as simulated conversations and fixes anything unclear. - 04
Roll out to a share
Publish to a share of matching conversations while the rest stay drafts. - 05
Raise it or pause
Increase the share as trust grows, or set it to zero to pause.
