Restaurant email marketing, written for a room that has to fill on Tuesday.
Email is the cheapest channel a restaurant owns and the easiest one to waste. This is where the addresses come from, what to write, and the point at which you should send a text instead.
Published 4 September 2026 · Written by the TableHub team
The list is the asset. The emails are just the interest payment.
A restaurant serving 900 covers a month touches roughly 400 distinct households. Capture an address from a third of them and inside a year you have around 1,600 people who have eaten your food and can be reached for close to nothing.
That is the entire game. Everything below — the moments, the subject lines, the sequence — exists to grow that number and keep it warm. A beautiful template sent to 90 addresses is worth less than a plain-text note sent to 1,600.
Four moments where a list actually grows
The booking form
Email is already required to send a confirmation. One checkbox underneath, worded plainly, turns a transactional address into a marketable one.
The catch. The checkbox has to be unticked by default and say what you will send. 'Occasional emails about menus and events, roughly monthly' converts better than 'subscribe to our newsletter'.
Pickup and delivery checkout
Direct orders are the richest source you have — the guest already typed an address and a name. Ask once, at the receipt screen.
The catch. Orders that came through DoorDash or Uber Eats do not give you this. That is the whole argument for direct ordering.
The check drop
A small card with a QR to a one-field form. First name and email, nothing else. Every extra field roughly halves completions.
The catch. Offer something real — a free starter on the next visit, not '10% off sometime'.
Waitlist and cancellations
People who wanted a table and did not get one are the warmest addresses in the building. Capture and follow up within 48 hours.
The catch. Follow up with an actual available slot, not a generic 'come back soon'.
Three of these four moments only exist if guests book and order on your own site. The arithmetic on that is on the commission-free ordering page.
Subject lines: four formulas that survive a phone screen
Roughly two thirds of email is opened on a phone, which gives you about 35 characters before the line truncates. Front-load the noun.
Specific dish + specific window
“Soft-shell crab is on until Sunday”
Names a thing and puts a clock on it. No adjectives needed.
One sentence a regular would text a friend
“We finally got the wood oven working”
Reads like a person, which is why it survives a phone-screen skim next to nine promotional emails.
The number
“42 people booked Saturday. There are 6 tables left.”
Real scarcity beats manufactured scarcity, and it only works if the number is true.
The plain question
“Wine dinner in October — worth doing?”
Invites a reply. Replies are the strongest deliverability signal a small sender can generate.
What to avoid: the word FREE in caps, three emoji, and anything that could have been sent by any restaurant in the country. “Delicious deals await!” is a subject line written by someone who has never worked a service.
A welcome sequence that does not read like a funnel
Four emails over three weeks. Set it once; it runs against every new address forever.
1. The welcome Immediately
Who cooks here, what you are known for, and one link to book. Two short paragraphs. No coupon yet — the coupon in email one teaches people to wait for coupons.
2. The one thing to order Day 3
A single dish with a photo and two sentences about why it exists. This is the email that turns a subscriber into a booking.
3. The reason to come on a weeknight Day 10
Your quiet service, framed as the better experience it usually is: shorter wait, the chef on the pass, the full menu still available.
4. The ask Day 21
A first-visit offer with a real expiry, plus an invitation to reply with dietary notes. Replies land you in the primary inbox next time.
Email or text? Decide by how fast the message expires
| Message | Channel | Why |
|---|---|---|
| Tonight is quiet, come in | SMS | Read within minutes. An email sent at 4pm is opened at 9pm, after service. |
| New autumn menu | Needs photos, descriptions and room to read. | |
| Your table is confirmed | SMS | Transactional, needs to arrive on the phone that is walking to the door. |
| Holiday bookings are open | Planned weeks ahead, and people forward it to whoever is organising. | |
| Two cancellations for 7:30 | SMS | Expires in an hour. |
| Story about the new supplier | Nobody wants 300 words as a text. |
The consent rules for texting are stricter and the penalties are real — the wording, timing and opt-out mechanics are covered in the SMS marketing guide. Broader tactics sit in the marketing ideas list.
Questions owners actually ask
- How often should a restaurant email its list?
- Once or twice a month. Monthly is the floor — go quarterly and half the list forgets they signed up, which shows up as spam complaints rather than unsubscribes. Weekly only works if you genuinely have something new every week, and almost no independent does.
- What is a good open rate for restaurant email?
- Restaurant and food-service senders typically land in the mid-30s to mid-40s for opens on a list built from real diners. If you are under 20%, the problem is usually list source, not subject lines — bought or scraped addresses drag everything down.
- Email or SMS for restaurants?
- SMS for anything time-sensitive: a slow Tuesday, a same-day cancellation, a two-hour offer. Email for anything that needs space: a new menu, a story about a supplier, a holiday booking window. Sending a 400-word newsletter by text is how you get opt-outs.
- Do I need consent to email diners?
- You need an opt-in in most jurisdictions, and under CAN-SPAM you always need a real physical address and a working one-click unsubscribe in every commercial message. Adding someone because they booked a table is not consent unless the booking form said so.
None of this works without the addresses.
TableHub captures name, email and phone on every booking and pickup order, so the list builds itself while you cook.