Table for six on Friday, and the gluten-free question.
Restaurant chatbot booking that takes the table at 19:40.
OpusDone takes the Friday table for six at 19:40 and writes it into your calendar, which is the exact moment nobody front of house can reach a keyboard. The gluten-free question arrives with it, and that one has limits. It answers allergen questions only as far as your approved notes go, then hands the rest to a person. Nothing about your kitchen gets invented.
- Answers through the whole service
- Allergen questions go to a person
- Bookings written into your calendar
Reviewed
Table for six, and the gluten question
Both of you are on the pass. The booking still gets taken.
- 12:55
Mid-service, six people
A request for Friday night arrives while there are nine covers waiting to go out.
- 12:56
Friday, two options
It offers at most two times from Friday itself and fills the rest from nearby days.
- 12:58
The gluten question
It repeats exactly what you wrote about gluten and hands anything beyond that to a person.
- 19:35
A late cancellation
It reads the booking back to the guest and asks them to confirm before removing it.
- 23:40
After the last table
The weekly digest shows what arrived after closing and how much was handled without you.
What can OpusDone handle while the pass is full?
It writes the time into your calendar and does not lose it
It offers at most six times, at most two from any one day, checked against your service hours and every day you have closed, and re-checked at the moment of writing so two parties cannot take one slot. Closing the restaurant for a holiday is one click, or a drag across a range, mirrored into Google as an all-day closed event.
Google Calendar or Cal.com. It books time, not table numbers — the floor plan stays yours.
The questions it takes off your desk
Five it will answer today, from knowledge you approved: “Do you have a table for six on Friday at nine?” · “Is there a gluten-free option on the menu?” · “Do you have highchairs?” · “Can we bring the dog to the terrace?” · “Is the set lunch available on Saturdays?”.
One script tag on the site, and Telegram in your pocket
The widget is a single script tag with no iframe, and Telegram is the other live channel — free to connect, and where you get the card with the last five messages and Take over. A guest who closed the tab before you got to them receives your reply by email.
Website widget and Telegram are the live channels today.
Why do table enquiries land in the worst twenty minutes of the day?
The rush and the enquiries share a clock
People decide where to eat while you are plating. The message sits until eleven, and the party of six has already booked the place two doors down that answered in a minute.
The dietary question is never simple
Gluten-free, nut allergy, a vegan in the group. It is a fair question and it deserves a careful answer from someone who knows the kitchen, not a cheerful guess from a machine.
Half the questions are not bookings at all
Highchairs, dogs on the terrace, the set lunch, whether you are open on the Monday of a public holiday. Small things, endlessly repeated, each one a person leaving the floor.
From your menu to a table for six
Done once, in the quiet hour after lunch. Nothing about the pass, the floor or the till changes.
- 01
It reads your site for menu, hours and address
The crawl finds your menu, FAQ, contact and hours pages by English and Spanish keywords, then reads the meta description, Open Graph tags and JSON-LD for the address, telephone and opening hours. One model pass turns that into structured services, FAQs, policies and four to ten draft knowledge entries. It writes only into empty fields, so anything you typed yourself survives untouched. - 02
You approve every line about the food
Only entries marked live ever reach the assistant; drafts, imports awaiting approval, archived and rejected entries are invisible to it. This is where you decide, in writing, exactly what may be said about dishes, allergens and set menus — and what must always come to a person. A quality gate discards navigation text and cookie boilerplate, anything under 80 or over 4,000 characters, and near-duplicates at 85% overlap. - 03
You set service hours and the days you close
Working hours, plus closed days set by clicking one day or dragging across the fortnight you shut in August. Minimum notice is 120 minutes by default, slot length 30 minutes, granularity 15, buffers zero and horizon 60 days, and all of it is editable. Closures are mirrored into Google as an all-day closure event carrying your restaurant’s name, and deleting that event does not reopen the day. - 04
You connect one calendar for the restaurant
Google Calendar over OAuth, or Cal.com with an API key. Every calendar you mark as busy is read and merged, so a private hire already in the diary removes the slot. It holds the booking in your calendar — the table plan stays yours — and its permissions are narrow: it can read and create events, and cannot delete a calendar. - 05
You test it on a Friday-night question
The sandbox runs your real instructions and your real tools and stops before it writes anything: no booking, no lead, no alert, no escalation. Ask for a table for six on Friday and add the gluten-free line, and watch exactly where it stops answering and asks for a person. It is free and never gated, so you can rewrite an entry and try again until it reads the way you would say it. - 06
One line on your site, and the messages stop piling up
The widget is a single script tag on the site you already have, and Telegram is the second live channel; both enter the same function, so the answer does not depend on the door. Hours and closed days are checked before a slot is offered and again before it is written, availability is re-read at the moment of writing so two parties cannot take the same table, and it offers at most six options with no more than two from any one day. It replies in the language the guest wrote in, and the AI disclosure required by Article 50 of the EU AI Act is added once per conversation and cannot be prompted away.
What does it say to somebody with a serious allergy?
Only what you wrote and approved, and then it gets a person. It will not reason about a dish, will not read an ingredients list and gives no dietary or medical guidance of any kind. Sensitive is a locked-on escalation reason, and if a guest asks for a human, the runtime escalates whether or not the model decided to.
Numbers you can change
What will OpusDone never do in your dining room?
A restaurant lives on being believed. So the assistant only says things you have already said.
It will not improvise a menu
No inventing dishes, prices, wines or a Christmas menu that has not been approved. If it is not live in your knowledge, it says so and passes the guest to you.
It will not take an order or a payment
It cannot check stock, track an order, apply a discount or send a document. It books time and it answers questions. Nothing else is on the menu.
It will not overbook Friday
Availability is read live at the instant of writing, so times floated earlier in the chat are never a held reservation. If a slot goes in between, the guest gets alternatives instead of an error.
It will not pretend to be the maître d’
The AI disclosure required by EU AI Act Article 50 is added after the model writes, once per conversation, in the guest’s language, and it cannot be prompted away.
Restaurant booking chatbot questions, answered
Does this replace our table management?
Tourists write in five languages. Does that matter?
Someone cancels at nine on a Friday.
A table for twelve with a deposit is a conversation I want myself.
A group of fourteen wants the whole terrace.
What happens to a booking made just before we open?
Allergies are a legal matter, not a chat matter.
More for restaurants and bars
Table for six booked while service ran
One calendar for the room, on Google Calendar or Cal.com. Availability is re-read at the moment of writing, so two parties can never be given the same table, and closing a day takes one click.
Solicitar acceso