Copy-paste restaurant phone answering scripts — reservations, takeout, hours, and after-hours
A great restaurant phone answering script does three things in under 30 seconds: greets warmly, captures the right details, and confirms back so nothing gets lost during a rush. Below are four copy-paste scripts you can use today — or hand to an AI answering service for restaurants so the line is covered even when the floor is slammed.
Use this restaurant reservation script for booking, modifying, or canceling a table. The goal is to capture party size, date, time, and a callback number, then read it all back before hanging up.
GREETING "Thank you for calling [Restaurant Name], this is [Name]. Would you like to make a reservation?" IF YES — CAPTURE "Wonderful. What date were you thinking of, and what time?" "And how many will be in your party?" "May I get a name for the reservation?" "And the best phone number in case anything changes?" CHECK AVAILABILITY "Give me one moment while I check the book for [day] at [time]... " [If open] "Perfect, I can seat [party size] at [time]." [If full] "That time is fully committed, but I have [alt time 1] or [alt time 2] open — would either work?" SPECIAL NOTES "Any allergies, a high chair, or a special occasion we should know about?" CONFIRM (read it back) "So that's [party size] under [name], [day] [date] at [time], callback [number]. Did I get that right?" CLOSE "You're all set — we'll see you [day]. We hold tables for 15 minutes, so please call if you're running late. Thanks for choosing [Restaurant Name]!"
- Every restaurant phone script follows the same three beats: greet, capture, confirm — read the details back before you hang up.
- The line that loses revenue is the one nobody answers during the rush; a 24/7 restaurant answering setup keeps reservations and takeout flowing.
- Scripts only work if they're consistent at peak; an AI voice agent runs the exact same flow on call #1 and call #100.
- If your POS is Toast, route orders and bookings straight into it — see how the Toast connection works.
How to build your restaurant call flow
A call flow is just the path a caller takes from "hello" to "done." Map yours once and every reservation, order, and FAQ becomes repeatable — whether a host, a manager, or an AI receptionist is on the line.
Open with a warm, branded greeting
Name the restaurant, give a name, and offer help in one breath: "Thanks for calling [Restaurant Name], this is [Name] — how can I help?" Skip reciting specials before you know why they called; it slows everyone down.
Identify the intent fast
Most calls are one of four things: a reservation, a takeout order, a quick question, or after-hours. Branch early so you can switch to the right script instead of improvising.
Capture the required fields
For each path, know your must-haves: reservations need party size, date, time, name, and callback; takeout needs items, name, number, and pickup method. Missing one field is what causes no-shows and wrong orders.
Confirm by reading it back
The single highest-value line in any script is the read-back. "So that's a table for four under Garcia at 7:30, callback ending 4412 — correct?" catches errors while the caller is still on the phone.
Close with the next step
Set the hold-table window, the pickup time, or the callback promise. End on the brand: "We'll see you Friday — thanks for choosing [Restaurant Name]."
Decide what happens when nobody can answer
The rush, the lunch double-seating, the moment after close — those are the calls that leak revenue. Route overflow to a teammate, voicemail with a real callback promise, or automated overflow coverage that runs the same flow.
Tired of the phone ringing through a dinner rush?
See a flat-monthly AI agent run your exact reservation and takeout scripts — answering every call, even when the floor is slammed.
How to customize each script for your restaurant
The scripts above are scaffolding, not a straitjacket. Start by replacing every bracketed placeholder — restaurant name, hours, address, hold-table window, party-size threshold for reservations — then adjust the tone to match your room. A neighborhood pizzeria and a tasting-menu spot answer the same intents very differently.
Next, encode your real policies. If you only take reservations for parties of six or more, say so in the Hours & FAQs flow. If takeout requires a card on file, add it to the payment beat. The goal is that the script answers the question the same way you would, so callers never get a different story depending on who picks up.
Finally, decide what carries the script when humans can't. A printed card by the host stand works for slow nights; for peak hours and after close, a restaurant-specific AI voice agent can follow these exact flows, push the order into your POS, and text the guest a confirmation. Either way, the script is the source of truth — see how setup works before you commit.
A reservation call, annotated
Here's the reservation flow in action. Hover the highlighted lines to see why each beat matters.
Five phone mistakes that cost restaurants covers
The script fixes most of these by design — but they're worth naming so your team knows what to avoid.
Letting it ring out at peak
The 6–8pm window is when both reservations and takeout spike — and when staff are least able to grab the phone. Unanswered calls don't leave voicemails; they call the next restaurant. This is the gap an after-hours and overflow setup is built to close.
Skipping the read-back
A missed allergy note or a wrong pickup time becomes a comped meal or a one-star review. Reading the order back on the call is the cheapest insurance you have.
Reciting specials before the intent
Front-loading the daily menu on every call adds 20 seconds the caller didn't ask for. Lead with help; offer specials only after you know they're ordering.
Inconsistent answers between staff
If one host says reservations start at four guests and another says six, callers lose trust. A shared script — or an AI agent that never improvises — keeps every answer identical.
Dead-air after-hours
A line that just rings into nothing after close trains regulars not to call. A simple after-hours greeting with hours, your online ordering link, and a callback option keeps the relationship warm.
Who should run your phone script?
Toggle each option to see the trade-offs. The right answer is usually a blend — staff during slow hours, automated coverage when the floor can't pick up.
| Host / staff | MapleVoice | Voicemail | |
|---|---|---|---|
| Answers during a dinner rush | Often misses | Always answers | No |
| Runs the exact same script every time | Varies by person | Identical, call after call | N/A |
| Covers after-hours & holidays | No | 24/7 | Records only |
| Captures party size, time, callback | If trained | Every field, every call | Hopes for a message |
| Pushes orders into your POS | Manual entry | Direct to Toast & others | No |
| Cost model | Wages + tied up at peak | Flat monthly, no per-minute | Free, but loses calls |
Hear the script answer a real call
Listen to how an AI voice agent handles a reservation and a takeout order start to finish.
Restaurant phone script go-live checklist
Run through this before you put any script — human or automated — on your live line.
Why the unanswered line matters
These are directional industry estimates, not figures we measured for your restaurant — your own call logs are the real source of truth.
Customize before you go live
These scripts are starting templates, not policy. Always confirm your real hours, reservation rules, and refund/allergy policies before publishing them — and re-read the after-hours greeting whenever your hours change. Whether a host reads it or it becomes a restaurant answering service script that runs automatically, the words are yours to own. If you'd rather have the line covered without a person on it, see how a restaurant answering service runs these flows for you.
Connect the script to your POS and tools
A script that books a table or takes an order but doesn't record it anywhere is only half a workflow. The last step is routing: a reservation should land in your booking system, a takeout order should hit the kitchen, and a callback request should reach whoever owns it.
If you run Toast, orders and reservation details can flow straight in through the Toast POS connection — no double entry, no transcribing tickets between calls. For everything else, calls and summaries can post to your other connected tools, or arrive as a clean text and email summary so the host stand always knows what happened on the phone.
This is also where flat-monthly pricing matters for restaurants: call volume swings hard between a Tuesday lunch and a Saturday night, and you shouldn't pay per minute for the privilege of being busy. Predictable cost is part of the playbook — see flat-monthly plans and the restaurant industry page for the full picture.
“Our line used to ring out every Friday at 7. Now the same script answers every call and the orders just show up in our system. (Illustrative.)”Illustrative
Put your phone script on autopilot
We set up your reservation, takeout, hours, and after-hours flows, connect them to your POS, and answer every call — flat monthly.