Most callers decide within ten seconds whether a business is worth their patience. A poorly designed IVR — too many options, confusing descriptions, no way out — burns that goodwill fast. This guide walks you through how to design and configure an IVR phone menu that actually works: one that routes callers to the right person, sets the right expectations, and doesn't make people hang up and call a competitor.
Whether you're setting up a phone system for the first time or rebuilding a menu that's grown too complicated, the process is the same. Start with the caller, not the org chart.
Why IVR Menu Design Matters More Than Most Businesses Think
When a caller reaches your IVR, they have already decided to contact you. That is a warm lead, a customer with a question, or someone with a problem you can solve — and they chose to call. A badly structured menu is where that intent evaporates.
The first ten seconds of a call are where expectations are set. A clear, confident greeting followed by a concise menu signals that your business is organised and easy to deal with. A rambling welcome message followed by eight options signals the opposite.
The two most common failure modes are opposite extremes: too many options, which causes confusion and hang-ups; and too few, which results in every caller landing on the same person and the whole system becoming pointless. The goal is a menu tight enough to be clear and broad enough to genuinely separate call types.
For more background on how IVR fits into your broader phone setup, see our guide on IVR vs auto attendant — the distinction matters for how you structure your system.
The Golden Rules of IVR Design
Before opening any phone system portal or writing any script, understand the principles that separate a functional IVR from a frustrating one. These rules are based on how callers actually behave, not how business owners assume they behave.
Keep Options to Four or Five Per Level
Human working memory has limits. Research on cognitive load consistently shows that beyond five choices, decision time increases sharply and error rate rises. In the context of a phone menu — where options are heard sequentially, not read visually — four options is comfortable, five is the ceiling, and six or more is a problem.
If your business has ten call types, the answer is not a ten-option menu. It is better grouping (see Step 2 below).
Put the Most Common Option First
Menu order should be determined by call volume, not by what seemed logical to the person who set it up. If 60% of your calls are sales enquiries, "For sales, press 1" goes first — even if accounting feels like it should come before everything else because it's the owner's department.
Callers listen in order. Burying the most common option at position four means the majority of your callers are waiting through options they don't need.
Keep Descriptions to One Short Phrase
"For enquiries relating to your account, billing, or any invoices you may have received" is a sentence. "For accounts and billing" is a menu option. Callers are holding a phone, often in a car or between tasks. They are not reading. Short phrases are processed faster and remembered longer while the rest of the menu plays.
Never Say "Our Options Have Changed"
"Please listen carefully as our menu options have recently changed" is one of the most universally disliked phrases in telephony. Callers have heard it for twenty years. It adds three seconds of delay and zero value. If your menu has changed, simply record the new menu. Callers will adapt.
Similarly, avoid "Your call is important to us" in the greeting. It has been repeated so often that it now signals the opposite.
Always Provide a Zero or Hash Escape Route
Every IVR must include a way to reach a human. Always. Not because callers will always use it, but because its absence generates frustration in the callers who need it most — elderly customers, people with complex questions, and anyone who has been mis-routed.
The convention is "press 0 to speak with our team" or "press hash to return to the main menu." This should be stated last in the options list, after the specific routing choices.
Step-by-Step IVR Setup Process
Step 1: Map Your Call Types Before Touching Any Settings
Open a blank document and write down every reason a customer calls your business. Do not filter yet — just list everything. For most SMBs, this list looks something like:
- Sales enquiry / quote request
- Existing order status
- Technical support or service request
- Billing question or invoice dispute
- Appointment booking or reschedule
- General question (hours, location, website)
- Complaint
Once you have the raw list, you will have a clear picture of the actual volume distribution. This is the foundation. Do not skip it. Businesses that skip straight to recording a script end up with menus that reflect internal assumptions, not caller behaviour.
Step 2: Group Call Types Into No More Than Four Teams or Destinations
Take your call type list and consolidate into logical groups. The target is four destinations — ideally with one fallback. Using the example above:
- Sales — quote requests, new customer enquiries
- Support — service requests, existing order issues, complaints
- Accounts — billing questions, invoice disputes
- Reception / general — appointments, location, hours, anything else
Four options. Clean, distinct, and each routable to a different team or ring group. If your business only has two or three staff, some of these destinations may ring the same person — that is fine. The IVR still provides structure for future growth and for setting caller expectations.
For businesses that need to route based on skill or knowledge area rather than department, read our guide on skills-based routing for a more advanced approach.
Step 3: Write the Menu Script and Test It Aloud
Write out the full greeting and option list as a script. Then read it aloud to someone who has not seen it. If they can repeat back the correct option for a given scenario without hesitation, the menu is clear. If they pause, look confused, or ask you to repeat it, revise.
The script test is the single most underused step in IVR setup. It takes five minutes and saves weeks of complaints.
See the sample script in the next section for a worked example.
Step 4: Record Professionally — Avoid Text-to-Speech for the Main Greeting
Text-to-speech has improved considerably, but for the primary greeting of a business phone system, a human voice recording sounds more trustworthy and more professional. Most callers will notice the difference, even if they cannot articulate it.
For the main greeting, either record internally using someone with a clear, steady voice and a quiet environment, or use a professional voice recording service. For sub-menus and less-trafficked options, quality TTS is acceptable.
File format matters: most business phone systems accept MP3 or WAV. Check your platform's specifications before recording.
Step 5: Configure Routing Rules for Each Option
With the script finalised and recordings ready, configure the destinations:
- Which ring group or extension does each option route to?
- What happens if nobody answers? (Queue, voicemail, overflow to another number?)
- What is the timeout behaviour if the caller presses nothing?
This is where your routing rules need to be clearly defined before you go into the settings. Changing routing logic after callers have memorised a menu creates confusion.
Step 6: Test Every Path Including the Wrong-Option Scenario
Before going live, walk through every possible caller journey:
- Press 1 — does it route correctly?
- Press 4 — does it route correctly?
- Press nothing — does the timeout fallback work?
- Press 0 — does it reach a human?
- Call after hours — does the correct after-hours message play?
- Press a number that isn't an option — what happens?
The "wrong option" scenario is the one most businesses skip and most commonly breaks. If a caller presses 7 on a four-option menu, the system should either prompt them to try again or route them to the fallback. Silence or a dropped call is not acceptable.
Sample IVR Script: Trades Business (3-Option Menu)
Below is a complete worked example for a plumbing or electrical business with three call types: new jobs, existing bookings, and accounts.
Main greeting (plays on answer):
"Thanks for calling Business Name. For new job enquiries and quotes, press 1. For existing bookings and service updates, press 2. For accounts and invoices, press 3. To speak with our team directly, press 0 or hold the line."
Option 1 — New enquiries (if unanswered after ring timeout):
"Thanks for your interest in Business Name. Our sales team is currently with another customer. Please leave your name, contact number, and a brief description of the job and we'll call you back within two business hours."
Option 2 — Existing bookings (if unanswered):
"You've reached the Business Name service team. Please leave your name, job number if you have it, and your contact number and we'll get back to you as soon as possible."
Option 3 — Accounts:
"You've reached the Business Name accounts team. Please leave your name, invoice number, and contact details and we'll follow up within one business day."
After-hours main greeting (plays outside business hours):
"Thanks for calling Business Name. Our office is currently closed. Our business hours are Monday to Friday, 7am to 5pm. For urgent after-hours service, press 1. To leave a general message, press 2."
This script is deliberately minimal. Every word earns its place. Notice there is no "please listen carefully as our options have changed," no "your call is important to us," and no filler.
Single-Level vs Multi-Level IVR: What Most SMBs Actually Need
A single-level IVR presents one menu and routes callers to a destination. A multi-level IVR presents an initial menu, and one or more options leads to a sub-menu with further choices.
For most Australian small businesses, a single-level IVR with four options is the right answer. It is fast, clear, and easy to maintain.
A two-level IVR makes sense when one destination genuinely needs further splitting — for example, a national business where option 1 is "Sales" and the sub-menu asks the caller to select their state. That is a defensible second level.
Three levels is almost always too complex for an SMB context. By the time a caller has navigated two menus and is facing a third, the mental overhead is significant and the odds of them pressing 0 or hanging up are high. If you find yourself designing a three-level menu, that is a signal to go back to Step 2 and consolidate your groups.
For further reading on how this applies specifically to smaller teams, see call routing for small business.
After-Hours IVR: A Separate Configuration, Not an Afterthought
Your IVR should behave differently outside business hours. This is not optional — it is a basic caller expectation. The two things callers need to know after hours are: (1) they have reached the right business, and (2) what to do next.
A well-configured after-hours setup includes:
- A greeting that confirms the business name and states that the office is closed
- Current business hours stated clearly
- An option for genuine emergencies (if your business offers urgent or after-hours service)
- A voicemail option for general enquiries
What it should not include is a silent transfer to a ringing extension that nobody answers. If your staff are not in the office, do not ring their desk phones. Route to voicemail or an after-hours message with a clear callback promise.
For a complete walkthrough of how to configure time-based routing, see our guide on after-hours routing.
Common IVR Mistakes Australian Businesses Make
Too Many Options
The most frequent mistake, and the most damaging. Eight options feels thorough to the person who built the menu. To the caller listening on a mobile in a car park, it is a cognitive overload. Pare it back.
Routing Everything to the Same Person
If all four options ring the same mobile number, the IVR is providing the appearance of structure without the substance. Callers still get the right person by chance, not by design. When that person is unavailable, every caller hits the same single point of failure. Proper routing rules distribute load and create resilience.
Forgetting to Update the Menu When the Business Changes
Staff leave. Departments are restructured. New services are added. The IVR menu, once set, is rarely revisited — until a caller complains that pressing 2 for "Sarah in accounts" results in a voicemail for someone who left eight months ago. Treat the IVR as a living document. Review it whenever there is a significant staffing or structural change.
No Voicemail Fallback
If a call rings out with no voicemail, the caller has nowhere to go. That enquiry is lost. Every routing destination should have a fallback — either a team voicemail, an overflow number, or a queue with a maximum wait time. The goal is that no call ends in silence.
How Pickle Handles IVR Setup
Setting up an IVR from scratch — mapping call types, writing scripts, configuring routing rules, recording greetings, testing every path — is a multi-hour task the first time, and an ongoing maintenance commitment after that.
Pickle handles the IVR configuration as part of the phone system setup. When a new customer comes on board, Pickle's team works through the call mapping and menu design with them directly, then builds and configures the system. Customers do not need to navigate portal settings or troubleshoot routing logic themselves.
If your current IVR is too complicated, was never properly configured, or simply has not been updated in years, Pickle can audit and rebuild it.
Call 1300 688 588 or email [email protected] to talk through your current setup.
Frequently Asked Questions
Q: How many options should an IVR menu have?
A: Four options per level is the practical target for most SMBs. Five is the ceiling. Beyond five, callers struggle to retain what they heard at the beginning of the menu by the time the last option plays — particularly on mobile where they may be distracted. If you have more than five genuine call types, consolidate them into broader groups rather than adding more options.
Q: Do I need a professional voice recording or can I use text-to-speech?
A: For the main greeting — the first thing every caller hears — a human recording is strongly recommended. It sounds more professional and sets a better first impression. Text-to-speech is acceptable for sub-menus, voicemail prompts, and less-trafficked options where cost or speed of update is a factor. The gap in quality between good TTS and human recording has narrowed, but it has not closed.
Q: What happens if a caller presses the wrong option?
A: Your IVR should handle invalid input gracefully. The standard behaviour is to play a prompt ("Sorry, that wasn't a valid option — please try again") and replay the menu. After two or three invalid attempts, the system should default to a fallback — usually the receptionist or a general voicemail. A caller pressing a non-existent number and hearing silence or a disconnection tone is a poor experience that reflects badly on the business.
Q: Should the IVR menu change after hours?
A: Yes, always. After-hours callers have different needs and expectations. They need to know the business is closed and what their options are — typically a voicemail or an emergency line if you offer urgent services. Playing the same menu after hours, where options ring desks that nobody is at, wastes the caller's time and generates missed calls with no message.
Q: How often should I review and update my IVR menu?
A: Review it whenever there is a meaningful change to your business — new staff, departing staff, restructured departments, new services, or changed business hours. Beyond that, a light review every six to twelve months is good practice to make sure every destination still routes to the right place and every voicemail prompt still reflects the correct name and team.