Restaurant owners worry about chat assistants for good reasons. They picture a guest with a severe nut allergy getting a casual answer, or a furious complaint met with a cheerful menu link. Those worries are fair. They are also exactly why handover matters.
Here are the common myths about restaurant assistants and handover, and what actually happens when it is set up well.
Myth 1: the assistant tries to answer everything
A well set up assistant answers what your website covers, such as opening hours, menus, booking policies and parking, and hands over what it does not. It should not guess. When a question falls outside the published information, or involves risk, it should say so and pass it to staff.
Myth 2: allergy questions can be automated
General information, such as "our menu marks common allergens", can be shared. But a guest asking whether a dish is safe for a serious allergy needs a person who can check with the kitchen. The assistant should acknowledge the question, capture it with the booking details and make sure the team follows up before the visit.
Myth 3: complaints should be deflected
Some businesses use chat to push complaints away. That makes things worse. A complaint should reach a manager quickly, with the guest's details and what happened. The assistant's job is to listen, apologise and get the right person involved.
Myth 4: big bookings are just bigger small bookings
Large groups, private hire and catering orders involve menus, deposits, timings and special arrangements. They are valuable and complex. The assistant can answer the basic questions and capture the enquiry, but the conversation should move to a person. Catering enquiries in particular are covered in catering and takeaway enquiries from your website.
Myth 5: handover means the guest has to start again
A good handover passes on everything: the question, the booking details, the guest's name and contact information. The guest should not have to repeat themselves. How this works in general is explained in how AI employees hand over to humans.
Myth 6: once it is set up, it runs itself
Handover only works if someone picks up the tickets. Decide who owns them, how quickly they should be answered and how staff will be alerted. A ticket that waits until Monday defeats the purpose.
Which conversations need a person
A simple list for restaurants:
- Serious allergy or dietary questions
- Complaints and problems with a previous visit
- Large group, event and private dining enquiries
- Catering orders
- Unusual requests the website does not cover
- Anything involving refunds or charges
Voucher questions are usually routine, though disputes over expired vouchers may need a person, as covered in voucher and gift card questions from restaurant guests.
How it works in practice
SpideyChat for restaurants answers routine questions from your own pages and creates a ticket for anything that needs staff, with the conversation attached. You can see it on the demo.
Guest: My son has a severe peanut allergy. Is the curry safe for him? Assistant: Thank you for letting us know. For a serious allergy, it's important that the kitchen team confirms directly. I've passed your question to the team with your details, and someone will be in touch before your visit.
Lessons from online shops
Ecommerce businesses face the same balance, as explored in ecommerce chat that knows when to hand over to you. The principle carries across: answer the routine instantly, and get people involved when it matters.
Getting started
List the questions your team would never want answered without them, and set up handover for those. Then check which plan suits your restaurant on the pricing page.