Guides

Executive impersonation takedowns vs manual reporting, which do you need

How manual reporting, platforms and managed takedown services handle fake executive profiles: who files, who follows up, authorization and cost.

ChainPatrol

Team

When a fake profile of your CEO appears, someone has to report it. The question is who, and how many times. Manual reporting means a person on your team files with the platform and waits. A platform with one-click reporting finds the fakes and gives you a button. A managed takedown service does the filing, the follow-up and the escalation. This guide sets the three side by side on what decides outcomes: who does the work, who follows up, how authorization is handled and what it costs.

We make ChainPatrol, so read this knowing where we sit. We describe how our own service works, and the points here apply to any vendor. If something is out of date, tell us and we’ll fix it.

Key takeaways

  • Manual reporting works for the first fake and gets harder with every one after it.

  • A platform solves detection, but every alert still needs someone to review it, file it and chase it.

  • A managed service owns filing and follow-up, in exchange for less hands-on control of each filing.

Side by side

Manual reporting

  • Who finds the fake: whoever notices.

  • Who files: your team.

  • Who follows up on a rejection: your team, if anyone remembers.

  • Authorization: you work out what each platform needs.

  • What your team does: searches, files and chases.

  • Cost: staff time.

Platform with one-click reporting

  • Who finds the fake: the platform’s detection.

  • Who files: your team, through the platform.

  • Who follows up on a rejection: your team.

  • Authorization: usually templates.

  • What your team does: reviews alerts and files.

  • Cost: license plus staff time.

Managed takedown service

  • Who finds the fake: the vendor’s detection and operations team.

  • Who files: the vendor.

  • Who follows up on a rejection: the vendor.

  • Authorization: prepared and kept on file by the vendor.

  • What your team does: reviews the cases that need a decision.

  • Cost: subscription.

Where manual reporting breaks

Manual reporting works for the first fake and gets harder with each one after it. Forms differ by platform, reports filed by someone other than the executive are often rejected, and the follow-up on a rejection rarely happens because nobody owns it. The fake stays live and keeps connecting with your staff. The hour spent filing is the smaller cost. The bigger one is every week the profile stays up.

Where a platform helps, and where it does not

A platform solves detection. It will find fakes faster than your team will notice them. It does not remove the queue: every alert still needs someone to review it, file it and chase it. If your fraud or security team is two people, the alerts can turn into a backlog. Ask any platform vendor what happens to an alert nobody clicks.

What a managed service changes

The vendor owns the outcome: detection, evidence, authorization, filing, re-filing and checking that the profile is really gone. You see the case list and reporting. The trade-off is less direct control over individual filings, which most teams are glad to give up.

At ChainPatrol, an operations team files and follows up each case. A letter of authorization is signed once during onboarding and attached to filings when a provider asks for it, and every case shows its status in the app. See executive impersonation protection for how it works.

How to decide

  • Only an occasional fake and someone on staff with time: manual reporting is fine. Keep a template and an authorization letter ready.

  • A security team that wants visibility and has capacity to work a queue: a platform.

  • Executives who are used as bait for investment or payment scams, or a team with no spare capacity: a managed service.

Questions to ask any vendor, including us

  • Who files the report, the executive or a representative, and where is the authorization kept?

  • What happens after a platform rejects a report?

  • Can I see every case, including the ones still open?

  • How many executives and profiles are covered, and what happens when someone new is added?

Frequently asked questions

How long does it take to remove a fake executive profile manually?

It depends on the platform and the evidence. Clear cases with the executive’s authorization can move quickly. Rejected reports and appeals can stretch for weeks, which is common when the report comes from a colleague instead of the executive.

Do we need a letter of authorization for executive takedowns?

For reports filed on someone’s behalf, platforms and hosts generally ask for one. A managed service like ChainPatrol drafts it during onboarding, keeps it on file and attaches it to filings.

Can we combine a platform with a managed service?

Yes. Some teams keep a platform for visibility and use a managed service for the filing. See running two brand protection vendors for how to split the work.

Want to see how this works on your executives? Book a demo.

Sources

Accessed November 2026. Check each source for the latest.

When a fake profile of your CEO appears, someone has to report it. The question is who, and how many times. Manual reporting means a person on your team files with the platform and waits. A platform with one-click reporting finds the fakes and gives you a button. A managed takedown service does the filing, the follow-up and the escalation. This guide sets the three side by side on what decides outcomes: who does the work, who follows up, how authorization is handled and what it costs.

We make ChainPatrol, so read this knowing where we sit. We describe how our own service works, and the points here apply to any vendor. If something is out of date, tell us and we’ll fix it.

Key takeaways

  • Manual reporting works for the first fake and gets harder with every one after it.

  • A platform solves detection, but every alert still needs someone to review it, file it and chase it.

  • A managed service owns filing and follow-up, in exchange for less hands-on control of each filing.

Side by side

Manual reporting

  • Who finds the fake: whoever notices.

  • Who files: your team.

  • Who follows up on a rejection: your team, if anyone remembers.

  • Authorization: you work out what each platform needs.

  • What your team does: searches, files and chases.

  • Cost: staff time.

Platform with one-click reporting

  • Who finds the fake: the platform’s detection.

  • Who files: your team, through the platform.

  • Who follows up on a rejection: your team.

  • Authorization: usually templates.

  • What your team does: reviews alerts and files.

  • Cost: license plus staff time.

Managed takedown service

  • Who finds the fake: the vendor’s detection and operations team.

  • Who files: the vendor.

  • Who follows up on a rejection: the vendor.

  • Authorization: prepared and kept on file by the vendor.

  • What your team does: reviews the cases that need a decision.

  • Cost: subscription.

Where manual reporting breaks

Manual reporting works for the first fake and gets harder with each one after it. Forms differ by platform, reports filed by someone other than the executive are often rejected, and the follow-up on a rejection rarely happens because nobody owns it. The fake stays live and keeps connecting with your staff. The hour spent filing is the smaller cost. The bigger one is every week the profile stays up.

Where a platform helps, and where it does not

A platform solves detection. It will find fakes faster than your team will notice them. It does not remove the queue: every alert still needs someone to review it, file it and chase it. If your fraud or security team is two people, the alerts can turn into a backlog. Ask any platform vendor what happens to an alert nobody clicks.

What a managed service changes

The vendor owns the outcome: detection, evidence, authorization, filing, re-filing and checking that the profile is really gone. You see the case list and reporting. The trade-off is less direct control over individual filings, which most teams are glad to give up.

At ChainPatrol, an operations team files and follows up each case. A letter of authorization is signed once during onboarding and attached to filings when a provider asks for it, and every case shows its status in the app. See executive impersonation protection for how it works.

How to decide

  • Only an occasional fake and someone on staff with time: manual reporting is fine. Keep a template and an authorization letter ready.

  • A security team that wants visibility and has capacity to work a queue: a platform.

  • Executives who are used as bait for investment or payment scams, or a team with no spare capacity: a managed service.

Questions to ask any vendor, including us

  • Who files the report, the executive or a representative, and where is the authorization kept?

  • What happens after a platform rejects a report?

  • Can I see every case, including the ones still open?

  • How many executives and profiles are covered, and what happens when someone new is added?

Frequently asked questions

How long does it take to remove a fake executive profile manually?

It depends on the platform and the evidence. Clear cases with the executive’s authorization can move quickly. Rejected reports and appeals can stretch for weeks, which is common when the report comes from a colleague instead of the executive.

Do we need a letter of authorization for executive takedowns?

For reports filed on someone’s behalf, platforms and hosts generally ask for one. A managed service like ChainPatrol drafts it during onboarding, keeps it on file and attaches it to filings.

Can we combine a platform with a managed service?

Yes. Some teams keep a platform for visibility and use a managed service for the filing. See running two brand protection vendors for how to split the work.

Want to see how this works on your executives? Book a demo.

Sources

Accessed November 2026. Check each source for the latest.

More buyer’s guides

How PhishFort and ChainPatrol compare on coverage, blocking before takedown, case visibility and fit, written by ChainPatrol.

ChainPatrol

Guides

Six brand protection and scam defense options crypto exchanges evaluate for fake support accounts, cloned logins, fake apps and phishing domains.

ChainPatrol

Guides

The main alternatives to PhishFort for phishing and impersonation takedowns, who each fits, and the questions to ask before you switch or add a vendor.

ChainPatrol

Guides