Your property, on the app your guests already have open
Booking confirmations, folio receipts, guest requests, daily briefings and breakfast reminders — any of them can leave Vestibel as a WhatsApp message, from your own number.
SEE IT IN ACTION
One catalogue of 168 notification events. You choose which reach WhatsApp, and where each one goes.
OVERVIEW AND BENEFITS
WhatsApp is a channel, not a second inbox
Vestibel wires WhatsApp in beside email and SMS as a delivery channel for the notification catalogue. The same events, the same editable templates, the same per-event settings — WhatsApp only decides which of your numbers sends and which chat receives.
Your own number
Pair the number guests already associate with your property, through a QR code or a pairing code. Pair more than one and choose which sends what.
Routed per event
Send the guest their confirmation and the overdue-housekeeping alert to an operations group — from the same system, in the same minute.
One set of words
Message copy comes from the shared template catalogue, so the WhatsApp and email versions of an event cannot drift apart.
WHY IT MATTERS
A message that arrives by email arrives too late
The channel a guest will actually answer is the one already on their phone. Meeting them there turns a complaint at checkout into a request somebody handled that afternoon.
168events in the notification catalogue
3destination types per event
1template catalogue across every channel
PRODUCT DETAILS
Where WhatsApp turns up across Vestibel
It is not one feature in one module. Any event in the catalogue can be routed to WhatsApp, and these are the flows properties switch on first.
A 30-minute walkthrough with your rooms, rates and outlets — no slides.
FAQ
FAQ
Any event in the notification catalogue that supports the channel — the catalogue currently holds 168 events across reservations, billing, housekeeping, ordering, services and staff operations. You enable them one at a time.
You pair one of your own numbers against the Vestibel gateway through a guided wizard, using a QR code or a pairing code. Onboarding is poll-based, so there is nothing to host and no webhook to configure.
Yes. Each event routes independently to direct recipient numbers, a group chat, the customer, or any combination — so an overdue-task alert can reach the operations group while the guest only ever sees their own confirmation.
Every event has an editable template per channel, using the placeholders that event provides, and you can reset any of them back to the seeded default.
