Prepare guests before arrival.
Bring online check-in, document collection, applicable deposit steps and supported keyless access into one journey. Automate agreed steps for the property while keeping exceptions with the team.
Katalyst Stay / Guest experience
Online check-in, document collection, security-deposit steps and supported keyless access, connected to the team preparing the welcome.
Development preview / release validation
Registration and the next required step.
Useful information and optional services.
Requests with an operating context.
Arrival instructions, missing documents and service requests often become separate conversations. The guest experience is being built around the stay, so the next step is easier to understand on both sides.
Bring online check-in, document collection, applicable deposit steps and supported keyless access into one journey. Automate agreed steps for the property while keeping exceptions with the team.
Present relevant services, such as transfers or additional housekeeping, as considered options rather than scattered messages.
Support staff with a shared view of guest requests and conversations. Exceptions still need a person, not a promise that software does everything.
Guest registration, guides, service requests and operator communication workflows are implemented in the developing product. Live scope, payment arrangements and access integrations require validation before rollout.
Deposit and access workflows form part of the developing Stay product. Their availability depends on the property, booking channel, payment policy and supported access integration. They are not universal plug-and-play features.
Direct government submission is in development and subject to authority onboarding, technical approval and property eligibility. The current proposition includes document collection and registration preparation; it does not claim a live government connection.
The unified inbox and human handover are part of the developing product. AI chat assistance is in development. Supported channels, guest information and operator control are agreed and validated before rollout.
No. The objective is a clearer journey with less repetitive administration. Operator review, exceptions and personal communication remain important.
No. Demonstrations should use sample or appropriately redacted records, not another operator’s private guest information.
A focused conversation
Walk through a guest arrival, a service request and the team response. We will confirm which parts can be demonstrated and which remain in development.
We confirm the relevant demonstration or development preview and a suitable time by email. Rollout is agreed separately.