A room with an open repair and a guest arriving tomorrow is a complaint waiting to be written. Pre-Arrival Fix reads open work orders and maintenance records, from the PMS's own maintenance module or from a field service system, and the arrivals already assigned to those rooms, with their arrival dates.
For each collision it proposes one of two things: raise the repair's priority and due time so it closes before the arrival, or move the reservation to a comparable room now, while there is choice. Engineering approves the priority change; the front office approves the move. Both see the same card.
This is a reference listing. It documents what Fibric would read from Pre-Arrival Fix 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
Room maintenance records and out-of-order or out-of-service rooms, through getRoomMaintenance, getOutOfOrderRooms, and getOutOfServiceRooms in the OPERA Cloud hsk module
apaleo maintenances of type OutOfService, OutOfOrder, or OutOfInventory, with from and to, and the Maintenance created and changed webhook types
Mews spaces in state OutOfService or OutOfOrder, through resources/getAll and ResourceUpdated events
WorkOrder and WorkOrderLineItem records with priority, status, and dates in Salesforce Field Service, where engineering works there
Arrivals with a room already assigned, through getReservations in OPERA Cloud or the unit-assigned webhook type in apaleo
Comparable rooms free for the same dates, through the OPERA Cloud inv module or the apaleo Availability API
Proposed actions
Target capability: propose raising a work order's priority and due time ahead of the arrival, through an update to the WorkOrder in Salesforce Field Service
Target capability: propose extending or shortening a maintenance window, through PATCH /operations/v1/maintenances in apaleo or putRoomMaintenance in OPERA Cloud
Target capability: propose moving the reservation to a comparable room, through postRoomAssignment in OPERA Cloud or assign-unit in apaleo
Target capability: propose marking the room out of order until the repair closes, through postOutOfOrderRooms in OPERA Cloud, so it is not assigned again
Target capability: propose a card to engineering and the front office in Microsoft Teams listing every collision for the coming arrivals window
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
What you can build
Move the repair up instead of the guest
A Salesforce Field Service WorkOrder on a room is due after the apaleo unit-assigned arrival date. Pre-Arrival Fix proposes a due-time change on the WorkOrder ahead of the arrival, for the chief engineer to approve.
An OPERA Cloud room maintenance record will not resolve before tomorrow's arrival. The operator finds a free room of the same type through the inv module and proposes postRoomAssignment, with the reason, for the front office.
A Mews space stays OutOfService past its expected date. Pre-Arrival Fix proposes that the arrivals assigned to it be moved and posts the list to Microsoft Teams for the two departments to approve together.
The to date on an apaleo maintenance passes but the repair is open. The operator proposes a PATCH on the maintenance with a new to date and lists the arrivals now affected, so nobody assigns the unit meanwhile.
A property management connector with maintenance and reservation read and room-assignment write: Oracle OPERA Cloud, apaleo, or Mews
Work orders in the PMS maintenance module, in Salesforce Field Service, or entered into the operator by engineering
Rooms assigned to arrivals ahead of time; a property that assigns at check-in gets collisions only for the current day
A Microsoft Teams channel shared by engineering and the front office, where collisions are approved
Authentication
Pre-Arrival Fix uses no credentials of its own. Maintenance records, work orders, arrivals, and availability are read through the connectors you connect; priority changes, maintenance windows, and room moves are written through them after approval.
Limits
It sees a collision only when a work order names the room and the arrival has a room assigned.
A move is proposed to a room of the same type or better, free for the whole stay. It never downgrades unless a person chooses.
Priority changes are proposals to engineering. The operator does not dispatch a technician or estimate repair time.
Amadeus HotSOS and Optii work orders are not read directly; they reach the operator through the PMS maintenance record or your channel.
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.
Per collision, one card with two options: change the repair's priority and due time, or move the reservation. Engineering approves the first; the front office approves the second. The card shows the work order, the arrival, and the rooms free for the stay.
What record is left per collision?
A receipt: the work order and its due time, the arrival and its room, which option was approved and by whom, the write the PMS or field service system accepted, and how to reverse it. Unresolved collisions stay on the list until the arrival or the repair closes.
Does it ever move a guest or change a work order on its own?
No. It finds collisions and proposes. A room assignment, a maintenance window, or a work order priority changes only after approval, once, through the connector. It does not dispatch technicians and never takes a room out of order without approval.
Ask about Pre-Arrival Fix
Ask about the capabilities and requirements in this listing.
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