Get support without repeating the whole story.

A support request starts directly in the signed-in property context. Area, user, description, history and optional screenshot stay together so every follow-up does not restart from zero.

STRYK Support AI responds first. It answers questions directly and guides you step by step. When personal clarification is needed, our team continues in the same conversation.

A clear topic, suitable severity, concise subject, observed behaviour, expected result and steps leading to the issue. Personal data belongs there only when genuinely required for resolution.

Yes. A relevant screenshot can be selected directly on a new request. STRYK checks file type and size and surfaces invalid attachments rather than silently discarding them.

The property selects an operationally appropriate level. Urgent means a case that concretely blocks live hotel operations, while a general question or cosmetic issue receives lower priority.

Yes. Before creation, the support assistant can look for relevant help for the described problem. If that is not enough, it becomes a complete support request with the context already captured.

The overview separates active requests and archive. Subject, status, topic, severity, requester and latest update can be shown and sorted according to the team’s workflow.

Yes. Status, topic, severity and other columns help find an existing request before a duplicate is created for the same issue.

All replies remain in one conversation. The property team and STRYK support see the same thread, while new information is added to the existing request instead of being lost across scattered emails.

The request shows its current state, latest update and relevant timeline steps. Received, read and answered messages remain distinguishable in the thread.

Yes. The detail view shows ownership and current progress, so the team always knows whether the request is open, in progress or resolved.

Yes. While the request remains replyable, the team adds its message directly to the thread. Follow-up, answer and next review therefore remain in the correct order.

Creation, status changes, replies, resolution and possible reactivation are combined chronologically. The property can see what has happened and which step remains open.

The property can confirm the resolution, give a satisfaction rating and optionally comment. The request moves to the archive under control and remains available for later traceability.

Yes. If the same issue returns or the solution does not hold, the existing request is reactivated with a reason. Previous diagnosis remains available instead of creating a second disconnected history.

Only authorised employees of the signed-in property can see its support history. Requests and answers from other properties remain fully separated.

Unnecessary identity, card, health or other sensitive guest data should be removed or obscured before attachment. The operationally relevant crop is usually sufficient.

Reopen the affected process, note the visible error, review date range and user role and check whether the issue can be reproduced. The request can then be classified much faster.

Yes. Step-by-step guides explain common workflows with prerequisites, workflow visualizations, success signals and typical errors. Support requests remain the direct route for individual incidents and unresolved questions.

The request starts in the right hotel area. History, ownership and next steps stay together until your team confirms the resolution.

Binding response or service times depend on the applicable support agreement.

The support centre, request history and public documentation are part of the single STRYK offer, with no setup fee or hidden support module tier. External partner costs or individual additional services may apply separately.

In your demo access you create a request with the affected area, topic, urgency and screenshot, receive the answer in the shared conversation and try resolution, rating and reopening.