Contact IX5 Support With a Complete, Focused Case
A good support request gives the reviewer a clear problem, a traceable account or event and evidence that can be checked without asking for secrets.
Support cannot reconstruct a match from “it did not work.” Describe the expected action, actual result and the time it happened. Then include only the account and technical details relevant to that issue.
Write a subject that identifies the queue
Use a subject such as “OTP not arriving,” “roster rejected before lock” or “match 438 score review.” A precise subject helps routing before the case is read in full.
Avoid putting several unrelated problems into one case. Separate incidents may involve different account, technical and event records.
- State the affected feature.
- Add the event or match reference.
- Mention whether a deadline is approaching.
- Do not label every issue “urgent”.
Describe the smallest reproducible timeline
List the last successful step, the action that failed and the screen that followed. Include the approximate time and time zone; this allows logs to be compared with your report.
Screenshots should show the full message and enough surrounding interface to identify the page. Remove unrelated personal notifications.
Match the evidence to the issue
A login problem needs device, app version and error wording. A scoring review needs match ID, the rule in question and permitted match evidence. A prize administration question needs the event result and account status.
More files are not automatically better. Unrelated uploads increase review time and privacy exposure.
- Never include passwords or OTPs.
- Do not send full card or bank credentials.
- Use supported file formats.
- Keep the case reference after submission.
Reply in the same thread and confirm the outcome
Add requested information to the existing case. Opening duplicates can split the record and make it unclear which response is current.
After a fix, verify it in the account or event page. If the outcome is still wrong, explain what changed since the first report rather than starting the story again.
Related reading for Contact IX5 Support Effectively
Useful answers before the next match
Show the complete error and enough page context to identify the action, while hiding unrelated personal information.
Usually not. Continue in one case unless support closes it or instructs you to create another.
Passwords, OTPs, full payment credentials and unrelated identity documents.
