IVR Routing for Many Departments: Menus That Scale Without Confusion
How to design phone menus for organisations with many departments: grouping, directories, skills-based routing, ownership rules and avoiding deep menu trees.
A small business can read out five options and be done. An organisation with a dozen teams, several sites and shared services faces a harder problem: how to get each caller to the right place without a menu so long that nobody remembers the first item. Add acquisitions, restructures and teams that change names, and the menu quickly becomes a map of the company's history instead of a tool for customers. This guide offers ways to keep multi-department routing understandable and maintainable. For the basics of menu writing, read IVR Menu Design.

Start with what callers need, not your org chart
Callers do not know which department handles which topic, and they should not have to. They know their problem: "my order is late", "I want to change my appointment", "I need a quote". Group the menu by these needs. Teams that share a need can sit behind one option and divide the work internally.
Organising by structure vs by need
| By org chart | By caller need | |
|---|---|---|
| Example options | Finance, logistics, customer service, sales operations | Orders and deliveries, billing, new enquiries |
| Caller must know | Which department owns their issue | Only what they want to do |
| Maintenance | Changes with every reorganisation | Stable as long as customer needs stay stable |
| Misroutes | Frequent, because internal names are unfamiliar | Fewer, because options match the caller's words |
To find the real list, look at a few months of call reasons from agent notes, voicemails, transfers and web enquiries. The top five to seven reasons usually cover most calls. Everything else can live behind an "other" route, a directory, or an agent who transfers.
Structuring a large menu
The top level: a handful of choices
Keep the first menu to four or five options, plus a way to reach a person. If you cannot fit your top reasons in five, combine related ones or move rare ones to a second level. Put the most common choice first.
The second level: only when needed
A second level is acceptable for branches that serve genuinely different groups, such as an "existing customers" option that splits into products. Avoid a third level. If a branch needs one, ask whether a different front-door design, such as asking a question in words, would do the job.
A scalable structure
- Greeting and languageOne short sentence, then a language choice if you serve several.
- Time gateOpen, closed, holiday and emergency checks happen before the menu is read.
- Main menuFour to five need-based options, with a way to reach a person.
- Second menu if neededOnly for branches with distinct sub-groups; never a third level.
- Directory or searchFor callers who know the person or team they want.
- DestinationA queue with an owner, a fallback and an out-of-hours plan.
Other ways to reach the right team
- Dial-by-name directory: useful when callers know the person. See Dial-by-Name Directories in an IVR.
- Extension numbers: frequent callers and partners often prefer to enter an extension; announce it once and keep it optional.
- Skills-based routing: one number and one queue, with calls handed to agents who have the right skill. Fewer menu options, more routing intelligence. See ACD Call Routing.
- Caller recognition: if a number is known, route to the account owner or the last team they spoke to, with a way to change.
- An AI front door: a voice agent asks what the caller needs and either answers or hands over. Treat it as a front end that still needs a path to a person. See IVR vs AI Voice Agent.
Ownership: who is responsible for each destination
Multi-department systems fail when nobody owns the destinations. A queue exists, calls go to it, and months later nobody remembers who staffs it. Write a simple ownership table and review it every quarter.
| Destination | Owner | Hours | Fallback if nobody answers | Reviewed |
|---|---|---|---|---|
| Orders and deliveries | Operations lead | Weekdays, set times | Overflow to customer service, then voicemail | Each quarter |
| Billing | Finance lead | Weekdays, set times | Callback request | Each quarter |
| New enquiries | Sales manager | Extended hours | Voicemail and callback within a set time | Each quarter |
| General help | Support lead | All open hours | Message plus alternative channels | Each month |
Fallbacks, overflow and transfers
When many departments exist, calls will land in the wrong place. Plan for it. Agents need an easy, cold or warm transfer to the right team, and a rule for what happens if that team is closed. Teams need a way to overflow when busy. And callers should not have to repeat their story.
- Allow transfers between every pair of departments that commonly exchange calls.
- Show the agent the menu choice the caller made, so they do not ask again.
- Set overflow queues deliberately, so a busy team passes calls to a team that can help.
- Define what happens at closing time for calls still in the queue.
- Track transfers per team; frequent transfers from one option mean the label confuses callers. Call Transfer Rate explains the measure.
Several sites and time zones
If departments sit in different places, hours and holidays differ too. Do not announce a team as available if its site is closed. Use per-team hours, and apply holiday calendars by site. Running a Multi-Site Contact Center gives further ideas.
Keeping the structure healthy
Quarterly review of a multi-department menu
- Top call reasons still match the menu options
- Every option has a living owner, hours and a fallback
- Team or product names in prompts are current
- Transfer and misroute rates reviewed by option
- Hours and holidays checked for every site
- Any option used by almost nobody is merged or removed
- A test call made through every branch
A hypothetical example
Imagine a regional services company with sales, installation, repairs, billing, a parts desk and a head office switchboard. Its old menu had eight options, one per team, and most callers pressed zero. After studying call notes, the company found that four reasons covered nearly every call: new enquiries, existing jobs, repairs and billing. The new menu has those four options plus a way to reach a person.
Installation and the parts desk now sit behind "existing jobs", where agents with the right skills take the calls. The switchboard moved to a name directory for the few callers who need it. The company did not add staff; it changed the shape of the menu to match how callers think. The same teams exist, but callers no longer have to know their names.
IVR Analytics explains how to measure option usage and drop-off, which tells you where to simplify.
Multiple departments in Call
In Call, each department can be a queue with its own name, answer target, hours, closed greeting, overflow queue and voicemail. A queue can require a skill, so only agents with that skill are offered its calls, and teams and skills are set up under team settings. Holiday calendars close the queues that use them, and an emergency closure, switched on by the platform operator, can close every queue at once. The routing simulator lets you test how a pretend call would move through the rules for any queue. Owners, administrators and managers can configure queues. See Setting Up Call Queues in Call and Setting Up IVR and Business Hours in Call to build it.
Frequently asked questions
How many options should the first menu have?
Four or five, plus a way to reach a person. If you have more reasons than that, group related ones or move rare ones to a second level or a directory.
Should I organise the menu by department or by customer need?
By customer need. Callers describe problems, not departments, and need-based menus survive reorganisations better.
When is a directory better than a menu?
When callers know the person or team they want, such as partners and repeat contacts. A directory lets them find the destination without wading through every option.
What is skills-based routing?
Instead of many menu options, calls go to a shared queue and are offered to agents who have the right skill. It reduces menu depth, but it needs good records of who can do what.
How do I stop calls ending up in the wrong department?
Use plain option labels, check the misroute and transfer data, and make transfers easy. A pattern of transfers from one option shows where the label confuses callers.
How often should I review a large menu?
Each quarter at minimum, and whenever teams, products or sites change. Include a test call through every branch.