Why did the platform reject my report?

Platform abuse forms are tuned for high volume and clear-cut categories. Brand impersonation, defamation and commercial fraud often fall outside the automated triggers, so a real violation gets a template rejection within minutes. Rejection is not a ruling on the merits — it usually means no human read it.

Can I appeal a rejected report?

Most platforms have a legal or IP channel that is separate from the in-app "report" button and is held to a different standard. A properly framed legal notice — naming the trademark, the statute or the personal-data breach — routes to a team that must respond, not to the automated queue that rejected you.

They keep making new accounts/sites after each removal. What stops that?

One-by-one reporting cannot win against automated re-creation. Escalation to the host, registrar or platform legal desk — plus deindexing the search results that send traffic to each new copy — attacks the operation rather than the individual copy.

Is it worth getting a lawyer for a single fake account?

For one isolated account, the platform's legal form is usually enough and you do not need us. It becomes a counsel matter when it recurs, when customers are losing money, or when it sits alongside other attacks on your brand.

Platform Won't Remove a Fake Account or Post? Next Steps

Short answer: a rejected report almost never means your case is weak — it means it went to an automated queue built for volume, not to a human who read it. There is a second door at almost every platform: a legal / IP channel held to a different standard, where a notice naming a statute has to be answered. If the problem also keeps regenerating, the fix is to stop reporting copies and start escalating the operation. Here is the map.

Why the front-door report failed

The in-app “Report” button is designed to triage millions of flags a day. It pattern-matches against a narrow set of obvious categories — spam, nudity, direct threats — and rejects almost everything else automatically, often within minutes. Brand impersonation, commercial fraud and defamation frequently do not trip those triggers, so a genuine violation gets a “this does not go against our Community Guidelines” template. No human saw it. The rejection is a routing outcome, not a verdict.

There is also a structural reason platforms are slow here: removing a business-dispute item carries its own liability if they get it wrong, so the automated layer is deliberately conservative and pushes anything ambiguous back to you.

The second door: the legal / IP channel

Almost every major platform runs a separate intake for legal claims that is not the report button:

Trademark / IP complaints — if the fake uses your logo, name or product images, this is usually the fastest lever, because platforms have a legal obligation around IP that they do not have around “this account is fake”.
Defamation / court-order channels — for false statements of fact, routed to legal, not moderation.
Personal-data / privacy requests — GDPR Article 17 and equivalents, for content exposing an individual’s data.

The difference is not the effort — it is the framing. A notice that names the trademark registration number, the statutory basis, or the specific false factual assertion is processed by a team that must respond. The same underlying complaint, sent as “please remove this fake account”, is the one that got rejected.

What you can do yourself, properly this time

Re-file through the legal channel, not the app. Find the platform’s IP / legal reporting form (it exists; it is just not the obvious button) and frame the claim under a named ground.
Attach proof of standing. Trademark certificate, company registry extract, the original asset they copied. Most legal forms ask for it; supplying it up front skips a round-trip.
Document the rejection. Keep the reference number and the template reply — a record that you used the platform’s own process and it failed is useful if the matter escalates.
Map the pattern. If new copies appear after each removal, list them all with timestamps. That is evidence of a coordinated operation, which changes the available remedies.

Where even the legal channel stops

Two situations defeat the do-it-yourself legal route: when the platform itself will not act despite a valid notice, and when the content regenerates faster than you can file. A single fake site goes down and a mirror appears on a new host overnight; an account is removed and three more open. Reporting individual copies is a treadmill the operator is happy to keep you on.

At that point the target is no longer the copy — it is the infrastructure behind it: the host (usually hidden behind a proxy like Cloudflare, so the first job is finding the real host behind it), the registrar, the search results that feed it traffic, and where applicable the operator’s identity.

What the counsel route adds

Standing and escalation. A counsel notice reaches the platform’s legal desk above the abuse queue, and where the platform stalls, it escalates to the host and registrar — parties with their own legal exposure who are rarely anonymous.
Search deindexing in parallel. Even copies that survive on new hosts stop reaching users when the URLs are removed from search under statute.
Operation-level pressure. Recurring impersonation is treated as one matter against one operator, not as an endless series of single reports.

Every step is filed under a named authority — trademark law, DMCA §512, GDPR Article 17, defamation — never as a payment or a threat. If a single account is your whole problem, the legal form above will likely solve it and you will not need us. When it recurs, targets your customers, or comes bundled with the rest of an attack, that is the matter we take.

You reported it and nothing happened. What now.