Keep tables full between festivals
Collect guests’ emails at the table, send birthday treats and festive menus, ask for reviews and sell out special dinners — from one account.
Email marketing for restaurants & cafés
A café in Indiranagar or a family restaurant in Lucknow can serve hundreds of people a week and still know almost none of them by name. Guests who order online often arrive through a delivery app that keeps their details. When a new menu launches or Sunday brunch has seats left, there is no list to tell.
Email gives a restaurant a list it owns. Collect addresses at the table, on your website and at events; send a short welcome with a reason to return; remember birthdays; announce festive menus a fortnight early; and ask guests for a review. MailNesto handles each of these with forms, automations and a drag-and-drop builder suited to photo-heavy menus.
Most restaurants don’t need to send much. Two campaigns a month and a handful of automations running quietly in the background is a sensible starting rhythm. The sections below show how to set that up, with a worked December at the end.
The problems we solve
Diners enjoy the meal, pay the bill and leave no way to invite them back.
Your most frequent customers order through apps that keep their details.
Weekends are packed; Monday to Wednesday need a reason to come in.
Happy guests rarely think to post a review unless someone asks.
What works for restaurants & cafés
Sign-ups at the table
A landing page behind a QR code on the table card or bill folder, offering a dessert on the next visit.
Birthday and anniversary treats
Date fields send a treat every year, a few days ahead so there is time to book.
Festive menus
A three-step countdown for Diwali, Christmas or New Year’s Eve with the menu and booking link.
Ticketed dinners
Chef’s tables and live-music nights with seat limits, Razorpay payments and QR tickets.
Review requests
A thank-you email with a direct link to your Google review page.
Direct online orders
Shopify, WooCommerce, Razorpay or the Orders API record orders and revenue per email.
Collect emails at the table and online
The best moment to ask is when the meal has gone well. Create a hosted landing page — “Join our dining club for a free dessert on your next visit” — and print its link as a QR code on table cards, bill folders and takeaway bags. Ask for name, email, birthday and, if you have more than one outlet, the favourite branch. Four fields is plenty; people are signing up between courses.
On your website, a pop-up or a slim sticky bar can make the same offer, shown after a delay or when someone is about to leave and never twice to the same visitor. If your reservation tool connects to Zapier or Pabbly Connect, or writes bookings to a Google Sheet, guests who agreed to hear from you can be added with their tags as soon as they book.
- A “Dining club” form design to start from
- Birthday fields that ask only for day and month
- Tags such as outlet-koramangala set on sign-up
- Invisible checks, CAPTCHA or honeypot fields keep bots off the list
Birthdays and anniversaries, a few days early
People plan celebrations ahead, so a birthday email on the day often arrives after the table is booked elsewhere. Set the date trigger to run four or five days before — it can run up to 30 days either side of a date — and the email has time to turn into a table for six. Offer something that suits a celebration: a complimentary cake, a round of mocktails or ₹500 off a bill above ₹2,500.
Wedding anniversaries work the same way with a custom date field. Both run every year on their own. Start from the “Birthday treat” recipe, then add a wait and a condition so anyone who hasn’t clicked gets a short second note on the day itself.
- Sends at the hour you choose, say 11 AM before lunch plans are made
- A coupon block shows the code clearly
- Merge tags greet each guest by name, with a fallback such as “friend”
- The “Welcome offer” recipe reminds new members about their first-visit treat
Ticketed dinners and events
A chef’s table, a regional food festival, a live-music night or a children’s baking workshop sells better with a proper event page. Set the seats and price per seat; guests pay through Razorpay and receive an email ticket with a QR code. Reminders go out a week before and the day before, and a follow-up afterwards can ask for feedback.
When a night sells out, new sign-ups join a waitlist, and if a seat frees up the next person is offered it with a 24-hour hold to pay. At the door, staff scan tickets on a phone and watch the checked-in count. Everyone who registers receives the event’s tags, so the next tasting menu can go first to last time’s guests through the “Early-bird countdown” recipe.
- Seat limits, guest counts and waitlists
- Paid tickets through Razorpay, or free RSVPs for launch tastings
- Add-to-calendar links in every ticket
- Refunds and cancellations recorded against each booking
Reviews and feedback
Happy guests rarely think of leaving a review on their own; one well-timed link makes it easy. If you take orders online, or your billing system sends orders through the Orders API or Razorpay, the “Thank-you & review request” recipe thanks each guest after the order and asks for a review a week later. Point the button straight at your Google review page.
For dine-in guests who joined at the table, add a rating question to the welcome journey instead. Everyone who answers is tagged, which can send a thank-you with the review link. Send it to all responders rather than only high scorers, and never offer a discount in return for a review; Google’s policies rule out both. Read low ratings in the survey report and reply personally.
- Click maps show how many people tapped the review button
- Survey reports with the average rating and every comment
- Responders tagged automatically to start a thank-you
- Unsubscribe reasons show when emails feel too frequent
Win back regulars and fill quiet nights
Cloud kitchens and cafés that take direct orders through a Shopify or WooCommerce site, the Orders API or Razorpay build up order history on each contact. MailNesto learns each customer’s rhythm — the person who orders biryani every other Friday — and predicts their next order date. The “Time to reorder” recipe can nudge them three days before, and “Win back lapsed customers” reaches anyone with no order in 90 days.
For dine-in restaurants without order data, use outlet and engagement instead: a “two-for-one starters on Tuesday” email to members near one outlet who opened something in the last 60 days, sent at 4 PM when evening plans are made. Keep weeknight offers to that segment, so regulars who come at weekends anyway aren’t trained to wait for a discount.
- Predicted next order date and 12-month spend for each customer
- Revenue per campaign in ₹ for direct orders
- Segments combining opens, clicks, tags, outlet and orders
- Abandoned-cart reminders for online ordering sites
A month of emails, worked through
An example plan you can copy and adjust — every step uses features and recipes that are in MailNesto today.
- 1 December
Christmas and New Year’s Eve announcement with the festive menu, an early-bird price for the NYE dinner and its booking deadline, using the “Festival countdown” recipe.
- 4 December
Resend to people who didn’t open, with a new subject line about limited seats.
- Every day
Birthday and anniversary treats go out four days ahead; new dining-club members get the welcome offer and a reminder three days later.
- 8 December
The countdown’s reminder goes out; a condition placed before it skips anyone with the NYE event tag, so people who already booked aren’t asked again.
- 11 December
Weeknight offer to the “near Outlet 2, opened in 60 days” segment, sent at 4 PM.
- 16 December
Last call for Christmas brunch; once seats run out, new sign-ups join the waitlist.
- 19 December
Plum cake and hamper pre-orders from your online shop, with a product block and a countdown to the order cut-off.
- 30–31 December
Day-before reminders and QR tickets for the NYE dinner go out automatically; staff check guests in at the door.
- 2 January
Post-event follow-up with a rating question; responders receive the Google review link and a thank-you.
Start with these automations
Recipes come with finished emails — change anything before you switch them on.
The numbers that matter for restaurants & cafés
Use a hidden field or a separate page per source, so you know whether table cards, bill folders or takeaway bags bring in more members.
Clicks on the booking link, checked against coupons redeemed at the till, show whether the offer and the timing work.
Sold-out nights with low check-ins suggest the reminders need parking or timing details.
For direct orders, revenue credited to each campaign and automation in ₹ shows which emails pay for themselves.
The click map shows how many guests reached your review page from each email.
Festive weeks tempt extra emails. A spike means you sent one too many.
Questions from restaurants & cafés
How do we collect emails from diners without being pushy?
Offer something small and specific, such as a dessert on the next visit, behind a QR code on the table card. Ask for four fields at most, include a clear consent line, and let staff mention it once rather than asking at every table.
Can MailNesto take table reservations?
It isn’t a reservation system. Ticketed nights can be sold through event pages. For everyday tables, keep your reservation tool and connect it through Zapier, Pabbly Connect, Google Sheets or a webhook, and your booking system can send confirmations through the transactional API using the “Table booking confirmed” template.
Can we see orders from every channel?
Orders reach MailNesto from Shopify, WooCommerce, Razorpay or any system that can post to the Orders API. Orders placed somewhere that can’t send them aren’t visible, so revenue figures cover direct orders only.
How often should a restaurant send emails?
Two campaigns a month plus automations such as birthdays and the welcome offer suits most places. Around big festivals you might add one or two more, then return to the usual rhythm.
Can each outlet have its own list and sender?
Yes. Lists can have their own sender name and pages, or you can keep one list with a branch field and use conditional blocks for addresses, menus and timings.
Is it fine to ask for Google reviews by email?
Yes, if you ask every guest the same way. Don’t send the link only to guests who rated you highly, and don’t offer discounts or freebies in exchange for reviews.
Do we need a website?
No. Hosted landing pages and event pages have their own links, which you can share on Instagram, print as QR codes or add to your Google Business Profile.