A single bad review is a customer service problem. Forty bad reviews in six hours, all posted after a price hike, a layoff story, or a founder’s bad tweet, is not a customer service problem at all. It is a coordinated signal, and most founders respond to it exactly the way they’d respond to one angry customer - a polite public reply, an apology, an offer to make it right - which is precisely the response that does nothing against a coordinated wave.
Why the usual playbook fails here
The standard advice for a bad review - acknowledge it, take it offline, fix what’s fixable - assumes the reviewer has a real grievance about a real transaction. Review bombing breaks that assumption. Many of the accounts posting have never used the product. The complaint is often generic, repeated nearly word for word across dozens of reviews, and timed to a single external trigger rather than to individual bad experiences spread across weeks.
Responding to each one individually, as if it were a real complaint, does two things wrong at once. It burns hours a small team doesn’t have, and it legitimizes the wave by treating coordinated noise as organic feedback - which is exactly the signal the platform’s own ranking algorithm picks up, pushing the brand’s rating down for everyone who searches it afterward, including the customers who were never part of the dispute.
What a real response actually requires
The founders who come out of this intact treat it as a platform integrity issue first, not a customer sentiment issue. That means documenting the pattern - timestamps, account ages, repeated phrasing - before responding publicly at all, and reporting the cluster to the platform through its abuse channel rather than arguing with each review in the comments.
It also means a short, factual public statement once, not fifty individual apologies. Something close to: here is what happened, here is what we’re doing about the underlying issue if there is one, and here is why this wave of reviews doesn’t reflect it. Said once, calmly, and left alone. Founders who keep re-engaging in every thread signal that the attack is working, which invites more of it.
The distinction that matters
Not every wave of bad reviews is coordinated, and treating every spike of criticism as an attack to be dismissed is its own failure mode - sometimes forty people really are angry about the same real thing, and that deserves the opposite response: fast, specific, and public about the fix. The job is telling the two apart quickly, because the tools for responding to a real grievance and the tools for responding to a coordinated one are not interchangeable, and using the wrong one is how a startup turns a one-week problem into a one-quarter reputation.