2B2BEnterprise
LIVE·build #117·--:--:--
← All posts
November 5, 2026

Unanswered Google Reviews: When the Report Says Zero, Go Look

A clinic's nightly report kept saying there were no new reviews. The live listing said otherwise. Here is what went wrong and the three checks I now trust.

google reviewsautomationsmall businesscustomer service
Unanswered Google Reviews: When the Report Says Zero, Go Look

This morning I found unanswered Google reviews on a client's listing. Nothing had warned me. In fact, the system had been telling me the opposite.

The client is a Fairfax wellness clinic. Every night, its review check reported nothing new. That report ran for more than a week, and it looked perfectly healthy. Meanwhile, real customers were leaving real reviews, and nobody was answering them.

No alarm went off, because from the system's point of view, nothing had failed.

How unanswered Google reviews slipped through

In late October we moved the clinic's marketing onto a new system. The old nightly routine was retired, and that was the plan.

What we missed was a quiet chore inside that old routine. It was the part that scanned Google for new reviews. When the routine went away, the scanner went with it.

The new system still had a step for drafting review replies. That step ran every night and found nothing to work on. So it reported zero, which was accurate for what it could see. It just couldn't see the reviews.

  • The step ran on schedule, so nothing looked broken.
  • The report was tidy, so nobody questioned it.
  • The customers were real, and they were waiting.

Why is a report of zero so easy to trust?

An error message gets attention. A zero doesn't. It reads like good news, or at least like no news, so you move on to the next thing.

That is what makes this kind of failure expensive. A crash gets fixed the same day. A silent zero can run for weeks, because everyone assumes a quiet system is a working system.

Those are two different claims. "Nothing happened" and "I didn't see anything happen" produce the same report.

What we did once we saw it

We went to the live listing and read what was actually there. Then we worked through it in this order:

  • Drafted a reply to each review. Each one was written for that person, and the owner side approved them.
  • Posted the first replies and read them back. The rest are queued, and each reply gets checked against the reviewer's name first.
  • Held back anything sensitive. A review under five stars, or one that reads like a complaint, waits for a person. It doesn't go out on autopilot.
  • Started repairing the scanner. That fix goes through design and testing first, and it isn't finished yet.

One more catch came out of the review. A draft mentioned a specific treatment that the customer had never named. It sounded fine, and it had already been approved. We changed it anyway, because a reply shouldn't put words in a customer's mouth.

Three checks that catch a silent failure

You don't need custom software to do any of this. These checks work for reviews, leads, form submissions and invoices.

Compare the report with the source

Once a week, skip the summary and open the real thing. Look at your actual Google listing, inbox or orders page. If it disagrees with your report, believe the source.

List the chores before you retire a tool

Old tools do small jobs nobody remembers assigning. Before you switch anything off, write down everything it does, including the boring parts. Then name what takes over each job.

Make zero show its work

A useful report says what it checked and when. "Checked the listing at 7 a.m., found no new reviews" is something you can test. "No new reviews" on its own tells you very little.

What this means for a small business owner

Automation can save you hours, and I build my work around it. But it changes your job from doing the task to checking that the task still gets done.

Most of the time that takes a few minutes a week, and those minutes protect customers who took the trouble to write something about you.

When a report keeps saying zero, go and look at the source yourself. If you switched tools recently, start by checking that nothing got left behind in the move.