Hotel front desk
The hotel desk turns room phones into guest phones. Each room of the hotel rings on one extension; the desk knows who stays in it, limits what the room may dial while it is vacant, resets the last guest's traces at check-out and rings wake-up calls in the guest's language.
Open it from Console, Admin, Settings, Telephony, Hotel desk (/admin/hotel). Reading it needs hotel:read, every change hotel:write. The built-in Receptionist, Manager and Owner roles hold both; give a front-desk clerk the Receptionist role.
Rooms
A room is a room number (letters and digits, up to 8) and the extension that rings in it. By default the extension is the room number with the hotel's prefix (setting room_prefix of the PMS connector: room 201, prefix 1, extension 1201); you can name any existing extension instead. Add rooms on the page, or install the Cloudbeds or Opera Cloud connector: the desk loads the PMS room list once when it starts and keeps the rooms current from the PMS events (Hotels: Cloudbeds and Opera Cloud).
Each room has two classes of service:
| State | Default | What the room phone may dial |
|---|---|---|
| vacant or out of order | restricted | the front desk and emergency numbers (911, 112, 065, 066, 999) only; internal also allows other rooms and hotel services |
| occupied | the hotel's checkin_cos (national by default) | internal, local, national or international; a room may set its own |
The class is written to the extension's class of service and the dial plan caps every call of the extension with it; emergency numbers are never stopped.
The room extension should belong to an account (a user per room) so the guest gets do-not-disturb, forwarding, the language of the prompts and their own call history. An extension without an owner still rings, is still restricted and still gets wake-up calls; do-not-disturb is refused for it (MPBX-HOTEL-NO-OWNER).
Check-in, check-out and room moves
| Action | What the phone system does |
|---|---|
| Check in (name, language, expected check-out day) | the extension gets the occupied class; the owner account gets the guest's language (prompts, voicemail menu, wake-up message), mapped to the nearest of the nine languages |
| Check out | pending wake-ups are cancelled; in one transaction the voicemail box loses its messages, greetings, PIN and notification address, the forwarding statuses go back to the company's defaults (Available, no temporary status, no schedule, no mobile number: do-not-disturb off) and the language is cleared; the extension gets the vacant class |
| Move | the guest, their language, expected check-out, do-not-disturb and pending wake-ups move to the new room; the room left is reset like a check-out |
| Do not disturb | the owner's status becomes Do not disturb (or Available); wake-up calls still ring |
The room phone's own call history (/me/calls, the app's Calls) starts at the current guest's check-in: an earlier guest's calls are not shown to the next one. The company's call history for administrators is unchanged.
The PMS does the same through its events: check-in, check-out, room move, out of order, guest name and language, wake-up set or cancelled.
Wake-up calls
Set a wake-up on a room with Wake-up call: HH:MM (its next occurrence) or a date and time, in the hotel's time zone (the PMS connector's timezone, else the company's time zone). At most three pending per room, at most 30 days ahead; the same minute twice is one wake-up. A guest can set their own through the hotel template flow, which calls POST /api/v1/hotel/wakeups/by-extension with the caller's extension (use an API key with hotel:write).
An AI agent answering a call from a room's own extension also has the tools set_wakeup and cancel_wakeup (time as HH:MM, HHMM or a full local date and time). They act on the calling room only; the agent never names a room, and other callers do not get them. Each change is audited (hotel.wakeup_set, hotel.wakeup_cancelled, by = agent).
At the time, the PBX rings the room's phones (do-not-disturb does not stop it) and, once a phone answers, plays the wake-up message twice in the guest's language, then hangs up. The message is a shipped system prompt (hotel-wakeup, nine languages, no text-to-speech at run time). Not answered: it rings again every wakeup_retry_minutes (default 5) up to wakeup_attempts (default 3). When no attempt is answered the wake-up is missed: the page shows it in red with a count at the top, the event hotel.wakeup_failed goes to the events WebSocket and the webhooks, and an audit row hotel.wakeup_missed names the front desk extension. Call the guest.
Wake-ups are stored in the database and claimed before they ring, so a restart loses none and two servers never ring the same one twice.
Events and audit
| Event | When |
|---|---|
hotel.checked_in, hotel.checked_out | a stay began or ended (room, extension, pms or desk) |
hotel.room_moved | a stay moved (from, to) |
hotel.wakeup_answered, hotel.wakeup_failed | a wake-up was answered, or every attempt was missed |
Events carry room numbers and extensions only, never the guest's name; they need hotel:read. Every desk action leaves an audit row hotel.<action> with the room number.
API
GET /hotel/rooms, POST /hotel/rooms, PUT and DELETE /hotel/rooms/{room}, POST /hotel/rooms/{room}/check-in, /check-out, /move, PUT /hotel/rooms/{room}/guest, /dnd, POST /hotel/rooms/{room}/wakeups, POST /hotel/wakeups/by-extension, GET /hotel/wakeups, DELETE /hotel/wakeups/{id}. Errors: hotel error codes.
Working with the lists
Hotel shows the rooms as a table: room, extension, status, guest, class of service, do-not-disturb and the pending wake-up calls. Search by room, extension or guest, and use the Status chip (vacant, occupied, out of order). The ... menu of a room offers Check in, Remove (vacant rooms) or Wake-up call, Move and Check out (occupied rooms); each opens a small dialog. Add room is in the header. The day's wake-up calls, with the missed ones in red, are in the second table. Below 640 pixels wide the tables turn into cards.