Key takeaways
- Use four options at most, ordered by how often callers need them, and say the purpose before the key.
- Always offer a fast way to reach a person; many guests want to talk to someone[1].
- A text-a-link option suits pickup and booking calls because mobile ordering is now mainstream[2].
- Put any call-recording notice at the start, before the options[3].
- Test every branch from a mobile phone after each change, including after hours.
When a phone menu helps and when it hurts
A phone menu, sometimes called a phone tree or IVR, sends callers to the right place before anyone picks up. Done well, it routes pickup orders to the kitchen line, private-event calls to the events manager and reservation calls to the host stand, while answering simple questions with a recorded message. Done badly, it is a maze that makes a guest press four buttons to ask whether you are open.
Not every restaurant needs one. If you have one phone, one host and mostly reservation calls, a menu adds a delay without adding a destination. A menu earns its place when calls regularly need to reach different people, when takeout and reservations compete for the same line, or when you want a reliable after-hours route.
Design rules for a short menu
- Four options at most. Callers remember about four choices; beyond that they wait for the end and press zero.
- Order by volume. The most common reason for calling goes first, so most callers press a key in the first ten seconds.
- Say the purpose before the key: “For pickup orders, press one,” not “Press one for pickup orders.” Callers listen for their need, then the number.
- Keep zero for a person, always, and say so once at the start and once at the end.
- No promotions before the options. Save the new brunch announcement for the hold message or the voicemail.
- One level only. If an option needs a second menu, it probably needs a person instead.
The quick exit matters more than any other rule. In Cornell research on reservations, about two-thirds of diners who had never booked online said they wanted to talk to someone to make a booking[1]. A menu that hides the person route loses exactly those guests.
Build it in six steps
Tally your calls
For a few shifts, have hosts mark each call by type: pickup or delivery, reservation, hours and directions, private events or catering, other. Rank the types by count.
Choose the options
Take the top three types as options and keep zero for a person. Fold hours and directions into a recorded answer if they are a top type.
Write the prompts
One sentence per option, purpose first. Read the whole menu aloud and time it; the last option should finish within about twenty seconds.
Route each option
Decide where each key rings during service and after close: host stand, kitchen or takeout line, events manager's phone, recorded message or voicemail box.
Set the after-hours branch
After close, the same keys should still make sense. Pickup can give tomorrow's hours and the ordering link; events can go to a message box checked each morning.
Test from a mobile phone
Call every branch, during and after hours, and confirm each one reaches a person or a working message. Repeat after any change.
A sample menu
Example: a fictional neighborhood pizzeria and wine bar whose tally shows pickup orders first, then reservations, then events. The greeting and options below take about eighteen seconds.
| Key | Prompt | During service | After close |
|---|---|---|---|
| Greeting | “Thanks for calling Ember and Vine. We're open today until ten.” | Plays first | Plays tomorrow's hours |
| 1 | “To order for pickup, press one.” | Rings the takeout line | Tomorrow's hours and an offer to text the ordering link |
| 2 | “To book or change a table, press two.” | Rings the host stand | Booking link by text, or voicemail for changes to tonight |
| 3 | “For private parties and catering, press three.” | Rings the events manager, then voicemail | Events voicemail, returned next morning |
| 0 | “To speak with someone, press zero at any time.” | Rings the host stand, then the manager | General voicemail |
In this example hours are given in the greeting rather than as an option, which removes a whole branch. Parking and directions live on the website and in the after-hours message.
In the example, the events branch rings a person first because private-party calls are the most valuable and the least frequent. If the events manager does not answer within five rings, the call falls to a dedicated message box rather than the general voicemail, so event requests are never buried among hours questions.
Rewriting prompts that confuse callers
Most menus are written by whoever set up the phone system, in the vendor's default wording. Small rewrites make a large difference to how quickly callers get where they are going.
- “Para español, oprima nueve” is a reasonable exception to the purpose-first rule if many of your guests prefer Spanish, but put it right after the greeting, not at the end.
- Replace “For all other inquiries” with a concrete phrase such as “For anything else, press zero to speak with us.” Callers do not know what counts as an inquiry.
- Avoid “Please listen carefully, as our menu options have changed.” Everyone already listens carefully; the sentence only adds delay.
- Drop internal labels. Callers do not know what “the to-go station” or “FOH” means; say pickup orders and tables.
- Do not repeat the restaurant name before every option. Once in the greeting is enough.
Read the final prompts to someone who has never eaten at the restaurant and ask them which key they would press for three made-up reasons: ordering a pizza for pickup, booking for six on Friday and asking about a birthday party. If they hesitate on any of the three, rewrite that prompt.
Offer a text link where it fits
If your phone system can send a text message, a “press one and we'll text you our ordering link” option is often the fastest route for a pickup caller. Mobile ordering is mainstream: 57% of adults have used it recently, including 74% of millennials and 65% of Gen Z adults[2]. With nearly three in four restaurant orders now taken to go[4], pickup is often the busiest branch of the menu.
Send the text only when the caller asks for it by pressing the key, and send only the link they requested. Keep the person route available for callers who would rather order by phone.
Recording notices and speed
If any branch records calls, put the notice at the very start, before the options: “Calls may be recorded for training.” Federal law generally allows recording with one party's consent, but some states, such as California, require all parties to agree[3]. A notice at the top covers every branch.
Speed is the other reason to keep the menu short. In National Restaurant Association research, 94% of consumers said speed is critical when ordering off-premises[5]. A menu that takes forty seconds to reach the pickup option works against those guests.
Testing checklist
- Every key reaches a person or a working message during service.
- Every key does something sensible after close and on closed days.
- Zero works at any point in the menu, not just at the end.
- Pressing nothing for ten seconds sends the caller to a person or the general voicemail, not a dead line.
- Ring groups and forwarding numbers are current after staff changes.
- The menu, the voicemail greeting and the website give the same hours.
- A text-link option sends the right link, and the page works on a small screen.
Run the checklist monthly and after every change to hours, staff or phone settings. Most phone-menu failures are not design problems; they are a forwarding number that still points to a manager who left in the spring.
Measure whether it worked
Most phone systems report how many callers pressed each key and how many hung up in the menu. Check those numbers after two weeks. A high hang-up rate before the first option means the greeting is too long. Lots of zeros means an option is missing or unclear. If one option is almost never used, remove it and the menu gets faster for everyone.
For the messages callers hear when no one picks up, see our voicemail greeting examples. For choosing the system itself, see business phone systems for restaurants.
Frequently asked questions
How many options should a restaurant phone menu have?
Four at most, including a zero option to reach a person. Order them by how often callers need each one.
Should a restaurant phone tree have a press zero option?
Yes. Say it at the start and the end, and make it work at any point. Many guests want to talk to someone, especially to book a table.
What should the after-hours phone menu do?
Give tomorrow's hours, offer booking and ordering links, and route event and change requests to message boxes that someone checks at a set time.
References
Cornell University Center for Hospitality Research (Kimes and Kies) (2012). The Role of Multi-Restaurant Reservation Sites in Restaurant Distribution Management (Cornell Hospitality Report, 2012) (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), US Code (2026). 18 U.S. Code § 2511 - Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑