An AI layer that reads your property, not the internet
A guest concierge that answers only from what your property published, a menu you photograph instead of typing, and guest documents that fill in the registration card themselves — grounded in your own data, inside the modules you already run.
SEE IT IN ACTION
Ask Vestibel proposes; the guest confirms. Nothing is booked, charged or requested without a tap.
OVERVIEW AND BENEFITS
Not a chatbot bolted on the side
Vestibel AI is not a separate product with its own login. It is a set of assistants wired into the surfaces where the work already happens — the in-room guest app, the menu editor, the guest profile, the translation catalogue — each one reading the property’s own data rather than a general model’s guesswork.
Grounded, or silent
The guest concierge answers only from the passages your property published. Where the context is silent it says so and hands off to reception rather than inventing a check-out time.
Proposes, never acts
The model’s output is inert data. A request, a booking or a charge is created only after the guest taps a confirmation chip, through the same audited action a staff member would use.
Hours of typing removed
Photograph a printed menu and get a structured catalogue. Scan a passport and get the registration fields. Generate a dish description from its own recipe.
WHY IT MATTERS
The cost of AI is the wrong answer, not the right one
An invented allergen claim or a made-up check-out time is a real liability for the property. Every assistant here is bounded — by the property’s own data, by an explicit confirmation step, or by a staff member reviewing the result before it is saved.
0writes without a human tap on the guest surface
1source of truth — your property’s own content
7assistants across guest, menu and front desk
PRODUCT DETAILS
What Vestibel AI actually does today
Every assistant below is shipped and switched on per plan — no waiting list, no beta programme.
Ask Vestibel — guest concierge
An unauthenticated in-room assistant launched from the room QR. It answers from your hotel info, WiFi, offers and things-to-do content, and knows the scanned room’s own stay.
Confirm-before-act
The concierge may propose a guest request, an experience booking or an offer added to the stay. A separate tap on a confirmation chip is what creates it — the answering path can never write.
Voice questions
Guests can ask by voice as well as by typing, on the same grounded answering path.
Menu scanning
Upload a photograph of a printed menu and get back a structured catalogue of categories, items, variants and prices to review before importing.
Dish descriptions
Generate an appetising description for a menu item from its own recipe ingredients, category and dietary flags — then edit it before it saves.
Nutrition estimates
Estimate per-serving macros for a dish from its recipe quantities and each ingredient’s own nutritional information.
Menu translation
Translate item names and descriptions into the locales your digital menu offers, so a guest reads the menu in their own language.
Interface translation
Fill in missing interface strings for a locale, leaving anything already translated untouched and keeping placeholders, brand names and phone numbers verbatim.
Identity document extraction
Scan an NIC, passport bio page, licence or residence card — front and back in one pass — and get structured guest fields for the registration card, for a human to check before saving.
Bounded by design, not by policy
The guest surface is reachable by anyone who photographs a room QR code, so the limits on it are structural rather than a promise. Asking a question and spending money are two different endpoints, and no amount of conversation can merge them.
Answer or hand off:where the retrieved context does not cover the question, the concierge says so and offers reception instead of guessing.
One room, one stay:the room bound from the scanned URL is the only trusted input, so a guest can never read or bill another room.
Throttled and capped:per-IP limits and a per-room daily cap bound what a photographed code can spend.
Yours to switch off:the AI surfaces are separate feature keys — take the guest app without the concierge if you prefer.
COMPARISON
Vestibel AI vs. a general chatbot
Capability
Vestibel AI
General chatbot
No AI
Answers only from your own content
Says "I don’t know" and hands off to reception
Cannot book or charge without a guest tap
Knows the scanned room’s live stay
Reads a printed menu into your catalogue
Fills the registration card from an ID scan
CUSTOMER STORIES
“
Vestibel gave us one guest record across rooms, restaurant and spa — check-in time is down 40% and we stopped losing restaurant charges entirely.
Dinesh Weerakoon · General Manager, The Banyan House
Placeholder story — no customer-story content exists yet.
A 30-minute walkthrough with your rooms, rates and outlets — no slides.
FAQ
FAQ
No. The answering path never writes a record. It can propose a guest request, an experience booking or an offer added to the stay, and the guest must tap a confirmation chip on a separate step before anything is created — through the same audited action a staff member would use.
It says so and offers to pass the question to reception. The concierge answers only from the passages your property published, so where that content is silent the correct output is a handoff, not a guess.
No. The assistants read your property’s own content to answer a single question or fill a single field; nothing is contributed to model training.
No. Both return a structured draft for a staff member to review, correct and save. Nothing is written to your catalogue or your guest record until someone accepts it.
Yes. The guest concierge is its own feature key, so you can run the in-room guest app — services, hotel info, offers — with the concierge switched off entirely.
Menu content and interface strings translate into whichever locales you enable for your property, and the guest concierge answers in the tone you configure.
