At 3 pm you welcome guests instead of typing up forms and IDs.

Guests complete the details required for arrival in advance through a protected personal process. Information remains connected to the correct booking and can be reviewed by front desk before check-in.

Front desk does not collect every required detail only when several guests arrive at once. Missing data becomes visible earlier while personal hospitality remains wherever the property wants it.

The link belongs to one specific booking and is sent through the appropriate communication path. It is not a general form where guests freely select a property or stay.

No. The process uses a personal protected reference to the booking. Public marketing or booking pages do not expose other stays and do not allow guest data to be retrieved by simple guessing.

The property defines guest and accompanying traveller details required for arrival, stay and legal registration. It should enable only fields genuinely needed and legally justified in its operation.

Yes. Travellers are assigned structurally to the correct stay. Adults and children do not become unclear free text on the main guest, and required registration details can be prepared per person.

Required identity and registration details can be prepared in the protected process. Front desk checks plausibility and completeness on the stay before using them for completed check-in or reporting.

Not necessarily. Submitted online details and operational check-in state are deliberately separate. The property can review information first and complete check-in only after room readiness, identity or payment checks.

Progress remains visible directly on the related booking and in the online check-in workspace. Employees do not need to search email replies or external forms to assess completeness.

The process remains incomplete and shows which details are missing. STRYK must not present an incomplete record as a finished check-in, allowing front desk to follow up precisely.

While the personal process remains valid and not operationally closed, permitted details can be completed or corrected. Changes to already verified or legally relevant data remain a deliberate front-desk process.

Validity follows the related booking and secure check-in window. Expired, withdrawn or no longer relevant processes must not continue to provide access to stay data.

The property requests only necessary data, protects the personal process and limits internal access by role. Lawful basis, notice, retention and deletion must fit the operation before production use.

The guest journey follows STRYK and booking engine multilingual foundations. Active guest languages, external copy and required information are maintained for the property rather than inferred from employee language.

Yes. The public flow is mobile-first so guests can complete it on their own device without installing an app. Fields, progress and confirmation remain fully usable on small screens.

No. The guest uses the protected process associated with the booking and does not create an employee or hotel account. Internal STRYK accounts remain exclusively for authorised hotel staff.

Yes. Structured traveller and registration details can flow into the responsible STRYK guest registration process. The property still reviews them before registration forms, exports or Feratel transmission.

Both paths use the same booking and guest context but serve different situations. Online check-in happens in advance on the guest’s device, while the kiosk is the property-specific self-service interface at arrival.

Complete guest details do not release a room automatically. Front desk and housekeeping confirm that it is ready. 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.

Common mistakes include general links, too many required fields, missing privacy notices and assuming a completed form automatically means operational check-in. Every step needs a visible success signal.

The property defines fields, languages, privacy notice, delivery timing and ownership. It then runs a complete test booking with main guest, companion, missing field, correction and visible front-desk review.

Online check-in is part of the single STRYK offer, with no setup fee or hidden STRYK module tier. Online payments follow the payment terms shown on the pricing page.

In your demo access you open the personal link on a phone, add the main guest and fellow traveller details, resolve a missing required field and complete the process. The new status appears on the booking immediately.