Improve a flow
Use results and transcripts to find where calls go wrong, change the draft, simulate the case that failed, and publish a better version.
At the end: a new published version that fixes what the last one got wrong, and a way to check it helped.
Your first version won't be your best. The results show where to change it; Writing good questions shows how.
Where to look
| What you see | What it usually means | What to try |
|---|---|---|
| Many calls end at the same question | The question is long or asks two things | Shorten it; ask one thing at a time |
| Few shoppers answer | Calls go out at the wrong moment | Start runs sooner after the event, or change Tries per shopper and Minutes between tries |
Many needs_team | An action is refused or doesn't answer in time | Check the action's replies on the call's Call results; fix your endpoint or its timeout |
| Answers you can't act on | The answer type is too loose | Change a text answer to a choice |
| A choice like "Something else" is common | Your choices miss a common reason | Read those calls' transcripts and add the missing choice |
| Shoppers ask the same off-script question | The flow can't answer it | Answer it in the flow's SOP, or allow a read action such as get_order |
Make the change
Find the calls
In Results → Responses, filter to the outcome or answer that went wrong, and open a few to read and hear them.
Edit the flow
Your edits go to a draft. The published version keeps running until you publish.Simulate the case that failed
Simulate with the same inputs, and the same action replies under Actions answer, as the calls that went wrong. See Simulate a call.
Publish
Once that simulation passes. See Publish and version.Check it helped
After a few days, compare How the calls ended in Results for the days before and after you published.
Add your team and set what each person can do.