How a request flows

Every request takes the same path, whether it is two towels for 512 or a late checkout. Knowing the path explains everything the app shows.

1. Spoken
   A staff member taps the badge, says the room first, then the request, and taps again. The badge confirms with a short tick as soon as the cloud has it, usually within a couple of seconds.
2. Understood
   The cloud turns the sentence into a request with a type, a room and a department. When something is genuinely unclear, it asks the speaker one question in the app rather than guessing.
3. Reviewed, where the hotel wants it
   Some requests wait for a person before they go anywhere: those with consequences in a hotel system, those a property has asked to see first, and everything at a hotel that has turned on front desk review. The reviewer can approve, edit a detail, or reject.
4. Routed
   The request goes to a person, by the hotel's own routing rules (type and room), or to a system through the connector. The person sees it on their phone and the badge buzzes twice.
5. Worked
   The assignee taps Begin work, then Mark complete. They can ask the person who raised it a question, hand it on, or decline it back to the department.
6. Recorded
   Every step, with who did it and when, stays on the request's record. Managers see it on the Overview and in the exports.

Time limits#

A request waiting for approval does not wait forever. Each property sets how long an approval may wait before it is escalated to a manager, and how long a manager has before it lapses. A lapsed request is marked as such on its record; nothing is sent on a decision nobody made.