CHECK 01Select the Closest Help Route
Start from the help or contact area reached through the verified IM777 page. Pick the category closest to the issue, such as access, verification, app responsiveness, or profile activity log.
Don't move a technical question to social media because it feels faster. Public channels are poor places for profile information and might attract people pretending to be help.
- Select the correct category.
- Retain the conversation private.
- Steer clear of unverified help profiles.
- Use the official help page.
CHECK 02Write a Short Timeline
Begin with the last step that worked, then give the first issue, approximate time, and what happened next. Include the precise wording shown on page.
List the troubleshooting already completed so the reply does not ask you to repeat them. Mobile Device model, system version, and app or browser version are especially useful for technical problems.
- Include the full issue wording.
- Name the mobile device and software version.
- List tests already tried.
- State where the issue began.
CHECK 03Attach Evidence Without Secrets
Crop screenshots to the relevant area and hide personal information that the team does not need. Keep dates, state labels, and reference numbers visible when they explain the case.
Never send a password, recovery link, single-use code, or full payment credential. A real investigation can proceed without those secrets.
- Leave the useful timestamp visible.
- Redact unrelated personal data.
- Send no password or security code.
- Use one or two clear screenshots.
CHECK 04Follow One Ticket to the End
Keep a copy of the ticket number and reply in the same thread. Duplicate cases can split the evidence and make it harder to tell which answer is current.
If the listed response timeframe passes, send one polite follow-up with the reference. Add new evidence only when something has changed.
- Steer clear of opening copies.
- Follow up after the listed timeframe.
- Close the loop when resolved.
- Retain the ticket reference.