Key takeaways
- A press-1 menu works when callers already know which of three or four destinations they need; working memory holds about 3 to 5 items[1].
- Menus fail on two-part calls, off-menu questions, after-hours dead ends and callers who simply want a person[2].
- A conversational agent lets the caller say why they called, handles more than one request in a call and leaves a written record of it.
- Whatever you run, every path needs a way to a person; dead ends are what trap callers[3].
What a press-1 menu still does well
A press-1 menu does one job well: it sends a caller who already knows what they want to the right phone without anyone picking up. Pickup orders ring the kitchen line, private-event calls ring the events office, everyone else rings the host stand. For a restaurant with separate lines and a person behind each one, that is cheap, predictable routing that never has a bad night.
It works best when the options are few and obvious. Working memory in young adults holds about 3 to 5 meaningful items, about four in all[1], and a caller listening to a menu is holding the options in their head while deciding which one fits. Three or four choices, each starting with the reason for calling, sit inside that limit. Seven do not, and callers either press zero or hang up.
- Fixed destinations. Kitchen line, events office, host stand, bookkeeping: each option rings a phone that someone answers.
- Repeat callers who learn the keys. Regular catering clients and suppliers press 3 without listening.
- One dominant question. Hours and the address read once in the greeting, so most callers never need an option for them.
- Vendor and staff calls. A dedicated option keeps sales pitches and shift swaps away from the host stand.
If that describes your calls, a well-built menu is still the right tool; how to set up a phone menu for a restaurant walks through building one, and separate lines for takeout, catering and reservations covers the numbers behind each option.
Where callers give up
Menus break on the calls restaurants get most often, at the worst possible times.
- Two reasons in one call. “Pickup for tonight, and do you do office lunches?” fits no single key. The caller picks one branch, and the second question is lost or needs another call.
- Questions that match no option. Is the patio open, is there a high chair, can you do a gluten-free crust? The caller presses zero and waits for a person who is seating guests.
- Long greetings. Every second of “please listen carefully, as our options have changed” is a second the guest spends deciding whether to try somewhere else. Speed is the point for takeout guests: 94% of consumers say it is critical when ordering off-premises[4].
- After-hours dead ends. A closed-hours branch that ends in a full voicemail box, or a recording with no next step.
- Callers who want a person. About two-thirds of diners who had not booked online said they wanted to talk to someone to make a booking[2]. A menu that buries the person route loses exactly those guests.
- Relay calls. Guests who are deaf, hard of hearing or speech-disabled may call through the free relay service at 7-1-1, where a communications assistant relays each prompt[5]. Long menus and short timeouts make those calls harder, and ADA-covered businesses must accept relay calls like any other[6].
None of these failures shows up as an error. The phone system logs a hang-up or a zero, the guest orders from someone else, and the menu looks fine on paper. That is why the test at the end of this article uses your own phone rather than a vendor's report.
How a conversational agent routes instead
A conversational agent, such as an SI Employee, replaces the list of keys with one question: what can I help with? The caller answers in their own words, and the agent works out where the call belongs, answers what it can from the information you approve and collects the details for what it cannot finish. Two requests in one call stop being a problem, and the record of the call is a transcript and summary rather than a key press.
- Caller
- SI Employee
- Your team
01Caller
Caller says why they called
“Pickup tonight, and do you do lunches for an office of 25?”
02SI Employee
Answers the quick question
Kitchen close and parking, answered from your approved house information.
03SI Employee
Texts the ordering link
With the caller's agreement, it texts your official ordering link.
04SI Employee
Takes the catering lead
Event date, guest count, service style and a callback number for the catering manager.
05Your team
Catering manager calls back
Summary and transcript arrive by email; menus and prices come from your team.
Example sequence using live capabilities. Texting the ordering link needs a registered SMS sender.
Example: in a press-1 setup this caller presses 1 for pickup, orders online, and either forgets the lunch question or calls back later to press 3. With the agent, both requests are handled in one call and the catering manager starts from a complete lead. The modelled pizzeria's Friday-night calls show the ordering-link step at volume, and AI phone answering for restaurants explains the mechanics.
Texting a link works for most callers, not all
Menus and agents increasingly answer pickup calls by sending the ordering link. It is fast, it keeps orders accurate, and it depends on the caller having a smartphone and agreeing to a text. Most do. In Pew's 2026 survey, 97% of adults aged 18 to 49 owned a smartphone, falling to 91% at 50 to 64 and 79% at 65 and older[7].
Source: Pew Research Center, 2026[7]
Show the data
| Age | Own a smartphone |
|---|---|
| 18-29 | 97% |
| 30-49 | 97% |
| 50-64 | 91% |
| 65+ | 79% |
About one in five adults 65 and older has no smartphone to receive the link, so the phone route has to stay open: a menu option or a handoff that reaches someone who takes the order the old way, or a staff callback. Never make the text the only route. The missed-call text-back guide covers consent wording for texts.
Side by side
| Press-1 menu | Conversational agent | |
|---|---|---|
| First 15 seconds | Listening to the options | Saying why they called |
| Two reasons in one call | One branch per call | Both handled in one conversation |
| Off-menu question | Press 0 and wait, or hang up | Answered if it is on your approved list, otherwise handed off |
| After close | Recorded message or voicemail | Questions answered, requests taken, call logged |
| Record of the call | Key presses and call length | Recording, transcript and summary |
| Setup effort | Write and record the prompts once | Approve house information, test scenarios, review calls |
The menu wins on simplicity; the agent wins on everything callers say that the menu never anticipated.
| Call | A menu handles it well when | An agent handles it better when |
|---|---|---|
| Pickup order | A dedicated kitchen line answers quickly | Nobody can reach the kitchen line at peak; the agent texts the ordering link |
| Reservation | The host stand is staffed and picks up | The stand is busy or closed; the agent takes a complete request for the host |
| Catering or event | An events office answers during office hours | The call comes on a Saturday or arrives mixed with another request |
| Hours, parking, directions | One recorded answer covers most callers | Callers ask follow-ups about the patio, high chairs or holiday hours |
| Complaint | Option 0 reaches a manager who answers | The agent hands it straight to the manager path |
| Vendors and staff call-outs | A separate option or number keeps them off the stand | The agent takes a message for the right manager |
Keep the menu, replace it, or combine them
Few restaurants need to choose all or nothing. Three setups cover most cases.
- Menu only. Fine for a counter-service shop with one dominant call type, a staffed line behind every option and little after-hours demand.
- Agent only. The main number forwards to a conversational agent on overflow and after close, while staff still pick up first during service. Suits full-service restaurants whose calls mix bookings, questions and catering.
- Menu in front, agent behind. A short menu with one key for the kitchen line, and everything else, including callers who press nothing, goes to the agent. Useful where the kitchen line is staffed but the host stand is not.
Two rules apply whichever you pick. First, every path ends at a person or a promised callback. Reviewing chatbots in banking, the CFPB described “doom loops” that trap customers whose issue falls outside a system's limited capabilities, without an offramp to a human[3]; a phone menu with no zero option does the same thing to a hungry caller. Second, plan the handoff numbers. If your main number forwards to the agent, transfers cannot go back to that same number, so give the manager path a direct line or a mobile. When an AI phone agent should hand off to staff covers what to route where.
Turning menu options into routing rules
If you replace a menu, keep its logic. Each option you once recorded was a decision about who handles what, and those decisions become the agent's routing rules. Write one line per former option and get the manager who owns each one to sign it off.
- Former option 1, pickup orders: answer kitchen close and pickup questions from the house sheet and offer to text the ordering link. A caller who wants to order by voice goes to the kitchen line or gets a callback request.
- Former option 2, reservations: collect party size, date, time, name and callback number, read them back and mark the request for the host to confirm. Never promise a table.
- Former option 3, private events and catering: ask the event questions in your order and send the lead to the catering manager by name. Menus and prices stay with your team.
- Former option 0, a person: during service, transfer to the host stand's direct line; after close, take an urgent message for the manager on call.
- The options you never had: complaints and allergy questions always go to the manager path, whatever the caller asked about first.
Example greeting if you keep a one-key menu in front: “Thanks for calling Harbor Street Kitchen. For the pickup counter, press 1. For anything else, stay on the line and tell us what you need.” About twelve seconds, one key, and an open route for everyone else.
What hang-ups inside the menu cost
| Input | Example |
|---|---|
| Calls reaching the menu per week | 300 |
| Callers who hang up in the menu (%) | 8% |
| Of those, orders or bookings (%) | 60% |
| Would have ordered or booked (%) | 50% |
| Average order or check | $45 |
| Unanswered calls a month | 104 |
| From new customers | 62 |
| Bookings that would have followed | 31 |
| Monthly value at risk | $1,403 |
How it is worked out: Calls a week × 4.33 weeks × unanswered share × new-customer share × booking rate × average value.
Assumptions
- Takeout callers are impatient: 94% of consumers say speed is critical when ordering off-premises.[4]
- Example: an 8% hang-up rate is a placeholder. Most phone systems report hang-ups by menu step; use two weeks of your own report.
- Example: $45 is a family pickup order; use your own average ticket.
The result is value at stake each month, not a forecast.
Example: 300 calls a week reach the menu, 8% hang up before reaching anyone, and half of the orders and bookings among them would have gone ahead: about $1,400 a month. If most of those callers drop before the first option, shorten the greeting before changing anything else.
Test both from a guest's phone
Call with two requests
Ask for pickup and a catering quote in one call. Count the calls, keys and minutes it takes to get both handled.
Ask something off the list
Patio, high chair, holiday hours. Note whether you get an answer, a handoff or a dead end.
Call after close
Try 11 pm and again at 7 am. Listen for tomorrow's hours and a clear next step.
Say nothing
Stay silent for ten seconds at the menu, and pause before answering the agent. Both should still get you somewhere useful.
Read what reached the team
Compare the menu's key-press report with the agent's summary. Which one told the manager what the guest wanted?
Run the test on your own number and on any system you are considering, at the same hour, with the same script. To hear the conversational side first, try a demo call.
Frequently asked questions
Is a conversational IVR just another name for an AI phone agent?
The labels overlap. A conversational IVR usually means a menu that accepts spoken words instead of key presses but still routes to fixed branches. An AI phone agent holds a conversation, answers from approved information and collects details. A test call with a two-part request shows which one you are buying.
How many options should a restaurant phone menu have?
Three or four at most. Working memory holds about 3 to 5 items[1], and callers are holding the options while they decide. Put the most common reason first and offer a person at any point.
Can we keep our menu and add an agent?
Yes. A common setup keeps one key for the kitchen line and sends everything else, including callers who press nothing, to the agent. Check that the agent's handoffs go to direct numbers rather than back to the main line.
What about callers who can't receive a text?
Keep a phone route for them. Smartphone ownership is 79% among adults 65 and older[7], so an ordering link cannot be the only way to order. Offer a handoff to staff or a callback.
Do phone menus work for relay calls?
They can, but every prompt has to be relayed by a communications assistant, so long menus and short timeouts make the call harder. Businesses covered by the ADA must accept relay calls[6]; keep menus short and timeouts generous.
References
Nelson Cowan, Current Directions in Psychological Science (via PubMed Central) (2010). The Magical Mystery Four: How is Working Memory Capacity Limited, and Why? (Current Directions in Psychological Science) (opens in a new tab) ↑
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) ↑
Consumer Financial Protection Bureau (2023). Chatbots in consumer finance (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) ↑
US Department of Justice, Civil Rights Division (ADA.gov) (2026). ADA Requirements: Effective Communication (opens in a new tab) ↑
US Department of Justice, Civil Rights Division (ADA.gov) (2026). ADA Requirements: Effective Communication (opens in a new tab) ↑
Pew Research Center (2026). Mobile Fact Sheet (opens in a new tab) ↑