Reservations
Guests ask on WhatsApp, and Whispr offers sittings from the capacity you set, applies your restaurant's rules and confirms instantly or after your team approves. Room, spa and transfer requests reach your team with the details already collected.
Guest conversation
Can we book the Italian restaurant tonight? Two adults and a six-year-old.
There is a table at 19:30 or 21:00. Children are welcome at the 19:30 sitting — shall I request that one?
19:30 please.
Your table for three at 19:30 is confirmed. Enjoy your evening.
Reservation lifecycle
ConfirmedWhat the guest sees
The guest names the restaurant and the evening, picks from the sittings you run and gets a clear answer in their own language, without waiting for the desk.
Illustrative interface representation with sample data.
Guest · WhatsApp · English
Whispr · from the sittings you manage
Guest confirms the details
Rules checked: party size, children, capacityApplied before anything is confirmed
Whispr · confirmed against your sittings
The lifecycle
Whispr recognises a reservation request in the conversation and asks only for what is missing.
The guest chooses from your restaurants and the sittings you run.
Each sitting offers only the places you made available for it.
Party size, children and age limits are checked against the restaurant's own rules.
Where a sitting carries a price, a notice period or a capacity limit, it is validated before a time is offered.
On instant confirmation the booking is confirmed once the guest says yes; on approval it waits for your team. The guest hears “confirmed” only then.
Two venue policies
Choose per restaurant. Whispr follows the policy you set for each venue.
| Aspect | Instant confirmation | Team approval |
|---|---|---|
| When the guest hears “confirmed” | Right after they confirm the summary | After your team approves it in Whispr |
| What your team does | Nothing extra — the booking joins the venue's list | Approves or declines from the reservation decisions view |
| Who it suits | Venues where your rules are enough | Venues where a person should decide |
Rooms and everything else
Dates, adults, children and their ages — plus room type or board where you have them — are collected before the request reaches your team, who approve or decline it in Whispr. The guest hears your decision in the same conversation — a request, not a confirmed booking.
The request is captured in the conversation and handed to your spa team with the details already collected.
Flight, time and party are collected once and passed to the team that arranges the transfer.
Which hotel systems are connected today, and which are on the roadmap.
Integrations →Tell us which restaurants you run and how they are booked today — we set the demo up the same way.
