Booking Operations Cockpit · Documentation
User Journey
The end-to-end path through Booking Operations Cockpit, from trigger to outcome.
← Booking Operations Cockpit- 1
Three sources → one lifecycle
A booking enters from one of three doors: a guest books on the host site, the channel manager pulls one in from a simulated OTA, or the group desk confirms an RFP. The cockpit reads all three from the shared booking table and tags each with its source. Selecting one builds its timeline from the booking's own fields plus the PMS check-in state for the current credential — so the desk reflects on-property reality.
- 2
Exception → resolution → ripple
When a channel pull collides with a direct booking for the same night, or an in-stay arrival was never checked in, the exception queue surfaces it. The operator resolves it; an owner's resolution is canonical and audited. A bulk action (pre-arrival / flag / notify) emits notification.sent on the spine, which the Notifications center #35 records as a simulated send — closing the loop without touching the outside world.