Booking Operations Cockpit · Documentation

How to Use This Demo

Driving Booking Operations Cockpit in the host, the Cloud/OSS inspector, and the operator console — with honest labels.

Booking Operations Cockpit
  1. 1

    Signing in + opening the app

    The ecosystem is gated. Sign in as the universal owner (admin / admin@123) for exception resolution and bulk actions, or as the read-only viewer to browse + resolve ephemerally. Open the Cockpit from the host launcher (Property & Partner Operations zone); it renders in the unified operator console.

  2. 2

    Working the grid + timelines

    The 'All bookings' tab lists every booking with source (direct / channel / group) and status badges, plus stat tiles. Filter by status or source, or search by property or booking id. Click a row to open its lifecycle timeline — created (with source), payment captured (simulated), check-in (if the PMS checked the guest in for your credential), cancelled — alongside cross-links to PMS #30, Fraud #18 and Refund #21.

    The 'Exceptions' tab lists no-shows and channel-collision overbookings; resolve them inline (viewer resolutions are ephemeral, owner resolutions canonical + audited). The 'Bulk actions' tab (owner-only) multi-selects upcoming bookings to send a simulated pre-arrival or flag them for review.

  3. 3

    The inspector + honest labels

    The dark 'Behind the scenes' inspector shows the shared trace. The cockpit runs no metered model, so its honesty story is about provenance and simulation, not cost: payment lines are marked simulated, and the bulk-send note states plainly that no real message leaves the demo (it lands in the #35 sent viewer).

How to Use This Demo · Booking Operations Cockpit · Abhishek Saxena