Blog ·
Restaurant Email Automation: What to Automate and What to Keep Human
Which guest emails a restaurant can automate, how to set them up from trigger to delivery, the UK consent rules, and how to measure results without duplicates.

Restaurant email automation means two jobs: sending the right email at the right moment (a confirmation, a reminder, a thank-you), and answering the emails guests send you (“Do you have a table for six on Friday?”). The first is well suited to simple triggers and templates. The second needs your opening hours, booking rules and policies behind every reply. Get both right and your team stops retyping the same message between services, while the guests who need a person still reach one.
This guide covers which emails to automate, how to build them from trigger to delivery, the UK consent rules that apply, and how to check the whole thing is working without spamming anyone.
TL;DR
- Automate the predictable emails first: booking confirmation, reminder, change or cancellation notice, and a post-visit follow-up.
- Build each one on three things: a trigger in your booking system, accurate data fields, and a template tested before it goes live.
- Confirmations and reminders about an existing booking are service messages. Marketing emails to guests need consent, or the UK “soft opt-in”.
- Inbound enquiries (groups, allergies, special occasions) need answers drawn from your own rules, and a clear route to a human when a decision is needed.
- Measure no-shows, reply times and duplicate messages, not just open rates.
Table of Contents
- What restaurant email automation covers
- Which guest emails to automate first
- How to set up an automated booking email, step by step
- Keep automated emails accurate and hospitable
- Inbound email is the harder half
- What to connect, and what staff should still handle
- The UK rules on guest emails
- Measure it without creating duplicates
- Where Nomi fits
- FAQ
- Sources
What restaurant email automation covers
It helps to split it into two flows, because they are solved differently.
Outbound, triggered by a booking. A guest books, and the system sends something without a person touching it. The trigger is an event: new booking, change, cancellation, a set time before the visit, or a set time after.
Inbound, triggered by a guest. A guest emails asking about availability, a menu, a birthday or a private room. Someone has to read it, check the diary and reply. This is where most restaurants lose time, because the email lands while the team is on the floor and gets buried in a shared inbox.
Most of the pages that rank for this topic are about a third thing: email marketing, meaning newsletters and win-back offers. That is a different job with different rules, and we cover where it touches the law further down. The rest of this guide is about the operational emails around a booking.
Which guest emails to automate first
FSR magazine lists four core automated reservation emails: a confirmation sent straight after booking, a reminder a day or two before, a follow-up or feedback request after the visit, and a cancellation or modification notice when the booking changes. Reservation platform documentation goes further, with standby-list, group enquiry and pre-order emails, and alerts for your own team when a booking comes in.
Here is a practical order to build them in:
| Trigger | What it must contain | Why it earns its place | |
|---|---|---|---|
| Booking confirmation | New booking | Name, date, time, party size, address, key policies | Guest knows it worked; you avoid “did my booking go through?” emails |
| Change or cancellation notice | Booking edited or cancelled | The new details, or confirmation it is cancelled | Stops double-held tables and confusion |
| Reminder | A set time before the visit | Details, a way to confirm or cancel, directions | Frees tables that would otherwise go unused |
| Post-visit follow-up | A set time after the visit | A thank-you, one clear next step | Keeps the relationship going |
| Team alert | New booking, large party, note added | The guest’s request, flagged | Nobody finds out about the nut allergy at the door |
Start with the confirmation and the reminder. They are the two guests notice, and they are the easiest to get right. If you want wording to adapt, our 12 booking confirmation templates give you ready-made starting points, and our piece on reducing no-shows with simple confirmations covers the reminder side in more detail.
How to set up an automated booking email, step by step
Every automated email, whatever software runs it, comes down to the same chain. Marathon Insights’ Zapier-based hospitality guide describes it as a trigger, mapped data fields, filter logic and a connected email platform. Here is the version for a restaurant.
- Pick the trigger. Usually a new booking in your reservation system. Write down the other events too: edit, cancel, no-show, visit completed.
- List the data you need in the email. At a minimum: first name, email address, date, time, party size and a booking reference. Add guest notes if your system stores them.
- Connect the systems. You need a source of booking data, something that sends email, and a link between them. Some reservation systems have email built in, which is the simplest route. Where they do not, a connector tool can pass the data across. SendPulse’s setup walkthrough suggests checking first whether software you already pay for has a built-in option.
- Write the template. Short, warm, specific. Use merge fields (the placeholders that fill in the guest’s name and booking details automatically) instead of typing details by hand.
- Add rules. Different wording for groups, for bookings made far ahead, or for bookings that include a note. A booking for twelve should not get the same email as a table for two.
- Set timing. FSR magazine suggests starting reminders 24 hours before and trying 12 hours if engagement is low. Test what suits your guests.
- Test with real bookings. Book yourself in with a long name, an apostrophe, a note and a party of ten. Check every link and every merged field.
- Switch on, then watch. Read the first week of sent emails with your own eyes.
The common failure points are boring ones: a date that pulls through in the wrong format, a missing address for the second site, or two systems both sending a confirmation for the same booking. Step 7 catches most of them.
Keep automated emails accurate and hospitable
An automated email still represents your restaurant. Two habits matter most.
Pull details from the booking, never retype them. FSR magazine recommends that templates take the guest’s name, party size, date and time directly from the reservation, include the restaurant address and offer an add-to-calendar link, and be tested before launch so links work and information fills in correctly. If you run more than one site, the address line matters.
State your rules in numbers. Vague policies create arguments. Compare these two lines:
- “We may hold your table for a short while.”
- “We hold your table for 15 minutes after your booking time.”
The second one is a rule a host can apply and a guest can plan around. Put the same specifics into confirmations: deposit terms, how late a party can change numbers, when the kitchen closes, whether you take cards only.
For tone, write the email as you would say it at the door. “We’ve reserved a table for four on Friday at 7.30 pm. Reply to this email if anything changes” works better than a block of capital-letter terms.
Inbound email is the harder half
Templates cover what you know will happen. They do not cover the guest who writes: “We’re a party of nine, one of us is coeliac, and it’s my mum’s 70th. Can you do 7 pm on Saturday and is there a set menu?”
That one message contains a group size, an allergy, an occasion, a time request and a menu question. A template cannot answer it. A rushed team might answer half of it, or answer it two days later.
What this email needs is a reply that uses your actual information: whether a table for nine exists that evening, what the group policy says, what the kitchen can do for coeliac guests. And it needs a person to see the allergy and the group size before anything is confirmed. Our guides on managing group bookings by email and on answering reservation questions across calls, emails and DMs set out the rules worth writing down first.
This is the problem Nomi was built around. Nomi is an AI host that answers guest emails using the knowledge and booking rules you give it, supports reservations through connected booking systems, and answers in multiple languages. When a request needs a human decision, such as an allergy, a complaint or a large booking, it flags it to your team. Your team stays in control of how it responds and which actions it can take. It can also recognise returning guests within your venue, so a regular does not start from zero.

What to connect, and what staff should still handle
For outbound emails you need your booking system. For inbound replies you also need your own knowledge: opening hours, menus, policies, group rules, who to escalate to. The more of that you have written down, the better any automation (or any new team member) performs.
Decide in advance which requests always go to a person. A sensible starting list:
- Allergies and dietary needs that affect safety
- Complaints
- Groups above a set size (write the number down)
- Private hire and events
- Anything outside your stated rules, such as a request to bring a cake or a late kitchen
Then decide who picks them up and by when. An escalation that lands in an inbox nobody owns is no better than the buried email you started with.
The UK rules on guest emails
This is general information, not legal advice. For anything specific, speak to a solicitor or check with the Information Commissioner’s Office (ICO).
The key distinction is between service emails and marketing emails. A confirmation or reminder about a booking the guest has made is part of delivering the service. A promotion for next month’s tasting menu is marketing.
For marketing, the ASA’s CAP Code states that you need consent before emailing consumers, unless the soft opt-in applies. The soft opt-in covers similar products or services, where you obtained the contact details during a sale or negotiation for one, and where you offered an opt-out when collecting them and offer one in every later email. Marketing emails must also carry the marketer’s full name and a valid address for opt-out requests. That page notes the section is under review in light of the Data (Use and Access) Act, so check the current wording.
In practice:
- Keep the post-visit “thank you” free of discounts unless the guest has agreed to marketing.
- Add a clear tick box for newsletters at booking, unticked.
- Honour unsubscribes immediately, and keep the two lists separate.
If you also serve guests in other countries, their rules differ, so check each market.
Measure it without creating duplicates
Open rates tell you little about a booking email. Measure what the emails are meant to change.
- No-shows and late cancellations. Count them for a month before you start and a month after. Note any change in your booking mix too.
- Reply time to enquiries. How long from a guest’s email to your first useful reply? Check a sample of ten, including ones that arrived during service.
- Back-and-forth. How many messages does a booking take to complete? Fewer is better.
- Duplicate or wrong emails. Ask the team to log any guest who says they got two confirmations or a wrong detail. Two systems sending the same message is the usual cause.
- Escalations. How many requests reached a person, and how fast were they handled?
SendPulse also suggests tracking open, click-through and unsubscribe rates for series emails, which is useful for follow-ups. Review monthly, change one thing at a time, and do not judge a change on one quiet week.
To avoid duplicates, give each message type one owner: the reservation system sends confirmations, and nothing else does. Write that down.
Where Nomi fits
If your bottleneck is the inbox, not the template, Nomi is built for it. It answers guest emails in your voice and from your rules, works with your booking system, and passes sensitive or unusual requests to your team. Plans on the pricing page are Starter at €49 per month, Standard at €149 per month and Pro at €299 per month, with extra credits from €45 one-off per 500 credits.

Nomi is also running an early access programme in which 20 restaurants try the AI host for free. Some ideas on our roadmap, such as tracking promises made to guests and personalised follow-ups, are product development and not all current features.
Our view
Most restaurants do not have an email problem. They have a rules problem. The opening hours are on the website, the group policy is in the manager’s head, and the allergy procedure lives with whoever is on shift. Email is simply where those gaps show up, at 6 pm, mid-service.
That is why we think automation works best when it starts from your own information and your own limits. Nomi answers using what you tell it, handles the repetitive questions, and brings the rest to your team: allergies, complaints, large bookings. People stay in charge of the decisions that matter.
We would rather a guest got a clear, accurate answer in a minute and a human call-back for the complicated case than a fast reply that guesses. Good hospitality is consistency plus judgement, and the first part is the part software can carry.
Nomi Team
FAQ
Are booking confirmation emails marketing emails?
Generally, a confirmation or reminder about a booking the guest made is a service message, not marketing. Once you add a promotion or an offer, you are in marketing territory, where UK rules on consent and the soft opt-in apply. If in doubt, keep service emails plain and ask a solicitor or the ICO about edge cases.
When should a reminder email go out?
A common starting point is 24 hours before the booking, then trying 12 hours if guests are not responding, as FSR magazine suggests. Your own no-show figures should decide the final timing. Include a one-click way to confirm or cancel.
Can I automate replies to enquiries without sounding robotic?
Yes, if replies draw on your own wording, policies and booking rules, and if anything sensitive goes to a person. Nomi is designed this way: it answers from the knowledge you provide and flags allergies, complaints and large bookings to your team.
How much does it cost to automate guest emails?
It depends on the route. Many reservation systems include basic confirmation emails. For AI-handled replies, Nomi’s plans run from €49 to €299 per month, as listed on its pricing page.
Sources
- How Automated Reservation Emails Are Transforming Restaurant Guest Experience, FSR magazine
- Email Automation for Hospitality: Complete Zapier Setup Guide, Marathon Insights
- 6 Automated Email Campaigns for Restaurants, SendPulse
- 10 Use of data for marketing, ASA CAP Code