A customer leaves a review you think is unfair, exaggerated, or flat-out wrong. You're angry, you type exactly what you're thinking, and you hit post. Most of the time nothing happens beyond a bruised ego on either side. But every so often a reply turns into a process server at the door. It doesn't happen because a business replied. It happens because of what the reply actually said.
The quick answer
Google review replies are public statements, and public statements carry the same basic legal rules whether they're posted by a customer or a business. Opinion is protected. False statements of fact are not. A reply that says 'we disagree with this account' or 'this isn't what our records show' is opinion, and opinion, however blunt, almost never crosses into defamation. A reply that says 'this customer stole from us' or accuses someone of a specific crime you can't prove is a factual claim, and if it's false, that's exactly the kind of statement defamation law exists to punish.
The good news: this threshold is genuinely hard to clear by accident. Most owners never come close to it, because most angry replies are opinion dressed up as frustration, not false factual claims. The cases that do happen share a specific shape, which is worth knowing so you can recognize it before you type it.
What actually makes a reply defamatory
Courts generally look for the same three things before a reply crosses the line, regardless of who wrote it.
- A false statement of fact, not opinion. 'They're a liar' stated as a fact is different from 'I think they're being unfair.' The more specific and provable the claim, the riskier it is if it isn't true.
- Publication. Posting it publicly, which a review reply always is, satisfies this automatically. There's no private version of a Google reply.
- Real harm. The statement has to cause actual reputational or financial damage to a specific, identifiable person, not just hurt feelings.
Truth is a complete defense. If what you said genuinely happened and you can back it up, there's no valid claim no matter how harsh it reads. The risk sits specifically in accusations you can't prove, aimed at a person your reader can identify.
A real case: the reply that became a lawsuit
In March 2025, a one-star Google review turned into an active lawsuit for a Wisconsin bar owner, and the timeline shows exactly how a reply escalates into real legal exposure. A customer, Brynn Dutelle, visited The Drunk Uncle in West Allis and left a review describing an uncomfortable interaction with the owner and a bartender. The owner, Neal Steffek, replied publicly: 'You are a fat nerd with no friends. That girl was hot AF for this giant snake.'
That reply alone, crude as it is, is closer to insult than defamation; ugly opinion is still opinion. The lawsuit didn't come from the reply itself. It came from what happened next: according to reporting from WISN and the Milwaukee Journal Sentinel, Steffek then posted on Dutelle's employer's Facebook page accusing her of sexually assaulting a bar employee, alongside her photo and her name as a district employee. Dutelle sued for defamation and retaliation on March 14, 2025. Two months later, West Allis's Common Council voted 9-0 to revoke the bar's liquor license, citing the lawsuit among other complaints.
The lesson isn't 'never reply when you're angry,' it's narrower than that: the legal exposure came from a specific false accusation, aimed at a named person, carried to a new audience. A rude reply under the review itself, however unwise, is a very different thing from that.
What turns a firm reply into a risky one
The pattern from real cases is consistent enough to name specifically. Watch for these in your own draft before you post it.
- Describe what happened from your side, stated as fact you can back up
- Say plainly that you disagree with the characterization, that's opinion and protected
- Move detailed disputes to a phone call or email instead of relitigating them publicly
- Wait a few hours if you're still angry before replying at all
- Accuse the reviewer of a crime, fraud, or dishonesty you can't document
- Post about the reviewer anywhere other than directly under their own review
- Share private details about them that weren't already in their review
- Reply while you're still angry about what they wrote
What's safe to say, even when you're right
You don't have to stay silent on an unfair review, and you don't have to grovel either. Correcting a factual inaccuracy about your business is safe if it's true: wrong dates, wrong service, wrong price, whatever your records actually show. Stating your own account of events is safe. Declining to relitigate private details of the transaction in public, and offering to continue the conversation directly, is safe and usually looks better to the next reader than either side airing everything.
Thank you for sharing this. Our records show a different sequence of events than what's described here, and we'd like to walk through the details with you directly, please reach out through the contact information on our profile. We take feedback like this seriously and have reviewed the interaction with our team.
Notice what that reply doesn't do: it doesn't call the reviewer a liar, doesn't accuse them of anything, and doesn't argue the specifics in public. It just states that the business's own records differ, which is a factual claim about your own records, not a claim about the reviewer's character.
Thinking about suing the customer instead?
Some owners skip the reply entirely and go straight to threatening or filing a lawsuit over the review. Think hard before you do.
A weak defamation claim over an honest, if harsh, review can end up costing far more than the review itself, and the lawsuit becomes its own news story, which is rarely the outcome an owner wanted. If a review crosses into genuinely false, damaging territory and you're weighing real legal action, our deeper breakdown on suing over a fake Google review covers when it's actually worth it and what a strong case looks like.
A 3-question check before you hit post
Most risky replies get written in under a minute, in the heat of the moment, which is exactly when the checklist matters most. Before you post a reply you're not sure about, ask three questions:
- 1. Is this a fact I can prove, or my opinion? If it's a fact, could you document it if someone asked you to?
- 2. Would I stand behind this exact wording if a lawyer read it back to me? Not the sentiment, the actual words.
- 3. Am I naming this person alongside an accusation I can't back up? That combination, a name plus an unproven accusation, is the single biggest red flag in real cases.
If any answer raises a flag, don't post it yet. Rewrite it around what you actually know, or set it aside and come back in an hour.
“The rudest reply you've ever wanted to post and the one that actually gets a business sued are rarely the same line.”
If you know you tend to reply hot, building a pause into the process helps more than willpower does. Try our free reply generator on a review that's making you angry right now and read the draft back before you'd ever post it yourself, or see how Resparo drafts the everyday replies for you while holding anything that reads like an accusation for your own review first. Pricing is straightforward if you want every reply handled that way.