Key takeaways
- A missed-call text back catches guests who would otherwise try the next restaurant, but only if it gives them a real next step.
- Send one short service message that names the restaurant, offers the official booking or ordering link, and promises a callback window.
- Keep promotions out of the auto-reply and honor any opt-out reply straight away.
- Measure recovered bookings and callback times, not just how many texts went out.
What a missed-call text back does
A missed-call text back is an automatic message sent to a caller's mobile number when nobody picks up. The caller dialed during the rush, the line rang out, and within seconds they receive a text with a way forward: a booking link, an ordering link, or a promise that someone will call back. It turns a dead end into a conversation.
It matters because guests who cannot get through rarely give up on dinner. They give up on you. In a Cornell study, when a restaurant was not listed on a diner's preferred reservation site, 58% said they would still try to book through another channel and only 18% said they would not book at all[1]. Guests are persistent about eating out; the question is whether their next attempt reaches your restaurant or a competitor's.
When it helps and when it backfires
| Situation | Does an auto-text help? | Why |
|---|---|---|
| Line busy during Friday dinner | Yes | The guest gets a booking link now and a callback later instead of a ringing phone |
| After hours, kitchen closed | Yes | Many guests plan the next day's meal at night; a link lets them act while they are thinking about it |
| Guest calling to report an allergic reaction or complaint | Only as a bridge | The text must promise a fast call from a manager, not push a link |
| Caller on a landline | No | The text never arrives; rely on voicemail and a callback list |
| Repeated calls from the same number within minutes | Partly | Send one text, not one per call, then flag the number for an urgent callback |
| Vendors and sales calls | Neutral | Filter known vendor numbers so they do not receive guest messages |
The pattern is simple. Auto-texts work for routine intent such as booking, ordering and hours, where a link solves the problem. They work badly for anything emotional or urgent, where only a person will do.
Why the timing matters
Restaurant guests do not keep business hours. Cornell research cited an OpenTable estimate that about a quarter of reservations were made between 10:00 p.m. and 10:00 a.m., when most restaurants are closed[2]. A call that rings out at 11 p.m. is often a booking intent that will go elsewhere by morning.
Guests also struggle to reach restaurants when they need to change plans. In a Cornell survey of frequent diners, respondents often found it hard to contact a restaurant to change a reservation, even though they believed guests should call when plans change[3]. A text thread gives those guests an easy way to tell you they are running late or need to cancel, which protects the table as much as the guest.
What the text should say
Every version needs four things: the restaurant's name, why they are getting the text, one clear next step, and how to stop. Keep it to one message. These templates cover the common cases.
- During service: “Sorry we missed your call at Harbor Grill. Book a table here: [link]. For anything else, reply to this text and a host will answer shortly. Reply STOP to opt out.”
- After hours: “Harbor Grill is closed for the night. You can book here: [link] or order for tomorrow here: [link]. We'll call back after 11 a.m. if you reply with your question.”
- Holiday closure: “Harbor Grill is closed today for the holiday and reopens Thursday at 5. Reservations: [link]. Reply STOP to opt out.”
- Catering line: “Thanks for calling Harbor Grill events. Reply with your date and guest count and our events manager will call you today.”
Never write “your table is held” or “your order is confirmed” in an auto-reply. Nothing has been booked yet. Promise only what the link or the callback will deliver.
Consent and wording rules
An automatic reply to someone who just called you is a service message, not a marketing blast, and it should stay that way. Do not add a promotion, a loyalty pitch or a review request. Those belong on a separate, opt-in marketing list.
Opt-outs apply even to service texts. Under the FCC rule a reply such as stop, quit, end, revoke, opt out, cancel or unsubscribe revokes consent, other clear wording counts too, and the request must be honored within ten business days at most[4]. Suppress the number at once, send no more than one plain confirmation, and make sure the suppression also covers future missed calls from that number.
- Send from a registered business texting number, not a staff mobile.
- Identify the restaurant at the start of the message.
- Include opt-out wording in the first message to each number.
- Send once per missed call event, with a cooldown of at least a few hours per number.
- Skip numbers marked as opted out, vendors or internal staff.
Set it up in five steps
Decide which calls trigger a text
Ring-outs, calls to voicemail and calls abandoned in the queue. Exclude calls answered and transferred, so guests who already spoke to someone are not confused.
Write one template per situation
Service hours, after hours, holiday closure and catering. Load them with the official booking and ordering links only.
Route replies to a person
Replies should land in a shared inbox the host or manager on shift can see, ideally the same place as other guest texts.
Build the callback list
Any reply that asks a question, and any repeated missed call, goes onto a callback list with a promised time.
Test with staff phones
Call from two mobiles and a landline, reply STOP from one, and confirm the right message, the suppression and the callback entry.
Habits that make auto-texts annoying
Guests forgive a missed call. They are less forgiving of a robot that seems to ignore them. Most complaints about missed-call texts come from a few avoidable habits, and each one has a simple fix.
- Texting every ring-out: a guest who redials three times gets three identical messages. Use a per-number cooldown.
- Links that open a generic home page: send the booking page or the ordering page itself, not a page the guest has to search.
- Promising a callback nobody makes: if the manager cannot call back tonight, say tomorrow and give the time.
- Long messages: anything that needs scrolling on a phone screen gets skipped. Two short sentences and a link is the target.
- Sending at 2 a.m. for a call that came in at closing: queue late replies with a sensible delay, or send the after-hours version straight away and leave it there.
- Ignoring replies that arrive as voice notes or photos: make sure the inbox shows them, and train staff to open them.
Review the message itself every season. Holiday hours, patio openings, a new ordering partner or a menu change can make a template wrong overnight, and an auto-reply that sends guests to an old link does more damage than no reply at all.
Measure whether it works
Track a few numbers weekly for the first month. Example targets for a single full-service restaurant are shown in brackets; set your own from your call logs.
- Missed calls that received a text (Example: above 90 in 100 mobile callers).
- Texts that led to a booking or order through the link, using a tagged link so you can count them.
- Replies that needed a person, and how long they waited for an answer.
- Opt-out replies, which should stay low; a spike means the message is unclear or too frequent.
- Callbacks completed by the promised time.
Phone ownership is not the limit here: 98% of US adults own a cellphone[5]. The limit is usually what happens after the text. If replies sit unanswered for an hour, the text has only delayed the disappointment. Pair the auto-reply with a phone coverage plan for short-staffed shifts so someone owns the replies on busy nights.
Example: Friday at a 90-seat bistro
Example: a fictional 90-seat bistro misses calls between 6:30 and 8:30 on Fridays because the host is seating a full waitlist. The owner turns on a missed-call text with the booking link and a reply-for-help line. Over four Fridays, the manager counts the tagged link and finds a handful of extra bookings each night, plus several guests who replied to say they were running late, which let the host release or hold tables with more confidence.
Example: two guests replied with allergy questions. Those went straight to the manager for a callback, as the template promised, instead of being answered by text. The owner kept the setup and added a Spanish version of the message for the catering line, following the approach in serving callers who prefer Spanish.
Frequently asked questions
Is a missed-call text back legal?
An automatic reply to someone who just called you is a service message, but opt-out rules still apply. Identify the restaurant, keep marketing out, include STOP wording and honor opt-outs straight away.
Should the text go out immediately?
Yes, within a minute of the missed call, while the guest is still deciding where to eat. Send one message per missed call event, not one per ring-out.
What if the caller is on a landline?
The text will not arrive. Keep a voicemail greeting that promises a callback window and work the callback list during quieter moments.
Can the auto-reply include a discount to win the guest back?
Avoid it. A discount turns a service reply into marketing, which needs separate opt-in consent. Offer the booking link and a fast callback instead.
References
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) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2009). How Restaurant Customers View Online Reservations (Cornell Hospitality Report Vol. 9, No. 5) (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), eCFR text of FCC rule (2026). 47 CFR § 64.1200 - Delivery restrictions (opens in a new tab) ↑
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑