A customer threatens a 1-star review unless you give in. Here is the calm script for in person, on the phone, and by text, plus the documentation habit that protects your business when it happens again.
System 4 from the Leveraged Owner Starter Pack
The tech is loading the van when the homeowner follows him out to the driveway. "That scratch on the baseboard was not there before you showed up," the customer says, arms crossed. "Knock two hundred off the invoice or I am leaving a 1-star review tonight." The tech looks back at you. The customer is watching you decide. Everything you do in the next sixty seconds sets the price of this job and every job after it.
Review threats work because the numbers behind them are brutal. 68% of consumers won't use a business with under 4 stars, 97% read reviews, 71% use Google to find local businesses, and 89% expect owner responses (BrightLocal 2026). A single angry review can cost you real jobs, and the customer making the threat knows it. That is why you need a system for this moment instead of a gut reaction.
This post is part of the Pillar C "5-Star Review Engine" system, the part that handles the moment before a review gets posted. Post-20 and post-60 cover how to respond after a bad review lands. This one covers the threat itself, while you can still do something about it.
The leverage math: 68% of consumers skip businesses under 4 stars (BrightLocal 2026). That is why "1-star review tonight" sounds terrifying. The playbook below takes the leverage back without caving.
Before the scripts, know what not to do. Every one of these feels right in the moment and backfires.
Quick note before the scripts: I am not a lawyer, and this is general information, not legal advice. If a situation looks serious, talk to an attorney who knows your state. What follows is a de-escalation playbook, not legal strategy.
The script has three jobs. Acknowledge the concern, separate the problem from the threat, and move the conversation to writing. Say it slow, keep your hands still, and do not raise your voice.
"I hear you, and I want to get this right. Here's what I can do. Let me take a look at the [baseboard / area of concern] with you right now, and I'll put what we find in writing before I leave today."
"If we caused it, we fix it. That's how [Business Name] works. What I can't do is change the price of the invoice based on a review. The price is the price, and the work is the work. Let me document this and get you an answer in writing by [time]."
Why this works. You never said the review can't be left. You never called them a liar. You promised documentation, which is the thing that actually protects you, and you gave a specific time for the written answer, which ends the driveway standoff.
On the phone you lose body language, so the script gets shorter and the documentation promise gets bigger. Write down the date, time, and exact words while they talk.
"[Customer Name], I want to make sure I understand. Can you tell me exactly what you want fixed?"
"Got it. I'm going to write that up and text you a summary of what we agreed to look at, so we're both looking at the same thing. Give me until [time] today and you'll have it in writing."
"I do need to be straight with you about one thing. I can't adjust the invoice in exchange for a review. But I can promise you this gets documented and handled properly. That's the best I can do, and it's what I'd want if it were my house."
The phrase "so we're both looking at the same thing" moves the conversation from threats to scope without accusing anyone of anything.
Text is your best friend here because the threat arrives in writing, word for word, and your calm reply sits right underneath it. Keep it short. Do not text angry, and do not text fast. If you are heated, walk around the truck once first.
Hi [Customer Name], this is [Your Name] with [Business Name]. I got your message. I want to look into [the concern] and get you an answer in writing by [time] today. If we caused it, we will make it right. The invoice amount stays as quoted, but the work gets handled properly either way.
The line "If we caused it, we will make it right" commits you to nothing beyond fairness, and it reads well to anyone who ever sees the thread, including Google or a future customer reading your posted reply under a bad review.
These are one-to-one replies to a customer you already have a job relationship with, not marketing blasts. If you ever mass-text customers, that is a different world: A2P 10DLC registration (the carrier registration system for business texting), opt-out language in the first text, and TCPA quiet hours all apply. The details live in our 10DLC registration guide for contractors and the TCPA quiet hours post.
The script buys you calm. Documentation wins the dispute. Build this habit on every job, not just the tense ones, because you never know which job turns tense.
Nobody can tell you how often review extortion happens in the trades, and anyone who gives you a number is making it up. Your own records are the measure. If you log every threat for six months, you will know exactly how big the problem is in your business, and you will have the evidence file ready for the ones that matter.
Here is the honest version. Google has a path for reporting reviews that violate its policies, and threats tied to reviews can fall under that. But Google does not promise to remove anything, and nobody can tell you in advance what it will do with a specific report. Treat the report as one tool, not the whole fix.
In general terms, here is how to handle the reporting side:
Saying it again because it matters: this is general information, not legal advice. Talk to an attorney about your situation before you take any legal step. With that said, here are the lines contractors most often trip over.
The pattern is simple. You document, you de-escalate, and you let professionals handle the legal questions. Your job is running the business, not winning a courtroom argument in a driveway.
Example: a two-truck HVAC shop finishes a system replacement. The next day the homeowner texts: "The drywall around the air handler is cracked. Take $300 off or I'm posting a 1-star review and telling everyone you damage houses." This is illustrative, not a real customer, and the numbers are made up to show the method.
Step one, the owner does not reply for twenty minutes. He reads the text twice and checks the job file: before-photos show the drywall already cracked around the old unit, and the signed work order notes "existing drywall damage noted at install." Step two, he sends the text script above, promising a written answer by 5 PM. Step three, at 4 PM he texts the before-photo with a short note: "Here's the photo our tech took before we started. The crack was already there. Happy to patch it for [price] or your drywall guy can handle it." Step four, he logs the threat text, the photos, and both replies in the job file.
No discount was given. No threat was made back. No argument about who is lying. The documentation did the talking, the tone stayed human, and the whole exchange now exists in writing. If the 1-star review lands anyway, the public reply writes itself: calm, factual, pointing at the record. If it never lands, which is the common outcome once someone realizes you have receipts, the system worked exactly as designed.
The full review system lives in the Pillar C "5-Star Review Engine" system post. When a review lands despite your best de-escalation, use How to Respond to Negative Google Reviews (With Templates) for the reply frameworks and Responding to 1-Star Google Reviews: 5 Frameworks by Complaint Type for complaint-specific responses. This post handles the threat; those two handle the aftermath.
The full setup SOP, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.
Free. The full 8-system Starter Pack is $27 if you want everything else.
This post is System 4 from the Leveraged Owner Starter Pack — the done-for-you version with the full step-by-step SOP, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems.
Stats sourced as labeled: review figures (68% under-4-stars avoidance, 97% read reviews, 71% Google discovery, 89% expect owner responses) from BrightLocal 2026.
Related guides from the Leveraged Owner blog:
Getting Google reviews from commercial clients: the different ask, timing, and follow-up for property managers, GCs, and facility directors — plus LinkedIn.
NiceJob vs. Broadly vs. Podium for contractors: honest pricing, what each review platform does well, and the free DIY alternative for shops on a budget.
Review velocity for contractors: how many Google reviews per month move the needle, why freshness beats total count, and what enough looks like by market size.