The Dealership Phone Tree, Done Right
How to build a press-1 menu callers don't hate: short options, the right destination behind every key, a recorded greeting, a fallback that always works — and when to skip the menu for an AI receptionist.
THE DEALER FUNNEL TEAM · SEPTEMBER 12, 2026 · 7 MIN READ
A good dealership phone tree offers three or four options at most — sales, service, parts, and a person — puts a real destination behind every key (a ring group, a person, an AI receptionist, or a shared voicemail), records the greeting in a human voice, and always sets a fallback so a mis-press never strands the caller.
Everyone claims to hate phone menus, but what callers actually hate is a bad one: nine options, a robot voice, a dead end behind option four. A short menu that instantly gets a caller to the right people is faster than a receptionist and never takes a lunch break.
This guide covers building one properly — what goes behind each key, the greeting, the fallback — and the honest question of when you shouldn't build a menu at all, because an AI receptionist that lets callers just say what they need is now the better front door for many stores.
What is an IVR menu, exactly?
An IVR (interactive voice response) menu — the phone tree — is a recorded greeting plus a set of keypad choices: “Thanks for calling Evans Auto. For sales, press 1. For service, press 2.” Each key maps to a destination in your phone system, and a fallback catches everyone who presses nothing or something invalid.
The menu itself is the easy part. The quality of a phone tree is decided by what's behind the keys — a key that leads to one desk phone is a coin flip; a key that leads to a well-configured ring group is a system.
How many options should a dealership phone menu have?
Three or four. Callers hold about that many choices in working memory, and every extra option taxes the person least equipped to handle it — the first-time caller. Sales, service, and a catch-all covers most stores; add parts if the parts counter genuinely takes direct calls. Anything deeper — submenus, “press 7 for our fax hours” — belongs in the bin.
One more rule: put the highest-volume choice first. If sixty percent of calls are service, service is option 1, whatever the org chart says.
What can sit behind each key
Every key on the menu maps to one of the same destinations the rest of your routing uses, so the menu is a front door to the system, not a separate system:
| DESTINATION | WHAT HAPPENS | BEST FOR |
|---|---|---|
| Ring a group | Rings a team — all at once, round-robin, or in waves | Sales, service, BDC |
| Ring a person | Rings one teammate directly | Parts manager, controller |
| AI receptionist | An AI answers, helps, books, and routes by voice | “Speak with our assistant,” overflow |
| Forward to a number | Sends the call to any outside line | Body shop, detached departments |
| Take a voicemail | Records to a shared, transcribed box | After-hours keys, the fallback |
| Announcement, then ring | Plays a recorded clip first, then rings the group | Seasonal notices, holiday hours |
The greeting: recorded beats robotic
You have two options: type the greeting and let a neural text-to-speech voice read it, or upload a recording. Text-to-speech is fine for getting live today and painless to edit. But a real person from your store — warm, unhurried, thirty seconds in a quiet office — is worth the take. It's the first hello most customers ever hear from you.
Keep the script tight: store name, the options in order, and nothing else. Hours, addresses, and website plugs make callers sit through a commercial to reach a human.
Always, always set the fallback
Some callers press nothing — rotary-habit dialers, distracted drivers, confused customers. The fallback decides what happens to them, and the correct answer is never “the call ends.” Route the fallback to a shared voicemail at minimum, a ring group if you can staff it, or the AI receptionist so the caller still gets helped. A phone tree is judged by its worst path, not its best.
Phone tree or AI receptionist — which front door?
The press-1 menu asks callers to translate their need into your org chart. An AI receptionist skips the translation: the caller says “my check-engine light is on” and lands in service without learning your keypad. For many stores the AI is now the better main-line answer.
You don't have to choose absolutely. A common hybrid keeps a short menu and adds “to speak with our assistant, press 3” — the menu for callers who know where they're going, the AI for everyone else. And after hours, pointing the whole line at the AI beats any menu, because a menu can only route and the AI can actually help.
Test it like a caller, not like an admin
Phone trees rot quietly: a group gets renamed, a greeting gets deleted, a key routes to someone who left in March. After every change — and once a quarter regardless — run the guided phone test and walk the tree as a stranger: every key, the fallback, the after-hours path. The transcript of one bad call costs more than the fifteen minutes of testing that would have caught it.
Frequently asked questions
How many options should a phone tree have?
Three or four, highest-volume first. Sales, service, and a catch-all covers most dealerships; deeper menus lose more callers than they route.
Should the greeting be recorded or text-to-speech?
Text-to-speech gets you live today and is easy to edit; a warm human recording from your own store is better once the script settles. Either way, keep it to the store name and the options.
What should happen when a caller presses nothing?
The fallback should route somewhere alive: a shared transcribed voicemail at minimum, a ring group, or the AI receptionist. A dead end after a mis-press is how phone trees earn their reputation.
Is an IVR menu better than an AI receptionist?
A short menu is fine for callers who already know where they're going. An AI receptionist helps everyone else — callers just say what they need. Many stores run the hybrid: a short menu with a “speak with our assistant” option, and the AI answering everything after hours.
Can the menu route to an AI agent for just one option?
Yes — any key can hand the call to an AI receptionist or an AI service scheduler while the other keys ring humans. That's the most common first step stores take with AI answering.
See it work a lead, end to end.
Thirty minutes on a live store, or try the AI yourself right now.