The five SMS messages every waitlist needs
The five SMS messages every restaurant waitlist needs are a join confirmation with a quoted wait, a table-ready alert, a quote-change update, a last-call no-show nudge, and a short thank-you. If you only template those five, you will cover the vast majority of what a host actually sends during a rush. Everything else is a variation.
Good waitlist texting is not about clever copy. It is about removing ambiguity at the exact moment a hungry guest is deciding whether to keep waiting, wander off, or get annoyed. Every message below is built to do one job, fit in a single SMS segment, and survive being read on a locked screen by someone half-paying-attention in a noisy lobby.
A single GSM-7 SMS can carry up to 160 characters; multipart GSM-7 messages use 153 per segment. If the final text contains characters outside GSM-7, including many curly quotes and some accented letters, UCS-2 limits are 70 or 67 per segment. Replace placeholders before checking length and cost.
1. Join confirmation templates
This is the receipt. It confirms the guest is on the list, sets the wait expectation, and gives them a way to act. A precise quoted wait here is the single biggest lever on walkaways, so never round down to be optimistic.
- “Bella Trattoria: you’re on the list, party of 4. Estimated wait 35–45 minutes. We’ll text when your table is ready. For changes, call the host at [staffed number].”
- “Oak & Ember: party of 2 added to the waitlist. Estimated wait 25 minutes. You may wait nearby; return when we send the table-ready update.”
- “You’re #6 on the list at Pier 9. Roughly 40 min. We’ll text the moment we’re ready for you.”
Notice the quoted wait is a range, not a single number. A 35–45 minute window is honest and forgiving; “35 minutes” becomes a broken promise at minute 36. For more on getting quotes right, see how to manage a restaurant waitlist.
2. Table-ready alert templates
This is the most important text you send and the one most often botched. It needs the restaurant name, the ready status, a hold window, and where to go. The hold window is what protects your turn time: it tells the guest you will not hold the table forever.
- “Bella Trattoria: your table is ready! Please check in at the host stand within 10 min. See you soon.”
- “Oak & Ember: we’re ready for your party of 2. Come on in — your table’s held for 10 minutes.”
- “Pier 9: your table is ready. Please return to the host stand by [time]. If your plans changed, call [staffed number].”
A table-ready template needs the restaurant name, a return instruction and a route for changes that staff actually monitor. StoveOps does not show inbound SMS or WhatsApp replies in its host queue, so do not ask guests to text HERE or CANCEL expecting the party status to change. See the SMS waitlist workflow.
3. Quote-change and “still waiting” templates
Rushes run long. The kitchen backs up, a four-top lingers over dessert, and your honest 30-minute quote becomes 50. The silent failure mode is saying nothing — guests assume they have been forgotten and leave. A short proactive update buys you patience.
- “Bella Trattoria: thanks for hanging in there. Running about 10 min behind — you’re next up after this turn. Almost there!”
- “Oak & Ember: your wait is running about 15 minutes longer than quoted. We’ll update you when the table is ready. For a change, call [staffed number].”
- “Pier 9: you’ve moved up to #2! About 12 min to go.”
Positive updates (“you’ve moved up to #2”) are just as valuable as apologies. They signal progress and give the guest a reason to stay put. Send one when a party crosses a meaningful threshold, not every five minutes — over-texting trains people to ignore you.
4. No-show and last-call nudge templates
After a table-ready update, a final reminder can restate the exact return deadline before the host releases a table under the restaurant’s policy. Check delivery and use a staffed contact route for changes; a text reply does not update the StoveOps host queue.
- “Bella Trattoria: we can hold your table until [time]. Please return to the host stand, or call [staffed number] if you cannot make it.”
- “Oak & Ember: your table is ready. We can hold it until 7:45. Please return or call [staffed number] if your plans changed.”
If a guest does not return by the stated hold time, apply your published policy and record the outcome. Check delivery first; a send request alone does not tell you whether the guest saw the message. See how to reduce restaurant no-shows for the wider playbook.
5. Thank-you and review-ask templates
The last text is low-effort, high-payoff. A brief thank-you after the visit feels human, and a soft review ask sent at the right moment lifts your rating without nagging. Keep marketing-style asks on a separate consent track from your transactional waitlist texts.
- “Thanks for dining with us at Bella Trattoria tonight! Hope it was great. We’d love a quick review: [link]”
- “It was a pleasure having you at Pier 9. Come back soon — and tell a friend!”
Send the review ask 60 to 90 minutes after the guest is seated, or the morning after a late dinner. Sending it while they are still chewing reads as tone-deaf. If your tool tracks repeat guests, a quietly different thank-you for a third or fourth visit (“great to see you again at Bella Trattoria”) lands far warmer than the same generic line everyone gets.
Writing rules that keep texts out of trouble
A few habits separate templates that work from ones that get ignored or, worse, get you a compliance headache.
- Name the restaurant in every single message. Guests forget which list they joined.
- One action per text. If a message asks for two things, guests do neither.
- Substitute the real name, time and contact route, then measure the final SMS encoding and segment count.
- Always offer an exit — CANCEL, STOP, or a clear way to leave the list.
- Personalize with the guest’s name and party size when your tool supports merge fields, but never let personalization push you over the segment limit.
On consent: treat your waitlist texts as transactional. The guest hands you their number to get a table-ready alert — that is the consent, and you should not repurpose it for promotions. Campaign and marketing texts need their own opt-in and an easy STOP. In the US, the TCPA governs this; Canada’s CASL and anti-spam rules are stricter on marketing messages. Brazil, Mexico and Spain lean heavily on WhatsApp, where opt-in and template approval are baked into the platform. When in doubt, separate transactional from marketing and keep records of consent.
SMS or WhatsApp? Match the channel to the market
The same template works across channels, but the channel should follow your guests. SMS is the safe default in the US and Canada: it needs no app, lands on every phone, and notification fatigue is low for a single table-ready ping. WhatsApp is the expectation in Brazil, Mexico and much of Spain and LatAm, where guests live in the app and replies feel natural.
The practical answer for many operators is to offer both and let the guest choose at sign-up. A digital waitlist that supports SMS, WhatsApp and email covers a mixed guest base without forcing anyone onto a channel they ignore. Email is a fine fallback for confirmations but too slow for a live table-ready alert.
When templates are not enough
Honesty matters here. Saved templates pasted by hand from a phone work fine for a small café doing 20 covers a night. The moment you are running a Friday rush, a second location, or a host who changes every shift, manual texting breaks down: messages get sent to the wrong party, quotes drift, replies pile up unread, and no one can see the lobby at a glance.
Use waitlist software to keep the party and outgoing update in one workflow. Confirm which events actually trigger messages, how delivery is recorded and how staff receive changes; do not assume every tool brings replies back into the host queue.
If you are weighing tools, run them during one real service, not a quiet walkthrough. StoveOps is self-serve with a 7-day free trial, runs beside the POS you already use rather than replacing it, and keeps your guest data yours — Basic is US$49/mo with 500 SMS/WhatsApp messages included, Professional is US$99/mo with 2,000 and a guest CRM. Compare the pricing against your monthly message volume before you commit, and put your five core templates to work on a live Friday. Questions on rollout go to contact@stoveops.com.