Spa treatments
Captured in the conversation with the guest's preferences and handed to the spa team as a case.
Restaurant Reservations
Less reservation back-and-forth. More time for your guests.
Guests book à la carte tables inside the conversation: Whispr offers the sittings your PMS reports as free, the guest picks one, and the table is confirmed once the PMS accepts it.
What the guest sees
Four messages instead of four phone calls.
Availability, a choice, a confirmation — in the guest's language, at any hour, without your restaurant desk picking up the phone or your front office relaying messages.
Illustrative interface representation with sample data.
Guest · restaurant reservation in chat
Hi! Could we get a table for four at Ocean Grill tomorrow evening?
Guest · WhatsApp · English
Of course. Ocean Grill has tables tomorrow at 19:00, 20:30 and 21:00 — which would you like?
Whispr · live availability from the PMS
20:30 please 🙏
Guest confirms the details
Reservation sent to the PMSNothing is promised until the PMS accepts
Your table for four is confirmed for tomorrow at 20:30. See you at Ocean Grill!
Whispr · sent after the PMS accepted
Two confirmations, kept apart
The guest chooses. The PMS decides.
A booking has two very different "yes" moments. Whispr never blurs them.
The guest confirms the details
Restaurant, date, party size and a sitting the PMS reported as free. This is the guest's choice — not yet a reservation.
The PMS accepts the reservation
Whispr writes the request to Veboni and waits. The reservation exists only when the PMS says it does.
Only then, the guest is told
The confirmation goes out after Veboni accepts. A declined or unanswered request is handed to your team, never shown as booked. Changes and cancellations go to your team too — Whispr does not cancel inside the PMS.
Two kinds of restaurant
Booked through Veboni, or managed by Whispr — tell us which, and Whispr behaves accordingly.
A restaurant whose tables live in Veboni is booked in Veboni. A restaurant whose sittings you hand to Whispr is governed by the rules you give it.
| Aspect | Booked through Veboni | Sittings Whispr manages |
|---|---|---|
| Availability | Read live from Veboni at the moment of the request | Kept by Whispr, per sitting, within the capacity you set |
| Who accepts | Veboni — the guest is told after it accepts | Whispr — the guest is told once the sitting is held |
| House rules — minimum age, children, party size, notice | Not applied by Whispr: what Veboni reports as free is what's offered | Applied before a time is offered |
| Changes and cancellations | Handed to your team; Whispr doesn't cancel in the PMS | Handed to your team |
Everything else
Not every reservation is a restaurant table.
Transfers and excursions
Details collected, case opened for the responsible department, guest updated when it's arranged.
Kids club and activities
Same pattern: captured in chat, handed to staff, tracked to completion — not booked automatically.
Live availability and write-back are Veboni-specific today. With Sedna360, reservation requests are captured and routed to your team.
How the reservation write-back fits the rest of the Veboni integration.
Integrations →Bring your restaurant setup to the demo.
Which restaurants book in Veboni, which sittings you'd hand to Whispr, the rules you apply today — we'll show you what a guest sees and what your team receives.