Key takeaways:
- Response speed matters more than response eloquence
- Platform notifications are unreliable on their own — build a backstop
- Decide in advance who responds, so nothing waits for a meeting
- A weekly five-minute review beats an elaborate system you abandon
Most businesses discover a bad review late. Sometimes weeks late, usually because a customer mentioned it. By then it has been read by everyone who looked you up in the meantime, and the unanswered state has done most of the damage.
Responding within a day or two changes how that review reads permanently. A complaint with a prompt, measured reply looks like a business that handles problems. The same complaint sitting alone for a month looks like a business that does not care.
Why notifications alone fail
Every platform offers email notifications and every one of them is imperfect. They land in a shared inbox nobody owns, get filtered as promotional mail, go to a former employee's address, or simply do not fire. Relying on them exclusively guarantees eventual misses.
Treat notifications as the fast path and add a deliberate backstop.
A setup that holds up
- Turn on notifications everywhere — Google Business Profile, and whichever secondary platforms you genuinely use. Send them to a named person's address, not a generic inbox
- Name one owner. One person is responsible for seeing and responding. Shared responsibility produces shared inaction
- Add a weekly sweep. A recurring five-minute calendar entry to open each profile and look. This is the backstop that catches what notifications dropped
- Set a response standard — within one working day for negatives, within the week for positives
Decide the responses in advance
The reason responses get delayed is rarely that nobody noticed. It is that nobody knew what to say, so it waited for a conversation that kept being postponed.
Agree in advance:
- Who writes the reply
- Who, if anyone, approves it — and ideally nobody, for anything routine
- The standard shape for a negative reply: acknowledge, apologise for the experience, move it offline, keep it under a hundred words
- Which situations need escalation — anything alleging injury, discrimination, or a regulatory matter
Pre-agreeing the boring 90% means the only reviews that need thought are the ones that genuinely do.
Watch the trend, not just the events
Individual reviews are incidents. The pattern is information. Once a month, look at:
- How many reviews arrived, against the month before
- Your average, and the direction it is moving
- Recurring themes — if three people mention waiting, that is an operational finding, not a reputation problem
That last point is the one people miss. Reviews are the cheapest customer research available, and the complaints that repeat are telling you precisely what to fix.
Keep it small
An elaborate monitoring process gets abandoned in the first busy week. Notifications on, one named owner, a five-minute weekly check, a known response shape. That is enough, and because it is small it survives.
Catch reviews early, respond plainly, and keep new ones arriving so the record stays current. Start collecting reviews with SnappyRatings →
