Concierge Booking Operations · Documentation
Business Problem & Solution
The problem Concierge Booking Operations solves in the hospitality ecosystem and how this downscaled demo proves it.
← Concierge Booking OperationsBooking on the guest's behalf
When a guest calls or writes to book or change a stay, an agent has to act for them — search availability across properties, build a quote, fold in loyalty and the right upsell, and confirm — without bouncing between the consumer site and a stack of back-office tools. Concierge Booking Operations is that single operator desk: create, modify, and cancel bookings for a guest in one console.
What the demo proves — and simplifies
It proves the agent desk writes to the same shared booking spine as the consumer site and the operator cockpit: a booking created here is the same `booking` entity #01, #20, and #30 read, emitted on the same event bus, with the confirmation flowing to #35. It simplifies the irreversible bits and labels them — payment and confirmation are simulated (no PSP, no SMTP), the upsell ranking is deterministic, and all figures are representative synthetic values.