Customer Experience Tech

What To Say When a Customer Leaves You a Review

Your review notification lands mid-rush. The reply you write in the next minute is read by next month's customer, and the shape of that one message decides whether your shop sounds like it listens. Here is the move for good reviews, bad reviews, and the ones in between.

September 15, 2026 7 min read 1338 words
Cover image for: What To Say When a Customer Leaves You a Review

Your phone buzzes while you are wiping down the counter, and the notification is a new customer review. The good kind, this time. You read it on your phone between a delivery and a refund, and now there is a small decision sitting there: do you type back, or let it ride until things slow down?

That little moment is where a lot of shops quietly lose money, and where a few of them quietly win it. The customer who wrote the review is rarely watching for your reply. The people who are watching are the ones searching for a shop like yours next month, with coffee money or repair money in their pocket, and they can read your review wall the way you can. A shop that answers its reviews reads as a shop that listens. One that does not reads as a shop that is fine on autopilot.

The numbers back that up without being dramatic. BrightLocal runs an annual Local Consumer Review Survey with a US consumer panel, and its 2024 edition found that 88% of consumers say they would use a business that replies to all of its reviews, compared with 47% for one that never responds at all. You can read the full Local Consumer Review Survey if you want the rest, but that one gap is the whole argument in a single line. Half the difference is not about being liked. It is about being perceived as reachable, and a reply is the cheapest reachable thing you can post.

Most people reading your reviews are not the customer who wrote them. They are deciding whether your shop is the one they will trust. Write for that reader.

So what should the reply actually say? The short version is that most reviews fall into three buckets, and each bucket wants a different move. Let us walk through all three, because the instinctive reply is usually the wrong one in at least two of them.

When the review is a compliment

The dangerous move here is the one-liner. "Thanks for the kind words!" costs you five seconds to type and tells a future customer nothing. It reads exactly the way it is: a stamp. The reply earns its keep by being specific enough that a stranger can tell a human wrote it.

Say what they said, in your own words, and tie it to something real in your shop. If the review mentions your counter person by name, name them back. If it mentions a fix, say what kind of fix. Specificity is the entire trick, because specificity is what a fake or lazy reply cannot fake well.

A reply that works: "Thanks, Dana. The heater was doing that weird clicking thing and we finally swapped the capacitor, so we are glad it is holding up through the cold snap. Give us a shout if it acts up again, and thanks for mentioning Marcus. He needed to hear that one." You told the customer their review was actually read, you showed a future customer you handle follow-through, and you used their mention to give your staff a moment of recognition. That is a lot of work for three lines.

When the review is a complaint

This is where the reflexes kick in, and the reflexes are usually wrong. The two wrong moves are defending ("It really was not that long a wait") and apologizing for everything ("So sorry, it is a shame about the weather"). Defending starts a public argument you will lose on tone alone, and a weather apology in a repair shop reads like you do not know what the review was about.

The reply that works does three things in order. First, name the issue so the next reader knows the complaint is real and you are not dodging it. Second, say what you did or are doing about it, in one plain sentence. Third, hand them a way to reach you that is quieter than the review page, so the conversation can move off the public stage. Here is the shape, written out for a shop that got called out on a slow pickup:

"Thanks for the honest note, Priya. You are right that the pickup ran longer than the time we quoted, and that is on us. We added a second person to the counter this week so the queue does not stack up the way it did that day. If your next pickup is late again, message us the number on your receipt and we will tell you exactly where your job is standing. We would love to get it right next time."

Notice what that reply did not do. It did not blame the customer, it did not make up a discount she never asked for, and it did not promise "we will fix everything." It made one true promise and kept it small, which is the only kind of promise that survives being quoted by a stranger.

What to keep out of the reply

A few things show up in almost every bad reply, and they are all easy to catch on your own before you post. Keep these out:

  • Blame aimed at the customer, even politely phrased. "Per our policy" is polite blame wearing a blazer.
  • Discounts you did not plan to honor. A 20% off coupon in a public reply is a standing invitation for every future reader to demand one.
  • Staff names without their okay. If you are going to mention Marcus, ask Marcus first. If he is not thrilled, the reply belongs in a follow-up text instead.
  • Legal-sounding language. The moment a reply sounds like a lawyer wrote it, it is about time to call one.
  • Anything you would not want read out loud at a staff meeting. The review page is a public record, not a draft folder.

Timing is a habit, not a race

There is a theory that a review must be answered within minutes or you lose the thread, and a few shops have turned reply-speed into an entire status system. For a small shop, same-day is the honest bar, and a consistent same-day rhythm beats a heroic two-minute burst followed by a three-day silence. The signal the survey data is pointing at is not speed. It is coverage. A business that answers every review slowly wins the perception game against one that answers some reviews fast and ignores the rest, because the ignored one is usually the angry one, and the angry one is the one future customers read twice.

The practical setup takes one quiet afternoon. Pick one person who owns review replies, not a rotating "whoever is free," and give them the same three lines every time: name the issue or the compliment, say what is being done, offer a direct path back. Same-day, no exceptions you will not keep. You can keep the routine in the same place you keep the rest of your day. If you run your counter on M&M POS, the download page lets you keep a review-reply queue on the home screen next to the receipts, so the reviews get answered at the exact moment you are already looking at the screen, and the follow-up text to the customer goes out from the same device instead of a second login.

For the wider habit, we keep a running list of small operational routines like this one over on the MuluShop blog, so the review replies slot in next to the other two or three things you already do every day instead of becoming a fourth thing to forget.

So here is the version you can do before you close for the day: open your review page, find the one you have not answered, and write it in the shape above. Specific, calm, and one quiet way back to you. Do that once and the reply wall stops looking like a wall. It starts looking like a conversation, and that is exactly the thing the next customer will read first.