IVR Flow Design: Map Your Phone Menu Before You Build It
How to draw an IVR call flow first: symbols, a step-by-step method, handling dead ends and errors, and checking the map with real callers before you build.
Phone menus are easy to build and hard to fix. Once recordings are made, routes set and staff trained, a change ripples everywhere. A flow diagram costs almost nothing, and it exposes loops, dead ends and missing cases before they reach a caller. This guide shows a practical way to draw one, what to put on it, and how to test the map. For menu-writing advice, read IVR Menu Design alongside it.

Why draw it first
A menu described in words always seems simpler than it is. "Press 1 for sales, 2 for support" hides at least a dozen decisions: what happens outside hours, when nobody answers, when the caller presses nothing. Drawing forces you to answer each question.
What a flow diagram gives you
- A shared pictureManagers, agents and installers argue about the same thing instead of different mental versions.
- Early fault findingLoops, dead ends and unreachable options are visible on paper.
- A recording scriptEach box that speaks becomes one line in the prompt list.
- A test planEvery path on the map is a test call to make later.
- DocumentationNew staff can see how calls travel without calling in to find out.
A small set of symbols
You do not need formal notation. Five shapes cover almost everything, as long as everyone uses them the same way.
| Shape | Meaning | Example |
|---|---|---|
| Rounded box | Start or end of the call | Incoming call; call ends after voicemail |
| Rectangle | A prompt the caller hears | Greeting, menu, closed message |
| Diamond | A decision the system makes | Open hours? Is a holiday set? Is the queue full? |
| Arrow label | What the caller pressed or said | 1, 2, 0, no input, wrong key |
| Double rectangle | A destination | Sales queue, support queue, voicemail, callback request |
A step-by-step method
Drawing your flow
- List why people callTake a month of call notes or voicemail and group the reasons. Real data beats guesses.
- Draw the happy pathGreeting, main menu, and the destination for each common reason.
- Add the time decisionsOpen or closed, holiday, emergency message. Put these before the menu so callers are not told options that do not exist.
- Add errorsWhat happens on no input, on a wrong key and on a repeated wrong key.
- Add the way outShow how a caller reaches a person from any level. See Letting Callers Reach a Person Quickly.
- Add the end statesVoicemail, callback, queue, hang-up. Nothing should end in empty space.
Keep the depth shallow
If your diagram needs three levels of menu, ask whether a caller will remember the path. Two levels is already plenty for most businesses. Where a branch grows, consider moving questions to a self-service message, or letting the agent sort it out after the call is answered.
Hunting for dead ends and loops
Once the map is drawn, put a finger on every box and ask a few questions. This is the part of the work that pays for the whole exercise.
Checks to run on your diagram
- Does every prompt box have an arrow for each key, for silence and for a wrong key?
- Can a caller get back to the main menu, and can they get out of it?
- Is there a loop with no limit? Add a count so it ends after two or three tries.
- Does every destination have a plan for when nobody is available?
- Do closed hours and holidays go to a useful message and not to a ringing phone?
- Is each option reachable, or is something on the map that no key leads to?
- Can someone who knows nothing about your business follow the labels?
Review it with real people
Show the diagram to a person who answers calls and to someone outside the team. Ask the first to describe three awkward calls they have had recently, and trace each through the map. Ask the second to "call" the menu by reading each prompt aloud while you follow along. Where they hesitate or pick the wrong option, your wording needs work.
Bring in any accessibility needs at this stage too, because they are cheaper to design in than to bolt on. Accessible Phone Menus for Every Caller lists what to consider.
Keep the diagram alive
The map is useful only if it matches the live system. Store it with a date and a version number, change it before changing the system, and note who approved each change. When hours, teams or seasonal campaigns change, update the diagram first, then the setup, then test. Updating Your IVR for Seasons and Campaigns describes that routine, and Testing an IVR Before Launch covers the final check.
A small worked example
Take a hypothetical dental clinic with a front desk, a billing contact and an emergency line. The first decision box checks whether the clinic is open. If closed, a message gives hours, an instruction for dental emergencies, and an option to leave a message. If open, the main menu offers appointments, billing and a way to reach a person. Each option leads to a queue; a long wait triggers an offer of a callback.
On paper that is a dozen boxes. When the owner walks through it, they notice that the billing queue has no plan for lunchtime, and that nothing happens if a caller chooses an option while all staff are on a call. Both are fixed in minutes on the diagram, instead of after launch.
Patterns that keep recurring
After drawing a few flows, you start to see the same shapes. Recognising them speeds up design and helps you avoid reinventing mistakes.
- The time gate. A decision at the very top that sends closed-hours calls to a message, before any menu is read out.
- The overflow valve. A queue that, when full or unanswered, sends callers to a second team, a callback offer or voicemail.
- The shortcut. A way for known callers, such as those with an order number, to skip the menu and reach the right place.
- The confirmation loop. A short yes or no step before a call goes to a costly or sensitive destination.
- The universal exit. The same key on every level that leads to a person or a message.
Name these patterns on your diagram. When a new option is requested, you can ask which pattern it fits instead of adding another special case.
How much detail belongs on one page
A single sheet that tries to show every prompt and branch becomes unreadable. Use two layers. The top layer shows only destinations and decisions, so the whole flow fits on one page. The second layer shows the detail of each branch, including prompt wording, key presses and error handling. People who want the overview read the first; those who build and test the system use the second.
Label each box with a short code, such as M1 for the main menu or Q2 for a queue. The same code appears in the prompt script and the test log, so a problem reported by a caller can be traced back to a box in seconds.
From diagram to setup in Call
In Call, the pieces on your diagram map to a few settings. Destinations are queues, each with their own hours, closed greeting, overflow queue and voicemail. Holidays and emergency closures decide where calls go when the team is not there. Callbacks collect the callers who asked to be called. The routing simulator lets you walk a pretend call through the hours, holiday, capacity and skill rules to see where it ends, without dialling anything, which is a natural way to compare the system with your drawing. Scripts for AI agents can also be drawn as diagrams. See Setting Up IVR and Business Hours in Call and Call Script Diagrams.
Frequently asked questions
What tool should I use to draw an IVR flow?
Whatever you will actually keep up to date: a whiteboard photo, a drawing tool or a spreadsheet of steps. The method matters more than the software.
How detailed should the diagram be?
Detailed enough that someone could build the menu from it without asking questions. Every prompt, key press, time rule and destination should appear.
Who should be involved in designing the flow?
Someone who answers calls, someone who manages the team, and whoever will build and maintain the system. Add a person outside the business to check the wording.
How many menu levels are too many?
More than two levels is usually too many for callers to remember. If you need more, look at merging options or moving some questions to self-service.
How do I handle callers who press nothing?
Repeat the menu once, then send them to a person or voicemail. Avoid endless loops, which strand callers and clog lines.
Should I update the diagram when I change the system?
Yes, and ideally before. An out-of-date diagram is worse than none because people trust it.