Sense the stay, act before they ask.
A Fibric operator reads the property management system, the room itself, and every guest request, reasons about what the guest is about to need, and acts to set the room right. Governed, on your real data, with a receipt for every move.
The whole stay, in one picture.
Each signal arrives as one canonical event the operator can reason on, no matter which system it came from.
The reservation and the guest
Arrivals, departures, room assignments, loyalty tier, and special requests stream in from the property management system, the spine of the whole stay.
Locks, climate, lighting
Door access, thermostat state, and lighting come in through connectors. The capability points to a connector through indirection, so swapping a lock or thermostat vendor is config, not a rewrite.
What guests ask, what rooms draw
Service requests, messages, and metered energy per room land as events too, so comfort and cost sit side by side in the same picture.
From signal to a plan worth confirming.
The base model proposes a validated plan. A deterministic executor disposes. The model never acts on its own.
Ready the room before arrival
When the PMS shows a guest inbound, the operator reasons about the room they are walking into and proposes to bring it to temperature and set the scene, in time, not late.
See the issue coming
A repeat request, a thermostat that will not hold, a late checkout colliding with housekeeping. The operator reads the pattern on real data and explains the risk in plain language.
Comfort against cost
It weighs guest comfort against energy draw, so a room is conditioned when someone is on the way and stood down when it sits empty, never one at the expense of the other.
Act on the stay, governed.
Single-flight per room, idempotency keys on every action, trust that fails closed. The room is acted on once, the way you confirmed, with a receipt you can read and reverse.
Set the room
It brings climate and lighting to the right state before the guest walks in, and stands the room down when occupancy clears, single-flight so it fires once.
Route the task
It opens a maintenance ticket or a housekeeping task to the right team, with the context attached, instead of a request lost in a thread.
Close the loop
It checks the request landed, confirms the room held, and writes an attributable, reversible receipt for every step, so nothing is acted on in the dark.
Prepare the room the moment a guest is on the way.
A property that conditions a room as a guest heads in, and stands it down when the room is empty. Connect one system and see your own stay in a picture. Pay for the integrations you run.