Reference · built on requestOperator by FibricHospitality & guests

Room Ready

Watches rooms turning inspected against guests waiting at the desk, and proposes which room to release first and who to tell.

Request accessPricing ↗

About

At midday there are guests in the lobby and rooms moving from dirty to clean to inspected. Room Ready reads the two lists side by side: the reservations waiting on queue at the front desk, with their queue priority and how long they have waited, and each room's status as attendants and inspectors update it.

When a room turns Inspected, it proposes which waiting guest gets it, using room type, the queue order, and the wait so far. It proposes the text that tells the guest, through the queue-room message in OPERA Cloud or an SMS through Twilio. The desk agent approves the release and the message in one step.

This is a reference listing. It documents what Fibric would read from Room Ready and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Reservations on queue and their priority, through getReservationsInQueue and getReservationQueueStatistics in the OPERA Cloud fof module
  • Room status transitions to Inspected, through Mews ResourceUpdated webhooks, Cloudbeds housekeeping/room_condition_changed, or the hsk module's room status in OPERA Cloud
  • Unit condition in apaleo: Clean, CleanToBeInspected, or Dirty, read after each Unit changed event
  • Counts of rooms by housekeeping and front office status, through getRoomsByRoomStatus in OPERA Cloud, so the desk sees what is coming
  • The mobile number on the waiting reservation, and the status of each message Twilio sends: queued, sent, delivered, undelivered, or failed
  • Inbound replies on the Twilio number, so a guest who answers is matched back to the reservation

Proposed actions

  • Target capability: propose releasing an inspected room to a named waiting reservation, through postRoomAssignment and deleteReservationFromQueue in OPERA Cloud
  • Target capability: propose the room-ready text to the guest, through deliverQueueRoomsTextMessage in OPERA Cloud or a Twilio Messages request from your number
  • Target capability: propose a change of queue priority through putReservationQueuePriority when a guest has waited past the limit you set
  • Target capability: propose which rooms inspectors walk next, ordered by the room types the queue is waiting for, as a message to housekeeping in Slack
  • Target capability: propose a Mews reservation update setting AssignedResourceId to the inspected space, for the desk to confirm

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Give the longest wait the next inspected room

    Reservations of the same room type sit on the OPERA Cloud queue. When getRoomsByRoomStatus shows another room inspected, Room Ready proposes it for the longer wait, with the deliverQueueRoomsTextMessage notice, in one card.

    With Oracle OPERA Cloud

  • Text the guest who went for lunch

    A Mews ResourceUpdated event turns a space Inspected. The operator proposes assigning it to the waiting reservation and an SMS through the Twilio Messages resource, and shows the delivered status back on the card.

    With Mews, Twilio

  • Point inspectors at the room types the lobby needs

    Cloudbeds room_condition_changed events show king rooms clean but uninspected while the queue waits for kings. Room Ready proposes an inspection order to the housekeeping channel in Slack.

    With Cloudbeds, Slack

Requirements

  • Oracle OPERA Cloud with the fof module queue operations, or Mews, Cloudbeds, or apaleo with the waiting list kept by the desk inside the operator
  • Housekeeping status flowing into the PMS as rooms are inspected, from attendants' devices or from an inspector at a terminal
  • A Twilio connector with a messaging number, or the OPERA Cloud queue-room text message configured, for guest notices
  • A guest mobile number on the reservation; without one the proposal is a desk action only
Authentication
Room Ready signs in nowhere. Queue, room status, and reservation contact details come through your property management connector; texts go out through your Twilio connector or the PMS's own queue message, after approval.

Limits

  • The queue itself is an OPERA Cloud feature. On Mews, Cloudbeds, and apaleo the waiting list is maintained inside the operator by the desk agent.
  • A room is proposed only when the PMS reports Inspected, or Clean where you do not inspect. A room walked but not marked is invisible.
  • One message per guest per room release. A second text needs a second approval.
  • It does not check the guest in and does not encode keys.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Room Ready ↗

Questions and answers

What does the desk agent approve?
The pairing of one inspected room with one waiting reservation, and the message to the guest. The card shows the queue position, the wait so far, the room, and the text. Approve both, approve the room without the text, or pick a different guest.
What record does a release leave?
A receipt per release: the room, the reservation, the queue position at the time, who approved, the PMS write, the message Twilio or OPERA Cloud sent, and its delivery status. Rooms released by the desk without the operator are logged as well, so the day reconciles.
Does it ever release a room or text a guest on its own?
No. It matches and proposes. The room assignment and the message go out only after a named agent approves, once. It does not check anyone in, and it never texts a number that is not on the reservation.
Ask about Room Ready

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy