Automating a restaurant does not mean replacing hospitality with robots. It means handing your tools the repetitive tasks that always happen too late or never: reminding a guest the day before, asking for a review, copying a form into the CRM, following up on a missed call, preparing the weekly numbers. During service, nobody has time for them.
This guide covers five restaurant automation scenarios. For each one you will find the trigger, the action, the types of tools you can use and the GDPR point to watch. The scenarios are deliberately generic: they work with most reservation, CRM and messaging software, as long as those tools expose the right data (native integration, API or webhook).
Note: tool labels and options change regularly. Always check your vendor's documentation to confirm that a feature exists in your plan before building a scenario on it.
Scenario 1: automate the day-before reminder
The problem. A table booked three weeks ago is easy to forget. A reminder the day before lets the guest confirm, change or cancel, and gives you time to resell the table.
- Trigger: a reservation exists for tomorrow and its status is "confirmed".
- Action: a short message with the date, time, party size and a link to modify or cancel. If the guest cancels, the table goes back into availability and, if you have one, your waitlist is notified.
- Possible tools: most reservation systems already send automatic reminders (SevenRooms, for example, lists pre-arrival reminders among its transactional emails). To use WhatsApp or SMS, you need a messaging tool connected to your reservation system, or an automation tool that reads tomorrow's bookings.
- GDPR point to watch: a reminder tied to an existing booking is a service message, not prospecting. Keep it strictly factual: no offers, no wine list promotion. As soon as you add advertising, it becomes marketing and you need consent. For WhatsApp, the platform's policy also requires opt-in permission from the recipient before you message them.
Common mistake: sending the same reminder by email, SMS and WhatsApp. Pick one main channel and one fallback.
Scenario 2: ask for a review after the visit, without nagging
The problem. Happy guests rarely think of posting a review, and unhappy ones speak up without you knowing. A well-timed follow-up message catches both.
- Trigger: the reservation moves to "completed" (guest attended), with a delay of a day or two.
- Action: a thank-you message with one simple question ("How was your visit?"). Two branches follow: a satisfied guest receives the link to your review page; an unhappy guest triggers an alert to the floor manager, who calls them back.
- Possible tools: the satisfaction features of your reservation system (SevenRooms offers feedback emails), a messaging tool, or an automation tool that reads the booking status and triggers the send. For replying afterwards, see our guide on how to respond to a restaurant's Google reviews.
- GDPR point to watch: a review request sent after a visit should be a one-off message with no promotion. If you sort guests by satisfaction, check the review platform's terms of use on selective solicitation and on incentives offered in exchange for a review. Keep the guest's answer only as long as necessary.
Common mistake: following up three times. One message, one reminder at most.
Scenario 3: sync website forms into the CRM
The problem. A private-dining request, a newsletter signup, a contact form: each lands in a different inbox, and someone retypes them into the CRM when they remember.
- Trigger: a website form is submitted.
- Action: create or update the guest record in the CRM, with the source ("private dining form", "newsletter"), the date, and the consent status as ticked by the person. A notification goes to the right person (events, management, floor).
- Possible tools: Webflow can send form submissions to a web address (webhook), which an automation tool such as Zapier or Make can receive in order to write to the CRM. Some CRMs also offer their own embeddable form. The full principle, with the mistakes to avoid, is covered in our guide on syncing forms, newsletter and CRM.
- GDPR point to watch: the newsletter checkbox must be unticked by default and separate from the contact request. What the person ticked must travel with their record. A signup copied into the CRM with no trace of consent is a risk.
Common mistake: creating a duplicate on every submission. Always look for the existing record (by email, for example) before creating a new one.
Scenario 4: missed-call alert
The problem. During the rush, the phone rings into the void. The guest who gets no answer calls the next restaurant.
- Trigger: an incoming call is not answered.
- Action: an automatic message (SMS or WhatsApp) explaining how to book online or reply in writing, and an internal alert for the person who will call back after service.
- Possible tools: a phone system or carrier that logs missed calls, connected to a messaging or automation tool. Heep offers exactly this: after an unanswered call, a WhatsApp message is sent, or an SMS if the number is not on WhatsApp (details in our article on Heep's unified messaging).
- GDPR point to watch: you are using the number of a caller you did not solicit. Limit yourself to a single reply, tied to their call, without adding them to a marketing list. Do not keep the number longer than needed to handle the request, unless they become a guest and agree to be contacted.
Common mistake: confusing "replying to a call" with "prospecting". The message should answer the request, not sell.
Scenario 5: a weekly report that sends itself
The problem. The numbers live in four tools (reservations, POS, advertising, reviews) and nobody brings them together. On Monday, management decides by instinct.
- Trigger: a fixed time, for example every Monday morning.
- Action: pull the previous week's indicators (covers, reservations, cancellations and no-shows, reviews received, ad spend), assemble them in one message or dashboard, send to management.
- Possible tools: scheduled exports from your tools, an automation tool, a spreadsheet or dashboard tool. Which indicators to track and how to read them: see our guide to restaurant KPIs to track every week.
- GDPR point to watch: a report does not need named data. Work on aggregates (number of covers, cancellation rate), not guest lists. Restrict access to the document to the people who need it.
Common mistake: piling on indicators. Five well-chosen numbers beat an unreadable table.
Rules that apply to every restaurant automation
Whatever the tool, a few rules prevent most problems.
- A service message is not a marketing message. Reminder, confirmation, reply to a call: service. Offer, newsletter, "come back and see us": marketing. For individuals, the CNIL requires prior consent given by a positive action, with an unticked box. It allows an exception for similar products or services offered to someone who is already a customer, with the right to object simply and free of charge. Check your case with legal counsel.
- Every scenario has an owner. One person knows it exists, checks it monthly and can switch it off.
- Test with your own contact details before going live, then on a few real bookings.
- Always keep a manual fallback. If the scenario fails, someone must be alerted.
- Document the data used, the retention period and how a person can object or request erasure. For SevenRooms email marketing, see our guide on emailing and GDPR.
- Start with a single scenario. The day-before reminder and the missed call are the easiest to scope.
- Measure before and after. Note a simple baseline (no-shows per week, unanswered calls, reviews received) so you can tell whether the scenario actually helps, rather than assuming it does.
- Review the wording. An automated message speaks in your name. Read it as a guest would, in the same tone you use at the door.
Restaurant automation: frequently asked questions
What is the first process to automate in a restaurant?
The day-before booking reminder is the best starting point: the trigger is clear, the message is factual and the effect on no-shows can be measured. The missed call comes second, because it prevents losing a booking request.
Do you need the guest's consent for an automated message?
It depends on the message. A booking reminder or confirmation is a service message. An offer, a newsletter or a commercial follow-up is prospecting, which in principle requires individuals' prior consent. For WhatsApp, the platform's policy also requires the recipient's permission.
Do you need a developer to automate a restaurant?
Not always. Simple scenarios use features built into your reservation software or an automation tool configured visually. A developer becomes useful when you need an API, several tools to connect or precise business rules.
How do you avoid sending errors?
Test with your own contact details, limit volume at the start, check the consent source of each contact and set up an alert if the scenario fails. Review the messages sent during the first few days.
Need help automating your restaurant?
The right scenarios depend on your tools, your team and how you work. māhie designs them with you instead of applying them in bulk.
- Scope the scenarios that are useful for your venue and drop the ones that are not worth it;
- Connect your website, reservation system, CRM and messaging channels through native integration, API or webhook;
- Set up the workflows and alerts that fire during service;
- Build a regular report from your own data;
- Train your team to monitor and adjust them.
To talk it through, see our Automation & AI offer and contact māhie.
