Guest Requests

Everything a guest asks the desk for, in one queue — an iron, a taxi, extra towels, and the one kind a property can be late for: a wake-up call. Its own table rather than a service ticket, because the column that matters is the time it is DUE, and a ticket has nowhere to put an alarm.

Switch: Settings > Hotel > Guest Requests.

Where it appears

A Guest Requests entry on the rail, a Requests due tile on the dashboard when anything is overdue, a banner across the front desk that refreshes every minute, and a Guest Request action on a stay.

Flow

flowchart LR
    A[Desk takes the request] --> B[(Open)]
    B --> C[(In progress)]
    C --> D[(Done)]
    B -. housekeeping .-> E[Housekeeping task]
    B -. a fault .-> F[Service ticket]

A request BRIDGES rather than duplicates: a housekeeping ask spawns a real floor job and a fault a real ticket, and the queue keeps the id so one line still reads as one ask.

Screens

Guest Requests - four readings of one queue: Due now, Today, Open, Done. The page ages itself on a timer, so a request due at 09:00 moves into Due now at 09:00 without anybody pulling it. Each open request says who owns it — or Unassigned — and how long it has waited (Open 3h), or how late it is once past due (Overdue 25m).
Request slip - printed on the counter roll and carried upstairs. A wake-up call prints its time in the largest type on the page.
Reports - Guest Requests and Wake-up Calls, the second read on its own because it is the one a property answers for.

Who may work it. The guest services grant, not the front-desk one: a bell desk or a floor phone answers requests all day and checks nobody in.

Switching off. Warns at save when requests are still open — a queue that goes away with work in it leaves a wake-up call nobody will make.