Protect the account while you solve the problem.

Sign-in prompt

Access requirements can appear after entry

An information page may open without an account while matching asks you to sign in. That difference should not be described as anonymous access. Use the provider button or email route displayed in the live flow and check the domain before entering credentials.

If a provider opens a new window, read its domain as well. Do not send a code to a person in chat who says they can activate your account. A one-time code is a key, not a support ticket.

• Check the domain before entering a password.
• Use a password unique to the account when email sign-in is offered.
• Keep recovery email and phone access secure.
• Never approve a sign-in you did not initiate.

Recovery

Secure the recovery channel first

If your email account is compromised, resetting the chat account alone may not hold. Change the email password, review active sessions and enable stronger authentication where available. Then use the product’s official recovery flow.

Do not create repeated new accounts to work around an unresolved restriction or billing issue. That can complicate ownership and receipts. Keep the error text and account identifier needed by support, but remove passwords and full payment details.

1. 1
   Secure email or provider

   Change exposed credentials and review unfamiliar sessions.

2. 2
   Use official recovery

   Start from the service or identity provider, not a message link.

3. 3
   Document the result

   Record the time and exact error if escalation is still needed.

Suspicious access

Treat unexpected codes as a warning

An unsolicited code or sign-in notification can mean someone typed your address by mistake or is attempting access. Do not forward the code. Open the relevant service directly, review sessions and change a reused password.

If a participant asked for the code, block and report them. If money or payment identity is involved, contact the provider using its official route.