What Support can help with
Support can help with account access, email confirmation, profile settings, location, Radar, Knocks, chat, plans, payments and verification. For a possible rules violation by a specific person, also use the built-in report action.
A request becomes a separate ticket with a subject and description. The authorised team can review it; status and response appear in Support, and an important update may generate an in-app notification. Avoid multiple identical tickets because they make investigation harder.
Precise facts make a problem easier to reproduce: include the section, action sequence, time, error text and platform. Never provide a password, confirmation code, full card number, CVV or secret key, even to someone claiming to be Support.
What in-app Support provides
One coherent history
The problem description, status and reply remain in the account instead of being lost across messengers.
Product context
The team sees the request category and can route it to payments, verification or safety.
A protected channel
There is no need to find an administrator’s personal contact or send secrets to an outsider.
How to create a useful request
-
Step 1
Choose a clear subject
Summarise the problem, such as “plan did not update” or “location cannot be detected”.
-
Step 2
Describe the steps
State what you did, what result you expected and what actually happened.
-
Step 3
Add safe context
Include time, device, interface language and exact error text, but no password or payment secrets.
-
Step 4
Follow the reply
Return to the section or check notifications, then continue within the existing ticket context.
Questions about Support
Where does the reply appear?
The reply appears in the application’s Support section and may be accompanied by an in-app notification.
Can I send a password or banking data?
No. Support should never require your password, confirmation code, CVV or complete payment credentials.