A useful request describes the problem, not your secrets
A technician needs the device type, symptom, exact message, timing, recent changes, and desired outcome. That is enough to begin intake. A password does not make the description better.
Never place these items in a form or email
Do not submit passwords, PINs, one-time codes, recovery codes, payment-card details, private keys, government identification, medical records, customer lists, or private business documents.
Share screenshots carefully
A screenshot can expose names, email addresses, account numbers, browser tabs, file names, and notifications. Crop the image to the relevant non-sensitive message and review every visible area before sending it.
Verify the support path
Start from a contact method you independently know belongs to the provider. Do not call a number supplied by an unexpected pop-up, and do not allow remote access because an unsolicited caller creates urgency.
Enter credentials yourself
During legitimate support, the account owner can enter a password privately. If a task requires a code or approval, ask why, confirm the domain or application, and do not read the secret aloud.
General guidance cannot diagnose every device or security event. Stop if a step risks data, access, hardware, or personal safety.