Reply with the right stay in view.

STRYK keeps manual messages as a conversation attached to a specific booking. Guest, stay, dates, room, channel and delivery state therefore remain traceable together.

A guest may have several stays booked. Check the dates and room for the selected stay before replying, so arrival or breakfast information relates to the right visit.

In the guest area or directly from guest details. The team selects the relevant booking there and then continues in the same conversation.

No. The channel is derived from the booking source. This keeps a direct booking in the email flow and an OTA booking in its intended channel context.

Direct, manual, phone, walk-in, website and STRYK Booking Engine reservations use email conversations. A valid guest email address is required for delivery.

STRYK recognises bookings from connected portals and keeps the message in the relevant booking conversation. Messages to portal guests are sent via the portal, this is available for Booking.com and Airbnb, provided the portal is connected for your hotel. Direct and manual bookings use email.

Yes. Emails can be created as clear plain text or HTML and reviewed before sending. Channel messages deliberately remain plain text.

The property maintains recurring content such as arrival instructions, parking information or departure messages centrally. Active templates reduce work without losing booking context.

The central placeholder catalogue can offer resolvable guest, booking, room, price and property data for the current context. A template therefore becomes a specific message for that stay.

The preview combines subject and body with the details from the selected booking. Any unresolved placeholders are listed visibly before the team can send.

Yes. When a returning guest has several stays, the team deliberately selects the relevant booking. Messages are not mixed indiscriminately in the guest profile.

Email delivery stops with a clear error. The team adds the contact details first instead of creating an apparently sent message.

Yes. Sent and incoming entries remain readable against guest and booking with direction, channel, subject, body, state and time.

The property can use the STRYK inbox or a connected mailbox. Forwarding or IMAP must be genuinely configured and tested before replies are assigned to the relevant booking thread.

Unread incoming messages appear in the shared message and notification context. The team can open them and deliberately mark them read.

Reading and sending depend on dedicated permissions. An employee receives access to guests and messages only when the role genuinely requires that work.

Successful delivery creates a message state and activity entry with booking, guest, channel and subject. Failures are not recorded as success.

Yes. Hotel automations can trigger active templates along the stay. Conditions, test runs, execution history and error control remain visible in the automation area.

STRYK runs in the browser; authorised users open booking conversations, recent messages and unread entries there with the same permissions. The same applies in the STRYK app for iPhone and Android.

Yes. Messages, templates, bookings and guests remain clearly assigned to the relevant property. A booking from another property can never be used as message context.

Check the displayed delivery status and any recipient or mailbox errors. If the outcome is unclear, resolve the existing send request before sending the same message again.

Yes. As an alternative to prepared STRYK delivery, a Google, Microsoft, IONOS or other mailbox can be connected through tested SMTP configuration. The external mail provider may charge its own fees.

Guest communication is part of STRYK Guest AI. Try free for 1 month. + €4.00 per room and €6.00 per apartment or holiday home per month. Guest AI is billed in advance; Intelligent Pricing is billed for the previous month. After the trial, both modules can be cancelled at any time effective at month-end; the STRYK contract’s three-month notice period does not apply. Guest AI periods expressly ordered with annual billing are committed from the order until the agreed annual service period ends, irrespective of payment receipt. Cancellation at that date can be recorded at any time; ordinary cancellation does not entitle the customer to a proportional refund of annual fees. Intelligent Pricing remains cancellable monthly even with annual STRYK payment. Statutory rights concerning defects, billing errors or justified extraordinary termination remain unaffected. 12-month contract, with cancellation notice due three months before the term ends. Without cancellation, the contract renews for 12 months. Monthly payment is the default. A switch to annual prepayment takes effect on the next billing date and starts a new 12-month term. Becomes paid after one calendar month unless cancelled.