Help straight from STRYK, with your hotel’s context.
If a balance does not add up at check-out, you open a support case right in STRYK. The support assistant first looks for an answer in our guides. If that is not enough, we, the STRYK team, take over with the area, description and screenshot, and questions, answers and the solution stay in one thread.

With context
The area you came from is sent to us automatically with the case.
Help first, then people
The support assistant looks for answers in the STRYK guides.
One thread
Questions, answers, status and solution on one case.
Data-minimising
STRYK strips credentials and typical personal data before passing text on.
A case with topic, urgency and screenshot.
You choose a topic and urgency, describe what happened and what you expected, and attach a screenshot if needed. The area you came from is sent along. That lets our team place the case correctly without first asking where the problem is.
- Topic and urgency
- Screenshot as PNG, JPEG or WebP
- Current work area sent along
- Active cases and archive with filters and search
The quick answer first. A person when it is not enough.
Before a case is created, the AI support assistant searches the STRYK guides and help articles for a solution. If the answer does not fit, it hands the case to the STRYK team with everything recorded so far. We think nobody should have to tell their story twice.
- Answers from the STRYK guides
- Sources with each answer
- Handover to the STRYK team
- Details you entered are kept
Question, answer and solution stay on the same case.
All messages stay in one conversation, and the timeline shows creation, status changes and replies. Once the problem is solved, you confirm the solution and rate the case. If it comes back, you reopen the same case with a reason, and the earlier diagnosis is kept.
- Shared conversation
- Timeline with status and owner
- Confirm and rate the solution
- Reopen resolved cases
Guides right where you are working.
Every area has its own help menu, and the help reader shows guides from the same editorial team as our website, in 18 languages. You send us requests and ideas as product feedback straight from STRYK. For closer support there are full-service packages.
- Help menu in every area
- Help reader with guides
- Product feedback from STRYK
- Full-service packages for more support
From problem to confirmed solution.
Our rule: one case, one thread, from the first report to confirmation.
- 01
Look for help
The support assistant checks the guides for your problem.
- 02
Open a case
Topic, urgency, description and screenshot, with the area sent along.
- 03
Work it out together
Questions and answers run in the same thread.
- 04
Confirm the solution
You confirm and rate it, and reopen the case if needed.
Part of your complete system.
Support, help and onboarding all draw on the same hotel context. So we know what it is about before we reply.
Common questions: STRYK support
What makes STRYK support different?
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.
Who helps me in STRYK Support?
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.
Which details make a good support request?
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.
Can a screenshot be attached?
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.
How is severity selected?
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.
Does STRYK first look for direct help?
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.
Show more questions
Where does the team see open requests?
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.
Can support history be searched and filtered?
Yes. Status, topic, severity and other columns help find an existing request before a duplicate is created for the same issue.
How does communication work after creation?
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.
Which status information is visible?
The request shows its current state, latest update and relevant timeline steps. Received, read and answered messages remain distinguishable in the thread.
Can the property see who is handling the request?
Yes. The detail view shows ownership and current progress, so the team always knows whether the request is open, in progress or resolved.
Can the property answer follow-up questions?
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.
What does a support request timeline show?
Creation, status changes, replies, resolution and possible reactivation are combined chronologically. The property can see what has happened and which step remains open.
How is a request closed as resolved?
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.
Can a resolved request be reopened?
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.
Who may see support requests?
Only authorised employees of the signed-in property can see its support history. Requests and answers from other properties remain fully separated.
Which data should a screenshot avoid?
Unnecessary identity, card, health or other sensitive guest data should be removed or obscured before attachment. The operationally relevant crop is usually sufficient.
What should the team check before reporting an incident?
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.
Does public documentation provide additional help?
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.
How does STRYK support help with an issue?
The request starts in the right hotel area. History, ownership and next steps stay together until your team confirms the resolution.
Is there a guaranteed response time?
Binding response or service times depend on the applicable support agreement.
What does STRYK support cost?
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.
What can you try with support in your demo access?
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.
Get to know our support.
Try STRYK for 14 days and ask your first question right in the program, or we will show you the support centre in a demo.