Restaurant email automation: 12-minute response time

What restaurant email automation actually is

Restaurant email automation is a workflow inside your existing Gmail that watches the inbox for reservation inquiries, reads and classifies each one as it arrives, checks your availability source, and drafts a complete reply for a manager to approve. The manager opens the draft, edits it if needed (most go out unchanged), and hits send. The guest receives a personalized response in under 12 minutes. The manager spent about 45 seconds on it instead of 8 minutes writing a reply from scratch. This is not an autoresponder. An autoresponder fires a generic acknowledgement. Restaurant email automation drafts a contextual reply that handles the specific request: date, party size, occasion, dietary requirements, available tables, and the relevant menu options. The booking inbox is part of a wider pattern covered in our guide to what restaurant automation is.

The email problem every restaurant has

Your restaurant's Gmail inbox is open 24 hours a day. Your team is not. Reservation inquiries land at 10pm, at 6am, and during the lunch rush when the person responsible for bookings is on the floor. The inquiry sits until someone happens to open the inbox. By then the guest has booked somewhere else. This is not a discipline problem. It is a structural mismatch between when inquiries arrive and when the team is free to answer them. A shared inbox with three people and no clear owner makes it worse, because everyone assumes someone else has it. The fix is not another reminder to check email faster. The fix is a system that drafts the reply the moment the inquiry lands, so the only human step left is a quick read and a click.

The numbers from a real engagement

A London hospitality group with 22 staff across 8 venues was averaging 38 hours between receiving a reservation inquiry and sending a reply. The inbox was shared across three people with no clear ownership, inquiries arrived at all hours, and nobody owned the 11pm to 8am window. We built a Gmail-side responder using the Gmail API that read each inquiry, checked availability in the group's OpenTable calendar through a Make workflow, and drafted a reply in under a minute. The front-of-house manager approved and sent from the inbox they already used. After one month, average response time moved from 38 hours to 12 minutes, reservation conversion rose from 31 percent to 58 percent, and weekly inquiries held at 40. At two covers per inquiry and a £180 average spend, the 27-point lift in conversion works out to roughly £3,900 per week in recovered revenue. The quarterly engagement cost £10,500 and paid for itself in under 3 weeks.

How the technical side works

The system connects to your existing Gmail account through the Gmail API. It reads incoming mail in a specific label or folder, extracts the key details with AI, queries your availability source through a Zapier or Make connector, and writes a draft into your Gmail drafts. The manager gets a notification on their phone through the Gmail app they already have, opens the draft, reviews it in about 20 seconds, edits if needed, and sends. Nothing about the Gmail interface changes. Nothing about the manager approval step changes. The only thing that disappears is the 8 to 12 minutes of composing each reply from a blank screen. Because the draft already references the guest's date, party size, and the tables actually free that night, the manager is editing a near-final reply rather than starting from nothing.

What it does not do

The system does not send emails on its own. Every reply passes through a human approval step, and that is a deliberate choice. A restaurant inbox is a brand touchpoint, and a system that could occasionally send a wrong or off-brand reply unsupervised is a risk worth designing out. The system does not replace your booking platform either. It reads from whatever availability source your team already maintains, whether that is OpenTable, ResDiary, Resy, SevenRooms, or a shared Google Calendar. Migrating platforms is never a prerequisite. The system also does not try to handle complex inquiries. A nuanced corporate event request, a birthday dinner with specific decorating requirements, or a group menu negotiation gets flagged for personal attention rather than auto-drafted, so the human keeps the conversations that need a human.

The revenue arithmetic of response time

The revenue case for restaurant email automation is straightforward and usually undersold. Here is the calculation an owner can run for themselves. A 40-cover independent in London takes 35 to 60 inquiries per week across email, web form, and social DM. Without automation, average response time sits at 18 to 48 hours, with most falling in the 24 to 36 hour band. Research across hospitality consistently puts conversion at 45 to 60 percent when you reply within 12 minutes, and at 15 to 25 percent once you slip past 24 hours. On 50 inquiries a week, the gap between a 12-minute reply and a 24-hour reply is roughly 17 more bookings per week. At a £180 average spend for two covers, that is about £3,060 per week in extra revenue from the exact same inquiry volume. Read against any sensible build cost, the first few recovered bookings already cover the work.

Email automation approaches for restaurants, compared

Not every approach is the same thing, and the differences decide whether the inbox actually gets faster. Use this to place each option.

• Native autoresponder (Gmail Vacation Responder): runs in Gmail, no approval step, live in minutes, free. It only sends a generic acknowledgement, so it does not improve conversion.
• Email marketing platform (Mailchimp, Klaviyo): runs in a separate dashboard, campaign-level approval, live in days, roughly £50 to £300 per month. Built for broadcasts, not for answering an individual booking inquiry.
• AI-drafted inbox responder: runs inside your existing Gmail with per-draft approval, live in the first few weeks, around £2,000 to £3,500 per month. This is the approach described throughout this article.
• Agency-built email AI system: where it runs and how it is approved varies, typically 8 to 12 weeks to go live, around £4,000 to £8,000. Heavier, slower, and often more than an independent restaurant needs.

What "automation" really means here

The word automation gets misread in a restaurant context. It does not mean unsupervised, and it does not mean a machine sending mail nobody has read. In its useful form it works like this. A workflow inside your existing Gmail, built on the Gmail API, watches the inbox for reservation inquiries. When one arrives, it reads the request, checks your availability source through a Zapier or Make connector, and drafts a complete reply in your voice. The manager gets a phone notification through Gmail, reads the draft in 20 seconds, edits if needed, and sends. The guest gets a personalized response in under 12 minutes no matter when the inquiry came in. The automation is in the drafting. The decision stays human. That line matters to the team who actually use it and to the guests, who simply experience a fast, human reply.

How to set it up without new software

The setup needs five things: a Gmail account with API access enabled, a defined availability source such as OpenTable, ResDiary, Resy, or a shared Google Calendar, a set of response templates calibrated to your real inquiry types, a Zapier or Make workflow joining Gmail to that source, and a notification path for the manager reviewing drafts. None of that requires your team to learn a new tool. A focused build delivers it in the first few weeks. A technical hire building the same thing from scratch would spend 6 to 10 weeks and then carry the ongoing maintenance. The work that matters is rarely the wiring. It is calibrating the templates to your voice and adjusting them as your inquiry patterns shift through the seasons.

How twohundred would approach it

If you brought this to us, the first move is not building anything. It is a 30-day baseline: current first-response time, current conversion on direct inquiries, and the real weekly inquiry volume across email, web form, and DM. Without that, you cannot prove the system worked, and an outside operator who skips the baseline is selling you a dream. Then we build the Gmail-side responder, run it in parallel with every reply human-approved, and measure the same 30 days against the baseline. We name an internal owner for the templates and venue knowledge on day one, because the replies go stale within a quarter without one. This is one workflow in a wider AI workflow automation practice at twohundred, and the booking inbox is usually the first one we build because it pays back fastest.

Frequently asked questions

Does restaurant email automation work with our existing Gmail?

Yes. The system runs inside Gmail through the Gmail API rather than replacing it. Your team uses the same inbox they open every morning, and the manager approval step they already trust stays exactly as it is. Nothing about the interface changes.

Can guests tell the reply was drafted by AI?

No. The response reads as a personalized reply from your team because that is effectively what it is. The AI drafts it, your manager reviews and approves it, and the guest receives a human-checked response that happens to arrive in 12 minutes instead of 38 hours.

Does it work with booking platforms other than OpenTable?

Yes. It connects to any booking platform with a calendar export or an API. ResDiary, Resy, SevenRooms, and Google Calendar are all supported through Make or Zapier. If your platform exports to Google Calendar, that is often the simplest path to wire up.

What happens if the team does not approve a draft quickly enough?

The system places the draft in Gmail and sends a notification. If a draft sits longer than a set threshold, typically 30 minutes, a second notification goes to a backup approver. Response time never slides back toward 38 hours just because the primary manager is off shift.

What does a realistic rollout look like?

For an independent operator it is about four weeks end to end. Week one is baseline measurement and an inbox audit. Week two is the build and approval-loop configuration inside Gmail. Week three is parallel running with every reply human-approved. Week four measures the same window against the week-one baseline, so you know whether response time and conversion actually moved.

---

Related Services

For operators ready to move beyond individual tools, AI implementation services covers the full deployment cycle from pilot to live. Connecting the system to your existing reservation, POS, or CRM stack is handled through AI integration services.