Operator Booking Console (PL-T190)

The operator console lives at /operator and is built around a tablet-sized iPad behind the bar — high information density, large hit-targets, no menus more than two taps deep. The /operator/today landing aggregates the day's schedule, status distribution, check-in-due ±30 min, walk-in counter, and next-slots per resource type into a single API call (GET /chain/operator/{location}/today) so the page paints in one round-trip. The Cmd-K command palette (OperatorCommandPalette) opens a fuzzy-filtered action list — new booking, check-in, walk-in, wait-list, ring-back, cancel — with badge tags showing the current walk-in count and check-in-due number, so the operator can keep both hands on the keyboard. /operator/quick-book embeds the QuickBookForm with a deterministic idempotency key and a 409-conflict picker that lets the operator pick alternative slots with Cmd-1, Cmd-2, Cmd-3; on success a toast offers an optional SMS confirmation send. /operator/walk-ins is a 3-panel layout: walk-in queue, ring-back queue, wait-list — items can be HTML5-dragged onto the floorplan, or assigned via a bottom-sheet on touch devices that don't drag well.

Customer search (CustomerSearch) debounces fuzzy queries against ChainPassport plus the last 90 days of guest-details, dedupes on phone/email, and autofocuses a "Create new" CTA when there are zero hits. /operator/check-in shows arrivals in a ±30 min window with name/phone filter and one-tap check-in against POST /chain/bookings/{id}/check-in. The whole console subscribes to SSE chain.bookings.{tenant}.{location} with a 400 ms debounced refetch so today's data and walk-ins stay live without polling.