Online incidents reward speed, but they punish guesses. The most useful first response is a disciplined process that protects people, preserves the record, and gives decision-makers enough verified information to choose a proportionate next step.
Understand the situation before answering it
Review bombing is a sudden wave of ratings or comments from people who may be reacting to an online controversy rather than describing a genuine customer experience. A low rating alone is not proof of manipulation. The useful question is whether the reviews show a documented pattern that conflicts with the platform’s policies.
Owners often start by reading every review and replying to each one. That creates stress and can make the profile more chaotic. Start a log instead. Record what arrived, when it arrived, what the reviewer claims, and whether business records can connect the claim to a real interaction.
Start an incident log even if the situation seems small. Record the time, source, audience, known business facts, open questions, and decisions. Label information as confirmed, reported, or unknown. That simple distinction prevents an assumption from slowly becoming an “official fact” as messages move between owners, managers, employees, vendors, and advisers.
Do not make the public comment section your investigation room. Move fact gathering to a controlled workspace. Keep one unedited evidence set, one current timeline, and one list of approved messages. If new material changes the assessment, note what changed and when rather than silently rewriting the record.
Common mistakes that increase pressure
Calling every critic fake
Some reviews may reflect genuine experiences. Overclaiming weakens otherwise credible reports.
Coordinating positive reviews
Asking friends or employees to offset the attack can violate platform rules and damage the evidence.
Submitting vague reports
A report is stronger when it identifies a specific policy reason and a concise fact pattern.
Another common mistake is confusing visibility with importance. A loud post may have little effect on customers, while a quiet inquiry from a regulator, landlord, insurer, franchise partner, or key client may require immediate attention. Track the audiences that can affect safety, operations, and trust—not only the number displayed beneath a post.
A step-by-step response
- Establish the baseline. Record the normal review pace, average rating, and recent legitimate activity before the spike. This helps show what changed.
- Create a review log. For each suspicious review, capture the URL or identifier, account name, publication time, rating, text, and any stated experience.
- Classify carefully. Group reviews by possible policy issue such as off-topic commentary, harassment, conflict of interest, impersonation, or lack of a described experience.
- Report through official channels. Use the platform’s actual reporting flow. Keep explanations factual, short, and tied to policy language rather than the financial harm alone.
- Respond selectively. A neutral public response may help real customers understand that the business is reviewing unusual activity. Avoid accusing individual reviewers without proof.
Set review times instead of watching continuously. For an active incident, the team might check at agreed intervals for new source material, threats, media inquiries, changes in reach, or customer confusion. Between those checks, owners and staff need permission to return to normal operations. Constant monitoring increases anxiety and encourages unnecessary replies.
Evidence-preservation checklist
Preserve evidence before content is edited, deleted, hidden, or made private. Keep original files when possible and avoid marking them up. Store working copies separately. For each capture, record where it came from, who collected it, and the date and time. A useful incident folder includes:
- Profile URL and business listing identifier
- Before-and-after review counts
- Individual review links or platform IDs
- Screenshots with timestamps
- Repeated wording, timing, or account patterns
- Business records checked for a matching visit
- The post or forum directing people to the profile
- A written timeline that separates verified facts from allegations and open questions
- Copies of every platform report, confirmation number, appeal, and response
- Versions of public, employee, customer, or media messages with approval notes
Screenshots are useful but incomplete. Whenever feasible, also keep the URL, account identifier, full page context, and a screen recording showing how the content appeared. Do not access private accounts without authorization, impersonate another person, or ask employees to use personal accounts to gather material. Ethical preservation protects the credibility of the record.
How to communicate while facts are developing
A holding statement is not a miniature press release. It is a temporary bridge when a real audience needs acknowledgment before the review is complete. A sound holding statement can say that the business is aware, taking the concern seriously, reviewing the facts, supporting affected people, and using an identified channel for relevant information. It should not claim certainty the business does not have.
Different audiences need different information. Employees need operational guidance and a place to report threats or questions. Customers need to know what affects their experience. Reporters need a contact and a realistic response time. Platforms need policy-relevant evidence. Counsel needs an organized, complete record. Sending one long statement to everyone usually serves none of them well.
Before publication, ask four questions: Is every factual statement verified? Does this disclose private or protected information? Could this sentence be read as a threat, admission, diagnosis, or legal conclusion? Does the message help the audience make a practical decision? If the answer creates doubt, narrow the message and seek appropriate review.
When legal counsel or law enforcement may be appropriate
Speak with qualified counsel when reviews contain threats, impersonation, extortion demands, disclosure of private information, or serious factual allegations that may require a legal response. A lawyer can advise on subpoenas, preservation duties, defamation standards, or contact with law enforcement. Platforms make their own decisions, and no consultant can guarantee removal.
Criticism, a negative rating, or an angry tone alone is generally different from a credible threat. Do not use police reports or legal threats as public-relations props. Escalation should be based on safety and legal facts, documented privately, and handled through the proper channel.
Move from response to recovery
Recovery begins when the business can return to accurate, useful, normal communication without pretending the incident never happened. Close open stakeholder questions, correct business information, document commitments, support employees, and record what the response plan should change. Do not flood review platforms, manufacture praise, or publish excessive promotional content to “push down” criticism.
Choose a small set of measures: volume and source of new questions, unresolved platform reports, repeat customer concerns, staff safety reports, accuracy of listings and owned pages, and completion of promised actions. Review those measures at a defined point. A recovery plan is strongest when it has owners, dates, and a clear end condition.
A calm outside assessment can help
Main Street Resolve helps local businesses organize incident facts, preserve relevant evidence, prepare appropriate platform reports, and communicate with customers, staff, media, and other stakeholders. We do not guarantee removals, suppress legitimate experiences, or offer legal representation.