The first hour
Just got a bad Google review? Do this first.
Here's the thing nobody tells you while your stomach is still in a knot: one bad review will not sink your business. Almost no customer reads a business page and bounces because of a single one star review sitting among a real history of good ones. What actually hurts a business is what the owner does in the next hour. A furious reply, a text to the customer, a word to staff that turns into a fake five star campaign. That's the damage that sticks. The review fades. The reaction does not.
So before you do anything else, slow down. Here is exactly what to do, in order, from the moment you see it to the week after.
The first hour: do nothing public
The first hour is not for responding. It's for getting your facts straight and keeping yourself out of trouble.
Do not reply yet. A reply written in the first ten minutes is a reply written angry, and it will read that way to every future customer who scrolls past it for the next several years. Google reviews do not expire. Neither does your reply.
Do not text or call the customer. It feels like the fastest way to fix things, but a customer who just left a public complaint and then gets a personal message from the owner within minutes often reads that as pressure, not concern. Some will screenshot it and post that too.
Do not tell staff to go leave positive reviews. This is the single most common mistake owners make under pressure, and it is the one most likely to get your whole listing penalized. Google can detect a burst of five star reviews from accounts tied to your business, and when it does, it does not just remove the fake ones. It can suppress your real reviews along with them.
Do screenshot the review. Reviews get edited or deleted by the person who wrote them, sometimes within hours. Get a screenshot with the date visible before anything changes.
Do check whether it's actually about your business. Wrong location, wrong business name, a competitor with a similar name three towns over. It happens more than you'd think, especially for businesses with common names. Pull up your appointment book, your point of sale, or your booking system and look for anything matching the date, time, or details in the review. If nothing matches after a real check, that changes everything about what you do next.
The first few hours: find out what actually happened
Before you write a word in public, you need to know what the review is actually describing. Talk to whoever worked that shift, but do it like a manager gathering facts, not a detective building a case.
Ask what happened in plain terms: who was at the counter, what time, was it busy, was there a wait, did anything go wrong that they remember. You are not trying to catch anyone. You are trying to understand the day well enough to write an honest reply.
What you learn usually sorts into one of three buckets.
True. Staff confirms it, or there's no reason to doubt it: a real wait, a real mistake, a real bad interaction. This is the easiest case to handle even though it stings the most, because you can be honest.
Partly true. Something happened, but the review overstates it, or leaves out context that matters. Maybe the forty minute wait was real, but it was a Friday night with three call outs. You still own your side of it. The context is for your reply, not an excuse to skip owning it.
Fabricated or mistaken. Nobody matching the description came in, no transaction lines up, and staff has no memory of anything close to what's described. This happens with competitor sabotage, angry exes of employees, and simple mix ups between similarly named businesses.
Whichever bucket it lands in, do not turn this into a witch hunt. A single review is not evidence of a pattern, and treating it that way in front of your team teaches them to hide problems from you instead of telling you about them.
Day one: write the public reply
Once you know what happened, write the reply the same day, calm and short. Every reply is doing double duty: it's for the person who wrote it, and it's for the next hundred people who read your reviews before they ever contact you. A short, human, non defensive reply to a bad review often does more for your reputation than another five star review would.
Here's what to say in each case.
If it was true
You're right, and I'm sorry. We should have had someone check on you sooner. I've talked with the team about the wait times on busy nights and I'd like the chance to make it right. Please reach out to me directly at [email] and I'll take care of it.
If it was partly true
Thanks for the honest feedback. We were short staffed that night, which isn't an excuse, just context. We're working on better coverage for busy shifts. I'd like to hear more about your visit directly, if you're open to it: [email].
If it looks fabricated or mistaken
I've checked our records for this date and can't find a visit or order matching what's described here. If this was about a different location or business, I'd appreciate a correction. If I'm missing something, please reach out directly at [email] so I can look into it properly.
Notice what none of these do: none of them argue the point in public, none of them reveal what the customer ordered or paid, and none of them offer money to make the review go away. Keep it that way. More on exactly why in the section below.
Day two to seven: fix it, then ask
If the complaint was true or partly true, this is the week to actually fix the underlying thing, not just apologize for it. If it was a wait time, change the staffing on that shift. If it was a rude interaction, have the direct, private conversation with that employee. The fix matters more than the reply, because the next customer who has the same bad experience is the one who really hurts you.
This is also the week to ask your genuinely happy recent customers for reviews, so your average has a chance to recover. This is legitimate, as long as you ask everyone who had a good visit that week, not just the three regulars you know will gush. Pull your recent customer list, whether that's an appointment book, a point of sale export, or a loyalty list, and send the same ask to all of them. Some will ignore it. Some will leave a review. What you should never do is filter who gets asked based on how happy you think they were, which is a different problem covered in detail below.
Week two onward: put a private channel in place
The real prevention step isn't a better reply template. It's giving customers a way to tell you something is wrong before they tell Google. Most people who leave a bad review never complained to you first, not because nothing was wrong, but because there was no easy way to say so in the moment. A QR sign at the counter or table that goes straight to your inbox, privately, gives that customer a place to land before frustration turns into a public post. I cover the mechanics of this in how to make a QR code suggestion box for free, and the fuller comparison of every option in the suggestion box went digital.
None of this replaces responding well when a bad review does land, which is worth its own deeper read: how to respond to a 1 star review, with examples you can copy.
Do not do this
A short list, because under pressure it's easy to reach for the wrong move.
- Do not argue in public. Even if the customer is wrong, a back and forth in the replies makes your business look combative to everyone who reads it later, not just the one person you're arguing with.
- Do not reveal the customer's details or their order. Naming what someone bought, how much they paid, or details about their visit in a public reply is both a privacy problem and a bad look, even when it's meant to prove you're right.
- Do not buy fake reviews to bury it. This gets flagged more often than owners expect, and the penalty tends to land on your whole listing, not just the fake reviews.
- Do not offer money for removal. Offering a refund or gift card in exchange for taking down or editing a review violates Google's policies, and a customer who screenshots that offer before deleting the review has just made things worse for you.
- Do not use a star question funnel to filter who gets asked for a review. Routing happy customers to Google and quietly steering unhappy ones somewhere else is called review gating, and it can get your review acquisition penalized even though each individual step feels reasonable. The full breakdown is in review gating: why routing unhappy customers away from Google can backfire.
Knoted has nothing to do with any of this by design. It's not a review tool. It never routes anyone toward or away from Google, has no star ratings, and doesn't touch your review pipeline at all. It's a private line straight to you, so the next hard thing a customer wants to say has somewhere to go before it becomes a review.
One bad review is a Tuesday. What you do in the hour after it is what actually gets written down, one way or the other.
Common questions
Should I reply to a bad review right away?
No. Reply the same day, but not the same minute. Give yourself an hour to find out what actually happened and cool off. A reply written angry reads angry, and it sits under your business name forever.
Can I get a bad review taken down?
Sometimes, if it breaks Google's policies, such as being fake, off topic, or containing hate speech. A genuine complaint from a real customer will not come down just because you disagree with it. The full walkthrough is in Can you remove a Google review? What actually works.
Is it okay to ask happy customers for reviews after a bad one lands?
Yes, as long as you ask everyone who had a good experience, not just the ones you know will say something glowing. Asking your whole recent customer list is honest. Asking only your favorites and steering the rest away is review gating, and Google can penalize it.
What if the review is fake or not even about my business?
Check your records first. If you cannot find any transaction, appointment, or order matching the details, flag it to Google as not being about a real customer. That takes days to resolve, so still follow the same-day reply step in the meantime; a calm public reply looks better than silence even while a flag is pending.