Concierge Booking Operations · Documentation
User Journey
The end-to-end path through Concierge Booking Operations, from trigger to outcome.
← Concierge Booking Operations- 1
Search → build → confirm
A guest wants three nights somewhere on the coast. The agent searches the destination, picks a property, builds a room + rate + dates quote, runs the upsell (offering an upgrade and breakfast), and — as owner — confirms. The booking is created through the shared adapter and a confirmation is generated for the guest.
- 2
How it ripples outward
The confirm emits `booking.created` (a cancel emits `booking.cancelled`) on the shared bus, so the booking shows up in the operator cockpit (#20) and PMS (#30), accrues loyalty (#12), and rolls into analytics — without any duplication. The confirmation rides #35's `notification.sent` path. Tasks in the queue derive from open booking-change conversations and upcoming bookings.