Quandoo is closing: from 30 September it stops taking bookings. See how to move to mee-table →

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.

A couple on their sofa in the evening, choosing a restaurant together on their phones
Most of these questions arrive like this: from the sofa, the night before. The chatbot answers while your phone stays quiet.
The real chat: the guest asks, the assistant answers with the free times, and one tap jumps to step three, Saturday, four people, with the evening discounts in view.
Are you open on Saturday night? Any table for four?
Yes, on Saturday evening we still have tables for four at 8pm and 9.30pm. Shall I take you to the booking form?

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.

Tomorrow evening at half seven, for two.
Tomorrow at 7.30pm we have room for two. I can open the booking form with the day and the number of guests already filled in.

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.

Do you have gluten-free dishes? I have a celiac guest.
For allergies and intolerances, please ask the restaurant yourself, when you arrive or by phone: they will give you the information in writing, dish by dish.

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.

How much is the tasting menu?
For prices, the restaurant will give you exact, up-to-date information, the menu on their site or a quick call is the safest source.

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.

Can we come at 4 in the afternoon?
We serve lunch until 2.30pm and dinner from 7pm. At 4 in the afternoon the kitchen is shut. Would you like a table for lunch or for dinner?

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.

Any discount if we book early?
Yes: on Tuesday evening the discount is on the 7pm sitting, marked on the list of times here on the page. I can take you straight to the booking form for that sitting.

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.

Where can we park?
There is a public car park two streets away, and free parking on the street after 8pm. The map is on our "How to find us" page.

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.

OK, book me in.
→ [Book, Saturday, 4 guests]

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.

Start free, 14 daysHow the assistant works, step by step

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.