A concierge on duty at 2am that will not make things up
Guests scan the code in their room and ask. Ask Vestibel answers from your own property information, by text or by voice — and can propose a request or an add-to-stay for the guest to confirm.
SEE IT IN ACTION
When the retrieved context is silent, the correct answer is “I don’t know” and a handoff to reception.
OVERVIEW AND BENEFITS
Grounded, or silent
The guest is unauthenticated and the model knows nothing about your property. Anything not in the retrieved passages would, by definition, be invented — so the agent answers from context or declines and offers reception.
Answers only from your own information
Retrieval runs per question over the property information you maintain, and the answer is built from what it returns.
It cannot spend a guest’s money
Asking and acting are two separate requests. The answering path cannot write a record at all.
Voice as well as text
A guest can speak the question; speech-to-text transcribes it before the concierge answers.
WHY IT MATTERS
An invented check-out time is a real liability
The failure mode of a property chatbot is not silence. It is telling a guest something plausible and false about your own hotel — an allergen, a policy, a price — with your name on it.
2steps to any action — ask, then confirm
0records written by the answering path
1QR code — no app, no account
PRODUCT DETAILS
What the concierge can actually do
A narrow surface, deliberately. It answers, it proposes, and it hands over — and every one of those is bounded.
Ask and answer
Property questions answered from retrieved context, with a reception handoff when there is none.
Voice questions
Speech-to-text so a guest can ask out loud instead of typing on a tablet.
Grounded retrieval
Your property information is indexed for retrieval and re-indexed when you change it.
Propose an action
A request or an add-to-stay is offered as a confirmation chip, never created outright.
Conversation flagging
Staff can flag a conversation for review, so a poor answer is surfaced rather than lost.
Answering a question and spending money are two different endpoints, on purpose. There is no auto-confirm path and no way for an answer to become a charge on its own.
Ask, then tap:a proposal becomes real only when the guest taps to confirm, and a second tap cannot create a duplicate.
Nothing in the answer is trusted:the room, the price and the entitlement are re-resolved server-side before anything is written.
It delegates, never reimplements:a confirmed action runs through the same audited booking and billing code the front desk uses.
COMPARISON
Ask Vestibel vs. a bolted-on chatbot
Capability
Ask Vestibel
Generic chatbot
Reception only
Answers from your own property information
Declines when it has no grounding
Available at 2am
Can raise a request the guest confirms
Actions run through the audited billing path
Voice as well as text
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 endpoint cannot write a domain record. A proposal becomes a request or a charge only through a separate confirmation request the guest triggers by tapping.
It answers only from retrieved passages. When retrieval returns nothing relevant enough it reports that it could not answer, and the surface turns that into an offer to reach reception.
No. It lives behind the in-room QR code, which resolves the room, the stay and the folio from the code itself. Nothing to install, nothing to log into.
It is part of the hotel-side Guest App and entitled per plan, so what you see depends on your plan and your operation mode.
