Drop your IVR flow CSV here, or
Up to 100 MB. No signup.
What columns do we expect?
We expect one row per transition between two IVR nodes. Column names are flexible — lowercase equivalents, camelCase, and common vendor formats all work.
source,source_label,target,target_label,target_category,volume
entry,Main line,menu_1,Main Menu,menu,12450
menu_1,Main Menu,queue_sales,Sales Queue,queue,5120
menu_1,Main Menu,queue_support,Support Queue,queue,4890
menu_1,Main Menu,menu_2,Hours Info,menu,1200
menu_2,Hours Info,hangup_info,Hangup after info,hangup-resolved,850
menu_1,Main Menu,invalid_1,Invalid input,hangup-unresolved,1240target_category values we treat as legitimate outcomes (not dead-ends): agent, queue, callback, voicemail, survey, selfservice-complete, hangup-resolved. Anything else with zero outgoing transitions is flagged as a dead-end.
Flow summary
Interactive journey graph
Drag any node to re-arrange. Circle size = call volume. Red arrows = loops. Red-outlined circles = dead-end leaves.
AI analysis
What the data is saying
Click Generate AI summary for a narrative read of this flow — dead-ends, loops, self-service rate, and what to do about it. The payload is shown before it leaves your browser.
Top dead-ends
Nodes where calls end without reaching an agent, voicemail, callback, or completed self-service. Sort by call volume — fix the top 2 and you typically recover 40–60% of dead-end calls.
| Node | Label | Calls into dead-end | % of entries |
|---|