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.
"7:30" in the evening means 19:30. A chatbot that answers about the morning here loses the booking โ ours understands the moment of the day.
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 a stale answer becomes a complaint at the till. Better a clean handoff than a wrong number.
The restaurateur declares lunch and dinner windows once; the chatbot and the booking form both respect them. Nobody books at a time when the room is dark.
Time-slot discounts come from the same panel that runs the booking widget. The chatbot sells your empty hours, not someone else's ads.
The restaurateur ticks up to five pages of their own site (menu, directions, parking) and the chatbot answers with what is written there. Nothing is uploaded anywhere.
The handoff is the whole point: the chatbot never books on its own. It opens the real booking form with day and party size pre-filled, and the guest confirms. The booking stays direct and commission-free.
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 party size already filled in, and the guest confirms. The reservation follows the same rules, capacity and no-show protection as every other booking.