It's 7:30 on a Saturday. Your host has a party of five at the stand, a two-top waiting for their check, and the phone has rung four times in two minutes. She lets it ring. One caller wanted to know whether you validate parking. Another wanted a table for two at 8:30, and booked one on an app at the place across the street.
Nobody did anything wrong. The host chose the guests in front of her, which is the right call. The problem is that the phone and the door need the same person at the same moment, every weekend.
What people actually call about during service
Before choosing any phone setup, keep a tally sheet by the host stand for one week: a tick per call, sorted into the rows below. You'll probably find a handful of call types cover most of the rings.
| The caller wants | Can an assistant finish it? | How |
|---|---|---|
| A table tonight or later | Yes, within your rules | Checks availability and books in your reservation system, or texts a booking link |
| To change or cancel a booking | Yes | Finds the booking by name and phone number and updates it |
| Hours, kitchen close, parking, corkage | Yes | Answers from your approved info sheet |
| Walk-in wait time | Partly | Only if your waitlist tool shares live waits; otherwise your general guidance |
| Takeout | Yes, usually by link | Texts your online ordering link so the order lands in your POS |
| Allergy or dietary safety | No | Doesn't answer from the menu; notes it and routes it to a manager |
| A party of 12 or a private event | Starts it | Takes date, headcount and contact; a manager calls back |
| A complaint or a lost item | Starts it | Takes details for the manager, with an honest callback window |
The last three rows matter most. A good setup doesn't answer everything. It answers the routine calls in seconds and hands the rest to the right person with the details already written down.
How a booking call works
Flowchart
A reservation call during service
- Start7:32 PM: “Do you have a table for six at 8:30?”
- StepAssistant says it's the restaurant's automated assistant and checks availability
- DecisionParty bigger than your auto-book limit?YesA personTakes date, headcount and number; a manager calls back to confirmNo
- DecisionIs the requested time open?NoStepOffers the nearest open times or the waitlistYes
- DecisionAllergy or dietary need mentioned?YesA personNoted on the booking and flagged to a manager; no safety promisesNo
- StepReads back date, time, party size and name, then books
- DoneGuest gets a confirmation text; the booking appears in the host's book
Two settings in that flow are yours. The auto-book limit, say parties up to six, keeps large tables with a person, because they affect the floor plan and the kitchen's pacing. And you choose when the assistant picks up: during service you might let the host stand ring three times first, then let the assistant take it. On most lines that delay comes from your phone system's no-answer forwarding setting, which the call forwarding guide explains.
Allergy questions go to a person, every time
A guest asking whether the pesto has nuts in it, or whether the fryer is shared, is asking a safety question. Tree nuts are one of the nine major food allergens the FDA recognizes, alongside peanuts, crustacean shellfish and sesame, and reactions can be severe. Menu descriptions rarely list every ingredient, and they never mention cross-contact like a shared fryer or prep station. So the assistant doesn't answer allergy or ingredient questions from the menu at all: when a caller mentions an allergy, or asks what's in a dish for a dietary reason, it notes the need and routes it to a manager.
The script is short: “I can't confirm what's safe for an allergy, but I've noted it on your reservation and a manager will call you back before your visit to talk it through.” For a same-hour booking with no time for a call, the manager speaks with the guest on arrival, before they order. The note has to travel with the booking, so the server sees it at the table and not only whoever answered the phone.
Before and after
Saturday at the host stand, two ways
The host answers
- 01Host leaves a party of five at the stand to grab the phone
- 02Two callers hang up after ringing out
- 03Booking for six goes on a sticky note, never entered
- 04“Is the sauce nut-free?” answered from memory
ResultGuests wait at the door, and a table goes next door
Assistant answers after three rings
- 01Host stays with the guests in front of her
- 02Every call picked up; hours and parking answered in seconds
- 03Booking for six entered and confirmed by text
- 04Nut question noted on the booking for a manager
ResultThe floor keeps moving, and no booking lives on paper
Fitting it to your reservation system
The assistant is only as useful as its access to your book. Whether you run OpenTable, Resy, Tock or a paper book, ask your platform two questions: can a third-party phone assistant create and change reservations, and does that require a partner integration? Platforms differ, and the answer decides how much the assistant can finish.
If the answer is no, there's a workable fallback. The assistant texts the caller your online booking link while they're still on the line, or takes the details and drops them into a short queue the host confirms between seatings. Either beats a phone that rings out. One launch detail: if software sends booking links and confirmation texts from your restaurant's own number, that number has to be text-enabled and registered for business texting, which takes time; the same forwarding guide covers it.
Takeout follows the same logic. Texting a link to your online ordering keeps orders accurate and puts them straight into your POS. Full voice ordering can work for a short menu, but long menus with many modifiers are where spoken orders go wrong. Allergies need extra care here, because a takeout caller has no booking to carry a note: anyone ordering takeout who mentions an allergy gets a manager callback or transfer before they order, and the ordering link is never a substitute.
Your one-page setup sheet
Fill this in before you switch anything on. It doubles as the script your assistant, or your next new host, works from.
- Basics: hours by day, kitchen close, holiday closures, address, parking and transit directions.
- Booking rules: the largest party it may book alone, how far ahead, how long you hold a table for late guests, any deposit or card hold for big groups.
- Links: online booking, takeout ordering, gift cards, catering inquiries.
- Transfers: a manager's direct number, not the main line, so a transfer can't ring straight back to the assistant. If the manager can't pick up mid-rush, the assistant promises a callback within a set window, say within 30 minutes, instead of letting the caller ring out.
- Always to a person: allergies, parties over your limit, private events, complaints, press, and anyone who asks.
- Daily changes: a simple way to update what's 86'd and today's specials, such as a text from the manager before service.
- Timing: how many rings before the assistant answers during service, and whether it answers after close.
Call it like a guest before Friday
Before the assistant takes a real service, spend fifteen minutes calling it yourself, ideally from a noisy room. Each of these calls has a right answer you can check:
- 01Ask for a table for eight on Saturday. It should hand off to a manager if eight is over your limit, not book it.
- 02Ask for a 9:15 PM table when the kitchen closes at 9. It should offer an earlier time.
- 03Say your daughter has a peanut allergy. It should note it and promise a manager, never reassure.
- 04Cancel a reservation under a name that doesn't exist. It should say it can't find one, not invent one.
- 05Say “Just let me talk to someone.” It should transfer on the first ask.
- 06Ask whether the short rib is available after you've marked it 86'd. It should say it's sold out tonight.
Anything that fails goes back into the setup sheet, and you call again. Repeat after any menu or policy change.
Catering inquiries deserve their own follow-up path, covered in restaurant catering inquiry follow-up. The restaurants page shows how the phone line sits alongside reviews and delivery-app disputes.