A call flow template every restaurant can ship in 48 hours
Steal this restaurant call flow: greeting, ordering with an upsell, reservations, hours and menu FAQs, catering capture, and human-transfer triggers.
A restaurant call flow is the script your phone follows on every call: greet the caller, sort them into one of four branches — order, reservation, question, or catering — handle the branch, and hand off to a human when the call needs one. The full template is below, with the actual lines, ready to adapt to your menu.
It works the same whether a host answers or an AI voice agent does. The difference is coverage: a script on a laminated card only helps when someone picks up, and during a Friday rush or after close, nobody does. Write the flow once and you can run it either way.
The greeting: one line, three jobs
Everything below hangs off the same opener. The greeting has three jobs: confirm the caller reached the right place, set a friendly tone, and sort the call with a single question.
“Thanks for calling [Restaurant Name]! Are you calling to place an order, book a table, or ask a question?” That’s the whole greeting. Don’t read specials, don’t recite the menu, don’t make the caller sit through a preamble — the fastest route to what they want is the whole game.
If an AI agent is answering, let it introduce itself honestly. Callers mostly care that someone picked up and got them handled, not whether it was a person.
Branch 1: phone orders, with one upsell — not a pitch
Order calls are usually your highest-volume branch and the easiest to template. The framework:
- Take the order item by item, confirming each as you go: “One large pepperoni — anything extra on that?”
- Upsell exactly once, at a natural moment, tied to what they ordered: “Want to add drinks or a side of garlic bread with that?” One relevant offer, then move on. Two upsells feels like a script; zero leaves easy revenue on the counter.
- Confirm pickup or delivery, and quote a realistic ready time — a padded honest estimate beats an optimistic one that creates a lobby full of waiting customers.
- Get a name and phone number.
- Read the full order and total back before hanging up. The read-back kills the most expensive mistake in phone ordering: the remake.
Branch 2: reservations
Capture five things, confirm them back, done: party size, date and time, name, phone number, and any notes — birthday, high chair, accessibility, patio preference.
The part most scripts skip is the no. If the requested slot is gone, offer the two nearest alternatives before declining: “7:30 is booked, but I have 6:45 or 8:15 — would either work?” A reservation call that ends in “sorry, we’re full” with no alternative is a caller you just handed to the restaurant down the street.
Branch 3: hours, menu, and the FAQ list
Most question calls are the same ten questions on repeat. Write the answers down once and answer only from that list — never guess. The pre-load:
- Hours, including holiday hours — typically the question callers ask most.
- Address, parking, and nearest landmark.
- Gluten-free, vegan, and vegetarian basics — what you offer and what you don’t.
- Whether you deliver, through which apps, and whether ordering direct is cheaper.
- Wait-time policy, large-party policy, patio and dog rules, gift cards.
Branch 4: catering capture, plus the calls a human should take
Catering calls tend to be rare and disproportionately valuable, which is exactly why nobody should improvise a price on the spot — not a new host, and not an AI agent. This branch captures and hands off. Collect: name and best callback number, email, event date and time, headcount, what they have in mind, pickup or delivery, and a budget ballpark if they volunteer one. Then promise a specific callback window — “the manager will call you back before 4pm today” — and make sure that callback actually happens. The goal is a clean handoff, not a closed deal on the call.
Catering is the planned handoff; a good flow knows its unplanned ones too. These calls go to a person immediately — ideally with a quick summary of who’s calling and why, so your staff doesn’t start from zero:
- Complaints, refund requests, or any caller who’s upset.
- Allergy questions beyond your written facts — a wrong answer here is a safety issue, not an embarrassment.
- Payment disputes or anything involving money already charged.
- Press, inspectors, vendors — anything that’s business, not dinner.
- Any question outside the approved facts. “Let me get someone who can answer that” always beats a confident guess.
Running it: laminated card or AI agent
You can run this entire template with a well-trained host and a card by the phone — and if your phone is genuinely covered through every rush, every close, and every Sunday, that’s a fine answer.
The gap is Friday at 7pm, when the people who could answer are the same people running food. That’s the honest case for AI for restaurant calls: an agent running this exact flow answers in under two seconds, 24/7, takes the order or books the table, writes it into your POS or booking system (Toast and the like) instead of a message someone re-keys, and transfers the edge cases to your team with context. A managed service like MapleVoice builds and tunes the flow to your menu and has it live in about 48 hours, for a flat monthly price with no per-minute meter.
Frequently asked questions
What should a restaurant phone script include?
Six pieces: a greeting that sorts the call in one question; an order-taking branch with item-by-item confirmation, one relevant upsell, and a full read-back; a reservation branch that captures party size, time, name, and number and offers alternatives when full; pre-written answers to your ten most common questions; a catering-capture branch that collects details and promises a callback; and clear triggers for handing the call to a human.
Can AI take phone orders for a restaurant?
Yes. A modern AI voice agent takes the order item by item, confirms it back, offers an upsell, quotes a ready time, and writes the order into your POS (such as Toast) rather than leaving a message to re-key — and it transfers to staff when a call needs a person. You can hear example calls on our call recordings page.
How do restaurants stop missing calls during the dinner rush?
Three honest options: dedicate a staffer to the phone (expensive at exactly your busiest hour), let calls roll to voicemail (many callers simply call the next restaurant instead), or put an AI voice agent on the line that answers every call in under two seconds, 24/7, and runs the same call flow your best host would — booking, ordering, and transferring the rest.
Keep reading
Hear it answer a real call
MapleVoice builds and runs a fully-managed AI voice agent for your business — live in about 48 hours, flat monthly price.