Business Problem & Solution

Bookings arrive from everywhere — the direct consumer site, third-party channels, and the corporate/group sales desk — and an operator who has to flip between three systems to answer 'what is going on right now?' will miss the overbooking and the no-show that cost real money. The hard part isn't any single booking; it's seeing all of them, from any source, in one consistent place with the right actions attached.

The Booking Operations Cockpit is that desk. It merges direct (host #01), channel (#17) and group (#40) bookings into one filterable grid, gives each booking a lifecycle timeline, surfaces operational exceptions, and lets the owner run bulk actions — all on the shared booking record, never a copy.

It proves the coupling is real: a booking the channel manager pulls in, or one the group desk confirms, shows up here with its true source and status because every app reads the one shared booking table over the event spine. The exception queue is the payoff — a channel pull that collides with a direct booking surfaces as an overbooking without any app reconciling by hand.

It simplifies the irreversible bits and labels them: the payment line on a timeline is a simulated capture, and bulk sends land in an in-app 'sent' viewer rather than a real inbox. The lifecycle is real end-to-end; only the parts that would move money or send messages are faked, and they say so.

Synthetic bookings only — direct bookings from the foundation, plus channel-origin and group bookings created deterministically within the demo. Exceptions are derived from the booking state (no-show = in-stay, never checked in, arrival past; overbooking = a synthetic channel collision). Figures are representative and labelled; no real brands, customers, or PII.