Try HotelOS
Back to the operating layer

Front desk, housekeeping & operations

Flowservice in motion.

The front desk, housekeeping and operations board for the whole house: arrivals grouped by boat and car time, rooms moving from dirty to ready, and a folio that already includes dinner.

Try FlowSee the capabilities

Flow reads the same stays as Desk and the same kitchen charges as Calm Kitchen. The front desk sees who is arriving, when, and what is still blocking them; housekeeping works from one board; the duty manager gets a written shift brief instead of a stand-up scramble.

What it does

Built around how
the work actually moves.

Capability 01

A front desk that already knows

Arrivals, in-house guests and departures for any date, grouped by transfer time (speedboat, seaplane, car), each with a readiness ring and plain-language blockers such as “ID details missing for 2 adults”. Details saved in Desk and the PMS are already there.

  • Arrivals grouped by boat and car time
  • Readiness at a glance, blockers in plain language
  • Check-in that pre-fills from PMS, Desk and staff, where switched on
  • Every pre-filled field shows where it came from
Capability 02

One bill at checkout

The stay's folio shows the room account from your PMS and the Calm Kitchen dining ledger side by side, with one balance due. A dinner already posted to the room is marked as such and never counted twice.

  • Room folio and dining ledger in one balance
  • Charges already on the room folio shown, not double-counted
  • Unmatched dining checks flagged for a person to review
  • Checkout sets the room to dirty and creates the cleaning task
Capability 03

The floor, on one board

Housekeeping moves rooms from start to clean, inspected and ready, and flags maintenance from the same screen, in English, Spanish or Indonesian. Supervisors see the whole grid; front desk sees what is ready.

  • Start → Mark clean → Inspect → Ready
  • Maintenance flagged as a task with the room attached
  • Supervisor grid and front-desk readiness from the same data
  • Operations tasks and cases in one list
Capability 04

The day, handled

A dashboard that ranks what needs attention now, a written shift brief and handover, reviews with a draft reply to approve, and Nexus on every page for questions like “Which arrivals still need a room ready?”.

  • Ops radar and shift brief from live operations
  • Handover notes that carry to the next shift
  • Review replies drafted, approved and marked responded
  • An autonomy setting that keeps guest-facing actions confirmed

In the suite

Flow as it runs today.

A faithful recreation of the screen your team opens, shown with fictional data. Same context, same data and the same Nexus as every other surface.

Flow interface

How it works

From first signal
to a settled outcome.

Every Flow workflow starts from something real in the property, and every step keeps a person in charge of what reaches a guest, the books or the PMS.

  1. 01

    Know

    Arrivals are grouped by transfer time with what is ready and what is missing, from the same record Desk updates.

  2. 02

    Prepare

    Housekeeping moves rooms to ready; the front desk sees it without a radio call.

  3. 03

    Serve

    Maintenance and service issues become tasks; Nexus answers questions and asks before it changes anything.

  4. 04

    Settle

    Room and dining meet on one folio at checkout, and the room goes back to housekeeping as a task.

Scope agreed in writing

Know what you are signing up for.

Confirm features, integration scope and support in your order form before relying on them for operations.

Subject to assessment

Plan your
connected workflows.

Availability is confirmed in writing for your property. Provider permissions, technical validation and any required approvals must be in place before activation. A request does not guarantee delivery.

  • Property management
  • Messaging

What changes

The same property,
on a calmer shift.

01

Calmer mornings

The shift starts with a written board and brief: front office, housekeeping and duty manager on the same plan.

02

No re-typing at arrival

What reservations already know about a guest is on the front desk screen when they walk in.

03

No checkout arguments

Restaurant and room charges on one folio, with double counting ruled out.

Bring Flow into the operating layer

Run the house as one moving plan.

Stop running arrivals from a printout, housekeeping from a group chat and checkout from two systems. Bring them onto one board that everyone reads.

Talk to us about FlowBack to HotelOS