Choose the Closest Help channel
Start from the help or contact area reached via the official 77BE page. Pick the category closest to the problem, such as access, verification, app performance, or profile activity.
Don't move a technical question to social media since it feels faster. Public channels are poor places for profile information and might attract people pretending to be support.
- Work from the official help page.
- Choose the correct category.
- Hold on to the conversation private.
- Steer clear of unverified support accounts.
Write a Short Timeline
Start with the last step that worked, then give the first error, approximate time, and what happened next. Include the precise wording provided on page.
List the checks already completed so the reply doesn't ask you to repeat them. Device model, system version, and app or browser version are especially practical for technical problems.
- State where the problem began.
- Include the full on-page error.
- Name the phone or tablet and software version.
- List tests already tried.
Attach Evidence Without Secrets
Crop screenshots to the related area and hide personal specifics that the team doesn't need. Keep dates, status labels, and case references visible when they explain the case.
Never send a password, recovery link, single-use code, or full payment credential. A real investigation may proceed without those secrets.
- Choose one or two clear screenshots.
- Hold on to the practical timestamp visible.
- Redact unrelated personal data.
- Send no password or security code.
Follow One Ticket to the End
Hold on to the ticket number and reply in the same thread. Duplicate cases may split the evidence and make it harder to tell which answer is latest.
If the published response period passes, send one polite follow-up with the reference. Add new evidence only when something has changed.
- Hold on to the ticket reference.
- Steer clear of opening copies.
- Follow up after the published period.
- Close the loop when resolved.