A phone tree is the menu callers hear when they dial a business: "For billing, press 2." The best phone tree examples have three to five options, one or two levels, and a clear path to a human. Below are eight complete menus with diagrams, word-for-word scripts, option counts and routing logic, plus a blank template you can copy.
Key takeaways
- A well-built support phone tree has 3 to 5 options per level and no more than 2 levels, with a zero or "operator" escape on every menu.
- In a 2019 Clutch survey of 501 people, 88% preferred speaking to a live agent over a phone menu, and 69% named irrelevant options as their top frustration.
- Every example below includes a fallback path (no input, invalid input, voicemail) and an after-hours variant, because the main menu is only half the routing logic.
- Clinic, property and home services menus must put emergency language ("hang up and dial 911") before any option, since a phone tree is not an emergency system.
- Track four numbers after launch: zero-out rate, abandon rate, misroutes and time to answer.
What is a phone tree, and how is it different from an IVR?
A phone tree is a menu of spoken options that routes a caller to the right person, queue or recording. It is the structure; an auto attendant is the system that plays it, and IVR (interactive voice response) is the broader category that can also read data or accept speech.
A group calling tree, used by schools and churches to relay notices person to person, is a different thing. These examples cover business phone trees only.
Quick answer, a basic 1-level phone tree:
"Thanks for calling [Business]. For sales, press 1. For support, press 2. For billing, press 3. To speak with someone else, press 0."
How to read the diagrams
Each diagram shows the option number, the label, and where the call lands. "Queue" means callers wait for the next available agent. "Ring group" means several phones ring at once or in sequence. Option counts include only choices that route a call, not the repeat or zero keys.
What rules sit behind every phone tree example?
Every example below follows the same rules: three to five options per level, two levels at most, the busiest option first, and a zero escape to a person. The rules exist because callers lose patience quickly, and the available survey data, while dated and vendor-run, points the same way.
- Order by call volume, not org chart. If most calls are order status, that is option 1, even if sales sits higher on your org chart.
- Say the choice, then the number. "For returns, press 2" lets callers listen for their word.
- Always allow zero. In the Clutch data, 70% of people have pressed zero and 65% have said "operator" or "agent" to bypass a menu. They will try it whether you plan for it or not.
The evidence for keeping menus short: the 2019 Clutch survey found 88% preferred a live agent, and listening to irrelevant options (69%) was the top frustration. A Vonage survey of 2,000 consumers reported 51% had abandoned a business over an IVR-based call center experience and 46% said menus are usually too long. Both are vendor-run surveys, so treat them as directional.
For build steps and prompt-writing detail, see our IVR phone menu setup guide.
What do 8 customer support phone trees look like by industry?
Eight industries need eight different menus because callers want different things first. An online store leads with order status, a clinic leads with urgency, and a plumber leads with emergency dispatch. Each example gives the audience, a diagram, the script, option count and routing logic.
1. E-commerce store
For: online retailers where most calls are "where is my order?"
Main menu
1 Order status -> text-back link, else support queue
2 Returns -> support queue
3 Shipping -> support queue
4 Something else -> support queue -> voicemail
0 / no input -> support queue
Script: "Thanks for calling [Business]. For order status, press 1. For returns and exchanges, press 2. For shipping questions, press 3. For anything else, press 4. To repeat these options, press 9."
Size: 4 options, 1 level. Routing: option 1 can send an order-tracking text so the caller may not need an agent. After hours: "Our team is back at 9 a.m. Eastern. Press 1 to get a tracking link by text."
2. SaaS company
For: software teams separating outages from how-to questions.
Main menu
1 Technical support
1 System down or errors -> priority queue
2 How-to question -> standard queue
2 Billing -> billing ring group
3 Onboarding -> onboarding ring group
4 Sales -> sales ring group
Script: "Thanks for calling [Business]. For technical support, press 1. For billing, press 2. For onboarding help, press 3. For sales, press 4." Second level: "If your system is down or showing errors, press 1. For how-to questions, press 2."
Size: 4 top options plus 2 sub-options, 2 levels. After hours: play a status-page message, then offer voicemail that becomes a ticket.
3. Medical or dental clinic
For: practices that handle appointments, clinical questions and refills.
Caution: a phone tree is not an emergency service. The emergency line comes before any option.
Greeting: "If this is an emergency, hang up and dial 911."
1 Appointments -> front desk ring group
2 Nurse or urgent concern -> clinical queue
3 Billing and insurance -> billing voicemail/queue
4 Prescription refills -> refill voicemail
Script: "Thank you for calling [Clinic]. If this is a medical or dental emergency, hang up and dial 911. To schedule or change an appointment, press 1. To speak with a nurse about a symptom or concern, press 2. For billing and insurance, press 3. For prescription refills, press 4."
Size: 4 options, 1 level. After hours: repeat the 911 line, then give your practice's on-call instructions and a voicemail option.
4. Home services
For: plumbers, HVAC, electricians and similar trades that separate emergency dispatch from quotes.
Main menu
1 Emergency -> on-call tech, then backup tech, then voicemail + text alert
2 Quote or new service -> office queue
3 Existing job -> dispatcher
4 Billing -> office voicemail
Script: "Thanks for calling [Business]. If you have an emergency such as flooding or no heat, press 1. If you smell gas, leave the building and call 911 first. For a quote or to book service, press 2. To check on a current job, press 3. For billing, press 4."
Size: 4 options, 1 level. After hours: option 1 stays live around the clock; options 2 to 4 go to voicemail.
5. Law firm or professional services
For: firms where client confidentiality and intake both matter.
Main menu
1 Existing client -> assistant ring group -> voicemail
2 New matter -> intake queue
3 Billing -> accounting voicemail
4 Directory -> dial by name
0 Receptionist
Script: "Thank you for calling [Firm]. If you are a current client, press 1. If you are calling about a new legal matter, press 2. For billing, press 3. To reach someone by name, press 4."
Size: 4 options, 1 level. After hours: promise a callback by a stated time, such as "by noon the next business day."
6. Property management
For: landlords and managers fielding maintenance, leasing and rent calls.
Main menu
1 Maintenance emergency -> on-call ring group, escalate to manager
2 Maintenance request -> request voicemail/queue
3 Leasing -> leasing ring group
4 Payments and account -> office queue
Script: "Thanks for calling [Company]. If there is a fire, hang up and dial 911. For a maintenance emergency such as flooding or no heat, press 1. For a non-urgent repair, press 2. For leasing, press 3. For rent and account questions, press 4."
Size: 4 options, 1 level. After hours: keep option 1 live; define in writing what counts as an emergency.
7. Restaurant or retail
For: businesses where staff are busy and many calls are just "what time do you close?"
Main menu
1 Hours and location -> recording, then hang up or press 0
2 Reservations/orders -> host stand ring group
3 Catering or events -> manager voicemail
Script: "Thanks for calling [Business]. For hours and directions, press 1. To place an order or make a reservation, press 2. For catering and events, press 3."
Size: 3 options, 1 level. After hours: play hours automatically and take catering messages only.
8. Nonprofit or school
For: organizations with donors, families and staff all calling one number.
Main menu
1 Donations -> development voicemail/ring group
2 Programs and events -> front office
3 Volunteering -> coordinator voicemail
4 Staff directory
dial by name or extension
Script: "Thank you for calling [Organization]. To donate or ask about a gift, press 1. For programs and events, press 2. To volunteer, press 3. To reach a staff member, press 4."
Size: 4 options, 2 levels (directory only). After hours: announce office hours and the website for donations.
Which fallback and after-hours branches should every menu have?
Every menu needs branches for silence, wrong keys, closed hours and overload, because callers hit those paths constantly. Each branch below has a ready script. Build them once and reuse them across any of the eight examples.
No input and invalid input handling
- Invalid key: "Sorry, that's not a valid choice. Let's try again." Replay once.
- No input: "I didn't hear a selection." Replay once, then route to the zero destination.
- Second failure: send the caller to a person or voicemail, never to a third replay.
After-hours, holiday and overflow routing
- After hours: "You've reached [Business] outside of business hours. We open at [time]. To leave a message, stay on the line."
- Holiday: "We're closed for [holiday] and reopen on [date]."
- Overflow: if no agent is free within [X] seconds, offer a callback or voicemail.
Callback and voicemail-to-ticket options
A callback option keeps the caller's place without holding. Voicemail-to-ticket turns a message into a work item. Voicalyst supports these branches through IVR phone menus and call routing and voicemail transcription, and AI call summaries condense longer calls for follow-up. See the AI call summary guide for how teams use them.
What does a support phone tree template look like?
A support phone tree template is a menu skeleton with blank slots for options, destinations and fallbacks. Fill in your top four call reasons first, assign each a destination, then add the greeting, escape and after-hours variants. Copy the block below.
GREETING
"Thanks for calling [BUSINESS]. [If safety-relevant: If this is an
emergency, hang up and dial 911.]"
MENU (3-5 options, busiest first)
1 [TOP REASON] -> [QUEUE / RING GROUP / RECORDING]
2 [SECOND REASON] -> [DESTINATION]
3 [THIRD REASON] -> [DESTINATION]
4 [OTHER] -> [DESTINATION]
0 / "operator" -> [PERSON OR GENERAL QUEUE]
9 repeat
PROMPT
"For [REASON 1], press 1. For [REASON 2], press 2.
For [REASON 3], press 3. For anything else, press 4.
To repeat these options, press 9."
FALLBACKS
Invalid -> replay once -> [PERSON/VOICEMAIL]
No input -> replay once -> [PERSON/VOICEMAIL]
Busy > [X] seconds -> [CALLBACK / VOICEMAIL]
AFTER HOURS
"We're closed. We reopen [TIME]. [Emergency path if any.]
To leave a message, stay on the line."
Run the finished version through the business phone system guide for customer support to confirm your system supports every destination type you chose.
How do you test and improve a phone tree?
Test a phone tree by calling it yourself, then measure real caller behavior and cut or merge options that underperform. Plan on at least one review after the first few weeks of live calls, since actual call patterns rarely match what you guessed.
Test-call checklist
- Press every option and confirm it reaches the intended destination.
- Press 0 and say "operator" on each menu.
- Wait in silence, then press a wrong key.
- Call outside business hours and on a listed holiday.
- Call from a mobile phone and a landline, and have someone unfamiliar with the menu try it.
Metrics to watch
| Metric | What it tells you |
|---|---|
| Zero-out rate | Share of callers who press 0 or say "operator"; high means the menu isn't helping |
| Abandon rate | Callers who hang up before reaching anyone |
| Misroutes | Calls transferred after landing in the wrong place |
| Time to answer | How long callers wait after choosing |
When to cut or merge options
Cut an option that few callers choose, merge two options that go to the same team, and move the busiest option to position 1. Reread the setup guide before rebuilding.
If you want to build any of these menus without stitching tools together, Voicalyst includes phone menus, queues and voicemail in one cloud phone system.
Frequently Asked Questions
What is an example of a phone tree?
A simple phone tree greets the caller, then offers numbered choices: press 1 for order status, 2 for returns, 3 for shipping, 4 for anything else. Each number sends the call to a specific person, queue or recording. Pressing 0 or staying on the line reaches a human or voicemail.
How many options should a phone menu have?
Keep each level to three to five options, and limit the whole menu to two levels. Put the most common reason for calling first. Most small businesses do well with four options and a zero escape to a person. Add a second level only where one option splits into clearly different requests.
What is the difference between a phone tree and an IVR?
A phone tree is the menu structure callers navigate by keypad or voice. An auto attendant is the system that plays that menu and routes calls. IVR (interactive voice response) is the broader term, often meaning menus that also look up data or accept spoken input. Small businesses usually need only the first two.
How do I write a phone menu script?
Open with your business name, say how to reach 911 if relevant, then give the option before the number: "For billing, press 2." Order choices by call volume, keep every prompt under about 10 seconds total per level, and end with "To repeat these options, press 9." Record in a natural voice.