Department Call Routing: How to Design an IVR Callers Don't Hate

Everyone has been stuck in a phone menu that seemed designed to keep them from a human. Seven options, none that fit, and a loop back to the start. Those experiences shape how people feel about the business before anyone says hello.

The opposite is just as real. A clear greeting, three sensible choices, and a person picking up within a few rings. The caller barely notices the routing, and that is exactly the point.

This guide shows how to design department call routing for a growing business or agency: how to map your callers, write a short menu, choose the right ring strategy for each team, and test the whole thing before it goes live.

Start with callers, not departments

The most common routing mistake is building the menu around your org chart. Callers don’t know your departments. They know why they are calling.

Spend a week tallying the reasons people call. A simple tally sheet at the front desk works, or review recent call notes. Take Crestview Creative, a fictional 12-person agency. Their tally looked roughly like this:

• New business inquiries
• Existing clients with a campaign or website question
• Billing and invoice questions
• Vendors, job applicants and sales pitches
• Urgent issues, such as a client site being down

That list becomes the backbone of the menu. Notice that “urgent issues” earned its own path. Mixing emergencies into general support means a client with a broken checkout waits behind someone asking for a logo file.

Map every path on paper first

Before touching any settings, draw the flow. For each caller type, answer four questions:

1. Where should the call ring first? A specific person, a team, or an AI agent.
2. How long should it ring? Usually 15–25 seconds per step.
3. What happens if nobody answers? Another team, voicemail, or a callback option.
4. What changes after hours? A different destination, message or urgent line.

Here is Crestview’s worksheet:

Caller need	Menu option	Rings first	If unanswered	After hours
New business	1	Sales ring group	Sales lead’s mobile, then voicemail with instant text-back	AI receptionist books a call
Client support	2	Account managers	Support queue, then ticket voicemail	Voicemail creates ticket
Billing	3	Office manager	Billing voicemail	Voicemail, reply next business day
Urgent site issue	9	On-call developer	Backup developer	On-call rotation
Everything else	0 or no input	Front desk	General voicemail	General voicemail

Two design choices stand out. Pressing nothing sends the caller to a person rather than repeating the menu, and new business never ends in a plain voicemail. Missed sales calls get an automatic text so the lead isn’t lost.

Write a menu people can follow

Keep it short

Three to four options is plenty for most small businesses. If you need more, you probably need smarter routing, not a bigger menu. Put the most common reason first.

Lead with the reason, then the number

Callers remember “for billing, press 3” better than “press 3 for billing,” because they hear the thing they care about before the digit. Sample greeting:

“Thanks for calling Crestview Creative. If you’re interested in working with us, press 1. If you’re a current client, press 2. For billing, press 3. If your website is down right now, press 9. Or stay on the line to reach our front desk.”

That greeting runs well under 20 seconds. Skip the “please listen carefully as our options have changed” line; it adds time and rarely helps.

Consider speech or AI answering

Some callers won’t press buttons at all. An AI receptionist can greet callers, ask what they need in plain language, answer common questions and transfer or book appointments. On SaaSVisionary, one AI phone agent is included on the Team plan and unlimited agents on Unlimited.

Choose a ring strategy for each team

How a call rings inside a department matters as much as the menu. The common strategies:

• Simultaneous ring. Everyone in the group rings at once, first to answer wins. Good for sales, where speed matters most.
• Sequential (hunt) ring. Rings one person, then the next, in a fixed order. Good when a primary contact should get first chance.
• Round robin. Rotates who rings first to spread the load. Good for support teams with shared responsibility.
• Direct to owner. Existing clients ring their own account manager first, then the team. Works well when your CRM knows which manager owns the contact.

Mix strategies as needed. Crestview uses simultaneous ring for sales, owner-first for client support and a single person for billing.

Plan for the moments nobody answers

Fallbacks are where call flows succeed or fail. Every path needs a planned ending.

• Voicemail with a purpose. Department-specific greetings that tell callers when to expect a reply.
• Missed-call text-back. An automatic text such as “Sorry we missed you, this is Crestview. How can we help?” keeps the conversation going. Keep it relevant to the caller’s inquiry and follow carrier messaging rules.
• Voicemail to task. Route voicemails into the CRM as tasks with an owner, not into an inbox nobody checks.
• Business hours schedules. Switch routes automatically for evenings, weekends and holidays. Update holiday schedules at the start of each year.

Test before and after launch

Call flows break in subtle ways. Run a structured test before going live, and repeat it after any change.

Test checklist

• Call each menu option during business hours and confirm the right phones ring.
• Let each path ring out and confirm the fallback works.
• Press nothing and confirm you reach a person or the general line.
• Press an invalid key and confirm the menu handles it gracefully.
• Call after hours and on a scheduled holiday.
• Leave a voicemail on each path and confirm a task or notification appears.
• Confirm missed-call texts arrive and read correctly.
• Call from a mobile phone with poor reception to check prompt clarity.

Keep measuring

Once live, review a few numbers monthly: calls per menu option, how often each path reaches voicemail, and missed calls by time of day. If one department regularly goes to voicemail at lunch, adjust staffing or add a backup ring step. A phone system with call reporting tied to your CRM makes this review take minutes. If you also track which marketing sources drive calls, call attribution shows which campaigns are worth the phone traffic.

When the right people pick up, the conversation still needs structure. Our agency phone scripts cover discovery, support and escalation calls.

Frequently asked questions

How many options should an IVR phone menu have?

For most small businesses and agencies, three or four options work best. Callers struggle to remember longer lists and often press zero out of frustration. Put the most common reason first, give urgent issues a clear path, and let callers who press nothing reach a person. If you need more options, consider nested menus or AI answering instead.

What is the difference between a ring group and a call queue?

A ring group rings several phones at once or in order, and the call goes to voicemail or another step if nobody answers within a set time. A call queue holds callers on the line, often with music or position updates, until an agent is free. Ring groups suit small teams, while queues suit higher call volumes.

How should calls be handled after business hours?

Set a separate after-hours route that plays a greeting with your hours and offers the best alternative: voicemail that becomes a task, an urgent line for true emergencies, or an AI receptionist that answers questions and books callbacks. Switch schedules automatically, including holidays, so nobody has to remember to change settings.

Can I route existing clients directly to their account manager?

Yes, if your phone system is connected to your CRM. When a known caller dials in, the system can look up the contact’s owner and ring that person first, then fall back to the wider team. It saves clients from explaining themselves and makes the relationship feel personal.

Ready to map and launch your call flows? Start a free 14-day trial.