IS7 Game Support: How to Report a Problem
A clear problem report saves back-and-forth. Find the provider’s support route, describe what happened, and include the reference that identifies the issue without exposing private information.
Start from a channel you can verify
Use support information shown inside your installed IS7 app or through a provider channel you have independently verified. A familiar logo or a name containing IS7 does not establish that a social account can access or resolve your case.
This website provides information and a referral download link. It does not operate the app’s account, payment or game-support systems. We have not listed a support phone number, email address or chat account because those details have not been verified.
Gather the details that identify the issue
- Where it happened: the app screen and, for a game issue, the exact game title.
- When it happened: the date, approximate time and your time zone.
- What you did: the action immediately before the problem, followed by what appeared on screen.
- The reference: a round ID, transaction ID or existing case number, if supplied.
- What you tried: brief checks such as reopening the app, with the result of each.
Use a short report format
A practical format is: ‘On [date and time], I was on [screen or game]. After [action], I saw [message or result]. I expected [normal behaviour]. The reference is [ID]. I tried [check], and [what happened].’ Replace the brackets with the facts of your case.
Describe what you observed rather than guessing the cause. ‘The page stayed blank after I selected the game’ gives support something to investigate. ‘Your server is broken’ adds a conclusion that the available evidence may not support.
Share screenshots carefully
Keep the error message visible, along with the relevant screen label. Hide passwords, verification codes, unrelated personal messages and full payment details. If identity verification is requested, use the provider’s verified process rather than sending documents to an unsolicited contact.
Keep your own copy of the report and any case number. When following up, refer to the same issue and add new information. Repeating the report across unrelated accounts can make it harder to track which response belongs to your case.
Choose the relevant reference
For an unresponsive app, start with loading problems. For an account entry, use wallet records. If a message itself looks suspicious, read account security before sharing more information.