Reference · built on requestOperator by FibricHospitality & guests

Walk Risk

Counts arrivals against rooms that can be sold tonight, net of rooms out of order, and proposes which reservations to relocate and where.

Request accessPricing ↗

About

Overbooking is a plan until a room goes out of order in the afternoon. Walk Risk reads arrivals for tonight, rooms that can be sold by type, rooms out of order or out of service, and the work orders that say when each comes back. It runs the count again whenever any of those changes.

When arrivals exceed sellable rooms, it proposes which reservations to relocate, ranked by the rules you give it, and the sister property with rooms free for those dates. The front office manager decides. The guest is called by a person, and the relocation is recorded against the reservation.

This is a reference listing. It documents what Fibric would read from Walk Risk 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

  • Arrivals for the day and their status through the rsv and fof modules in OPERA Cloud, including reservations in queue
  • Reservations by status Confirmed, InHouse, and Canceled through GET /booking/v1/reservations in apaleo, and by status in Cloudbeds
  • Available room types and sell limits: getAvailableRoomTypes in Cloudbeds, the inv and par modules in OPERA Cloud
  • Rooms out of order, out of service, or out of inventory: apaleo maintenances, Mews resource states, OPERA Cloud room status
  • Work orders on those rooms in MaintainX, UpKeep, or Limble, with status and expected completion
  • Availability at sister properties in the same chain, where the property management system exposes it

Proposed actions

  • Target capability: propose a relocation list ranked by your rules, such as rate, loyalty tier, and length of stay, for the front office to approve
  • Target capability: propose the receiving property for each relocated reservation, with its availability for the same dates
  • Target capability: propose a reservation note or trace recording the relocation, the reason, and who approved it
  • Target capability: propose a message to the team channel with the count, the rooms out of order, and the time each is expected back
  • Target capability: propose holding a relocation until a work order due before check-in time is closed

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

What you can build

  • Decide before the evening rush

    A block of rooms goes out of order in apaleo after a leak, and MaintainX puts the repair past check-in. The operator recounts and proposes the reservations to relocate, posted to Teams for the manager.

    With apaleo, MaintainX, Microsoft Teams

  • Keep the loyalty guest

    The ranked list excludes the tiers you protect. The proposal shows who stays and why, from the OPERA Cloud profile, and which reservations are next in line, posted to Slack.

    With Oracle OPERA Cloud, Slack

  • Hold the walk until the room is fixed

    A work order in UpKeep is due before check-in. The operator proposes waiting, posts the expected time to Slack, and recounts the Mews inventory when the order closes.

    With UpKeep, Slack, Mews

Requirements

  • A property management system connector exposing arrivals, availability by room type, and room status: Oracle OPERA Cloud, apaleo, Mews, or Cloudbeds
  • A maintenance connector with the work orders behind each out-of-order room, such as MaintainX, UpKeep, or Limble
  • A Teams or Slack channel where the front office manager receives and approves proposals
  • Your relocation rules: who is never relocated, which sister properties are acceptable, and in what order
Authentication
Walk Risk carries no credentials. It reads arrivals, inventory, and work orders through your property management and maintenance connectors, and posts proposals to Teams or Slack through those connectors.

Limits

  • It counts rooms. It does not predict no-shows or late cancellations beyond the history it is given.
  • The relocation is proposed, not booked. A person calls the guest and books the receiving property.
  • Sister-property availability is visible only where the property management system shares inventory across properties.
  • A room comes back into the count when its work order closes, not when a technician says it will.

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 Walk Risk ↗

Questions and answers

What does the front office manager approve on a walk night?
The list of reservations to relocate and the receiving property for each. The proposal shows tonight's count, the rooms out of order and when each returns, and the rule that placed each reservation on the list. The manager reorders, removes, or approves.
What record is left when a guest is relocated?
A receipt on the reservation: the count at the time, the rooms out of order, the rule applied, the receiving property, who approved it, and who called the guest. The team channel post is kept with it.
Does it ever move a reservation itself?
No. A person calls the guest, books the receiving property, and confirms. The operator never cancels, amends, or reassigns a reservation, and it never contacts a guest.
Ask about Walk Risk

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