IVR and Auto Attendant Design: The Australian Business Guide

Almost every Australian business with more than a handful of staff ends up with a phone menu. Almost none of them design it: it accretes. Someone adds an option for accounts, someone else adds a sub-menu for warranty claims, a Christmas message gets recorded in 2023 and never removed, and three years later callers are pressing zero to escape a system that was supposed to help them.

A well-designed auto attendant is valuable: it gets callers to the right person faster than a receptionist can, it works at 6am, and it stops your best people answering questions about opening hours. A badly designed one is one of the most reliable ways to annoy a customer who was ready to spend money.

This guide covers the design rules that separate the two, written for Australian businesses and Australian calling habits.

1. IVR vs Auto Attendant: The Distinction That Matters

The terms are used interchangeably by most providers, and for most purchasing decisions that’s harmless. But they describe different levels of capability, and knowing which one you’re buying prevents disappointment.

The overwhelming majority of Australian businesses under 50 staff need an auto attendant and nothing more. If a provider is quoting you for IVR, ask what transaction it’s going to complete. If the answer is "it routes calls", you’re being quoted for an auto attendant with a better name.

2. Do You Even Need One?

This deserves asking honestly, because the answer is sometimes no.

A menu adds a fixed delay to every single call. If your call volume is low and your team is small, a well-configured ring group, where an incoming call rings several people at once and the first available answers, delivers a better caller experience than any menu. A human answering on the third ring beats a perfect menu every time.

3. The Seven Design Rules

These are the rules that hold up across almost every Australian business we’ve looked at.

Rule 1: Five options maximum, and aim for four

Callers hold menu options in working memory while listening. Past about five, they stop tracking and start waiting for whichever option sounds closest or press zero. If you have eight destinations, group them into four categories rather than reading out eight.

Rule 2: One level deep unless you can prove otherwise

Every sub-menu roughly doubles the abandonment rate at that point in the call. A second level is defensible when a category splits (sales → new business vs existing account). A third level almost never is. If your menu tree has three levels, the problem is usually your org chart leaking into your phone system.

Rule 3: Put the action before the number

Say "For sales, press 1", not "Press 1 for sales". The caller is listening for their own need, not for numbers. When the category comes first they can stop processing the rest of the sentence as soon as they hear a match. It’s a small change that measurably reduces menu repeats.

Rule 4: Order by volume, not by org chart

Your most-called department goes first. Look at your call reports and order the menu by actual traffic. Most businesses put sales first out of habit when 60% of their calls are existing customers with a service question.

Rule 5: Always offer a person

Every menu needs an explicit path to a human, and it should be stated: "or stay on the line to speak with reception". Don’t rely on callers knowing that zero works. Hiding the human option doesn’t reduce your workload; it produces callers who press every key until something happens, and then arrive irritated.

Rule 6: Handle no-input and wrong-input gracefully

A caller on a mobile in a carpark may not press anything. Configure a timeout that re-reads the menu once, then routes to a default destination rather than hanging up. Never disconnect a caller for failing to make a selection. It’s the single most damaging thing a phone menu can do.

Rule 7: Keep the greeting under eight seconds

Callers are waiting to act. A twenty-second brand statement before the first option is time your caller spends becoming annoyed. Name the business, then go straight to the options. Save the marketing message for hold music, where it has an audience that’s already waiting.

4. A Menu Script That Works

Here’s a structure you can adapt directly. It’s deliberately plain.

That’s 14 seconds read at a natural pace, offers three options plus a human, and requires no explanation. Compare it with what most businesses actually run: a fifteen-second welcome message, a request to listen carefully because options have changed, six options, a sub-menu, and no stated path to a person.

5. After Hours, Public Holidays and the Australian Calendar

This is where Australian businesses get caught out more than anywhere else, because our public holidays are state-based and several move each year.

A time-of-day rule that only knows "Monday to Friday, 9 to 5" will cheerfully answer with your business-hours greeting on Melbourne Cup Day, on WA Day, on Easter Tuesday in Tasmania, and on every regional show day. The caller hears "press 1 for sales", presses 1, and rings out to an empty office.

What to configure:

1. Standard business hours per weekday, in your local timezone and check the platform handles daylight saving automatically if you’re in a DST state.
2. A separate after-hours greeting that states when you reopen and offers a voicemail or an emergency path. "We're closed" without "we reopen at 8:30am Monday" leaves the caller with an unanswered question.
3. A holiday calendar loaded with the public holidays for the state each site operates in, not a single national list.
4. An override switch your reception staff can activate from a handset or app. Unplanned closures happen; nobody should need to raise a support ticket to change the greeting during a flood or a power outage.
5. An emergency bypass for urgent calls, if your business has them: typically an option that diverts to an on-call mobile.

If your team works across states or from home, the timezone handling matters more still: our guide to phone systems for remote and hybrid teams covers presence and follow-the-sun routing in more depth.

6. Where the Menu Sends the Call

A menu option is only as good as its destination. Three patterns, in ascending order of robustness:

The upgrade from ring group to queue is the one most businesses delay too long. A ring group with everyone busy sends the caller to voicemail; a queue holds them with an indication of the wait. Callers will wait a surprisingly long time when they’re told where they’re in the line, and abandon almost immediately when they’re dumped into voicemail. Our call centre software guide covers queue configuration for teams of five to thirty.

For multi-site businesses, you can route on caller location before the menu is even played: see our explainer on MOLI codes for how location-based routing works on 1300 and 1800 numbers, and where its accuracy runs out.

7. Recording the Prompts

You’ve three options, and the right one depends less on budget than most people assume.

• Professional voice talent, roughly $150–$400 for a standard menu set in Australia. Worth it if your brand is premium or your callers are consumers. Ask for the raw files so you can re-record single lines later without a new session.
• Text-to-speech: included in most modern platforms and now good. Its real advantage isn’t cost, it’s that you can change a prompt in thirty seconds. For anything that changes seasonally, this wins outright.
• In-house recording: free, and almost always the worst option. A menu recorded on a handset in an open-plan office sounds exactly like that, and it’s the first thing a caller hears about you.

Whichever you choose: record all prompts in the same voice, at the same level, in the same session or with the same settings. A menu where option 3 is noticeably louder or in a different voice reads as neglect.

8. Measuring Whether It Works

An auto attendant is one of the few parts of a phone system with clean, available metrics. Check these monthly; all are standard reports in a modern hosted platform.

The most diagnostic single number is transfers after answering. It tells you the menu is confidently sending callers to the wrong place, which is worse than no menu at all, because the caller has now waited twice. If that number is high, your menu categories don’t match how your customers describe their own problems, and the fix is to rename the options in their words rather than yours.

9. Where AI Changes This

The menu-driven auto attendant is a workaround for a limitation that’s starting to lift. The reason callers press numbers is that the system couldn’t previously understand "I need to change my delivery address".

Conversational routing, where the caller simply states what they want and is routed on intent, is now available on the more advanced Australian platforms, and it removes the menu-depth problem entirely because there’s no menu. Callers with an unusual need are no longer forced into the nearest wrong category.

Two caveats worth holding onto. First, it needs to fail well: a caller whose intent isn’t understood twice should reach a person, not a loop. Second, it doesn’t remove the need for the thinking in this guide: you still have to define the destinations, the after-hours behaviour and the holiday calendar. It changes how callers select, not what they’re selecting from.

Our AI voice agents guide covers what these systems handle and what they cost per call, and the AI contact centre buyer's guide sets out the four layers of AI worth paying for.

10. The Build Checklist

Work through this in order before you record anything.

1. Pull three months of call reports and list your actual call reasons by volume.
2. Group them into no more than five categories, named in your customers' words.
3. Order the categories by volume, highest first.
4. Assign each to a queue or ring group, not a single extension.
5. Write the greeting script; read it aloud and time it. Under eight seconds to the first option.
6. Add the explicit path to a human as the final line.
7. Define the no-input behaviour: repeat once, then route to default.
8. Build the after-hours greeting with your reopening time stated.
9. Load the public holiday calendar for each site's state.
10. Configure a manual override reception can trigger from a handset or app.
11. Record all prompts in one voice, one session, Australian English.
12. Test every option, including no-input and invalid keys, from a mobile and a landline.
13. Diarise a review at 30 days against the metrics in section 8.

If you’re setting this up as part of a provider change, do it before cutover rather than after: our switching checklist puts it in sequence with porting and the rest of the migration.

Frequently Asked Questions

What is the difference between an IVR and an auto attendant?

An auto attendant routes calls to a person or team based on menu key presses. An IVR does that and also completes transactions by looking up data: checking a balance, confirming a booking, taking a payment. Auto attendants are included in essentially every hosted PBX; true IVR requires integration with the system holding your data and is usually a paid tier. Most Australian businesses under 50 staff need an auto attendant only.

How many options should a phone menu have?

Five at most, and four is better. Callers hold menu options in working memory while listening, and past five they stop tracking and either pick the closest-sounding option or press zero. If you’ve more destinations than that, group them into broader categories rather than reading out a longer list.

Should you say "press 1 for sales" or "for sales, press 1"?

Say "for sales, press 1": put the category before the number. Callers listen for their own need rather than for numbers, so leading with the category lets them stop processing as soon as they hear a match. It measurably reduces the number of callers who need the menu repeated.

How do I handle Australian public holidays in my phone system?

Load a holiday calendar with the public holidays for the state each site operates in, rather than a single national list. Australian public holidays are state-based and several move each year, so a simple Monday-to-Friday time rule will answer with your business-hours greeting on Melbourne Cup Day, WA Day, Easter Tuesday in Tasmania and regional show days. Also configure a manual override that reception can trigger from a handset for unplanned closures.

What is a good abandonment rate for a phone menu?

Under 5% abandonment during the menu itself, under 15% of callers opting out to an operator, and under 15% of answered calls needing a transfer afterwards. Transfers after answering is the most diagnostic figure: a high rate means the menu is confidently routing callers to the wrong place, which is worse than having no menu, because the caller has waited twice.

Should I use text-to-speech or a professional voice for IVR prompts?

Professional voice talent costs roughly AUD $150 to $400 for a standard Australian menu set and suits consumer-facing or premium brands. Modern text-to-speech is good and its real advantage is that prompts can be changed in seconds, which wins for anything seasonal. Whichever you choose, set the voice to Australian English: most platforms default to US English and record every prompt in the same voice and at the same level.

Is an auto attendant always better than a receptionist answering?

No. A menu adds a fixed delay to every call, and a human answering on the third ring beats a perfect menu. Add a menu when you take more than about 30 calls a day, have three or more distinct destinations, transfer more than a quarter of calls after answering, or need to handle calls outside staffed hours. Below that, a ring group and a good voicemail serve callers better.