The questionsoperators actually ask.

An operating layer that sits above your PMS. Guest email (Desk), front desk and housekeeping (Flow), finance and analytics (Clarity), restaurants and bars (Calm Kitchen), the owner's view (Command) and the phone in your team's pocket (HotelOS Go) run on one shared context instead of five disconnected tools, with one AI assistant, Nexus, in every app. Your PMS stays the system of record; HotelOS is where the work around it happens.

No. Start with the one surface where the coordination cost is already visible, usually Desk for guest email or Flow for the front desk and housekeeping, and add the next when there is a reason to. The suite is designed to be entered at one door.

Your PMS remains the system of record for reservations and folios. HotelOS is designed to work above it. We confirm compatibility, permissions and supported data flows for your property before agreeing an integration.

Nexus is the AI assistant built into Desk, Flow, Clarity, Calm Kitchen, Command and HotelOS Go. It answers questions from your live data with tables and charts, names its sources in Desk and checks its figures in Clarity, and prepares changes (a rule, a budget, an 86) as cards a person approves. One conversation history follows you across the apps.

Not unless you decide it should. Desk starts in Copilot: it drafts every reply and your team sends. Autopilot, if you switch it on, sends only routine answers above a confidence level you set; replies about bookings, complaints, cancellations and payments always wait for a person. With PMS Autopilot on, Desk can book a reservation when a guest accepts a quote your team sent, and still leaves the confirmation email as a draft. Nexus never emails guests.

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.

People approve; the software prepares. Guest replies are drafts until your team sends them, unless you switch on Autopilot for routine questions within limits you set. Changes Nexus proposes wait on an approval card, high-risk decisions need an owner in Command, and each person's Nexus can only see and do what their role allows.

Your HotelOS database is stored in the EU, in Frankfurt. Some uploaded files and attachments are currently stored in Asia-Pacific. Named sub-processors, including some in the US, process customer data under standard contractual clauses.

Live, and taking on new properties. Try it on yours: tell us about your property and we set it up on your stack, with the modules, users and connections agreed in writing first. The roadmap is shaped by the operators using it.

Twenty minutes, screen-share, your questions first. We run the operating layer against your stack and your shift pattern rather than a generic deck, and you get an honest answer on fit — including when the answer is not yet.