Reference · built on requestOperator by FibricHospitality & guests

Arrival Prep

Reads tomorrow's arrivals, guest preferences, and room status, and proposes room assignments and prep tasks before check-in.

Request accessPricing ↗

About

Tomorrow's arrivals are already in the property management system tonight, with the preferences on each profile and the state of every room. Arrival Prep reads the three together: the arrival list from Oracle OPERA Cloud, Mews, Cloudbeds, or apaleo, the preferences and notes on each guest profile, and the housekeeping state of the rooms that are free.

For each arrival it proposes a room that matches the profile, and the tasks the room needs before the guest walks in: an extra bed, an allergy note for the attendant, a connecting room held. Each proposal reaches the front office manager as one card, with the reason beside it. Nothing is assigned until a person approves.

This is a reference listing. It documents what Fibric would read from Arrival Prep 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 next business date, through getReservations in the OPERA Cloud rsv module, reservations/getAll in Mews, or GET /booking/v1/reservations in apaleo
  • Preferences and stay history on each guest profile, through getPreferenceForProfile and getStayHistory in the OPERA Cloud crm module, or Mews customers
  • Room state for every unassigned room: Dirty, Clean, Inspected, OutOfService, or OutOfOrder in Mews; housekeeping status through the hsk module in OPERA Cloud
  • Preferences and traces on the arrival itself, through getReservationPreference and getTracesByReservation in OPERA Cloud
  • Room assignments and unassignments as they happen, through the unit-assigned and unit-unassigned webhook types in apaleo
  • Cloudbeds reservation/accommodation_changed and housekeeping/room_condition_changed webhooks, so a room that changed hands overnight is not proposed twice
  • Membership of the front office channel in Slack or Microsoft Teams, so each arrival card reaches the desk that owns it

Proposed actions

  • Target capability: propose a room for each arrival, applied through postRoomAssignment in OPERA Cloud, assign-unit in apaleo, or AssignedResourceId in Mews once approved
  • Target capability: propose a prep task for the room with a deadline and department, through tasks/add in Mews, for the housekeeping lead to approve
  • Target capability: propose a guest housekeeping note on the reservation, through setGuestHousekeepingNotes in OPERA Cloud, carrying the preference it came from
  • Target capability: propose the next day's arrival board as one message in Slack or Microsoft Teams, each arrival with its proposed room and open tasks
  • Target capability: propose an advance check-in through postAdvanceCheckIn in OPERA Cloud when the assigned room is already inspected

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

What you can build

  • Match a preference to a room the night before

    A returning guest's profile in OPERA Cloud carries a high-floor preference. Arrival Prep proposes an inspected high-floor room through postRoomAssignment and a note for the attendant. The front office manager approves both from one card in Slack.

    With Oracle OPERA Cloud, Slack

  • Get the crib in the room before the family arrives

    A Mews reservation lists an infant. The operator proposes a task through tasks/add with a deadline before the scheduled arrival and the housekeeping department set, and a room away from the elevator bank.

    With Mews, Microsoft Teams

  • Stop assigning rooms that engineering still holds

    Maintenance records in apaleo show a unit out of service until midday. Arrival Prep leaves it out of every proposal for early arrivals and posts the reason with the arrival board in Microsoft Teams.

    With apaleo, Microsoft Teams

  • Keep the desk in step with overnight changes

    A Cloudbeds reservation/accommodation_changed webhook lands before the morning shift. The operator withdraws its earlier proposal for that arrival and issues a fresh one, so the desk approves the current picture.

    With Cloudbeds, Slack

Requirements

  • A property management connector with reservation, profile, and housekeeping read access: Oracle OPERA Cloud, Mews, Cloudbeds, or apaleo
  • Write access on that connector for room assignment and, in Mews, for tasks/add
  • A Slack or Microsoft Teams connector with a channel for the front office, where proposals are posted and approved
  • Preference codes maintained on guest profiles; Arrival Prep does not infer a preference that is not recorded
Authentication
Arrival Prep holds no credentials. It reads arrivals, profiles, and room state through the property management connector you connect, and proposes assignments and tasks through that same connector and your messaging connector.

Limits

  • It proposes from the room states the PMS reports. A room marked Inspected that is not, in fact, ready is still proposed.
  • Housekeeping systems such as Amadeus HotSOS or Optii are not read directly; tasks are proposed in the PMS task list or your messaging channel.
  • Assignments are proposed once per arrival per day. A late change after approval is a new proposal, not a silent edit.
  • It never checks a guest in without approval, never moves an in-house guest, and never changes a rate.

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 Arrival Prep ↗

Questions and answers

What does the front office manager approve?
One card per arrival: the proposed room, the preference or note that led to it, and any prep tasks, each with its own approve or dismiss. The room is written to the PMS and the task is created only after approval. Editing the room number before approving is allowed.
What record does a proposal leave?
A receipt per proposal: the arrival, the room considered, the preference it matched, who approved, the write the PMS acknowledged, and how to unassign. Dismissed proposals are kept too, with the reason given.
Does it ever assign a room by itself?
No. It reads, matches, and proposes. A room assignment, a task, or a housekeeping note is written only after a named person approves it, once, through the connector. It does not check guests in and does not touch in-house reservations.
Ask about Arrival Prep

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