Why You Cannot Hear Your Own System
Familiarity does something specific and unhelpful here. Every option in your menu means something obvious to you, because you know what your teams are called and what they do. You also know which option you want before the greeting starts, so you have never experienced the part where somebody has to decide.
The result is that internal reviews of phone menus almost always conclude that the menu is fine. Everybody in the room is a person who already knows the answer, and the one group whose opinion matters is not in the room. This is why the audit below is done by ringing rather than by discussing, and why three of the calls should be made by somebody who does not work for you.
The configuration screen shows intent, not reality
Looking at the flow diagram tells you what was meant to happen. It does not tell you that the third option routes to somebody who left in March, that the hold music stops after ninety seconds, or that pressing zero puts callers back at the start. All three of those are common, all three are invisible on screen, and all three are obvious within one call.
The Seven Calls
Fifteen minutes, from a mobile that is not connected to your system. Do not tell your team you are doing it, because the point is to observe the ordinary state rather than a prepared one.
| Call | What it exposes |
|---|---|
| 1. Monday, 8:35am | The busiest moment of your week. Nearly every phone system is tested at 2pm on a Wednesday, which is the one time it definitely works. |
| 2. Say and press nothing | What happens to a caller who is driving, is on an old handset, or simply did not catch it. Silence must reach a person. If it loops or hangs up, that is a fault. |
| 3. Press zero straight away | The single most common caller behaviour in existence. Zero should reach a human whether or not you announce it. |
| 4. Choose the wrong option on purpose | Two things: whether the person who answers can transfer you competently, and whether anything about you travels with the transfer or you start again from nothing. |
| 5. Let it ring out entirely | The end of the line. This is where you discover whether a path rings forever, which is the most expensive fault in phone design. |
| 6. 6:15pm, then again Saturday morning | After hours behaviour, which is configured once at setup and then almost never verified again. |
| 7. From a mobile with one bar | Whether spoken prompts and speech recognition still work on imperfect audio, which is how a real share of your calls arrive. |
Three of these should be made by an outsider
Give a friend, a family member or a customer a specific goal, such as "find out whether they can come on Thursday", and ask them to describe what happened afterwards. Where they hesitated is the finding. It is the only reliable way to learn that a word like "operations" or "service delivery" means nothing at all outside your building, because nobody who works there can un-know what it means.
What to Write Down
For each call, four things, and the fourth matters most.
Seconds
Time from connection to reaching a person. This is your customer's actual experience of your business, in one number.
Steps
How many decisions the caller had to make. Every one is a chance to get it wrong and a reason to give up.
Words
Anything you heard that a caller could not act on. Website addresses, awards, "options have recently changed".
Dead ends
Any point where the call could stop with nothing happening. Ring outs, unowned mailboxes, loops.
Fix 1 and 2: The Two That Cost Real Money
Everything else on this page is an improvement. These two are losses.
Fix 1. Any ring group with one person in it. Walk every group and count the people. A group of one means that a flat battery, a meeting, a tunnel or a second call converts directly into a lost customer, with nothing recorded anywhere. It is the most common configuration fault in Australian small business phone systems and the cheapest to fix. Two people minimum, everywhere, including the group that only handles one thing.
Fix 2. Any path that rings forever. Call 5 in the audit finds these. A caller in that situation has no information, no options and no way of knowing whether anybody will ever pick up, so they hang up somewhere around forty seconds and ring the next business on the list. Your system records nothing, because from its point of view nothing happened. Every branch of the flow needs a defined end: a callback, an AI answer that takes details and books a time, or at minimum a monitored mailbox with a stated commitment about when somebody will ring back.
| Stage | What should happen | Rough timing |
|---|---|---|
| First group | The people who should get this call. Two or more. | 15 to 20 seconds |
| Widen | Anybody else who could reasonably help, including people who normally would not. | Another 15 to 20 seconds |
| Queue or callback | Join a queue if you run one, otherwise offer the callback. | To a defined maximum |
| Defined end | AI answer, or a monitored mailbox with a real commitment. | Always |
Fix 3: Rename Every Option
Costs nothing, takes twenty minutes, and it is the largest improvement most businesses can make to their phone experience. Menu options are almost always named after internal teams, and callers have no idea what your internal teams are.
| Currently says | Should say | Because |
|---|---|---|
| Customer service | An order you have already placed | Every caller believes their call is customer service, so the option sorts nobody. |
| Accounts | A bill or a payment | A good share of callers read accounts as opening one. |
| Operations | A booking or a job time | Nobody outside the business knows what operations means. |
| Technical support | Something is not working | Plain language beats a job title, and it is quicker to say. |
| Sales | You are not a customer yet | Blunt, and it works. It should also be your fastest answered option. |
| General enquiries | Delete it | It collects everybody who is unsure, so it becomes your largest queue handled by your least specialised people. Make the default path the general path instead. |
Test the new wording the same way you tested the old: read the options to three people who do not work there and ask which they would pick for three specific situations. Hesitation means the wording is wrong, not the caller.
Fix 4: Cut It to Four, and One Level
Two hard limits, both grounded in what people can actually hold in their head while listening.
Four options, and three is better. Past four, callers have forgotten the first by the time they hear the last, and will choose whatever they heard most recently rather than what they need. That produces transfers, which produce repeated explanations, which produce the impression of a disorganised business.
One level, never two. A submenu is where callers give up. If you genuinely cannot sort your calls in four options, the answer is not a fifth option or a second layer, it is a person or an AI answer that can understand an ordinary sentence.
Order by your real call counts rather than by department seniority, so the most common reason for ringing has the shortest path. If you do not know your call counts, sort your last two hundred calls by what the caller actually wanted and count them, which takes about an hour and reliably surprises people.
Fix 5: Rewrite the Greeting
A greeting has three jobs: confirm they rang the right place, say what happens next, get out of the way. Under seven seconds. Four things to delete on sight.
| Delete | Why |
|---|---|
| Your website address | Nobody has ever written one down from a phone message. A caller on the phone has already decided they want to speak to a person. |
| "Our options have recently changed" | Useful to the two people who ring you weekly. A delay for everybody else, permanently, because it never gets removed. |
| Your opening hours, during opening hours | They are open. They rang. Telling them the hours costs seconds and helps nobody. |
| Awards, tag lines and "leading provider of" | They already chose you enough to ring. This is the wrong moment to sell, and it reads as a business more interested in itself than in the call. |
What works instead is short and specific: the business name, then what is about to happen. "Thanks for calling Fairfield Electrical, I will put you through to the team now" is four seconds and does everything a greeting needs to do for most businesses.
Fix 6: Make Holding Bearable
Waiting is not the problem. Waiting without information is. Four settings decide whether people stay.
| Setting | Get it right |
|---|---|
| Position or expected wait | Only if it is accurate. A wrong estimate is worse than silence, because it turns general patience into a specific complaint. |
| Callback that keeps their place | The most appreciated setting in queue design. It converts waiting from something being done to the caller into a decision they made. |
| Vary the message | The same fifteen seconds looping makes two minutes feel like ten. Keep it useful rather than promotional. |
| A maximum wait that is enforced | Beyond a defined point, a queue is just abandonment with extra steps. Move them automatically to a callback or an AI answer. |
Two things not to do. Do not advertise on hold, because somebody waiting to query an invoice is not a receptive audience for your product range. And do not say the call is important while making them wait ten minutes, because the gap between the claim and the experience irritates more than silence would.
Fix 7 to 11: The Housekeeping
| Fix | What to do |
|---|---|
| 7. Public holidays | Load twelve months ahead, by state, because Australian public holidays differ 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 too: the Christmas shutdown, a stocktake day, a conference Friday. |
| 8. Voicemail as the second step | Move it to last. Widen the ring group first, then offer a callback, then use a mailbox. A large share of callers under about forty will not leave one at all, so a mailbox is a hang up with extra steps and you never learn they rang. |
| 9. Mailboxes nobody owns | Every mailbox gets a named owner and a checking frequency, or it gets deleted. Unowned mailboxes are among the most reliable sources of lost business anywhere. |
| 10. Destinations that no longer exist | Walk every menu option and every transfer target once a quarter. Ten minutes. People leave, teams merge, and nothing tells the phone system. |
| 11. Zero that loops | Zero must reach a person, always, from anywhere in the flow. If it returns to the menu, callers conclude the business cannot be reached, and they are effectively right. |
Two more worth checking while you are in there: hold music that stops partway, which reliably makes callers think they were cut off, and an after hours message recorded by somebody who left two years ago, which customers notice and staff notice more.
The Bigger Question: Do You Need a Menu?
Having done the audit, it is worth asking whether the menu should exist at all. Menus sort callers into groups that need different people. If your callers do not need different people, the menu is a cost you impose on customers for no return.
For most businesses under about fifteen people who answer calls, the better design is no menu: a short greeting, then ring a group. For businesses with genuinely distinct teams, multiple locations, a language choice or an urgent path, a menu earns its place. And there is now a third answer, which is that a menu was always a workaround for machines that could only understand a digit. When the system can take "my hot water is out and I am in Coburg" and either handle it or route it, the workaround is no longer needed. Our note on answering every call without a menu covers what that looks like in practice.
Whichever you choose, the rest of this still applies
An AI answer does not remove the need for real hours, a defined overflow, two people in the ring group and an end of the line. Those are the parts that stop calls disappearing, and they are needed regardless of what picks up first. Skipping them and adding AI produces a very modern way of losing the same calls.
After Hours, Properly
After hours should produce an outcome, not a message. A mailbox nobody checks until Tuesday is worse than plainly saying you are closed, because at least the second is honest with the caller.
Three options, in descending order of usefulness. An AI answer that takes the details, handles the common questions and books a time, which genuinely deals with the caller. A callback commitment with a stated time that is actually kept. Or a clear statement of when you open, with a way to leave a message that gets transcribed and read. What should not happen is an unbounded ring, a mailbox with no owner, or a diversion to somebody's personal mobile that turns their evening into work by default.
That last one connects to a genuine obligation. Australian employees can refuse unreasonable contact outside working hours, and the provisions cover small business employers. A system with real hours and a defined after hours path is the arrangement that makes that workable, because the off switch stops being a matter of individual willpower. Our note on the right to disconnect and your phone system covers it.
How to Tell It Worked
| Measure | What it tells you |
|---|---|
| Abandoned calls, and the stage they abandoned at | The most useful number available. Where people give up tells you which part of the design is failing. |
| Time to a person | Your customer's experience of your business, expressed as one number. Track the change. |
| Transfers per call | High transfers mean the menu is sorting people incorrectly, which is nearly always a naming problem rather than a routing one. |
| Zero presses | Callers escaping. A high rate means your options do not match the reasons people ring. |
| Calls answered at each stage | Whether your first ring group actually covers, or whether everything is landing on overflow. |
| Repeat callers within 48 hours | Whether calls are finishing. Rising repeats mean people are ringing back because the first attempt achieved nothing. |
Our note on the five numbers your phone system should report covers how to read these, and most of them are available on any modern system without extra licensing.
How We Run This With Customers
VOCPhone maps the flow with you from your actual call mix rather than from your organisational chart, and the first step is usually counting your last two hundred calls by what the caller wanted. That conversation on its own tends to delete two menu options and reorder the rest, before anything is configured.
Everything described here is configuration rather than a paid extra: ring groups, overflow, callback, hours, public holidays by state, transcription and an AI answer for the after hours path. We run the seven test calls with you at handover and again each quarter, because a call flow is not a thing you set up once. It drifts as people join and leave, as services change, and as somebody adds a helpful message that stays for three years.
Frequently Asked Questions
How do I test my business phone system properly?
Seven calls, about fifteen minutes, from a mobile that is not connected to your system, with a pen, and without telling your team, because the point is to observe the ordinary state rather than a prepared one. Ring on a Monday at 8:35am, which is the busiest moment of your week, since nearly every phone system is only ever tested at 2pm on a Wednesday when it definitely works. Say and press nothing, to find out what happens to a caller who is driving or did not catch the options, since silence must reach a person rather than loop or hang up. Press zero immediately, which is the most common caller behaviour there is. Choose the wrong option deliberately, which tests both whether the person answering can transfer competently and whether anything about you travels with the transfer. Let it ring out entirely, which is how you discover a path that rings forever. Ring at 6:15pm and again on a Saturday morning, since after hours is configured once at setup and almost never verified afterwards. And ring from a mobile with one bar, because that is how a real share of your calls actually arrive. For each call write down the seconds to reach a person, how many decisions you had to make, anything you heard that you could not act on, and any dead end.
What is the most common fault in a business phone system?
A ring group with only one person in it, and it is both the most common and the cheapest to fix. A group of one means a flat battery, a meeting, a tunnel or simply being on another call converts directly into a lost customer, with nothing recorded anywhere to tell you it happened. Walk every group in your system and count the people; two minimum, everywhere, including the group that only handles one thing. The second most common fault is more expensive and even more invisible: a path that rings forever. A caller in that position has no information, no options and no way of knowing whether anybody will ever pick up, so they hang up somewhere around forty seconds and ring the next business on the list, and your system records nothing because from its point of view nothing happened. That is why businesses can go years without finding it, and why it never appears in any report. The fix is that every branch of the flow needs a defined end: a callback, an AI answer that takes details and books a time, or at minimum a monitored mailbox with a stated commitment about when somebody will ring back.
Why do callers choose the wrong option on our phone menu?
Because the options are named after your internal teams and callers do not know your internal teams. Renaming them costs nothing, takes about twenty minutes, and is the largest single improvement most businesses can make to their phone experience. Customer service sorts nobody, because every caller believes that is what their call is; use something concrete like an order you have already placed. Accounts is read by a good share of callers as opening one; use a bill or a payment. Operations means nothing at all outside your business; use a booking or a job time. Technical support is a job title where plain language works better and is quicker to say; use something is not working. Sales can become you are not a customer yet, which is blunt, works, and should also be your fastest answered option. And general enquiries should simply be deleted, because it collects everybody who is unsure and therefore becomes your largest queue handled by your least specialised people; make the default path the general path instead. Test new wording the way you should have tested the old: read the options to three people who do not work there and ask what they would pick for three specific situations.
How many options should a phone menu have?
Four at most, and three is better, with one level and never two. The limits are not arbitrary, they follow from what people can hold in their head while listening. Past four options a caller has forgotten the first by the time they hear the last, and will choose whatever they heard most recently rather than what they actually need, which produces transfers, which produce repeated explanations, which produce the impression of a disorganised business. A second level is where callers give up altogether, and if you genuinely cannot sort your calls within four options, the answer is not a fifth option or a submenu, it is a person or an AI answer that can understand an ordinary sentence. Order the options by your real call counts rather than by department seniority, so the most common reason for ringing has the shortest path; if you do not know your call counts, sort your last two hundred calls by what the caller actually wanted and count them, which takes about an hour and reliably surprises people. Also always keep a do nothing path so silence reaches a person, and make zero reach a human from anywhere in the flow, announced or not.
What should a business phone greeting say?
Three jobs, in under seven seconds: confirm they rang the right place, say what happens next, and get out of the way. For most businesses that is as simple as "Thanks for calling Fairfield Electrical, I will put you through to the team now", which takes about four seconds and does everything a greeting needs to. Four things to delete on sight. Your website address, because nobody has ever written one down from a phone message and a caller on the phone has already decided they want a person. The sentence about options having recently changed, which is useful to the two people who ring you weekly, is a permanent delay for everybody else, and never gets removed once added. Your opening hours during opening hours, since they are open and they rang. And awards, tag lines and being a leading provider of anything, because the caller already chose you enough to ring and this is the wrong moment to sell, reading instead as a business more interested in itself than in the call. If the caller is going to wait, use those seconds to tell them where they are in the queue, or to offer a callback that keeps their place.
How long should someone be on hold, and what should they hear?
Waiting is not the problem; waiting without information is. Four settings decide whether people stay. Give position in queue or expected wait, but only if it is accurate, because a wrong estimate is worse than silence since it converts general patience into a specific complaint you will hear about. Offer a callback that keeps their place, which is the most appreciated setting in queue design because it turns waiting from something being done to the caller into a decision they made themselves. Vary the message, because the same fifteen seconds on a loop makes two minutes feel like ten. And set a maximum wait that is actually enforced, since beyond a defined point a queue is abandonment with extra steps, so move people automatically to a callback or an AI answer instead. Two things not to do. Do not advertise on hold, because somebody waiting to query an invoice is not a receptive audience for your product range. And do not tell people their call is important to you while making them wait ten minutes, because the gap between the claim and the experience irritates considerably more than saying nothing would have.
What should happen to calls after hours?
After hours should produce an outcome rather than a message. A mailbox that nobody checks until Tuesday is worse than plainly telling the caller you are closed, because at least the second is honest. Three options, in descending order of usefulness. An AI answer that takes the details, handles the common questions and books a time, which genuinely deals with the caller and, incidentally, removes the guilt that keeps staff answering at 9pm. A callback commitment with a stated time that is actually kept. Or a clear statement of when you open, together with a way to leave a message that gets transcribed and read by somebody. What should not happen is an unbounded ring, a mailbox with no owner, or a diversion to somebody's personal mobile that quietly turns their evening into work by default. That last point connects to a real obligation, since Australian employees can refuse unreasonable contact outside working hours and the provisions now cover small business employers. A system with real hours, twelve months of public holidays loaded by state, and a defined after hours path is what makes that workable, because the off switch stops depending on individual willpower.
Should we get rid of our phone menu entirely?
Possibly, and it is worth asking properly rather than assuming the menu has to exist. Menus exist to sort callers into groups that need different people, so if your callers do not need different people, the menu is a cost you impose on customers for no return at all. For most businesses with fewer than about fifteen people answering calls, the better design is no menu: a short greeting, then ring a group. A menu earns its place when you have genuinely distinct teams handling genuinely different calls, multiple locations, a language choice, or an urgent path that needs to jump the queue. There is now a third answer as well, which is that a menu was always a workaround for the fact that automated systems could only understand a digit, so when the system can take an ordinary sentence like my hot water is out and I am in Coburg and either handle it or route it, the workaround stops being necessary. Whichever way you go, the rest still applies: real hours, a defined overflow, two people in every ring group and an end of the line. Skipping those and adding AI produces a very modern way of losing exactly the same calls.
