Skip to main content

Hotels: Cloudbeds and Opera Cloud

A hotel's property management system (PMS) tells the phone system who is in which room. Check-in opens the room extension, check-out closes it and wipes the last guest's traces, wake-up calls come from the PMS, and rooms may call each other under rules.

Connectors​

Install them from Console, Admin, Integrations (cloudbeds, opera, category hospitality). Credentials are sealed with the company's key and never shown again. Create a hook endpoint for the connector (see integration-hooks.md) and give its address to the PMS.

SettingMeaningDefault
timezoneIANA zone of the hotel; every wake-up time is local to itUTC
room_prefixdigits put before the room number to get the extension (room 201, prefix 1: extension 1201)none
front_deskthe extension every room can always call0
checkin_cosclass of service while a guest stays: internal, local, national, internationalnational
room_to_roomoccupied_only, always, neveroccupied_only
wakeup_attemptsrings per wake-up before the front desk is alerted (1 to 6)3
wakeup_retry_minutesminutes between rings (1 to 30)5

Cloudbeds: property_id and an API key. Webhooks: reservation/status_changed (checked_in, checked_out; the rooms come from getReservation), reservation/notes_created, housekeeping/room_condition_changed. Cloudbeds has no wake-up object, so the front desk writes WAKEUP 06:30 (or WAKEUP CANCEL) in the reservation notes; the notes event sets or cancels it for every assigned room.

Opera Cloud (OHIP): gateway address, client id and secret, integration user and password, application key, enterprise id and hotel code. Business events: CHECKED_IN, CHECKED_OUT, ROOM_MOVE, ROOM_STATUS_CHANGED, WAKE_UP_CALL_CREATED, _UPDATED, _CANCELLED. An event for another hotel code is refused.

Both connectors give the AI agent one tool, room_status (occupied or vacant, housekeeping condition).

What happens​

PMS eventPhone system
check-inroom extension gets checkin_cos; the guest's language selects prompts and the wake-up message
check-outextension back to restricted (front desk and emergency numbers only); voicemail, forwarding, DND reset; pending wake-ups cancelled
room moveold room closed and reset, new room opened, wake-ups and language follow the guest
out of serviceroom restricted
housekeepingrecorded only
wake-up set / cancelscheduled in the hotel's zone; the same minute twice is one wake-up; at most 3 pending per room; at most 30 days ahead; a vacant room is refused

A wake-up rings at its minute, then every wakeup_retry_minutes until answered or out of attempts, then the front desk is alerted.

Dialing rules​

Every room can always call the front desk and emergency numbers (911, 112, 065, 066, 999). A vacant or out-of-order room can call nothing else. Between rooms: per room_to_room. Other numbers need the class: 4 digits or fewer is internal, 7 to 9 digits local, 10 or more national, + or 00 international. Staff extensions are not rooms and are not restricted by these rules.

Template flow​

pbx/crates/flows/templates/hotel-front-desk.json: guests (calling from a room) get a menu with front desk, housekeeping, wake-up request and room service; outside callers get front desk, reservations and a guest directory. Every timeout, wrong key and failure ends at the front desk, then its voicemail. The wake-up path collects four digits (0630) and posts them with the caller's extension to POST /api/v1/hotel/wakeups/by-extension (the HTTP node needs the http capability; replace the example host with your PBX's address, store an API key with hotel:write as the flow secret hotel_api_key, and record the prompts).

The desk​

The PMS feeds the company's hotel desk (Hotel front desk): rooms and wake-ups are stored in the database, the room list is loaded from the PMS once when the desk starts, and the front desk can check guests in and out, move rooms and set wake-up calls from the console as well. Hook endpoints use the shared_secret scheme for both PMSs until a hotel lab confirms the vendor signature headers.