Email · Restaurants
Restaurant emailfor the night they book.
Reservations, private events, and the menu that actually changed. Quiet rooms and multi-site groups do not share a cadence.
The short answer
Mail the occasion, not the weekday.
Restaurant email works when it helps someone book a table, hold a room, or hear about a menu that is really new. The list should come from guests who gave it to you at the table, on a reservation, or in an online order where the box was clearly marketing. A daily special blasted to everyone is how a 40-seat room trains its regulars to unsubscribe.
Buying cycle
Tonight, a birthday, or a buyout.
Most guest decisions are short. They want a table this weekend, a prix fixe on a holiday, or a private room for a date they already have. A smaller set of guests, the ones who host, plan a month out. Those two clocks should not share one email. The weekend table needs a short note when you still have chairs. The buyout needs a human and a date.
Seasonal menus, patio weeks, and the dead stretch after the holidays are the real calendar. If Saturday is already full, the email should not sell Saturday. Capacity is part of the copy.
Constraints
Where the address was collected.
A card at the table is only useful if the guest knew it was for news and events, and if someone can read the handwriting into a list you are allowed to keep. Online ordering tools often store an address so they can send a receipt. That is not the same as permission to announce a wine dinner. We read the capture before we send.
A single dining room and a group of several restaurants are different businesses. The room can mail a few times a month when something changed. The group has to segment by location, or a guest in one city hears about a patio they cannot sit on. SMS for a reservation reminder is a separate opt-in from the email list.
- Do not mail a sold-out service.
- Keep each location's list separate when the menus differ.
- Holiday and patio weeks get a plan. Ordinary Tuesdays do not need a send.
- Receipt addresses stay transactional until there is a real opt-in.
Channels and KPIs
Covers and event holds.
The messages that earn their place are a reservation nudge for guests who used to come and went quiet, a seasonal menu, a private-dining note to people who have booked events, and a short announce when hours change. Loyalty points and SMS alerts can sit beside this. They are not a copy of the same paragraph in another channel.
We watch reservations and event inquiries that follow a send, redemptions when an offer was specific enough to count, and unsubscribes. A quiet restaurant should look at covers, not at a revenue-per-recipient chart built for a store. Open rate will not tell you the dining room filled.
- Reservations tied to a named send, not to 'email' as a lump.
- Private dining inquiries, kept apart from ordinary table bookings.
- Unsubscribe and complaint rate, because the list is small and local.
Mistakes
Daily blasts and one list for every room.
The failure mode is a template that goes out every day because the tool made it easy: soup, happy hour, a photo, a code. Regulars mute it. The other failure is a group that emails every address about every location, so the list dies from irrelevance.
We also see teams export the ordering platform and start a newsletter the next morning. If the guest only agreed to a receipt, that export is the wrong file.
- No daily promotional blast.
- No group-wide send when the news is local to one address.
- No discount on every message until the check average falls over.
- No SMS add-on that assumes the email opt-in covered the phone.
Example engagement
Three rooms, one shared list.
A small group, three dining rooms in one city, different menus. Every guest who had ever ordered online sat on one list. A weekly email advertised all three. The quietest room, about 40 seats, was using the same tone and frequency as the largest. Private dining leads arrived in a shared inbox and aged there.
We split the lists by room, stopped using receipt-only addresses, and kept a short calendar: seasonal menu, a holiday seating, and a note to guests who had not booked in a few months. Private dining went to a named manager. The 40-seat room mailed less than the other two, on purpose. Bookings from those sends were the readout, not opens.
3 rooms
Lists split by location before the next send
Fewer sends
The smallest room mailed only when the menu or the date changed
The example uses anonymized results from a Quorum engagement. It is one account, not a benchmark you should budget against.
Questions
Restaurants questions.
How often should a single restaurant email?
When the menu, the hours, or a bookable date changed, and occasionally to guests who went quiet. A standing weekly send with nothing new in it is how small lists shrink.
Can we use the online ordering email list?
Only if the guest opted into marketing, in words they could see. An address collected to send a receipt stays on receipts.
What about groups with different concepts?
Each concept gets its own list and its own offers. A guest of one room can join another, but they have to be asked. One master blast is the mistake.
Do reservation reminders count as marketing?
A reminder for a table they booked is operational. A promo attached to that reminder is marketing and needs the right consent. We keep those jobs apart. SMS reminders are a separate opt-in again.
Should every email include a discount?
No. A full room does not need a code. Use a specific offer for a slow service or a first visit, and say which night it applies to. A permanent percent off teaches guests to wait.
Can you write the menu descriptions?
We can announce a menu the kitchen already finalized. We do not invent dishes, allergens, or prices. If the menu is still in flux, the email waits.
Talk through restaurants.
One conversation. A diagnostic. A plan you can kill if it is not the work.