Restaurant Email Auto-Reply: 35% of Booking Requests Go Unanswered in 24h

There are two ways to miss an email: never seeing it, or seeing it and putting it off until after service. The second is far more common, and the only one a tool can fix.

An email does not ring, it waits. In a business where nobody owns the inbox, it waits 2.4 hours on average, often a whole night, sometimes indefinitely. The channel is not dead: it is unowned.

So we treated the inbox as a queue rather than as a mailbox. Every inbound message gets three things before a single word is drafted: a type, a deadline, a destination.

Why email is still a real booking channel

Email has been declared dead since 2019. In practice, it still represents a significant share of inbound enquiries, and not from just any guest.

• Corporate clients and groups. An organiser booking a business lunch for 12 does not send an Instagram DM. They send an email with dietary requirements and ask for written confirmation.
• International tourists. A visitor who discovers your restaurant via Google Maps will often use email rather than WhatsApp, especially outside Europe.
• Events and private dining. Birthdays, corporate dinners, buyouts: detailed requests come by email. These are often the highest-value tickets of the year.

The figures point the same way: a large share of group and event enquiries arrives by email, 65% of guests prefer a written channel for complex requests (Meta Business Messaging Survey, 2024), and a restaurant's reply time to an inbound email is measured in hours, not minutes. Put plainly: the longest requests land on the least-watched channel.

The problem: 35% of emails unanswered in 24h

On the restaurant side, it is one email among forty. Not urgent, to handle after service, then forgotten. On the guest side, it is a request for a birthday dinner for 10 left unanswered for two hours: they write to the restaurant next door. Table lost, average ticket £450. In all, 35% of booking emails sent to a restaurant receive no reply within 24 hours; at a £50 average check, that is thousands of pounds in lost revenue every month.

Delay is the real problem. A reply in four hours still converts. A reply the next day, rarely. No reply at all, never.

Observed case, private dining restaurant, Paris 8th

• Before Heep: privatisation emails handled by the manager outside service hours. Average response time: 6 hours.
• After Heep: acknowledgement in 30 seconds, request qualified, forwarded to the right contact in under 2 minutes.
• Result: +4 confirmed private events per month, around €2,800 in additional revenue.

What a well-configured auto-reply must do

A basic auto-reply says "Thank you for your message, we will reply as soon as possible." Better than nothing, and it qualifies nothing. A useful one does four things, in this order.

1. Acknowledge within 5 minutes

   The guest knows their message arrived. They do not follow up, and they do not shop around.

2. Qualify the request

   Number of guests, date, occasion type, dietary needs: extracted from the inbound email and used to prepare the booking, instead of being asked for again.

3. Propose genuinely available slots

   Connected to your system (Zenchef, TheFork, SevenRooms), the assistant offers matching availability, not polite placeholders.

4. Confirm or escalate based on complexity

   Standard booking: confirmed. Private dining or special menu: forwarded to the manager with full context. The threshold makes the difference, and it is yours to set.

The 4 email types to automate first

• Standard booking requests. Date, time, covers: 80% of inbound emails. Fully automatable, direct confirmation into the booking system.
• Group and event enquiries. Instant acknowledgement, qualification, then handoff to the events manager with a structured summary.
• Information requests (menu, allergies, hours). Reply with exact information from your restaurant profile. Zero copy-paste.
• Booking confirmations and reminders. Confirmation sent after the booking, then a reminder 48h before to reduce no-shows.

How many emails is your restaurant leaving unanswered each week? Calculate your lost revenue across all channels

How Heep handles restaurant booking emails

Heep does not replace your email address: it watches it and replies the moment a message arrives, including at 11 pm and on a Sunday.

In practice, the 7:45 pm email is no longer read next morning for a manual reply at 10 am, once the guest has booked elsewhere. It gets a reply in under 5 minutes, and the booking is written into Zenchef straight after.

The tone does not move: formal for fine dining, relaxed for a brasserie. It knows your allergens, opening hours, current menu and group policies, because your settings describe them.

What stays in your hands: the tone, the threshold at which an email stops being standard, and who receives those. The full journey of a request is described in how Heep works end-to-end; the write into the book, in the Zenchef integration.