01
Answers the menu question the moment it is asked
Hours, the last booking of the night, dietary tags, corkage and walk-in policy — answered from your own pages while the host stand is on the floor.
AI for restaurants. Your menu answers mid-service.
AI for restaurants answers what a diner asks mid-service, from the pages you already publish — the last booking of the night, the wine list, which dishes carry a dietary tag. It captures the reservation enquiry with covers, the sitting and any dietary note attached, at any hour and in the guest's own language. Confirming a table stays with whoever holds the book, and an allergen question goes straight to your kitchen.
Answers from your menu pageCovers and dietary notes capturedYou read every answer first
Fig. 01.A · Restaurants24/7
Answers while service is on
Never
An allergen confirmed in chat
£0
Free plan, 50 message credits
Fig. 02.A · pain quotesThe everyday problem
Saturday's booking message arrives mid-service, when nobody is free to read it
The messages that decide a Saturday come in during Friday's service. A couple wants the last booking of the night; a table of eight wants to know whether you can seat them; somebody asks whether the risotto is gluten-free before choosing between you and the place two doors down. The host stand is on the floor, the chef is on the pass, and by the time anyone types a reply the guest has booked elsewhere. Nothing was wrong with the answer — it was on your menu page. It just arrived late.
Web19:20
“'Anything for six on Saturday, or are you full?'”
Voicemail20:05
“A booking left on the machine while both phones were out on the floor.”
WhatsApp23:40
“'Is the risotto gluten-free? Choosing between you and the place on the corner.'”
What you get
What it takes off the host stand.
02
Takes the reservation enquiry, then hands it on
Covers, date and time, the occasion and any dietary note, captured in one pass and passed to whoever holds the book. The assistant confirms no table itself.
03
Sends the allergy question to the pass, not to a guess
A guest asking whether a dish is safe gets your published tags, the page they came from, and their question forwarded to the kitchen — never a yes.
Question coverage
What a diner asks in the minutes before choosing you
Opening hours and the last booking of the night, the dinner and wine menus, which dishes carry a vegan or gluten-free tag, high chairs and the children's menu, walk-ins, private dining — each answered from the page you publish it on. Allergen confirmation, a party bigger than your largest table and a private-hire brief leave the chat window for the person you named.
Last booking of the nightDinner menu and wine listVegan and gluten-free tagsAllergens — kitchen confirmsChildren's menu and high chairsWalk-ins and waiting listPrivate dining enquiries
a
Adoomi
ChatVoice
My daughter has a nut allergy — can she eat the pad thai?
I won't answer that one myself. Our menu marks which dishes are prepared without nuts and I can show you that page, but whether tonight's pad thai is safe for an allergy is the kitchen's call — I'm sending your question through to them in your words. Where shall they reach you?
Fine. And do you take walk-ins on a Tuesday?
Our walk-in policy is on the reservations page and I can read it back to you. What I can't do is hold a table or tell you how busy tonight looks — the host stand has the book, so I'll pass your name and the time you want over and they'll come back to you.
AllergensWalk-insPrivate dining
Type a question…● Voice
Buyer intent
A reservation enquiry that reaches the host stand already qualified
'Anything Saturday?' is not a reservation. Adoomi asks what your host would ask anyway — how many covers, what time, whether it is a birthday or an anniversary, whether anyone has a dietary requirement — and the enquiry lands with all of it, in the guest's own words. Private dining and large parties are captured against the fields your events lead needs instead. What a guest types is EU-hosted, exportable or deletable on request under GDPR, and no conversation content is written into logs.
Vague enquiries, no context.
Your team chases the basics before they can reply.
a
Adoomi
EnquiryTable booking
Covers and timeAs the guest stated
Dietary noteNut allergy, flagged to the kitchen
Contactcaptured@…
3 of 4 captured · 1 in progress
With AdoomiNew enquiry · readyEnq · table booking
EnquiryTable booking
Covers and timeAs the guest stated
Dietary noteNut allergy, flagged to the kitchen
Contactcaptured@…
One clean handoff.
Your team opens the enquiry and replies — no chasing.
STEP · 01
Name the enquiry
Table, private dining, a menu question or a complaint
STEP · 02
Take the covers and the time
How many, which night, how late they can eat
STEP · 03
Note what the kitchen needs
Dietary requirements, the occasion, high chairs
STEP · 04
Hand it to the right person
Host stand, events lead — or the pass, for an allergen check
Fig. 06.A · after-hoursOut-of-hours
Nobody books a Saturday table during office hours
Reservation messages cluster in the hours after your kitchen closes and before it opens: someone deciding between two restaurants on a Wednesday night, a parent checking the children's menu before Sunday lunch, a group hunting a late table when the theatre comes out. Adoomi answers those from your published hours and menu pages 24/7, in the language the guest writes in, and captures the rest — so the morning starts with a list your reservations team can work through rather than an unread inbox.
19:40
“'What time is the last booking on a Saturday?'”
Answered from your hours page
22:15
“'Table for six Friday, one gluten-free'”
Captured with covers and the note
23:50
“'Is the satay safe with a nut allergy?'”
Forwarded to the pass, unanswered
09:00
“The reservations list”
Enquiries ready to confirm or call back
Time back
Your chef stops being the allergen helpdesk
Dietary tags, corkage, whether the set menu runs on a Saturday, whether you take walk-ins, where to park for a pre-theatre table — every one of those is on a page you already publish, and every one of them currently interrupts somebody mid-shift. Adoomi answers them from those pages. What still reaches a person is what needs one: the allergen check only your kitchen can settle, the party larger than your biggest table, the private-hire brief, the complaint about last night.
Before Adoomi
- The Saturday booking message arrives at the exact moment the host stand is seating a table of eight.
- The chef gets pulled off the pass to answer whether the laksa has peanuts in it.
- A private-hire enquiry sits in the same inbox as a two-cover Tuesday and is read in the same order.
- 'Anything Saturday?' takes four messages before anyone knows how many people are coming.
With Adoomi
- Hours, dietary tags, corkage and walk-in policy answered from your own pages while service runs.
- The pass gets the allergy question as the guest typed it, and nothing has been promised.
- Every booking that lands carries the covers, the sitting, the occasion and the dietary note.
- Private hire and complaints go to the person you named, ahead of the routine queue.
Fig. 08.A · controlsTrust & safety
The kitchen confirms allergens — the chat window never does
Your menu tags are the whole of what it may say about a dish. It reads them back, shows the page they came from, and hands the real question to the pass — only the kitchen knows what went onto tonight's plate, so tonight's plate is the kitchen's answer to give. No table is confirmed either: reservation enquiries are captured and go to whoever takes bookings today. Licensing and age policy get an answer only where you wrote one. None of this makes your restaurant compliant with anything.
01
Your menu and hours pages, nothing else
The assistant draws on the pages you approved. Where they do not settle a question, it says so instead of reaching for what a restaurant usually does.
02
No dish is ever declared safe
It can repeat a published tag and forward a question. Declaring a dish safe for an allergy is not something it is able to do, whichever way a guest asks.
03
No table held, no price quoted
It holds no diary and quotes nothing for private hire. Reservation and event enquiries are captured and passed to the person who prices and confirms them.
04
You approve it before service
Read every answer it proposes, edit the ones that do not sound like your room, and block anything you would rather it never said. Nothing changes without you.
How it works
How AI for restaurants works on your own site.
01
Connect content
Connect the pages a diner reads: menu, wine list, opening hours, private dining, the children's and set menus. Anything not published there is something the assistant declines rather than attempts.
02
Add the snippet
Name where enquiries land — the inbox that holds the book, a WhatsApp number a guest can carry on with, and the head chef who takes every allergen question.
03
Test & go live
Read every proposed answer, throw the awkward ones at it yourself, then add one line to your website. Connect, review and publish comes to ~10 min.
FAQ
FAQs about AI for restaurants.
The kitchen answers that one, not the chat window. The assistant will say which dishes your menu tags as nut-free and show the page that says so, then send the question through to the pass in the guest's exact wording. No dish is ever declared safe in chat.
Bookings are captured, never confirmed. The assistant holds no diary and cannot see your table plan, so it takes covers, date and time, the occasion and any dietary note, then passes the enquiry to whoever runs the book — your inbox, your WhatsApp, or the book on the host stand.
Your own pages are the source. The site is re-read on a schedule and whenever a page changes, so an updated wine list or set menu follows within that cycle. Anything that exists only on the kitchen printout, tonight's specials included, is not something it will state.
Private hire leaves the chat window. The assistant captures the date, the numbers, the occasion and a contact, quotes no price and holds no room, then routes the enquiry to your events lead by email alert or a WhatsApp handoff carrying the guest's original message.
Complaints get no reply from the assistant. A guest raising a problem with a meal or a bill is routed straight to your manager, with what they wrote carried across, so nobody has to retell it. No refund, discount or apology is offered on your behalf.
Pricing starts at £0 a month: the Free plan carries 50 message credits, and paid tiers step up to 200 at £8, 500 at £20 and 4,000 at £75. Credits are spent by the assistant's answers, never by your team's replies. Connecting, reading and adding one line runs to ~10 min.
Why this matters
A narrow assistant is the point, not a limitation
AI for restaurants is worth more for being narrow. The table plan and the diary stay on the host stand, so Friday's real position comes from the person holding them. Adoomi answers from the menu, hours and policy pages you approved, hands the allergen question to your kitchen with the guest's own wording attached, and passes the reservation enquiry to whoever confirms tables today. No outcome is claimed here: what is described is how the assistant is built to behave.
Answered from your menu and hours pages
The last booking of the night, dietary tags, corkage and walk-in policy — answered while the floor is full and after the kitchen closes.
A dish confirmed safe for an allergy
The assistant repeats published tags and forwards the question to your kitchen. No wording from a guest unlocks an assurance it does not have.
Free plan, 50 message credits, no card
Enough to put a weekend of real reservation and menu questions through it before you decide. Setup runs to ~10 min.
From the guides library
Guides for Restaurants.
Start free
Point it at your menu and try to catch it out
Connect the pages a diner reads before choosing — menu, wine list, opening hours, private dining, the set menu — then read the answers it proposes and change any you would not give across the pass. Reservation enquiries go to the inbox or WhatsApp number you name; allergen checks go to your kitchen. Starting costs nothing: £0 a month, 50 message credits, no card. The pricing page lays the plans side by side, and the guardrails and handoff page walks a decline through end to end.
No table confirmed in chatAllergen checks go to the kitchenFree plan, £0, no card
Fig. 12.A · RestaurantsExplore
More Hospitality and Leisure chatbots
- AI chatbot for CafesSee how Adoomi handles enquiries for cafes.
- AI chatbot for Gyms / wellness studiosSee how Adoomi handles enquiries for gyms / wellness studios.
- AI chatbot for Hotels / guest housesSee how Adoomi handles enquiries for hotels / guest houses.