Skip to content

Guides

Spot an account takeover in a support request

Attackers often use support to get into an account. A few checks and a firm habit of never skipping them protect your customers without making real ones jump through hoops.

Last reviewed

Know the usual red flags

Watch for urgency, a new email address that differs slightly from the one on file, a request to change the email or phone first, and refusal to use the registered address.

Verify with what the attacker lacks

Ask for something only the owner can see in the product, such as a recent invoice amount or a project name. Do not ask for details that can be found online.

Never reset to a new address on request

Send resets and changes only to the address already on file. If the customer lost access to it, use a slower route with extra proof.

Treat payment changes as high risk

Changing a payout account or card should need more checks than a password reset. Write the extra steps down and apply them every time.

Log and tell the owner

Record what was asked and what you checked. If the account was taken over, tell the real owner on the registered address and help them secure it.

Do not make it personal

Explain that the checks protect the account. Real customers accept this; people who push to skip it are telling you something.

Questions

What should I ask to verify someone?

Something only the account owner would see in the product, not facts that can be found online.

What if the customer has lost their email?

Use a slower route with more proof, and never change the address on a single message.

Should payout changes need more checks?

Yes. Changes that move money are higher risk than a password reset and should need extra verification.

Written by Flatdesk, a help desk for small support teams at one flat price per agent. Try it free for 14 days, no card.