Restaurants: Missed-Call Text-Back Examples
Ready-to-use missed-call text-back templates for restaurant reservation calls, takeout orders, catering inquiries and after-hours, with timing and tone tips.
In short
A missed call at a restaurant is a missed cover, a lost takeout order, or a catering job that walked to the place down the street. Phones ring hardest at exactly the moments the floor is slammed — the lunch rush, the dinner service, a Friday night — so calls go unanswered and most callers never leave a voicemail. A missed-call text-back fixes this by firing an automatic SMS the second a call rings out, so the guest gets a real reply in seconds instead of silence. The best messages name the caller where you can, name your restaurant, acknowledge the missed call, and ask one clear question that keeps the conversation going. Below are copy-paste templates for the four situations a restaurant faces most — missed reservation calls, takeout and order calls, catering and event inquiries, and after-hours — each with square-bracket tokens you swap for your details. Pick the ones that match your phone lines, drop in your restaurant name and hours, and you have an instant reply system you can switch on today.
Key takeaways
- A strong text-back names four things — the caller's name where you have it, your restaurant, an acknowledgement of the missed call, and one clear question that invites a reply.
- Speed is the whole point — a text sent within seconds catches the guest before they book a table or order takeout somewhere else, so automate the send rather than replying by hand.
- Write a different template for each line — reservations, takeout orders, catering and after-hours each need their own wording and their own next step.
- Always set expectations — tell the caller when a human will follow up so the automated text reads as helpful rather than a dead-end bot reply.
- Include an opt-out on the first message and keep each text under 160 characters so it sends as a single segment and stays compliant.
Some links to tools we rate — including HighLevel — are affiliate links. If you start a trial through them we may earn a commission, at no extra cost to you. We only recommend tools we would set up for our own clients.
A missed call at a restaurant is a missed cover. Guests pick up the phone while they are ready to spend — booking a Friday table, placing a takeout order, or pricing a catering job — and if your line rings out during the rush, most will not leave a voicemail. They call the place down the street. A missed call text back for restaurants closes that gap by firing an automatic SMS the second a call goes unanswered, so the caller gets a real reply in seconds instead of silence. This guide gives you copy-paste text-back templates for the four situations a restaurant faces most: missed reservation calls, takeout and order calls, catering and event inquiries, and after-hours. Swap the [square-bracket] tokens for your own details and turn them on today.
What makes a good restaurant text-back?
Every effective text-back names four things: the caller's name where you have it, your restaurant, a short acknowledgement that you missed the call, and one clear question that invites a reply. That is the whole formula. The message has to arrive within seconds — the value collapses the longer it takes — and it should ask a single question the guest can answer in a couple of taps. Keep the tone warm and human, the way a good host talks, and on the first text in any thread include an opt-out line. For the full mechanics behind all of this, read our missed-call text-back guide.
When should each text-back fire?
The trigger is always the same — a call that goes unanswered — but the wording depends on which line was missed and what time it is. The table below maps each scenario to the goal the message needs to hit.
| Scenario | Message goal |
|---|---|
| Missed reservation call | Capture party size and time, and get the booking back on track |
| Missed takeout / order call | Point the caller to ordering or a callback without making them redial |
| Catering / event inquiry | Reference the event, offer a menu or quick call, win the high-value lead |
| After-hours call | Acknowledge you are closed, set a callback expectation, capture the need |
| No reply after first text | Send one friendly nudge, then hand off to a human |
Match the message to the moment and the line. A reservation caller wants a table; a takeout caller wants food ready to collect; a catering caller wants a quote and reassurance. Sending the same generic text to all three wastes the opportunity — the templates below are written for each. If missed calls are a chronic problem, our guide on how to stop missing calls at a restaurant covers the staffing and routing side.
Missed reservation-call text-back templates
Reservation calls are time-sensitive and easy to lose during service. The text should capture the party size and time and make booking effortless, so the guest does not just call the restaurant next door.
Instant reply (caller unknown):
Hi, this is [Restaurant] — sorry we missed your call! Were you after a table? Reply with your party size and time and we'll get you booked. Reply STOP to opt out.
Instant reply (known guest):
Hi [First name], [Restaurant] here — sorry we missed you during service! Looking to book a table? Just reply with the day, time and how many and we'll sort it. Reply STOP to opt out.
Nudge (a few hours later, no reply):
Hi [First name], still happy to hold a table for you at [Restaurant]. Reply with a day, time and party size and I'll confirm it for you.
Confirmation reply:
Hi [First name], you're booked at [Restaurant] — [Party size] guests, [Day] at [Time]. See you then! Reply here if anything changes.
Missed takeout and order text-back templates
Takeout callers want food ordered and a collection time, fast. Keep these practical and point them straight to the next step so they never have to redial a busy line mid-rush.
Instant reply:
Hi, [Restaurant] here — sorry we missed your call! Want to place an order? Reply here or order online at [Order link] and we'll have it ready for you. Reply STOP to opt out.
Instant reply (known customer):
Hi [First name], [Restaurant] — sorry we missed you! Placing your usual or something new today? Reply with your order and a pickup time and we'll get started. Reply STOP to opt out.
Nudge (no reply):
Hi [First name], still here whenever you're ready to order from [Restaurant]. Reply with what you'd like and we'll have it hot and ready for collection.
Order-ready reply:
Hi [First name], your order from [Restaurant] is ready for pickup at [Time]. See you soon — reply here if you're running late and we'll keep it warm.
Catering and event inquiry templates
Catering and private-event calls are your highest-value missed calls — one booking can be worth dozens of covers, and these callers are usually shopping several venues at once. The text-back has to keep the connection alive and reference their event so it feels personal and fast.
Instant reply:
Hi, thanks for calling [Restaurant] about catering! Sorry we missed you. Reply with your date, guest count and event type and we'll send menu and pricing options. Reply STOP to opt out.
Instant reply (known lead):
Hi [First name], [Restaurant] here re: your [Event] on [Date]. Sorry we missed your call — reply here and I'll send our catering menu and hold your date while we chat. Reply STOP to opt out.
Menu or quote follow-up:
Hi [First name], following up on your catering enquiry for [Event]. I can send a menu, a quote, or set up a quick call — which is most useful? Reply here anytime.
Nudge (no reply):
Hi [First name], still holding [Date] for your [Event] at [Restaurant]. Just reply with your guest count and I'll get a tailored menu and price over to you today.
For more ways to fill tables and win bookings, see our guide to restaurant marketing.
After-hours text-back templates
After-hours calls are the easiest bookings to lose, because the alternative is silence until you reopen. A good after-hours text says you are closed, sets a clear callback or reopen expectation, and still captures what the caller needs.
Instant reply (reservations):
Hi, thanks for calling [Restaurant]! We're closed right now (hours: [Hours]). Reply with the day, time and party size you'd like and we'll confirm your table when we open [Next open day]. Reply STOP to opt out.
Instant reply (takeout):
Hi, [Restaurant] is closed at the moment. We're back [Next open day] at [Time] — reply with your order and we'll have it ready as soon as we open. Reply STOP to opt out.
Weekend or holiday reply:
Hi, thanks for reaching [Restaurant] — we're closed for [Day/Holiday] and back [Return day] at [Time]. Reply with how we can help and you'll be first on our list. Reply STOP to opt out.
Sending these automatically
Texting back every missed call by hand does not work when the floor is slammed, and it is far too slow to matter — by the time someone at the host stand notices the missed call and types a reply, the guest has already booked elsewhere. A CRM or automation platform can watch your phone lines and fire the right template the instant a call is missed, then route the reply to the manager or host stand. HighLevel is one option that does this — it detects the missed call, sends the SMS in seconds, and keeps the whole conversation in one thread. Honestly, any tool that connects to your phone system and sends within seconds will beat manual texting; the value is in the automation and the speed, not the brand. If you want to try it, you can start a free HighLevel trial and wire up the templates above.
To compare the tools that do this, see our roundup of the best missed-call text-back services. You will find more restaurant playbooks in our Restaurant & Hospitality Marketing hub.
Best practices that make these templates work
The templates do the heavy lifting, but a few habits sharpen them. Personalise with a first name and the specific request wherever your system knows them — "your table on Friday" pulls a guest back into the conversation in a way that "your call" never will. Keep each text under 160 characters so it sends as a single segment rather than a costly multi-part message. Set expectations every time: tell an after-hours caller exactly when you reopen or when a human will follow up, so the automated text reads as helpful rather than a dead-end bot reply.
Ask one question per message, not three. If a text asks the caller to pick a time, choose a party size, and browse the menu all at once, most people answer none of them. Pick the single most useful question for that moment and save the rest for the live conversation. And the instant a guest replies, hand the thread to a real person at the restaurant — the text-back exists to reopen the door, not to run the whole booking on its own. These small disciplines are what turn a folder of templates into a recovery system that actually fills tables and lands catering jobs.
Turn missed calls into covers this week
Pick the templates that match your phone lines, swap in your restaurant name, hours and tokens, and connect them to a tool that fires them automatically. If you would rather have someone build the whole system for you — lines watched, templates written, replies routed — take a look at our pricing or book a call and we will map it to your restaurant. Recovering the calls you are already missing is one of the cheapest ways to fill more tables and win more catering.
Frequently asked questions
What is a missed-call text-back for a restaurant?
Why do restaurants miss so many calls?
How fast should the text-back be sent?
What should a restaurant missed-call text include?
Should reservations and takeout have different text-back messages?
What should an after-hours text-back say?
How does a text-back help with catering and event inquiries?
Do I need an opt-out on text-back messages?
Can I automate missed-call text-back for a restaurant?
How many follow-up texts should I send if there is no reply?
What tone works best for restaurant text-backs?
About the author

Founder, GHL Spark
Farhad is the founder of GHL Spark, where he builds and white-labels GoHighLevel SaaS platforms for agencies and SaaS operators. He writes about the parts of GoHighLevel that actually break in production — A2P registration, onboarding, support load and automation.
More from Farhad