Playbook, restaurant
The handover a restaurant cannot do by email
Most handovers in this file end the same way: take a name, an email and a message, send it to whoever handles it, and reply within the day. In a restaurant one category breaks that pattern completely. A guest asking about an allergy is usually eating in a few hours, and a form that reaches an inbox is not a route to a person in time. The wording has to put the phone first and the form second.
Why this is not the general answer
The handling pattern for asking for a person holds across every trade. What follows is the part that does not.
- This trade has two speeds of handover in the same chat window, and using the wrong one is the failure: a Christmas party enquiry can wait until tomorrow, an allergy before tonight cannot.
- The restaurant's own procedure already answers the question of who takes an allergy call, and the handover should route to that person rather than to a general inbox.
- Timing is against the form here in a way it is not in other trades, because the enquiry often arrives after the office closes and before service starts, which is exactly when nobody is reading email.
- The rest of the handovers here are ordinary: a booking nobody can see, a complaint about a meal, a private hire enquiry, all of which are served perfectly well by a name, an email and a message.
How it arrives
- can i speak to someone about an allergy
- i need to talk to the chef
- can someone call me back about my booking
- i want to complain about last night
- who do i speak to about hiring the room
- is there a phone number for the restaurant
What has to be indexed for this to work
| Who takes which call, and when | The allergy route, the bookings route, the events route and the complaints route, with the hours each is answered. A single number for everything is fine as an answer, but you have to have decided that rather than left it unstated. |
|---|---|
| The address the enquiry form should reach | Somebody who reads it during opening hours rather than a general address checked on a Tuesday. Enquiries are stored as well as emailed, so nothing is lost if the email bounces, but nothing is chased either unless a person is expecting it. |
| The phrases that mean somebody wants a person | Speak to someone, is there a number, can you call me, I need to talk to the chef, and the trade specific ones such as who do I speak to about a party. Worth listing what your guests actually type so the recogniser is tuned to your room rather than to a generic set. |
The reply
You will get a faster answer by phone for anything to do with an allergy, and the number at the top of this page reaches the restaurant from midday. If you would rather not call, leave your name, email and a short message and a manager will pick it up, though that will be during service hours rather than straight away. For a party or private hire enquiry the form is the better route, since the events diary is not on the phone.
It sorts the request before it answers it. The allergy path leads with a number and states when that number is answered, so the guest is not left calling a locked building. The form is offered second with an honest note about the delay, and the event enquiry is pushed towards the form because that is genuinely where it gets handled better.
Where it stops
The trigger. An explicit request for a person, or any allergy question at all, which should be treated as a handover request even when it is phrased as an information question.
I can put you in touch with the team. For anything about an allergy please call the number at the top of the page, because that reaches somebody who can speak to the kitchen. For a booking, a party or a complaint, leave your name, email and a message here and it will go straight to a manager.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- That a manager will call back within a specific time, when nobody has committed to that.
- That the message has reached a person, when it has been emailed and stored and not yet read.
- That the guest should wait for a reply, when the question is about an allergy before a booking today.
- That there is no way to reach a person, when a phone number is published on the site.
Questions
- What happens to the enquiry after somebody fills the form in?
- It is emailed to the address you nominate and stored as well, so a delivery failure does not lose the enquiry. That matters more in this trade than most, because the person who filled it in is often deciding between two restaurants that evening.
- How does it know somebody wants a person rather than an answer?
- It recognises the direct requests, the ones that name a person or ask for a number. What you should add on top is a fallback that treats every allergy question as a handover regardless of how it is phrased, because those arrive worded as ordinary menu questions.
- Should the phone number be in the fallback wording itself?
- Yes, spelled out rather than described. A guest reading a refusal wants the next step in the same sentence, and a fallback that says please contact us is a refusal with no route out of it.
Keep reading
- Everything for a restaurantHours, last orders, deposits and dietary options are safe ground. Confirming a dish is free of an allergen never is.
- Handling asking for a person in generalThe design question at the centre of a support assistant. Offer early, offer once, collect what a reply needs, promise a time you can keep.
- The car park closes before the second sitting doesThe multi storey locks before the late sitting finishes, the bay outside is a loading bay, and the evening tariff starts on the hour.
- A table is a slot, not an eveningShifting a table from seven to eight is not small when the same table is booked again at nine, and a chat window cannot move it.
- The wait time is an estimate made by somebody standing in the roomHow the list actually works: a number left with the host, a wait that is a guess, and a table for two seated ahead of a six.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.