Blog / IVR, Queues And Call Routing

IVR Phone Menu Setup: Scripts, Examples, and Best Practices

Plan an IVR phone menu around caller needs, staffed destinations, and clear fallbacks. Use practical setup steps, adaptable scripts, and a prelaunch checklist for sales, support, and service teams.

Business owner connects callers with helpful teams through a simple phone menu

An IVR phone menu helps callers reach the right person without having to guess which number to call. To set one up, map common caller needs to staffed destinations, write a short greeting, assign keypad choices, and decide what happens after hours or when callers do not make a selection. The scripts and checklist below are ready to adapt for sales, support, and home-service teams.

Key takeaways

  • A useful IVR phone menu starts with callers’ needs and staffed destinations, not a list of every department or employee.
  • Three to five clear choices is a practical starting point for the main menu; group additional options into short, related submenus.
  • Every menu needs a defined path for no input, an invalid key, human help, voicemail, and after-hours calls.
  • Testing each key, destination, schedule, and fallback from a caller’s perspective can expose dead ends before launch.
  • In a 2025 YouGov survey, 35% of Americans chose phone calls as their top way to contact businesses about customer service, compared with 23% who chose email (YouGov survey).

What is an IVR phone menu?

An IVR phone menu is an automated greeting that lets callers choose where their call goes, usually by pressing a key or, if the system supports it, saying a response. For example, a caller might press 1 for sales and 2 for customer support. Each selection should lead to a person, queue, voicemail box, or another useful next step.

IVR means interactive voice response: a phone system that responds to caller input. A phone menu is the spoken list of choices callers hear. Call routing is the set of rules that connects each choice to its destination. Providers may use different names for similar features, so check what a system can do. Voicalyst’s IVR phone menus and call routing page describes that product capability.

IVR vs. auto attendant

An auto attendant greets callers and directs them to a person, extension, or department. An IVR also accepts input and can use it to route calls or trigger actions. Business phone providers sometimes use the labels interchangeably, so compare the functions offered rather than relying on the feature name.

How do you plan an IVR phone menu?

Plan an IVR menu by listing why people call, matching each reason to a destination that can answer, and deciding what happens when that destination is unavailable. Confirm your business hours, staffing, voicemail coverage, and callback commitments before recording a greeting.

Team plans a clear phone menu by arranging a branching call routing tree

List the reasons people call

Start with recent calls, employee feedback, and the questions your team answers most. Group those reasons into a few broad needs, such as new business, existing orders, billing, appointments, or urgent service.

Avoid creating a menu option just because a role or department exists. If callers rarely need that team, or the team cannot reliably answer, send those calls to a relevant staffed group or offer a callback path.

Match each reason to a staffed destination

For every choice, write down where the call goes and who covers it. A destination could be a team queue, a specific employee, voicemail, or a callback process. Decide what happens if nobody answers: callers might wait briefly, leave a message, or request a return call.

If callers need to leave a message, set clear expectations about what happens next. These business voicemail greeting scripts can help you write a concise prompt.

Decide what happens outside business hours

Set a separate plan for weekends, holidays, and times when the usual teams are unavailable. Depending on your service, callers might leave voicemail, request a callback, hear the next opening time, or reach an on-call employee. Offer emergency routing only if a responsible person is available to handle those calls.

How do you set up an IVR phone menu?

To set up an IVR, create a menu and greeting, map each keypad choice to a staffed destination or useful action, connect the menu to your business number, and configure business-hours and fallback behavior. Provider interfaces differ, but the setup decisions are similar; this guide to customer support phone systems covers the wider routing context.

  1. Create the menu and write the greeting. State your business name, then give callers short, clear choices. Keep a copy of the approved script so the recorded greeting and routing settings stay in sync.
  2. Map each key to a destination. Choose a queue, person, voicemail box, or callback path for every option. Confirm who covers the destination and what callers should hear if nobody answers.
  3. Connect the menu to the business number. Point the main number or relevant line to the menu. If you are moving an existing number, learn how business number porting works.
  4. Set up schedules and fallbacks. Configure open hours, after-hours and holiday routes, no-input behavior, invalid-key handling, a human-help option, and voicemail or callbacks.
  5. Test the whole call flow. Call from an outside phone and press every key, including incorrect keys. Test during and outside business hours, and confirm each destination answers or reaches its intended fallback.

How many options should an IVR menu have?

Use about three to five clear choices on the main IVR menu as a practical starting point, not as a universal research-backed threshold. If your business has more common call reasons, group them into short, related submenus and make the human-help path easy to find.

Put the most common caller needs first. State choices consistently, such as “For a new estimate, press 1” and “For an existing appointment, press 2.” Avoid making callers listen to a long list of uncommon departments before they can choose.

A submenu makes sense when it groups related needs, such as billing questions, payment status, and invoices. Keep each submenu short, and make it easy to return to the main menu or reach a person.

What are useful IVR menu examples and scripts?

These IVR menu scripts use short prompts and destinations a small or midsize business can staff. Replace the bracketed text with your details, and offer emergency or on-call routing only if someone is prepared to answer those calls.

Sales IVR script

“Thank you for calling [Company]. If you’re a new customer interested in [product or service], press 1. If you’re an existing customer with a sales question, press 2. To reach our main team, press 0. To hear these options again, press 9.”

  • 1: New sales inquiries → sales queue or assigned representative.
  • 2: Existing customer sales questions → account team or customer support.
  • 0: Human help → staffed main team; if unavailable, offer voicemail or callback.
  • 9: Repeat the menu.

If you do not have a staffed main team, replace “press 0” with a monitored path and explain what callers can expect.

Customer support IVR script

“You’ve reached [Company] support. For help with an existing order or service, press 1. For billing, press 2. If you’re considering our service, press 3. To speak with a team member, press 0.”

  • 1: Existing order or service → support queue.
  • 2: Billing → billing team; if that team is not separately staffed, route to support.
  • 3: New-customer questions → sales queue.
  • 0: Human help → designated staffed team.

A 2025 U.S. customer experience survey found that 91% of customers appreciate an easy, frictionless experience, while 66% said long waits or hold times would cause them to leave (2025 customer experience survey). Keep the next step clear and avoid sending callers into queues your team cannot cover.

Home-service business IVR script

“Thank you for calling [Company]. For a new estimate or service request, press 1. If you have an existing appointment, press 2. If you are an existing customer with a service question, press 3. For an urgent service issue, press 4. To speak with our team, press 0.”

  • 1: New customer → scheduling or estimates team.
  • 2: Existing appointment → dispatcher or scheduling team.
  • 3: Existing customer question → customer support.
  • 4: Urgent service issue → on-call team, only if staffed; otherwise use an accurate alternative.
  • 0: Human help → staffed team.

Do not describe a line as “24/7 emergency service” unless a qualified person is actually available at all hours. If urgent calls are handled only during business hours, say so.

After-hours and holiday script

“Thank you for calling [Company]. Our office is currently closed. Our regular hours are [days and hours, time zone]. For [service-specific urgent issue], press 1 to reach our on-call team [only if staffed]. For all other requests, press 2 to leave a message, or visit [website] to [available action]. We’ll respond within [realistic timeframe].”

For holidays, name the next opening date if it is known. If callers can request a callback instead of leaving voicemail, describe how and when your team will respond.

What should an IVR phone menu script include?

An IVR script should identify the business, state the most common caller needs, explain each key choice, and offer clear instructions for human help and fallback paths. Include business hours and realistic response expectations where relevant, then read the finished script aloud to catch confusing wording before recording.

“Thank you for calling [Company name]. For [most common reason], press 1. For [second reason], press 2. For [third reason], press 3. To [human-help option], press 0. To hear the menu again, press 9.

If we can’t answer, [voicemail or callback instructions]. Our hours are [days and hours, time zone]. When we’re closed, [after-hours options and next response time].”

Check that the business name, option labels, hours, and destinations agree with the phone system settings. If callers should be able to press a key while the greeting is playing, verify that the system accepts early keypresses; not every setup handles them the same way.

How do you test an IVR phone menu before launch?

Test an IVR by calling from an outside phone and trying every valid and invalid selection, no-input behavior, business-hours schedule, after-hours route, and fallback. A usable menu speaks plainly, gives callers enough time to choose, and has a defined next step when the preferred destination cannot answer.

Diverse team tests a phone menu with headsets, handsets, and a blank checklist
  • Use plain language. Say what callers need to do, not internal department names they may not recognize.
  • Speak at a measured pace. Leave a short pause between options, pronounce numbers clearly, and avoid rushing through long service names.
  • Keep a human-help path easy to find. Offer a person where staffing allows; if the live team is unavailable, explain the voicemail or callback alternative.
  • Make the menu usable without speech recognition. Keypad choices give callers a reliable option when voice input is unavailable or inconvenient.
  • Test every key and fallback. Check valid choices, invalid keys, no input, repeat menu, voicemail, callback, human help, and every after-hours or holiday route.
  • Check destinations and schedules. Confirm each team is staffed when the menu sends calls there, and update hours and holiday dates before they change.
  • Review outcomes after launch. Look for repeated transfers, missed calls, voicemail volume, long waits, and calls that end during the menu. Use those patterns to refine options and staffing.

Frequently Asked Questions

What is an IVR phone menu?

An IVR phone menu is an automated phone system that greets callers and routes them based on keypad selections or, when available, spoken responses. For example, callers might press 1 for sales or 2 for support. Each choice should lead to a staffed team, voicemail, callback process, or another useful next step.

How many options should an IVR menu have?

Start with three to five clear choices on the main menu. This is a practical usability rule of thumb, not a universal threshold. Group additional choices into short, related submenus, put common needs first, and make the route to human help easy to find.

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

An IVR accepts caller input, usually keypad selections or spoken responses, and uses it to route calls or trigger actions. An auto attendant typically greets callers and directs them to a person, extension, or department. Providers sometimes use the terms interchangeably, so compare the functions a phone system includes.

How do I route calls after business hours?

Set a separate after-hours schedule that states your business hours and offers relevant next steps, such as leaving voicemail, requesting a callback, or reaching an on-call team. Route emergencies only if your business provides that service and someone responsible is available to answer.

Can callers reach a live person from an IVR?

Yes. Include an easy-to-find option for a person, such as “Press 0 for the team,” and decide where that selection goes. If a live team is unavailable, route callers to monitored voicemail or a callback request and state the response time your team can meet.

To build a menu that fits your call flow, explore Voicalyst’s IVR phone menu and call routing features or book a demo.

Put this into practice with Voicalyst

Voicalyst is the cloud phone system US sales and support teams set up in minutes: a business phone system with cloud telephony, AI call summaries and texting.

Start free trialBook a demo
VE

Voicalyst Editorial Team

Guides and research from the team building Voicalyst.