Skip to content
iMessage APIs
Industry playbooks7 min read

Restaurants: reservations, waitlists and the Saturday rush

A table held for a party that never arrives on a Saturday night is the most expensive empty seat in the business. Messaging fixes a surprising amount of it.

Restaurant messaging has a shape unlike other small businesses: almost nothing happens Monday to Thursday, and then several hundred messages need to go out across a Friday and Saturday. That spikiness is the first reason per-line pricing suits the trade — a flat monthly rate is far easier to forecast than a metered bill that triples in December.

The confirmation that actually reduces no-shows

A booking made eleven days ago has faded. The evening-before confirmation is what converts it back into a plan, and asking for a reply is what makes it a commitment.

Harbor Kitchen

iMessage

Hi Priya — Harbor Kitchen. We've got you for 4 tomorrow at 7:30. Reply Y to confirm, or let us know if the numbers changed.

Y — actually can we make it 5?

Done, table for 5 at 7:30. See you then.

The party-size correction is worth as much as the confirmation. That is a covered seat you would otherwise have lost.

Note what happened in the second message. An open invitation to correct the booking surfaces changes that would otherwise arrive as a surprise at the door. Restaurants that ask this question consistently report fewer mismatched tables on the night.

The waitlist message

Walk-ins waiting at the bar or outside are the clearest case for real-time messaging. The requirement is speed and precision, and nothing else.

Harbor Kitchen

iMessage

Your table's ready — come on in whenever you are.

2 mins!

Short, no branding furniture, no link. The customer is thirty feet away and looking at their phone. This is the one message where brevity beats warmth. Barbershops run the same play and it converts walkouts into customers.

Cancellation fills

A 7pm Saturday cancellation at 4pm is recoverable if you can reach people fast. Message the recent-diner list for that night only, first come first served, and close the loop the moment it goes.

Do not run this play more than about once a week

A 'we have a table tonight' message is exciting the first time and reads as desperation by the fourth. Reserve it for genuinely valuable slots. Frequency discipline matters more in hospitality than almost anywhere, because your customers are also your neighbours.

What not to send

  • Menu announcements. Nobody wants these in the thread with their family. Put them on email or social.
  • Birthday promotions to people who dined once. The data feels clever; the message feels invasive.
  • Anything after 9pm. You are in hospitality — you know when people are eating. Also, quiet hours are a legal matter, not a courtesy.
  • Review requests to a table that complained. Suppress on any flagged service issue.

The one number to watch

Covers lost to no-shows, per week. Everything else — confirmation reply rate, waitlist conversion, cancellation refills — is a diagnostic for that single figure. If you also let rooms, hotels and short-term rentals have a related but sharper version of this problem. If covers lost is falling, the programme works. If it is flat after six weeks, change the timing before you change anything else.

For the general rules on writing these messages so they read as hospitality rather than marketing, see how to write a business text people don't hate.

restaurantshospitalityreservations