Blog ·
How to Manage Guest Enquiries in a Restaurant
A practical system for managing restaurant guest enquiries: one inbox, written rules, fast replies, clear handover to staff, and where an AI host fits.

To manage guest enquiries well, do three things: bring every channel into one place, write down the answers to the questions you get every week, and decide in advance which requests need a person. Do that and nobody waits for a reply, nothing gets answered twice, and your team keeps its attention on the guests in the room. An AI host such as Nomi can take on the repetitive part of this: it answers from your own information and rules, and passes the awkward requests to your team.
This guide is for owners, general managers and front-of-house or reservations leads. It covers the routine step by step, with example replies you can adapt.
TL;DR
- Most enquiries repeat: availability, opening hours, menus, groups, occasions and policies. Write the answers once and reuse them.
- Put calls, emails and social messages in one shared view, with one named owner for each message.
- Decide in advance what is answered automatically and what goes to a person: allergies, complaints and large bookings go to a person.
- Reply fast. A 2023 test of 250 UK and Irish venues found one in three guest requests got no reply.
- Track response time, unanswered messages and bookings won, and review them monthly.
Table of Contents
- Why enquiries slip through
- Step 1: Bring every channel into one view
- Step 2: Write down the answers to your common questions
- Step 3: Decide what is automatic and what goes to a person
- Step 4: Reply fast, and say what happens next
- Step 5: Keep a record that carries the conversation
- Step 6: Cut no-shows and confusion with confirmations
- Step 7: Measure it
- Where an AI host fits
- Perspective
- Try it on your own enquiries
- FAQ
- Sources
Why enquiries slip through
Enquiries rarely arrive when you have time for them. They land at 7:30pm on a Friday, while your host is seating a party and the manager is at the pass. A message sits in the inbox, an Instagram DM goes unseen, and a voicemail is played back the next morning.
The cost is real. In a mystery-shopper style test of 250 venues across the UK and Ireland, reported by QSR Media UK in May 2023, one-third of guest requests received no reply at all. Only 22% were answered within an hour, and fewer than 5% of venues sent any automated acknowledgement. Even a simple question about bringing a birthday cake went unanswered by a substantial share of venues. That test is a few years old, but the pattern will be familiar to anyone who has looked at their own inbox on a Monday.
Two problems cause most of it:
- Too many channels. Phone, email, web form, Instagram, Facebook, Google messages and the booking platform each have their own inbox.
- No owner. When a message could be anyone’s job, it is usually nobody’s. Or two people reply, with different answers.
Step 1: Bring every channel into one view
List every place a guest can reach you today. Be honest: include the Instagram account that someone checks “when they remember” and the old email address still on a directory listing.
Then decide:
- Which channels you keep open. Close or redirect the ones nobody can staff. A dead channel is worse than no channel, because the guest thinks you ignored them.
- Where they all end up. Ideally one shared inbox or tool where each message has a status: new, in progress, answered, waiting for guest.
- Who owns it, per shift. Name one person for lunch and one for dinner. Write it on the rota.
A simple rule helps: a message is claimed by whoever opens it, and marked so the rest of the team can see. That stops double replies.
If you take bookings by phone, the same discipline applies. Our guide to taking a restaurant reservation over the phone and our piece on answering restaurant calls during service cover what to do when the phone rings while the room is full.
Step 2: Write down the answers to your common questions
Most enquiries fall into a handful of groups. Write a short, approved answer for each, in your own voice. This is the single most useful hour you will spend.
Availability and reservations

Every booking needs the same seven details: date, time, party size, name, phone number, any special occasion and any special requests. The ESL Room’s reservation training page lists these, along with the habit of repeating the details back to the guest to confirm them. It is a good habit in writing too.
A reply template:
“Thank you for getting in touch. We have a table for 4 on Saturday 14th at 7:30pm. Shall I book it under your name? Could I have a mobile number in case we need to reach you?”
When you are full, never stop at “no”. Offer two alternatives: a nearby time, or the next free day.
“We are fully booked at 8pm on Saturday, but we have 6:15pm or 9:00pm. Would either suit you?”
Opening hours, kitchen close and menus
State the details with numbers: when the kitchen takes its last order, when the bar closes, which days you are shut, and whether the lunch menu runs on weekends. Keep a current menu link ready, and note which dishes are seasonal so nobody promises a dish you no longer serve.
Special occasions
Ask what the occasion is, and what you can and cannot do. Can you bring a cake the guest provides? Is there a cake-handling charge? Can you add a card or a candle? Write the policy once, so every reply says the same thing.
Groups and large bookings
Decide the number at which a booking becomes a group. For many restaurants that is six to eight guests. Then write the group rules: deposit, pre-order or set menu, final numbers deadline, payment arrangements and the time limit on the table. Our piece on restaurant booking rules to write down walks through each of these.
Allergies and dietary needs
Treat these as a handover, not a template. Food businesses in the UK must be able to give allergen information for the 14 listed allergens, including celery, gluten-containing cereals, milk, eggs, peanuts, sesame and sulphites. A guest who writes ahead about an allergy needs a reply from someone who can check with the kitchen, and the reply should say exactly what was checked. A template can acknowledge the message and promise a personal answer. It should not answer the allergy question itself.
Policies
Children, dogs, dress code, deposits, cancellation windows and lateness. Keep these in one document, with the date it was last updated. If you change a policy, change the document first, then the replies. This is not legal advice: if you charge deposits or cancellation fees, check your wording against current consumer law or ask a qualified adviser.
Step 3: Decide what is automatic and what goes to a person
The line is simple to draw once you have written your answers. Use two lists.
Answer straight away, without a person:
- Opening hours, address, parking, menu links
- Availability for standard party sizes, when your booking system can check it
- Confirmation and reminder messages
- Standard policy questions with a fixed answer
Send to a person:
- Allergies and medical dietary needs
- Complaints, and anything emotional
- Large or unusual bookings, private hire and events
- Requests that break your rules (a table for 12 on a night you cap at 8)
- Anything you have not written an answer for
This matches what hospitality operators say about technology generally. In Bar & Restaurant’s July 2025 trade article on reservation systems, technology is presented as an aid that cuts repetitive work, while warm personal engagement stays important. Centralising booking and using automated SMS confirmations and waitlist updates can reduce manual follow-up and free staff to focus on hospitality. The same article recommends clear reservation policies, confirmations and reminders, staff trained on the system, and easy cancellations or changes.
Write the handover rule on one page and pin it up: “If it involves health, money, a complaint or more than eight people, it goes to the manager.”
Step 4: Reply fast, and say what happens next
Speed matters most on the first reply. Even if you cannot solve the request straight away, acknowledge it. The 2023 test above found that fewer than 5% of venues sent an automated acknowledgement, so a simple one stands out.
A good first reply does three things:
- Uses the guest’s name.
- Answers the question asked, not a nearby one.
- Says what happens next, and when.
For a handover: “Thank you, Priya. I have passed your allergy note to our head chef and the duty manager. You will hear back from one of us today by 5pm.” Then make sure that happens. A promise in a message is a promise to the guest.
Be careful with tone. Warm, calm and clear beats clever. Greet with the venue name, use the guest’s name, listen to the whole question, and confirm details by repeating them back. Restaurantsforms.com’s guest interaction scripts give examples of this tone for phone calls, and the same points carry over to email and DMs.
Step 5: Keep a record that carries the conversation
Enquiries often come back. A guest who asked about a birthday in March may book again in June. If the first conversation is buried in someone’s personal inbox, the next one starts from zero.
At a minimum, record against each guest:
- Name and contact details
- Allergies or dietary needs they have told you about
- Occasions and preferences (a quiet table, a high chair)
- Anything you promised
Keep this to what is needed to serve the guest. If you store personal data, check your data protection obligations under UK GDPR with the right adviser; this guide does not cover them.
Our reservation management guide goes deeper on keeping bookings and guest notes together.
Step 6: Cut no-shows and confusion with confirmations
A confirmation is also an enquiry-management tool. It answers the “is my booking definitely in?” question before the guest asks it, and it gives them an easy way to change or cancel. Include the date, time, party size, any deposit, your cancellation window and how to change the booking.
We have ready-made wording in 12 restaurant booking confirmation templates and a guide to reducing no-shows with simple booking confirmations.
Step 7: Measure it
You do not need a dashboard. Once a month, look at four numbers:
| What to track | How to find it | What it tells you |
|---|---|---|
| Time to first reply | Sample 20 messages across channels | Whether guests wait too long |
| Unanswered messages | Count messages with no reply after 48 hours | Where things are falling through |
| Handover rate | Share of enquiries sent to a manager | Whether your rules are too tight or too loose |
| Bookings won | Enquiries that became confirmed bookings | Whether fast answers are paying off |
Set a target you can keep, such as every message acknowledged within an hour during opening times. Review the questions that come up most often and add them to your written answers. Our piece on why restaurants lose bookings between 5pm and 10pm shows where the gaps usually are during service.
Where an AI host fits
Once you have the rules written, the repetitive part is a job a machine can do. That is where an AI host helps. Nomi answers calls, emails and social media messages in multiple languages, using your own policies and booking rules. It works with your booking system to manage reservations and handles guest communication around the clock. When a request is an allergy, a complaint or a large booking, Nomi flags it for your team to deal with. It can also recognise returning guests within a venue, so the conversation does not start from zero, and your team stays in control of how it responds and which actions it can take.
The quality of the setup depends on your written answers, which is why Steps 2 and 3 come first. For a wider view of what to hand over and what to keep human, see our guide to what to automate in a restaurant.

Other AI tools for restaurant phones and enquiries exist, including Loman, Hostie, Certus and VoicePlug. When you compare any of them, judge them against the lists you wrote in Step 3: what they can answer from your information, how they pass requests to staff, and which booking systems they connect to.
Perspective
Restaurants rarely lose guests because the food let them down. They lose them because a question went unanswered while the team was busy serving other guests.
We built Nomi around that. Guest conversations, your business knowledge and your reservations belong in one place, so a team can answer consistently without stopping service. We think the right model keeps people in charge: Nomi answers from the information and rules you give it, and brings a request to your team when it needs a human decision or falls outside those rules.
Our longer-term aim is a guest relationship system: tracking requests and promises, coordinating group and event enquiries, and supporting follow-ups that help guests return. Those are areas we are developing, not features you should expect today. What you can use now is faster, more consistent replies and less repetitive typing for your team.
Nomi Team
Try it on your own enquiries
If you want the repetitive questions handled while your team looks after the room, Nomi is built for that. Plans are published on the pricing page: Starter is €49 per month, Standard €149 per month and Pro €299 per month. Extra credits start from €45 one-off per 500 credits. If email is where most of your enquiries land, see how Nomi answers guest emails, or start from the Nomi homepage.

FAQ
How quickly should a restaurant reply to an enquiry?
As quickly as you can keep up, ideally within an hour during opening times. In the 2023 UK and Ireland test, only 22% of requests were answered within an hour. Even an immediate acknowledgement that says when the guest will hear back puts you ahead of most.
Which enquiries should never be fully automated?
Allergies and medical dietary needs, complaints, large bookings, private hire and any request outside your written rules. These need a person who can check with the kitchen or make a judgement call. Routine questions such as opening hours and standard availability are suitable for automatic answers.
How do I stop two people replying to the same message?
Use one shared view of all channels, and have whoever opens a message mark it as theirs. Name one owner per shift. If your channels are split across personal phones and several inboxes, bring them together first.
What should every booking enquiry capture?
Date, time, party size, name, phone number, any special occasion and any special requests. Repeat the details back to the guest before you confirm. For groups, add your deposit, pre-order and final-numbers rules.
Sources
- One out of three customers don’t get a reply to their query: QSR Media UK
- Insiders Share Secrets of Managing Reservation Systems and Policies: Bar & Restaurant
- Allergen guidance for food businesses: Food Standards Agency
- Phone and Reservations: Taking Calls and Booking Tables
- Restaurant Guest Interaction Scripts