Phone Tree Template: Menu Script and Build Checklist

Quick answer

Searchers for “phone tree template” need words they can paste into an auto-attendant, not a glossary of IVR acronyms. Start from the script below, swap the bracketed labels, then run the build checklist.

Keep the daytime menu small. Long trees raise abandon rates before anyone reaches sales or support.

Copy-ready main menu template

Reorder keys so the highest-volume reason is #1. If billing is rare, fold it under 0 or a submenu later.

After-hours branch template

Day/night routing should swap the whole tree, not only the greeting.

Sample night prompt: "You have reached [Business Name] outside business hours. We are open [days] from [open] to [close] [timezone]. Please leave your name, number, and a short message after the tone. For emergencies, press 1." Map emergency 1 only if you staff it; otherwise omit the line.

Voicemail email-to-ticket beats a shared inbox nobody opens. Confirm the mailbox owner before go-live.

Build checklist (PBX)

1. Create the auto-attendant object and upload or TTS each prompt. 2. Bind keys to queues/extensions. 3. Set timeout: replay once, then send to 0 or voicemail. 4. Set holiday calendar overrides. 5. Enable call recording disclosure if your jurisdiction requires it on the first prompt.

6. From a mobile on another network, dial the main DID and press every key, including invalid digits. 7. Document the tree in one page next to transfer training so receptionists know what callers already heard.

If prompts stutter, fix media quality before rewriting the script; see VoIP jitter.

Design rules that prevent abandon

Three to four daytime options beat seven. Extra departments belong one level down after a human or a "more options" key.

Say the action before the number ("For sales, press 1") so callers can move as soon as they hear the department.

Never force a 45-second marketing message before the first key. Put promotions after hours or on key 4.

Overflow: if sales does not answer in N rings, offer callback voicemail or route to a covered queue. Dead-end rings train callers to hang up.

How to customize the main menu for your vertical

Start from the copy-ready main menu, then rename options to match how callers already speak. A dental office might use “appointments, billing, dental emergency”; a field-service shop might use “new service request, existing job status, parts, office”. Keep the first three options for the highest volume intents; bury rare paths under “more options” so the greeting stays under about 20-25 seconds.

Language: one language per tree unless you have staff who can answer both. A “press 9 for Spanish” jump is fine; dual full trees that nobody maintains create wrong-hour misroutes.

Numbering habits: reserve 0 for operator or receptionist, * or # only if your PBX documents them, and avoid renumbering every quarter. Callers memorize “billing is 2”; changing it silently spikes abandon.

Write prompts in the second person, present tense, and one action per sentence. Example: “For billing, press 2.” Avoid jokes, brand slogans, or music beds longer than a short confirm tone before the menu repeats.

After-hours, holidays, and overflow design

After-hours branch goals: set expectation (“we open at 8 a.m. local”), offer one self-serve path (voicemail, callback form SMS, or status line), and optionally escalate true emergencies to an on-call number. Do not promise live chat if nobody monitors it overnight.

Holiday calendar: maintain a dated override list in the PBX, not only in someone’s head. Test the override the afternoon before each holiday. Forgotten Christmas trees that still claim “press 1 for today’s appointments” damage trust.

Overflow when all agents busy: play estimated wait only if your platform’s estimate is honest; otherwise say “high call volume” and offer voicemail or callback. Infinite hold with no escape is an abandon machine.

Emergency carve-outs (medical, safety, outage): put them early in the after-hours prompt, not after three marketing options. Document who answers, response SLA, and when to call 911 instead of your tree.

PBX build checklist expanded

Inventory DIDs and which tree each published number should hit. Marketing often buys a vanity number that still points at an old ring group; fix routing before you rewrite prompts.

Record or TTS each prompt with the same voice profile. Mixed voices make callers think they were transferred to a different company. Keep a script sheet versioned next to the audio files.

Map each keypress to a destination type: user, ring group, queue, voicemail box, external forward, or submenu. Label destinations with human names (“Billing queue”) not only extension numbers.

Business hours object: confirm timezone, daylight-saving behavior, and lunch closures. A tree that thinks you are Eastern while the shop is Central misroutes every noon call.

Voicemail transcription and email inject: verify the mailbox owner and that PHI or card data is not encouraged in the greeting. If you take payments by phone, route to a PCI-aware flow instead of open voicemail.

Change control: one owner edits the live tree; others propose copy in a doc. Unreviewed “quick tweaks” are a leading cause of weekend outages.

Test script you can run in 15 minutes

From an outside line, call each published DID during open hours. Confirm the greeting, each keypress (1-0), and that wrong keys repeat the menu instead of dropping.

Call again one minute after posted close. Confirm after-hours greeting, emergency option if any, and voicemail or callback path. Leave a test message and confirm delivery to the right inbox.

Force a queue overflow if you can (multiple testers). Confirm music or comfort message, escape digit, and that abandon reports increment in the PBX analytics.

Disable a sample agent and confirm the ring group still answers. Re-enable and confirm no stuck DND state.

Log results in a shared sheet: DID, time, expected prompt, actual prompt, pass/fail, owner. Retest after every prompt change, not only at go-live.

Metrics and abandon prevention

Watch offer rate vs answer rate, average speed of answer, and menu depth before connect. If most callers hit 0 immediately, your menu labels are unclear or too long.

Shorten the greeting before you add more options. Every extra sentence raises early hang-ups. Put the company name once, then the first three choices.

Offer a callback or digital channel for high-wait queues. Publish the same status on your website so callers who hang up still know what to do next.

Sister pages for related ops: iPhone call forwarding when a person is the overflow target, and business call forwarding services when the whole DID should move.

Sample scripts for common industries

Home services (plumbing, HVAC): “Thank you for calling [Company]. For emergency water or heating issues, press 1. For scheduling a new visit, press 2. For an existing job status, press 3. For billing, press 4. For all other requests, press 0.” Keep emergency first so panicked callers do not hang up during a long marketing intro.

Professional services (accounting, law intake): “For new client inquiries, press 1. For existing client document questions, press 2. For billing, press 3. For the receptionist, press 0.” Avoid promising same-day attorney callbacks unless staffing is real; false SLAs create bar complaints and bad reviews.

Retail / clinic: “For appointments, press 1. For prescription or order pickup, press 2. For insurance or billing, press 3. Store hours and directions, press 4.” Put hours on the website too so the tree is not the only source of truth when you close early for inventory.

Record a short confirm prompt after each keypress (“Billing, please hold”) so callers who mis-press can hit a repeat key before they land in the wrong queue.

When you change an industry script, re-run the 15-minute test script on every published DID. Marketing vanity numbers are easy to forget and often still play last year’s menu.

Staffing the tree without burning agents

Match ring group size to offered calls in peak hours. A beautiful menu that dumps everyone into a two-person queue will still abandon. Use schedule-based routing: open-hours queue vs after-hours voicemail.

Skill-based routing beats a flat operator dump when billing questions dominate. Train billing agents on the same FAQ the website shows so transfers drop.

Do not hide a “press 0” operator if you advertise live help. Callers who mash 0 repeatedly are telling you the labels failed; fix labels before you remove 0.

Weekly review: top keypress paths, average handle time by queue, and top abandoned menu step. Change one prompt at a time so you can attribute improvements.

Handoff to live agents and voicemail hygiene

When a caller reaches a person, agents should confirm the menu path that got them there (“I see you pressed billing”). That feedback loop tells you which prompts are confusing without a formal survey.

Voicemail greetings must state the mailbox purpose, expected reply window, and what not to leave (full card numbers, passwords). Full mailboxes that reject messages should alarm to IT the same day, not after a week of silent failures.

If you forward overflow to a mobile, pair this tree with a documented handset or carrier forward path so nights and weekends do not depend on one person’s Settings screen. For iPhone steps see the sister forwarding guide on this site.

FAQ