The one-star review lands while you're between meetings. You read it. You read it again. You feel sick, then angry. The urge to reply inside the next ten minutes is strong, and that urge is where the damage gets done.
We handle reputation management work for Melbourne clients at CJ Digital, and we see the same pattern on repeat. The review is bad. The reply, written in the wrong frame of mind, is worse. It goes up without being read by anyone else. The customer responds. Other customers read the exchange and leave with a worse opinion of the business than the review alone would have given them. The review has now done more damage than it ever could have on its own.
This article is about process. A separate CJ Digital post covers reply wording, and we link to it at the end. The focus here is the discipline before the keyboard: who decides, what you check, who signs off, and whether to reply at all.
Default position: wait 24 hours before you reply to a bad Google review. The review is not going anywhere in that time. Your emotional reaction is. A reply posted inside the first hour is where regret lands. It is also the reply the reviewer is most likely to fire back at.
Twenty-four hours gives you time to:
There are three narrow situations where the 24-hour rule does not hold:
If the review does not fit one of those three, wait the 24 hours.
Before anyone drafts a reply, someone needs to work out what the review describes. This is administrative work and it happens offline. Records first, drafting second.
The questions to answer:
If you cannot answer those five questions, you are not ready to reply. A reply posted before the fact-finding is done is a defence against something the business does not yet understand.
A public reply to a bad review is a business decision that needs the usual business sign-off. Three people should be involved before a reply is posted:
What goes wrong when this does not happen: the person who read the review first writes the reply, posts it, and tells the rest of the business afterwards. The sequence is backwards. A public reply the business cannot defend is harder to walk back than a review nobody replied to.
Writing the angry version is a release, not a draft. Write the reply you would post if there were no consequences. Get everything off your chest. Name the reviewer, call out the inaccuracies, defend the staff, point out what the customer did wrong. Put it in a document, not in the Google reply field.
Then delete it.
The reply you will post is a separate piece of writing. It is short, professional, and does not engage with the substance of the review. Its job is to show other readers that your business handles complaints well. It is written for the audience of prospective customers who will read this exchange over the next 12 months, not for the reviewer.
The separation matters. The angry draft is for you. The reply is for the people watching.
Before the reply goes live, someone who was not involved in the original situation reads it. They are not there to redraft it. Their job is to catch:
The test: if a prospective customer saw only this reply, would they still consider your business? If the answer is no, the reply needs more work.
The decision to reply publicly at all is bigger than the wording. Some situations are better handled offline. Others need a public reply so other readers see the response. Some need both.
| Situation | Reply publicly? | Take offline? |
|---|---|---|
| The review is accurate and reflects a real service failure | Short acknowledgement, no excuses | Yes. Offer to discuss directly with the customer |
| The review contains factual errors | Correct the facts briefly, no argument on the substance | Yes, if the customer is reachable |
| The review describes a confidential matter (medical, legal, financial detail) | Brief non-specific response only | Yes. All substance handled privately |
| The review is from someone who is not a customer | No reply. Flag for removal | N/A |
| The review is clearly malicious (ex-employee, competitor, personal grudge) | No reply. Flag for removal and document | N/A |
| The review is about a staff member's conduct | Short reply acknowledging the concern | Yes. Internal process handled offline |
When a public reply does go up, it sits next to the review permanently. Other customers read both. A reply written as a reflex is the evidence potential customers use to decide whether to bring their business to you.
If any of the following is true when you are about to post a reply, stop:
Any one of these is a reason to stop. Two or more is a reason to have somebody take your phone.
Discipline before the reply protects against a short list of recurring problems:
The discipline's real value is in keeping the review contained.
Before any of this process can run, the business has to know the review exists. Small businesses often find out about bad reviews days or weeks after they were posted, because the owner does not have notifications enabled, the Google Business Profile is managed by a former employee, or nobody knows whose phone the alerts go to. The discipline in this article assumes the business is aware of the review in the first place.
If you are not sure who monitors your reviews, who has access to reply, or what your escalation protocol is when a bad one lands, fix that before you need it. A documented protocol, a monitoring tool that alerts the right person, and a short checklist of the steps in this article is cheap preparation. It is also what stops the 9pm reply from ever being drafted.
We handle online reputation management for Melbourne businesses at CJ Digital. If you have a review situation you are not sure how to handle, or you want a protocol set up before you need one, get in touch. If you are looking for wording guidance for a reply, our earlier post on responding to Google Business Profile reviews covers that ground.
