A party is the group on the bill — one family across three rooms, a tour group, a company account. Every folio hangs off one, and every outlet bills to it.
SEE IT IN ACTION
Guest history, preferences, allergens and consent live on the profile, not scattered across bookings.
OVERVIEW AND BENEFITS
One record per guest, one bill per party
The guest profile carries who they are and what they need. The party carries who is paying. Keeping them separate is what lets three rooms settle as one bill without merging three people into one record.
History that follows the guest
Past stays, spend, preferences and notes attach to the person, not to the booking.
Allergens recorded as safety data
Coded allergens with severity sit alongside free-text notes, and the register warns before an order is fired.
Groups that bill as one
Attach several rooms and several guests to one party and settle the whole thing together.
WHY IT MATTERS
A guest you cannot recognise is a guest you cannot serve
Preferences, allergies and history only help if they surface at the moment someone is taking the order — not buried in a profile nobody opens.
1record per guest across every visit
3allergen severities, defaulting to severe
0duplicate profiles from a repeat booking
Illustrative figures — replace with measured results before publishing.
PRODUCT DETAILS
Everything you know about a guest, in one place
Identity, preferences, safety data, notes and consent — with the controls a property actually needs around them.
Guest profiles
Contact details, stay history, total spend, VIP flag and last stay date.
Parties
The billing group — rooms, tables and guests attached, with a readable reference.
Allergens
Coded allergens with severity plus free-text declarations, surfaced as a pre-order warning.
Typed notes
Attributed, categorised notes with management-only visibility for incidents.
Blacklist
Refuse service with a required reason, and a separately permissioned override that is always logged.
Consent & erasure
A consent ledger per purpose, subject-access export and a documented erasure path.
The allergen check warns, it never blocks
The person eating is frequently not the person on the folio. A guest with a peanut allergy ordering satay for the table is the ordinary case, not an error.
Warn at the register:the check runs before the order is fired, where somebody can actually act on it.
Never under-state risk:an ungraded declaration defaults to severe, because it means nobody asked.
Show the prose too:coded allergens and the guest’s own wording are rendered together, always.
COMPARISON
Vestibel vs. a guest list
Capability
Vestibel
Guest list
Legacy PMS
One record per guest across visits
Group billing without merging identities
Coded allergens with severity
Attributed notes with restricted visibility
Consent ledger and subject-access export
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
The people being billed in any context — a dine-in table, a room-service order, a multi-day stay, a walk-in spa visit. Every folio belongs to exactly one, and rooms and tables attach to the party rather than to the bill.
Yes. All three rooms attach to the same party, so every charge lands on one folio — and you can still split it any way at checkout.
It refuses at booking, at check-in and at seating. A holder of the separate override permission can proceed by stating a reason, and that override is logged with the actor and the grounds.
There is a documented erasure path that redacts personal data in place while keeping records a property is legally required to retain. Every erasure returns an explicit statement of what it could not remove.
