Restaurant chatbot examples: real answers, real bookings
These are real conversations with the AI assistant built into the mee-table WordPress plugin, answering with the restaurant's own hours, tables and discounts. Including the two questions a restaurant chatbot must never answer.

The chatbot reads the real availability grid for the next 7 days. It never invents a time: it offers only slots that are actually free.
Said in the evening, "half seven" means 7.30 at night. A chatbot that answers about the morning here has lost the booking; ours knows which half of the day you meant.
This is the answer a restaurant chatbot MUST give. In the EU, allergen information legally has to come from the restaurant, in writing. A chatbot that improvises here is a liability, see the Air Canada case, where a company paid for what its bot invented.
Same rule: prices change, and an out-of-date answer turns into an argument at the till. Better to hand the question over than to give a wrong number.
You set your lunch and dinner hours once, and both the chatbot and the booking form keep to them. Nobody books a table for a time when the lights are off.
The discounts by time come from the same panel that runs the booking widget. The chatbot sells your empty hours, not somebody else's advertising.
You tick up to five pages of your own site (the menu, how to find you, the parking) and the chatbot answers from what is written there. Nothing is uploaded anywhere.
Handing over is the whole point: the chatbot never books on its own. It opens the real booking form with the day and the number of guests already filled in, and the guest confirms. The booking stays direct, with no commission on it.
Try these examples live
This chatbot is not a mock-up: it ships inside the mee-table WordPress booking plugin, the first with a built-in AI assistant. It runs on the restaurant's own free Groq key, guests' data never leaves the site, and every conversation ends where it should: on your booking form.
Frequently asked questions
What should a restaurant chatbot answer?
Opening hours, free tables in the coming days, time-slot discounts, events, and practical questions like parking or directions. Everything it answers should come from the restaurant's real data, not from a generic model.
What must a restaurant chatbot never answer?
Prices and allergens. Prices change and a stale answer creates complaints; allergen information must legally come from the restaurant in writing (EU Regulation 1169/2011). A good chatbot hands both questions to the restaurant.
Does the mee-table chatbot need its own AI subscription?
No. It runs on a free Groq API key that the restaurant owner creates in two minutes. While the key field is empty, nothing is sent anywhere and the chat does not appear.
Can the chatbot book a table by itself?
Deliberately not. It takes the guest to the booking form with the day and the number of guests already filled in, and the guest confirms. That booking then follows the same rules, the same capacity and the same no-show protection as any other.