Ops

Sensor at 2am. Compliance logged. You slept.

Housekeeping coordination, maintenance dispatch, quality inspections, IoT monitoring, and guest support. One suite where a failed inspection auto-creates the repair job.

Ops · Act 1

Run the property

Five departments reported before your coffee.

The general manager opens one dashboard. Occupancy for today. Revenue by department. Last night's audit results. Open maintenance jobs. Unresolved guest requests.

Revenue per available room, average daily rate, and occupancy trends over time. The numbers that used to require logging into seven apps arrive on one screen before the first coffee.

Morning dashboard with live operational feeds from multiple departments

The fixer and the verifier are never the same person.

A housekeeper completes a room inspection. Two items fail: a stained duvet cover and a loose bathroom tile. The inspection app auto-creates two maintenance work orders with photo evidence, room number, and priority.

The nearest qualified tech with the lightest workload receives the job. Not round-robin. The repair completes. The room flips to "ready." The housekeeper's board updates. Overdue jobs reassign automatically.

Inspection checklist flowing into auto-created work orders with tech assignment

The guest never complained.

A sensor alert at 2am. A work order at 2:01am. A tech assigned at 7am. A repair logged. A guest notified. You slept through all of it.

Support and sensors

The complaint resolved before the guest repeated anything.

A guest reports "AC not cooling in Suite 401." The support agent opens the ticket. The customer context panel loads automatically: booking source, loyalty tier, purchase history, and door access log from four connected systems.

The agent creates a maintenance ticket directly from the support thread. The ticket carries the full context. For complaints under a configurable threshold, the agent processes a refund inline, and a balanced journal entry posts to accounting.

Support ticket with auto-loaded guest context panel showing booking, loyalty, and purchase data

The walk-in cooler at 3am.

A water-leak sensor trips under the ice machine at 4am. A work order auto-creates with priority "critical." The on-call engineer receives the assignment with the sensor location and equipment ID.

The repair logs. The equipment record updates. The compliance entry closes. Nobody woke a manager. Nobody checked a dashboard. The system handled it.

IoT sensor dashboard with alert-to-work-order cascade

A support ticket in Desk resolves a guest complaint with a complimentary spa credit.

Campaigns sends a recovery email with a personalized rebooking offer based on the guest's stay history and loyalty tier.

The guest who complained last Tuesday rebooks next month. One resolution, one follow-up, no manual handoff between departments.

Pricing

What it costs

Operations run at 1% of revenue processed, additive to the 2% Commerce rate for 3% total when both are active. Operators who prefer fixed costs can pay per-app instead.

Housekeeping and maintenance tools cost $2-5 per user per month from separate vendors. IoT monitoring is an additional subscription. Guest complaint tracking lives in a separate helpdesk. None connect to the reservation system, the accounting ledger, or the guest-facing channels.

A sensor alert in the current stack creates a note in a notebook. Here, it creates a work order, dispatches a tech, logs the compliance event, and posts the accounting entry.