How to Design a Call Flow People Do Not Hate

What a Call Flow Actually Is

A call flow is the complete map of what happens to an inbound call from the moment it arrives to the moment it ends, including every path nobody intended. Most businesses have never seen theirs written down, which is precisely why theirs contains three dead ends and a message about a public holiday from two years ago.

Before designing anything, draw the one you have. A sheet of paper is fine. Start at the number, and for every branch answer three questions: what does the caller hear, what happens if they do nothing, and what happens if nobody answers. That third question is where the problems live, and it is the one that has usually never been asked.

Start from the calls, not from the departments

Take your last two hundred calls and sort them by what the caller actually wanted, by hand. Count them. Almost every business is wrong about the proportions, and the proportions are the entire basis of a good design: the most common reason for calling should require the least effort, and anything under about five per cent should not be a menu option at all. Designing from the org chart instead produces a menu that is fair to your departments and hostile to your customers.

The First Ten Seconds

Callers decide in the first ten seconds whether this is going to be easy. That decision governs everything after it: whether they listen to the options, whether they press zero over the top, whether they wait, and what they tell other people about your business.

What happens in the first ten seconds	What the caller concludes
A person answers	This will be quick. Best outcome available, and still the right answer for many businesses.
A short greeting, then ringing	Fine. Almost as good as a person, and it is the default that most small businesses should use.
A greeting that says what is about to happen	Reassured. Knowing you are being put through to the team is enough.
A menu of four clear options	Tolerable, if one of them obviously matches.
A menu of seven options, read slowly	Irritated before anything has happened. Most will pick the wrong one to escape.
A message about the website, then a menu	The business is prioritising its own convenience. This is the most common own goal in phone design.
Music, with no explanation	Uncertainty. Did it connect? Am I in a queue? How long is this?

Writing the Greeting

A greeting has three jobs and one common mistake. The jobs are to confirm they rang the right place, to say what happens next, and to get out of the way. The mistake is using it to broadcast something the business wants to say.

Use	Instead of
"Thanks for calling Harper Plumbing. I will put you through to our team now."	"Thank you for calling Harper Plumbing, Australia's leading provider of residential and commercial plumbing solutions since 1994. Did you know you can find answers to many common questions at our website, www dot harper plumbing dot com dot au. Please listen carefully as our menu options have recently changed."
"Thanks for calling Harper Plumbing. If this is a burst pipe or a blocked drain, press 1 and we will get to you first. For anything else, stay on and someone will pick up."	"Press 1 for sales. Press 2 for accounts. Press 3 for service. Press 4 for our warehouse. Press 5 for all other enquiries. Press 9 to repeat these options."
"Thanks for calling. Our team is on other calls, so you are third in line, or press 1 and we will ring you back without losing your place."	Forty seconds of music with no indication of anything at all.

Four rules for the wording. Never read out a web address. Nobody has ever written one down from a phone message, and every caller who is already on the phone has decided they want to talk to somebody. Never say the options have recently changed, which is a message for the two people who ring you weekly and a delay for everybody else. Never state your opening hours in the greeting during opening hours. And keep it under about seven seconds, because the greeting is not the place to do marketing to somebody who has already chosen you enough to ring.

The honest position in 2026 is that most small businesses should not have a menu at all, and a good number of medium ones should have a much smaller one than they do. Menus exist to sort callers into groups that need different people. If your callers do not need different people, a menu is pure cost imposed on the customer.

❌

Skip the menu when

Fewer than about fifteen people answer calls. Most calls could be handled by whoever picks up. You have one main thing you do. Or your team is small enough that a transfer costs three seconds. Ring a group instead.

✅

Use a menu when

Genuinely different teams handle genuinely different calls, and sending a caller to the wrong one wastes real time. Multiple locations. A language choice. Or an urgent path that must jump the queue.

🤖

Replace the menu when

An AI answer can take an ordinary sentence, work out what is needed, and either handle it or route it. This removes the main justification for menus, which was that a machine could only understand a number.

That third option is the genuinely new thing. A menu was always a workaround for the fact that automated systems could not understand speech, so callers had to translate their problem into a digit. When the system can take "my hot water is out and I am in Coburg" and act on it, the workaround is no longer necessary. Our note on why phone menus are becoming obsolete covers the argument, and the practical guidance below applies to whichever you use, because both still need hours, overflow and a defined end of the line.

Menu Rules, If You Need One

Rule	Why
One level. Never two.	A submenu is where callers give up. If you genuinely need more sorting than four options allow, the answer is a person or an AI answer, not another layer.
Four options maximum, three is better	People cannot hold more than about four spoken options in memory, and by the fifth they have forgotten the first and will pick whatever they heard last.
Most common option first	Order by your actual call counts, not by department seniority. The most frequent reason for calling should be the shortest wait.
Say the option before the number	"For a repair, press 1" beats "press 1 for a repair". The caller is listening for their problem, not for a digit.
Always have a do nothing path	A caller who presses nothing, is on a rotary phone, or is driving must still reach a person. Silence should route to your busiest group, not repeat the menu forever.
Zero always works	Whether or not you announce it. People will press it. Hiding the exit is the most resented pattern in phone systems.
Never ask a question you cannot act on	Asking for an account number and then not using it is worse than not asking. Every question must change what happens next.
Repeat at most once	Two failed attempts means route them to a person. A third loop teaches callers that your business cannot be reached.

Naming Options the Way Callers Think

This is the single highest value edit available to most businesses, it costs nothing, and it takes twenty minutes. Menu options are almost always named after internal teams, and callers do not know your internal teams.

Instead of	Say	Because
"Customer service"	"An order you have already placed"	Everyone thinks their call is customer service, so the option sorts nothing.
"Accounts"	"A bill or a payment"	Half your callers think accounts means opening one.
"Operations"	"A booking or a job time"	Nobody outside your business knows what operations does.
"Technical support"	"Something is not working"	Plain language beats a job title, and it is faster to say.
"General enquiries"	Remove it entirely	It is where uncertain callers go, so it becomes the biggest queue with the least specialised staff. Make the default path the general path.
"New business"	"You are not a customer yet"	Blunt, and it works. This is also the option that should be answered fastest.

The test that settles any menu argument

Read the options aloud to somebody who does not work in your business and ask which they would choose for three specific scenarios. If they hesitate, the wording is wrong, not the caller. Do this with three different people and you will fix more in half an hour than any amount of internal discussion achieves, because internal discussion is conducted entirely by people who already know the answer.

Queue and Hold Design

Holding is not automatically bad. Being held without information is. Four settings determine whether people wait or hang up.

Setting	Get it right
Tell them where they are	Position in queue or expected wait, but only if it is accurate. A wrong estimate is worse than none, because it converts patience into a specific grievance.
Offer a callback that holds their place	The single most appreciated feature in queue design. It converts waiting from something done to the caller into a choice they made.
Change the message occasionally	The same fifteen seconds on repeat makes two minutes feel like ten. Vary it, and keep it useful rather than promotional.
Set a maximum wait, and mean it	Past a defined point the queue stops being a queue and becomes abandonment with extra steps. Move them to a callback or an AI answer automatically.

Two things to avoid. Do not use the hold message to advertise, because a person waiting to complain about an invoice does not want to hear about your new product range. And do not tell people their call is important while making them wait ten minutes, because the mismatch between the statement and the experience is more annoying than saying nothing at all.

Overflow and the End of the Line

This is where most call flows fall apart, because it is the part nobody designs. Every branch needs a defined answer to the question "what if nobody picks up".

Stage	What should happen	Typical timing
First group	Ring the people who should get it. Two or more, never one.	15 to 20 seconds
Widen	Add anybody else who could reasonably help, including people who normally would not take this call.	A further 15 to 20 seconds
Queue or callback	If the business runs a queue, join it. Otherwise offer the callback.	Up to your defined maximum
Defined end	An AI answer that takes details and books a time, or a monitored mailbox with a stated callback commitment.	Always. This is the step that is usually missing.

An unbounded ring is the worst outcome in phone design and it is extremely common. The caller has no information, no options, and no idea whether anybody will ever answer, so they hang up somewhere around forty seconds and ring the next business on the list. Nothing in your system records that they existed, which is why this failure is invisible in every report you have and why businesses go years without discovering it. Every path must end somewhere defined.

Hours, Holidays and the Exception

Four things, and the third is the one that catches everyone.

Set the hours you actually trade, including Saturday if you trade Saturdays, and set them per location if locations differ. Load twelve months of public holidays in advance, by state, because Australian public holidays vary between states and the day you notice a missing one is the day you are closed and the phone is not. Add the closures that are not public holidays, which means the Christmas shutdown, a stocktake day, or the Friday of a conference, and this is the category that always gets missed. And have a way to close early or open late without editing the flow, because a burst pipe in the office at 2pm should not require somebody who understands the configuration to be available.

After hours should produce an outcome rather than a message. A mailbox that nobody checks until Tuesday is worse than a straightforward statement that you are closed, because at least the second one is honest. An AI answer that takes the details and books a time genuinely deals with the caller, which also happens to be the thing that stops your staff answering at 9pm out of guilt.

What to Do About Voicemail

Voicemail has been quietly dying for years and most businesses have not adjusted. A significant share of callers under about forty will not leave one under any circumstances, so a voicemail box is functionally a hang up with extra steps for those callers, and you never learn they rang.

Instead of a mailbox	Use
After hours	An AI answer that takes details, answers common questions and books a time. Failing that, a mailbox with transcription so it is read rather than listened to.
When a queue is too long	A callback that holds their place.
For an individual who is unavailable	Route back to their team rather than to their mailbox. A message in one person's mailbox while they are on leave is an enquiry that will not be answered for a fortnight.
For overflow during the day	Widen the ring group first. Voicemail should be the last resort, not the second step.

If you keep voicemail, transcribe it and deliver it where somebody will see it, and set an explicit rule about who checks which mailbox and how often. Unowned mailboxes are one of the most reliable sources of lost business in any organisation.

Ten Things That Are Almost Always Broken

Fault	Fix
1. A ring group with one person in it	Add a second. This single change prevents more lost calls than anything else on the list.
2. A path that rings forever	Give every branch a defined end.
3. A menu option that routes to somebody who left	Walk every option once a quarter. It takes ten minutes.
4. Public holidays configured for last year only	Load twelve months ahead, by state.
5. A greeting that reads out the website	Delete that sentence. It has never worked.
6. Hold music that stops, so callers think they were cut off	Check the loop. Silence on hold reliably produces hang ups.
7. An after hours message recorded by someone who no longer works there	Re-record it. Callers notice, and staff notice more.
8. Zero not working, or looping back to the menu	Make zero reach a person, always.
9. A mailbox nobody owns	Assign an owner and a checking frequency, or remove the mailbox.
10. A menu option for something you stopped selling	Remove it, and stop apologising for it in the greeting.

The Seven Test Calls

Fifteen minutes, from a mobile that is not connected to your system, with somebody writing down what happens. This finds more than any amount of reviewing the configuration screen, because the configuration screen shows what you intended.

Call	What you are checking
1. At 8:35am on a Monday	The busiest moment of the week. Most flows are tested at 2pm on a Wednesday, when everything works.
2. Say nothing at all	What happens to a caller who is driving, on an old handset, or simply did not hear. Silence must reach a person, not loop.
3. Press zero immediately	The most common caller behaviour there is. It must work.
4. Choose the wrong option deliberately	Whether the person who answers can transfer the call properly and whether the context travels with it.
5. Let it ring out completely	The end of the line. This is where the unbounded ring is discovered.
6. At 6:15pm, and again on a Saturday	After hours behaviour, which is usually configured once and never verified.
7. From a mobile in poor coverage	Whether spoken options and speech recognition still work when the audio is imperfect, which is how a real proportion of your calls arrive.

Have somebody outside the business make three of them

You cannot hear your own call flow properly, because you know what all the options mean and you know which one you want. Ask a friend or a family member to ring with a specific goal and describe what they experienced. Their hesitation is data, and it is the only reliable way to find out that "operations" means nothing to anybody who does not work there.

How to Tell If It Improved

Measure	What it tells you
Abandoned calls, and where they abandoned	The single most useful number. The stage at which people give up tells you which part of the design failed.
Transfers per call	High transfer rates mean the menu is sorting people incorrectly, which is usually a naming problem rather than a routing one.
Zero presses	Callers escaping. A high rate means your options do not match why people ring.
Time to a human	The caller's actual experience of your business, in one number.
Repeat callers within 48 hours	Whether calls are finishing. Rising repeats mean people are ringing back because the first attempt achieved nothing.
Calls answered at each stage	Shows whether your first ring group is genuinely covering, or whether everything is being caught by overflow.

Our guide to the contact centre metrics that matter covers how to read these properly, and it applies to a four person business as much as to a large team.

How We Design Them

Uniden Voice builds the flow with you from your actual call mix rather than from your organisational chart, which usually means the first thing we do is count your last two hundred calls and show you the proportions. That conversation alone tends to remove two menu options and reorder the rest.

Everything on this page is configuration rather than a paid extra: ring groups, overflow, hours, holidays by state, callback, transcription and an AI answer for the after hours path. We also run the seven test calls with you at handover and once a quarter afterwards, because a call flow is not a thing you set up, it is a thing that drifts as people join and leave and services change.

Frequently Asked Questions

How should a business phone greeting be worded?

A greeting has three jobs: confirm the caller reached the right place, say what happens next, and get out of the way. Something like "Thanks for calling Harper Plumbing, I will put you through to our team now" does all three in about four seconds and outperforms a menu for most small businesses. Four rules for the wording. Never read out a web address, because nobody has ever written one down from a phone message and every caller on the phone has already decided they want to speak to somebody. Never say your menu options have recently changed, which is a message for the two people who ring you weekly and a delay for everybody else. Never state your opening hours during opening hours. And keep the whole thing under about seven seconds, because a greeting is not the place to market to somebody who already chose you enough to ring. The common mistake is using the greeting to broadcast what the business wants to say, which is how you end up with twenty seconds about being a leading provider since 1994 before the caller can do anything at all. If a caller is going to wait, tell them that instead: their position, or the option of a callback that keeps their place.

Should my business have a phone menu at all?

Most small businesses should not, and many medium ones should have a much smaller menu than they do. Menus exist to sort callers into groups that need different people, so if your callers do not need different people, a menu is a cost imposed on the customer for no benefit. Skip it when fewer than about fifteen people answer calls, when most calls could be handled by whoever picks up, when you do one main thing, or when your team is small enough that a transfer costs three seconds; ring a group instead. Use one when genuinely different teams handle genuinely different calls and sending a caller to the wrong one wastes real time, when you have multiple locations, when there is a language choice, or when there is an urgent path that needs to jump the queue. The genuinely new option in 2026 is replacing the menu with an AI answer that takes an ordinary sentence and either handles it or routes it. A menu was always a workaround for the fact that automated systems could only understand a digit, so when the system understands "my hot water is out and I am in Coburg", the workaround has stopped being necessary. Whichever you use, you still need hours, overflow and a defined end of the line.

What are the rules for designing an auto attendant menu?

Eight, and breaking any of them is felt by every caller. One level, never two, because a submenu is where callers give up, and if you need more sorting than four options allow, the answer is a person or an AI answer rather than another layer. Four options maximum and three is better, since people cannot hold more than about four spoken options in memory and will pick whatever they heard last. Most common option first, ordered by your actual call counts rather than department seniority, so the most frequent reason for ringing has the shortest path. Say the option before the number, because "for a repair, press 1" beats "press 1 for a repair" when the caller is listening for their problem rather than a digit. Always have a do nothing path, so a caller who presses nothing, is driving, or is on an old handset still reaches a person rather than looping. Zero always works, announced or not, because people will press it and hiding the exit is the most resented pattern in phone systems. Never ask a question you cannot act on, since requesting an account number and then not using it is worse than not asking. And repeat at most once, because a third loop teaches callers your business cannot be reached.

Why do callers pick the wrong menu option?

Almost always because the options are named after your internal teams, and callers do not know your internal teams. This is the highest value edit available to most businesses, it costs nothing, and it takes about twenty minutes. Replace customer service, which sorts nothing because every caller believes their call is customer service, with something concrete like "an order you have already placed". Replace accounts, which half your callers think means opening one, with "a bill or a payment". Replace operations, which means nothing to anybody outside your business, with "a booking or a job time". Replace technical support with "something is not working", because plain language beats a job title and is faster to say. Remove general enquiries entirely, since it is where uncertain callers go and therefore becomes your largest queue staffed by your least specialised people; make the default path the general path instead. And consider replacing new business with "you are not a customer yet", which is blunt and works, and which should be the fastest answered option you have. The test that settles any internal argument is to read the options to somebody who does not work there and ask which they would choose for three scenarios.

How long should callers be left on hold, and what should they hear?

Holding is not automatically bad; being held without information is. Four settings decide whether people wait or hang up. Tell them where they are, using position in queue or expected wait, but only if it is accurate, because a wrong estimate is worse than none since it converts general patience into a specific grievance. Offer a callback that holds their place, which is the single most appreciated feature in queue design because it turns waiting from something done to the caller into a choice they made. Change the message occasionally, since the same fifteen seconds on repeat makes two minutes feel like ten. And set a maximum wait and mean it, because past a defined point a queue stops being a queue and becomes abandonment with extra steps, so move people automatically to a callback or an AI answer. Two things to avoid: do not advertise in hold messages, because somebody waiting to query an invoice does not want to hear about your product range, and do not tell people their call is important while making them wait ten minutes, since the gap between the statement and the experience is more irritating than silence would have been.

What should happen when nobody answers a call?

Every branch of a call flow needs a defined answer to that question, and this is the part almost nobody designs. A workable sequence has four stages. Ring the first group, meaning the people who should get it, always two or more and never one, for about 15 to 20 seconds. Widen, adding anybody else who could reasonably help including people who would not normally take that call, for a further 15 to 20 seconds. Then queue or offer a callback, up to a defined maximum wait. Then a defined end: an AI answer that takes the details and books a time, or a monitored mailbox with a stated callback commitment. That last stage is the one usually missing. An unbounded ring is the worst outcome in phone design and it is extremely common: the caller has no information, no options and no idea whether anybody will ever answer, so they hang up around forty seconds and ring the next business on the list. Nothing in your system records that they existed, which is exactly why this failure is invisible in every report you have and why businesses go years without finding it.

Should we still use voicemail?

Sparingly, and rarely as the second step. A significant share of callers under about forty will not leave a voicemail under any circumstances, which makes a mailbox functionally a hang up with extra steps for those people, and you never learn they rang. Better alternatives exist for each situation. After hours, an AI answer that takes details, handles common questions and books a time deals with the caller properly; failing that, a mailbox with transcription so messages are read rather than listened to. When a queue is too long, a callback that holds their place. For an individual who is unavailable, route back to their team rather than to their personal mailbox, because a message sitting in one person's mailbox while they are on leave is an enquiry that will not be answered for a fortnight. And for daytime overflow, widen the ring group first, treating voicemail as a last resort rather than a second step. If you do keep voicemail, transcribe it, deliver it somewhere people will actually see it, and set an explicit rule about who checks which mailbox and how often, because unowned mailboxes are one of the most reliable sources of lost business in any organisation.

How do I test my phone system's call flow?

Seven calls, about fifteen minutes, from a mobile that is not connected to your system, with somebody writing down exactly what happens. This finds far more than reviewing the configuration screen, which only shows what you intended. Ring at 8:35am on a Monday, because most flows are tested at 2pm on a Wednesday when everything works. Say nothing at all, to see what happens to a caller who is driving or did not hear, since silence must reach a person rather than loop. Press zero immediately, which is the most common caller behaviour there is. Choose the wrong option deliberately, to check whether the person answering can transfer properly and whether context travels with the call. Let it ring out completely, which is how the unbounded ring gets discovered. Ring at 6:15pm and again on a Saturday, since after hours behaviour is usually configured once and never verified. And ring from a mobile in poor coverage, because that is how a real proportion of calls arrive and it tests whether spoken options still work on imperfect audio. Have somebody outside the business make three of them, because you cannot hear your own call flow properly when you already know what every option means.

Guides and Articles