Keep guest preferences ready for the next visit.

STRYK combines contact details, stays, bookings, messages, invoices, revenue, privacy state and relevant preferences in one guest profile. Guest care therefore does not restart from zero with every reservation.

Front desk recognises returning guests, finds previous stays and reviews open information without a side database. Personal care becomes reliable even in a small team when a different employee is on duty.

Before creating a guest, the team searches by name, email and other matching details. Potential duplicates are surfaced so existing history is used instead of being silently split across several profiles.

Yes. Authorised employees can merge verified duplicates under control. Bookings, relevant history and connections are aligned with the primary profile instead of simply deleting one profile and its valuable data.

The profile shows past and current stays connected to the guest. Travel dates, booking status and recurring patterns can be reviewed without manually assembling old bookings from different lists.

Yes. Booking, stay, invoice and payment remain operationally connected and can be traced from the guest profile. This helps with questions and reveals the history and value of a returning guest without duplicating finance data.

Messages appear in the guest area but always remain a conversation belonging to the correct booking. The team sees more than isolated text and can check dates, stay and the appropriate channel for direct or OTA bookings.

Relevant factual notes can be maintained in guest and booking context. The property should store only information required for service and operations, avoiding sensitive judgements or inappropriate profiling.

A guest profile can carry a traceable discount context for appropriate transactions. Rates still remain tied to plan, period and the specific booking; a discount never replaces controlled pricing review.

The property centrally decides whether guest photos are disabled or used for an explicit operational purpose. Photo mode supports authenticated display, preview, upload, camera capture, editing and removal; with photos disabled, no avatar placeholders appear.

Privacy state and relevant consent information are maintained structurally on the guest. Access and editing follow roles; the property remains responsible for defining lawful basis, retention and deletion processes appropriate to its operation.

Authorised employees can correct master data and handle privacy requests deliberately. Before removal, the property reviews legal retention, open stays and finance links so required booking or invoice evidence is not lost without control.

During booking creation, front desk first searches for an existing profile. If none is found, the guest is created within the same controlled process and connected directly to the stay, contact details and further booking information.

Multiple travellers are assigned structurally to the correct stay. Online check-in and guest registration can prepare required data without forcing everyone into one unclear free-text field.

The guest completes required details through a protected personal process before arrival. The property reviews submitted data on the correct stay before it is used for check-in and, where applicable, guest registration.

Front desk sees previous stays, messages, invoices, relevant notes and existing contact details in one profile. The next interaction starts personally and informed without asking the guest for information the hotel already has.

Operationally relevant notes and guest discounts stay connected to the profile with the correct stay and pricing context. The team sees what may be applied without maintaining private side files or uncontrolled free text.

Yes. Authorised users open guests, stays and booking messages in the STRYK app for iPhone and Android or in the browser.

The property grants guest access only to roles that need it for front desk, service, finance or legal processes. Housekeeping and other teams receive only the information required for their job, not the full guest profile by default.

First define required fields, search routine, duplicate policy, internal notes and privacy responsibility. Then test a returning guest, a new booking, a duplicate and a data correction from input to visible result.

Guest records, stay context and current CRM capabilities are part of the single STRYK offer. There is no setup fee or hidden STRYK module tier; external messaging, payment or partner charges may apply separately.

In your demo access you search for a guest before creating a new record, open the complete profile with stays and invoices, answer a booking message, resolve a potential duplicate and handle a privacy request.

A guest is easy to find, has no unresolved duplicate and is connected to the correct stays. Contact data, privacy state and operationally relevant notes are current, while unnecessary or sensitive free text is avoided.