Guests complete registration details and signature themselves, your team sees the check-in straight away.

The kiosk is the property-specific self-service interface for on-site arrivals. Guests identify their booking, complete required details and follow the permitted check-in flow without accessing the internal PMS.

It suits small teams, apartments, late arrivals and peak periods where standard details can be captured independently. Personal service remains possible and is not replaced by a mandatory full-automation concept.

Each property receives its own kiosk access through its STRYK domain. The kiosk opens directly in guest self-service, without going through internal hotel administration.

No. Access, booking search and check-in remain limited to the relevant property. Internal lists, finance, settings and data from other properties are not accessible to guests.

Guests use booking and identity details approved by the property. STRYK checks whether they belong to an active matching stay before personal details or the next step become visible.

An ambiguous search does not advance an arbitrary guest. The kiosk requests additional permitted identification or directs the guest to front desk instead of showing public lists of personal matches.

The kiosk uses guest, accompanying traveller and registration details approved for the property, booking and arrival. Configuration should contain only operationally necessary and legally justified fields.

Yes. Accompanying travellers are added structurally to the stay so required details can be reviewed per person. The kiosk does not place every traveller into one uncontrolled text field.

The check-in flow must consider the current stay and approved room state. A room that is not ready or operationally blocked must not be treated as ready merely because guest details were entered.

Yes. A successfully completed kiosk step becomes visible on the correct stay. Front desk and management then use the same status instead of reconciling a separate kiosk list.

Missing identification, mismatched booking, incomplete required details or blocked check-in remain visible as concrete states. The kiosk shows no false success and offers a clear path to personal assistance.

It can handle defined standard arrivals independently. Exceptions such as unclear identity, wrong booking, unready room, open payment or special assistance still need a defined escalation path to the hotel team.

The guest journey follows STRYK and booking engine multilingual foundations. The property activates appropriate guest languages and maintains external copy separately from employee language.

The kiosk runs in the browser, for example on a tablet or touchscreen with a stable internet connection. Payment terminals, key card encoders or other additional devices are not connected; what matters is an easily accessible location and a suitable screen size.

There is no payment and no payment terminal at the kiosk. Guests settle outstanding amounts online in advance via the integrated payment service, for example as a deposit or through automatic balance collection, or they are dealt with at reception.

After check-in, depending on the settings, the kiosk shows the room number, a key safe code you have stored or your own message. STRYK does not create key cards or digital keys.

STRYK is not connected to any locking systems. For key handover without reception, hotels use the room number display or a manually stored key safe code.

Access is property-bound, public sign-in attempts are rate-limited and the kiosk receives no general PMS role. Personal result lists, internal navigation and sensitive administration remain outside the self-service interface.

Check-in write actions require a confirmed connection to current hotel state. During an outage, the kiosk shows a clear error and help path instead of pretending an unsaved check-in succeeded.

Before launch, the property verifies location, device, domain, kiosk access, languages, identification, fields and escalation. Tests cover correct booking, wrong input, ambiguity, missing field, unready room and network outage.

The kiosk is a separate module included in the core price, with no set-up fee and no surcharge. The only cost is for the device on which the kiosk runs in the browser.

Yes. A test arrival covers booking search, identification, missing details, room readiness, completion and personal assistance. The property goes live only when the standard journey and exceptions work clearly for guests and staff.

In your demo access you identify an arrival, add missing details, review room readiness and status, and see how the guest can move directly to personal assistance when needed.