01
Answers what your pages already answer
Hours, menu tags, class timetables, parking, breakfast times and check-in windows — from your own pages, in the guest's language, at any hour.
AI chatbot for hospitality and leisure — hours, menus, booking enquiries.
Cafés, restaurants, hotels, gyms and tour operators take most of their enquiries at exactly the wrong moment — mid-service, mid-changeover, mid-class. The answer is usually already on the menu, the timetable or the room page; the guest simply did not find it, so they message instead. Adoomi is a chat window on your own website, trained only on the pages you approve, answering hours, menus, timetables, parking and check-in questions 24/7 in the guest's own language. Booking enquiries arrive with party size, date and dietary notes already captured. Allergen questions are the line it will not cross: it points to your published allergen information and leaves the confirmation with your kitchen, because a guest's safety is not something an assistant should guess at.
Trained on your pages onlyAnswers in the guest's languageBookings captured in full
Fig. 01.A · Hospitality and LeisureInstant
Replies mid-service
24/7
Every hour a guest is browsing
Grounded
Only your approved pages
All sub-verticals
Explore hospitality and leisure sub-verticals.
Each sub-vertical has its own page with sub-vertical-specific FAQs, chat examples and imagery.
Cafes
Cafés get asked the same things all day — opening hours, what is on the breakfast and lunch menu, dietary tags, takeaway, whether dogs are welcome, whether there is wifi — and Adoomi answers each from your own menu page while any allergen confirmation goes to the kitchen.
Explore
Gyms / wellness studios
Studios field class-timetable questions every Monday, plus trial passes, membership tiers and freeze rules, drop-ins, what to bring, parking and lockers — Adoomi answers those from your timetable and membership pages and never offers injury or training advice.
Explore
Hotels / guest houses
Guest houses lose direct bookings to the questions asked at midnight — parking and whether it is free, breakfast times, pet policy, family and interconnecting rooms, check-in and check-out windows, step-free access — so Adoomi answers each from your own pages and then captures the booking enquiry.
Explore
Restaurants
Restaurants take reservation messages mid-service alongside opening hours, last booking time, the dinner and wine menus, dietary options, high chairs and walk-in policy — Adoomi answers those from your menu page and captures party size, time and dietary flags, leaving allergen checks to the kitchen.
Explore
Tour operators
Tour operators answer the same pre-booking questions every season — the day-by-day itinerary, what is included, how fit you need to be, group size and age range, single supplements and departure dates — and Adoomi answers those from your tour pages while refunds and ATOL or ABTA specifics go to a person.
Explore
Fig. 02.A · pain quotesThe everyday problem
Peak service is also peak phone — no one free to answer
The brunch rush and the check-in surge fall in the same hours the phone rings hardest, so calls go to voicemail while the team is on the floor. Meanwhile the same handful of questions repeat all day on Instagram and WhatsApp: what time do you open, is there parking, is Tuesday's class beginner-friendly, do you have a vegan option. By the time someone reaches the late-evening booking message, the table has been booked somewhere that replied first.
Web07:42
“What time do you open on a Sunday, and is the kitchen on all day?”
WhatsApp21:15
“Any tables Saturday? One of us is gluten-free.”
IG DMSun
“Do you have parking, and is breakfast included in the room rate?”
What you get
Three jobs it does on a busy service.
02
Takes the booking enquiry properly
Covers, date, time, dietary notes, occasion, room type or departure — captured in one pass so your team confirms in a single reply.
03
Stops at the allergen line
Points to your published allergen information and leaves confirmation with the kitchen. It never gives an assurance of its own.
Question coverage
The questions guests ask before they book.
These arrive by web chat, WhatsApp and Instagram DM across cafés, restaurants, hotels, studios and tours — every one answered from pages you have already published and approved.
Opening and kitchen hours, and the last booking of the nightMenu, dietary tags, dog policy and wifi — with allergen confirmation left to the kitchenClass timetables, trial passes, what to bring, parking and lockersParking, breakfast, family rooms and check-in windows for direct bookersTour itineraries, what is included, fitness level and departure dates
a
Adoomi
ChatVoice
Is Tuesday morning yoga OK for a complete beginner, and do I need to bring a mat?
Our timetable page marks which classes are beginner-friendly, and Tuesday morning yoga is one of them. The what-to-bring list says mats are provided, so a towel and water are all you need. If you'd like the intro pass, I can take your name and preferred class and the desk will set it up.
And does the café do a gluten-free option? My son has coeliac disease.
Our menu marks which dishes are gluten-free and I can tell you which those are. What I won't do is confirm a dish is safe for coeliac disease — that depends on how it is prepared on the day, so I'm passing this to the kitchen team now, with your question exactly as you asked it. Can I take a contact for them?
Class timetableAllergensParking
Type a question…● Voice
Buyer intent
A booking enquiry that arrives complete, not as 'have you got space?'
A guest who types 'anything Saturday?' gets asked the things your host stand would ask anyway — how many covers, what time, any dietary notes, any occasion — and the enquiry lands with all of it attached, in the guest's own words. Studios get the class and the trial pass the enquirer is after; hotels get dates, room type and access needs; tour operators get the departure and the group size. Your team replies once to confirm, instead of trading four messages to work out what was being asked.
Vague enquiries, no context.
Your team chases the basics before they can reply.
a
Adoomi
Enquiry typeTable booking
Covers and timeSaturday evening
Dietary noteDairy-free
Contactcaptured@…
3 of 4 captured · 1 in progress
With AdoomiNew enquiry · readyEnq 9589
Enquiry typeTable booking
Covers and timeSaturday evening
Dietary noteDairy-free
Contactcaptured@…
One clean handoff.
Your team opens the enquiry and replies — no chasing.
STEP · 01
Pin the request
Table, class, room or tour
STEP · 02
Capture the details
Covers, date and time
STEP · 03
Note what matters
Dietary, access, occasion
STEP · 04
Route to the right person
Host stand, front desk or kitchen
Fig. 06.A · after-hoursOut-of-hours
The late-evening planner, the midnight arrival, the Sunday timetable check
Hospitality enquiries cluster exactly where staff cannot be: late evening, weekends, and the hour before a delayed train gets in. The assistant answers from your own pages at those hours — parking and breakfast times for a guest deciding whether to book direct, this week's timetable for someone eyeing a Monday class, the last booking of the night for a couple choosing between two restaurants. Late-arrival and key-collection questions are answered only from the instructions you have published, never improvised, and anything your pages do not settle is captured with contact details so the morning team opens a clean list rather than a backlog.
20:40
“Is the kitchen on all day Sunday?”
Answered from your hours page
21:15
“Table Saturday, one dairy-free”
Captured with covers and notes
22:30
“Is this dish safe for a nut allergy?”
Handed to the kitchen, no assurance given
08:00
“Morning list”
Booking enquiries ready to confirm
Time back
The repeat questions leave the floor; the guest-facing ones stay
Opening and kitchen hours, menu tags, dog and pet policy, wifi, what to bring to a class, what is included on a tour — the questions that repeat all week get answered from your own pages, at any hour. What still reaches your team is what genuinely needs judgement: the private-hire brief, the group booking above your stated capacity, the accessibility request, the allergen check only the kitchen can settle. The chef stays on the pass and the front desk stays with the guest in front of them.
Before Adoomi
- The phone goes to voicemail through the breakfast and lunch rush.
- The same hours-and-menu questions repeat all day in Instagram DMs.
- Allergen questions need the recipe checked, but the chef is on the pass.
- Weekend booking enquiries stack up unread until Monday.
With Adoomi
- Hours, menu tags, timetables and parking answered from your own pages in seconds.
- Reservation enquiries arrive with covers, time and dietary notes already attached.
- Allergen questions reach the kitchen in the guest's own words, never an assurance.
- The morning starts with a short list of enquiries that genuinely need a person.
Fig. 08.A · controlsTrust & safety
It answers from your pages — and it never gives an allergen assurance
Allergen questions are where an assistant has to be honest rather than helpful, and this is the boundary we treat as non-negotiable. Adoomi repeats the dietary tags your published menu carries and points the guest at that source, then says plainly that only your kitchen can confirm what is in a dish today — it never issues a definitive allergen assurance of its own, in line with Food Standards Agency allergen guidance. The same rule holds for licensing and age policy: unless you have configured an answer, it does not invent one. Group bookings above your stated capacity, accessibility requests and anything the pages do not settle go to a named person with the guest's question attached. You review every answer before a single guest sees it. The allergen rule itself is structural rather than behavioural — with no assurance available for it to give, the failure mode is a handover to your kitchen, not a wrong yes. The conversation itself is handled with the same care: EU-hosted, no tracking cookies in the chat window, and what a guest types exportable or deletable on request under GDPR. None of this makes your venue compliant with anything; it keeps the assistant inside the boundary you set.
01
Your pages, nothing else
Menu, timetable and room pages are the whole source. General knowledge is not a fallback.
02
The allergen line
Published tags are repeated; the confirmation goes to your kitchen, never an assurance from the assistant.
03
Licensing and age policy
Answered only where you configured an answer. Otherwise it routes to a named person.
04
You approve it first
Read and edit every answer before a guest sees it. Nothing changes behaviour without your sign-off.
How it works
How an AI chatbot for hospitality and leisure works.
01
Connect content
Connect your website so the assistant learns your menu, timetable, room and tour pages — and nothing else. Facts that never reached a page, like a full allergen matrix (which sharpens what it can repeat — confirmation of today's dish still goes to the kitchen) or a class-level guide, go in as a document upload.
02
Add the snippet
Set where enquiries land: the inbox that handles bookings, the WhatsApp number a guest can carry on with, and the named person who takes allergen, accessibility and large-group questions.
03
Test & go live
Read the answers it proposes, put your awkward questions to it, then add one line to your website. Connecting the site, reviewing and publishing runs to ~10 min.
FAQ
FAQs about AI chatbots for hospitality and leisure.
Allergen confirmation stays with your kitchen. The assistant repeats the dietary tags your published menu already carries and points the guest at that source, then says plainly that only your team can confirm what is in a dish today. It never gives an allergen assurance of its own.
Published facts only: opening and kitchen hours, menu and dietary tags, class timetables and trial passes, parking, breakfast times, pet policy, wifi, check-in windows, tour itineraries and what is included. Where a detail was never published, it hands the question over instead of filling the gap.
Booking enquiries are captured, not processed. The assistant collects covers, date and time, dietary notes, room type or departure and contact details, then passes the enquiry to whoever books today — your inbox, your WhatsApp, your diary. It holds no calendar and confirms nothing itself.
Out-of-hours questions get the same source-grounded answer, 24/7 and in the guest's own language. Late-arrival and key-collection queries are answered only from the instructions you have published, and anything those pages do not settle is captured with contact details for the morning team.
Licensing and age policy are answered only where you have configured the answer yourself. With nothing published, the assistant says it cannot confirm and routes the question to a named person, rather than guessing at a rule that varies by venue and by licence.
Multilingual replies are standard: a guest writing in French, Polish or Arabic gets your published information back in the same language, at any hour. The source never changes, so a translated answer states no fact your own approved pages do not already state.
Why this matters
Not a booking platform — a chat window on the site you already have
Most hospitality chatbots want to become your booking system, which means a migration, a second calendar and another place for staff to look. Adoomi does the opposite. It sits on your existing website as one line you add to a page, answers from the menu, timetable and room pages you already publish, and passes the completed booking enquiry to whoever handles bookings today — your inbox, your WhatsApp, your existing diary. Change the menu and the answer follows the next time it re-reads your pages — that happens on a schedule and whenever a source changes, so a daily specials board still needs its page updated before the chat window catches up.
Replies through service
Hours, menu tags, timetables, parking and check-in answered from your own pages while the floor is busy.
Covers the late-evening planner
Evening, weekend and late-arrival questions answered in the guest's own language, on web chat or WhatsApp.
Allergen checks go to the kitchen
The assistant repeats what your menu publishes and hands confirmation to a named person, rather than reassuring a guest itself.
Start free
Put your worst allergen question to it before a guest does
Point it at your menu, your timetable and your policies, then ask the questions you would least like it to get wrong — the nut question, the party too big for your largest table, the dog in the bar, the arrival after the last train. Read what it proposes to say and change anything you would not say yourself. The Free plan is £0 a month with 50 message credits — enough to test it on a weekend's worth of real questions — and paid plans step in at £8 for 200 credits when weekends outgrow it. The pricing page has the full comparison, and the guardrails and handoff page under Product shows the decline-and-capture flow end to end.
Answers from your menuAllergen checks to the kitchenYou approve every answer
Fig. 12.A · Hospitality and Leisure