Arrival emails, without writing each one from scratch.

STRYK reacts to real events around booking, stay, payment and invoice. These produce targeted messages or internal work steps rather than rigid bulk emails without booking context.

Examples include new or confirmed booking, modification, cancellation and no-show. Each rule also decides which sources, room categories and guests it may apply to.

Yes. Pre-arrival rules run at a defined interval before arrival and can trigger personal information or an online check-in reminder, for example.

Check-in, completed online check-in, long stay, checkout, post-departure and review request can each trigger their own workflows. Communication therefore matches the actual travel state.

Yes. Payment received, payment due and invoice created are separate triggers. The rule remains attached to the correct booking and finance context and cannot be confused with an arbitrary guest.

STRYK sends relevant guest messages, alerts the team, marks stays, creates housekeeping tasks and adds internal notes. Approved partner systems can also be included in the workflow.

It uses a central template and only placeholders that can actually be resolved in the current booking context. Subject, content, guest details and delivery path are reviewed before activation.

In automatic mode, channel follows booking context: direct and manual stays use email, while connected OTA stays use their permitted booking channel. The team does not have to guess the channel for every guest.

Yes. Minutes, hours or days before or after a suitable event can be defined. Timing is calculated from the real stay date.

Conditions limit the rule by length of stay, booking value, lead time, guest count, country, weekday, source, room category, tag, visit history and other attributes.

Yes. Rules can apply only to first-time visitors, returning guests, VIPs or guests above a defined visit or lifetime-value history.

A rule can require an existing tag, deliberately skip another tag or add or remove a tag after success. This helps prevent duplicate or conflicting workflows.

Yes. Title, description and priority are created in booking context. The task complements operations but does not replace the occupancy-based housekeeping daily plan.

Yes. An authorised administrator decides which information is passed to which destination. Failed handovers remain visible and can be retried deliberately.

A rule can be limited to one execution per booking. A validity period, priority and daily limit provide additional protection against unintended repetition.

A test run checks trigger, conditions and action with safe test context. The result is logged as a test, and the rule is activated only after operational review.

Success, failed, skipped and test remain traceable with time, booking, guest, trigger, action and detail. A failure is not disguised as an apparently successful send.

Overview and editor show enabled state, last run and today’s executions. A disabled rule or one outside its validity window triggers no action.

Only employees with dedicated automation-management permission. Read-only or housekeeping roles cannot activate rules that contact guests or trigger external systems.

Start with a clear booking confirmation, one pre-arrival message and an internal review for outstanding payment. Three well-tested rules create more value than a confusing forest of automations.

STRYK reviews the updated stay and recalculates timed steps from the new travel dates. Completed or deliberately excluded actions are not repeated without control.

Core automations, templates, test runs and logs are in the base price. After three free trial months, STRYK Guest AI optionally expands communication; external delivery or integration partners may charge their own fees.

In your demo access you build a rule from trigger through conditions and template to a test run. You then see exactly when it ran and what result it produced.