Three Bad Reviews In One Week Is Not Three Bad Days

You went six months without a bad one. Then Tuesday, Thursday and Saturday.

Your stomach does the thing. You open all three, you read them twice, and your hands go straight to the reply box because that is what you know how to do with a bad review.

Stop for a day. Those three are not three separate bad days that happened to land in the same week.

They are one thing, three times.

Clusters almost always have a single cause

A business that is running the way it usually runs produces bad reviews at a slow and fairly steady drip. One here, one two months later, the occasional person who was going to be unhappy no matter what.

When three show up inside a week, something changed. Not the customers. Something on your side.

The reason this matters more than the reviews themselves is that whatever changed is still changing things. Those three people wrote something down. The ten other people that week who had the same experience just quietly will not come back, and you will never hear from any of them.

The reviews are not the problem. They are the smoke alarm, and the alarm is worth less than finding the fire.

The five things it usually is

Somebody new. A new hire, or an old hand covering a role they do not normally do. Look at whether the three complaints share a shift, a day, a bay, a chair, a route.

A new supplier or product. You switched brands, switched vendors, switched what you stock. The complaints will be about the thing, not the person, and they will sound oddly specific and technical.

A process you changed. New booking system, new phone setup, new intake form, new way of handling deposits. These complaints do not sound like complaints about the work at all. They sound like people who were confused or left hanging.

A price you moved. Raised a rate, dropped a discount, started charging for something that used to be free. These read as anger about value rather than about quality, and they often mention what it used to be.

You got busy. The least obvious one and maybe the most common. Nothing changed except volume. Wait times got longer, the callback took three days instead of one, somebody got rushed. Nobody made a decision. It happened to you.

How to read three reviews as one signal

Line them up by date and service date, not by review date. When somebody actually came in matters more than when they got around to writing.

Then read them for overlap, and read past the emotion. The emotion is all going to sound the same. The facts will not.

Ask what all three had in common. Same day of the week. Same person. Same service. Same intake path. Same week your new guy started. Same week the supplier switched.

Then check the good reviews from that same window, because that is the part everybody skips. If the fives from that week are all about one thing and the ones are all about another, you have narrowed it fast.

Sometimes there is no overlap and it really was a coincidence. That happens. But check before you decide it, because the cost of assuming coincidence when it is a pattern is a month of quiet damage.

Then reply, and reply differently

Once you know the cause, the replies change completely, and for the better.

A generic apology to three people in the same week reads like a form letter, because it is one. Three replies that name the actual thing and say what you did read like a business that pays attention.

"You are right, our callback times got away from us last month while we were short staffed. We have added coverage on the phones since." That is a different document than "We are sorry you had this experience."

And it is not really for the three people. It is for the person reading in March who is trying to work out whether a cluster of bad weeks in September means anything about you. A run of specific, fixed, named problems is one of the more reassuring things a profile can show.

Do this

1. 1Do not reply yet. One day of holding costs you nothing and a fast wrong reply costs you the chance to say something real.
2. 2Line the three up by service date and write down what each person actually experienced, separate from how they felt about it.
3. 3List every change in your business in the four weeks before the earliest one. Staff, supplier, price, process, volume. Write it out, do not do it in your head.
4. 4Read the five star reviews from the same window and see if they contradict or confirm.
5. 5Talk to whoever was actually there. They usually know before you do and are waiting to be asked.
6. 6Fix the thing. That is the actual work and it is the only part that changes anything.
7. 7Now reply, naming the cause and the fix, once per review, in your own words.
8. 8Set a note for thirty days out to check whether it stopped.

Where the card fits

A word on timing, because this is where people get it backwards.

The instinct after a cluster is to go get a pile of new five stars and push the bad ones down the page. That works on the arithmetic. It does nothing about the cause, and if the cause is still running, you are now asking more people to review an experience that is currently producing complaints. Some of them will.

Fix it first. Then the volume matters, and it matters a lot, because a steady flow of recent reviews is what makes a bad week look like a bad week instead of a trend.

The tap card at shop.optechsol.llc is for the flow part. The customer taps their phone at the counter and the review page opens, so the good weeks are actually getting written down instead of lived and forgotten. A profile with that habit running absorbs a rough patch. A profile that only hears from unhappy people does not.

What it comes down to

Three in a week is information, and it is cheaper information than you usually get.

Somebody paid attention long enough to tell you something is off. Go find out what changed before you go find out how to apologize for it.