What do you need to understand first?
A helpful-looking reply can appear after you ask a public question. The person may copy a profile and refer to your exact issue. Knowing the problem does not establish authority to handle your secrets.
What might this look like?
You mention a stuck transfer in a public discussion. A direct message offers to synchronise your wallet through a supplied page. The page asks for recovery words. Leave it; synchronisation language does not make that disclosure necessary.
Where is the safety checkpoint?
How can you work through it?
Stop the supplied process
Close the link and decline remote access. Do not continue just to see what the helper will ask next.
Find help independently
Use a route you already trust or locate documentation yourself. Compare the entire website address rather than the profile name.
Keep secrets out of the conversation
A receiving reference can help describe an issue, but recovery words and private keys must never be sent for checking.
Save evidence if needed
Keep messages and website addresses without secrets. If access was exposed, use the scam-response guide and verified reporting channels.
When should you pause?
Someone claiming to be an administrator has not proved it. You can leave the conversation and ask for help without giving the sender another chance to pressure you.