Classify the incident before responding
Create a triage matrix with four dimensions: potential harm, confidence in the facts, reach and urgency. Routine incorrect product information may need a factual correction. An account using the brand's logo to solicit payments may require urgent platform reporting and customer warnings. A credible threat to someone's safety needs escalation through the organization's safety process, not a standard social reply.
Assign levels such as monitor, respond, escalate and emergency. Write observable criteria for each level instead of asking community managers to infer intent. For example, 'profile claims to be our support team and requests card details by direct message' is an actionable impersonation indicator; 'user disagrees with our policy' is not.
Capture evidence without amplifying the claim
Record the post or profile URL, platform, username, timestamp, screenshots, exact claim, visible reach indicators and relevant internal account history. Note when a screenshot was taken because posts can be edited or deleted. Store evidence in access-controlled systems and redact personal data that is not necessary to investigate the incident.
Avoid quoting a dangerous false claim in a way that spreads it to new audiences. For public corrections, lead with the verified information and direct users to an official source. If the allegation is unresolved, acknowledge that it is being checked rather than declaring it false. Never invent an investigation outcome to fill the silence.
Protect accounts and customers first
For suspected impersonation, verify official account handles and links from a trusted internal registry. Report the fake profile through the platform's impersonation process, preserve the report confirmation and notify account security owners. Check whether the real account has unusual sessions, changed admins, unauthorized connected apps or new payment requests.
If customers may have been tricked, publish a concise warning from verified channels explaining what the brand will never request in direct messages. Direct affected people to a safe support route. Do not ask them to post payment information, screenshots of identity documents or passwords publicly. Coordinate with legal, security and customer support before naming suspected actors.
Write response templates with decision rights
Prepare separate approved language for misinformation correction, suspected scam, impersonation warning, account compromise and unresolved allegation. Templates should contain verified facts, one safe next step and a route to support. Define who can approve each response: community lead for low-risk corrections, communications and legal for reputational incidents, security for suspected account compromise.
Use a single incident owner to prevent the brand from issuing conflicting statements across Facebook, Instagram, LinkedIn and other channels. Log what was posted, by whom, when and whether the platform removed the offending content. Do not promise a platform takedown time you cannot control.
Monitor after the initial response
Track whether the false claim is being repeated, whether new fake accounts appear and whether customers are asking the same question. Review direct messages and support tickets for evidence of actual harm. A one-time reply may not be enough when an impersonation campaign moves between platforms or uses paid ads.
Use an escalation clock based on risk, not vanity engagement. A low-reach scam asking for payment can be more urgent than a viral complaint about a late delivery. Monitor after hours only to the extent the organization has assigned coverage; an escalation policy that assumes a single employee is always online will fail.
Close the loop and prevent recurrence
Close each incident with a timeline, impact assessment, platform actions, customer communications, unresolved risks and prevention steps. Update the official-account directory, access permissions, two-factor authentication and staff training if weaknesses emerged. Review incident patterns monthly to identify repeat impersonators and recurring misunderstandings that better product information could prevent.
Pair this workflow with the site's social customer-care guide and UGC rights clearance article. Use the UTM Builder for links in official corrective posts so response traffic can be distinguished from normal campaigns. Success means reduced customer harm and faster resolution, not simply fewer negative comments.