Guest requests
Every guest request in one queue, approved in a tap.
Everything a guest books from the portal, a candlelit dinner, a couples massage, a trail ride, lands in one queue. You see the service, the requested time, which guest and the note, and you approve, decline or approve and schedule in a single tap.
Confirmed ones drop into the day agenda by time, and the charge goes to the guest's folio once, never twice. The team stops chasing requests across WhatsApp and paper: it all lives in one place, routed by section, with a record of who approved what.
Every request in one place, decided in a tap
Everything a guest books from the portal lands in one queue, with the service, the requested time, which guest and the note. You approve, decline or approve-and-schedule right there, and each request is routed to the section that handles it.
- One queue for spa, dining and experiences
- Approve, decline or approve and schedule
- Requested time and guest note
- Routed by section, with who approved it
The whole day, by time
Confirmed ones drop into the day's agenda in time order, each with the service and the guest. The team opens the agenda and knows what's coming, and the charge lands on the guest's folio once, never twice.
- The day's agenda in time order
- Service and guest on each item
- Confirmed ones enter automatically
- A single folio charge
- One queue for every request (spa, restaurant, experiences)
- Approve, decline or approve and schedule in a tap
- The day's agenda by time
- A single folio charge, never double-posted
Under the hood
A per-booking request queue with approve, decline or approve-and-schedule, section routing and a single folio charge; the day agenda comes from the confirmed services.