On-Property Service Intelligence · Documentation
User Journey
The end-to-end path through On-Property Service Intelligence, from trigger to outcome.
← On-Property Service Intelligence- 1
Signal → confirmed dispatch
A guest-app request for extra pillows arrives in intake. The operator perceives it: the pipeline classifies it as an amenity request at low priority with, say, an 84% confidence, and surfaces it as a draft. The operator confirms. The request is written through the adapter as `dispatched`, the owner action is audited, and `service.requested` is emitted on the shared bus.
- 2
Dispatch → the rest of the ecosystem
That one event ripples outward. App 14 (Housekeeping & Maintenance Ops) receives it and creates a work order, idempotently, then auto-assigns it to the best on-shift, skill-matched, least-loaded staff member — picking from the roster app 43 published. The request the operator confirmed in 07 is now a tracked, SLA-stamped, assigned job on the housekeeping board, with no one re-keying it. The same spine feeds the on-property activity that downstream operations and analytics apps read.