Start with what you know
Read the whole review before drafting. Separate the reported experience from your own explanation of it. “The appointment started late” describes an experience; “we were understaffed” is a possible explanation that needs checking.
Find the relevant location, date and service internally where possible. A public display name may not match a booking or order, so an unsuccessful search does not prove the review is false. If you cannot identify the visit, ask for details through an established private contact channel.
- What specific part of the experience is the customer unhappy about?
- Which facts can the team confirm, and which are still uncertain?
- Who can follow up, through which contact channel, and what can they actually offer?
Build a reply around three useful parts
Name the issue, acknowledge its impact and offer a next step you can deliver. The next step might be a private conversation to understand an appointment, a check on an order, or a clear explanation after you have confirmed what happened.
Avoid filling the reply with a description of how good your business usually is. Before publishing, ask whether each sentence helps this customer understand your response. Remove promises about refunds, process changes or staff action unless they have been approved.
Negative review response examples
Choose a situation to compare a generic reply with a more useful draft. These are editorial examples to adapt to the facts and contact channels of your business.
A missing order update
“I ordered a lamp last week and still have no update on collection.”
A generic reply
Sorry for the inconvenience. Customer satisfaction is our priority.
A more useful draft
We’re sorry you’ve been left without a collection update for your lamp. Please send your order reference through our usual customer service channel so our team can check its status and confirm the next step.
Why this is more useful
It names the missing update and explains what the order reference will help the team check.
Before you publish
Confirm that the contact channel is available and someone can check the order. Do not invent a collection date.
A repair bill above the estimate
“The repair cost more than the estimate, and I did not understand the extra charge.”
A generic reply
We’re sorry you feel that way. We always aim to provide excellent service.
A more useful draft
We’re sorry the extra repair charge was unclear. Please contact our service team privately with the job reference so we can compare the estimate with the final bill and explain the difference.
Why this is more useful
It addresses the unclear charge and identifies the documents needed to check it, without assuming either side is mistaken.
Before you publish
Compare the estimate, approved work and final bill before explaining the charge. Do not promise a refund before the team has reviewed the case.
Noise during a hotel stay
“The room was noisy at night and I barely slept.”
A generic reply
Thank you for your feedback. We hope to welcome you again soon.
A more useful draft
We’re sorry the noise disturbed your sleep. Please contact us privately with the dates of your stay so we can look into the disturbance and check which room and time were affected.
Why this is more useful
It recognises the impact on sleep and requests useful context without exposing booking details.
Before you publish
Verify the reported disturbance. Do not claim the room has been soundproofed or offer an unapproved refund.
A meal served at the wrong temperature
“My main course arrived cold, and getting someone’s attention was difficult.”
A generic reply
We’re sorry. This is not the standard we pride ourselves on.
A more useful draft
We’re sorry your main course arrived cold and you had difficulty getting help. Please contact the restaurant privately with the date and approximate time of your visit so we can review what happened with the team.
Why this is more useful
It responds to both parts of the complaint and gives a specific way to help reconstruct the service.
Before you publish
Check the service details before describing a cause or promising compensation. Do not say the issue is fixed unless it is.
When the review gives you little to work with
For a low rating with no explanation, do not invent a complaint. A short invitation is enough: “We’re sorry your experience did not meet your expectations. If you’d like to tell us more, please contact our team through the contact details on our website so we can understand what happened.”
If you disagree with a detailed review, check the event before contradicting it. You can describe a verified limitation without arguing about the reviewer’s intentions. Keep private booking, order and contact details out of the public reply.
Replying and reporting are separate decisions
Google recommends clear, professional replies and protecting reviewers’ private information. It prohibits incentives offered in exchange for changing or removing a review.
Google only removes reviews that violate its policies. Disagreement with a review is not enough. If you suspect a violation, consult Google’s reporting guidance; reporting does not guarantee removal.
Keep the final decision in your hands with Repliku
In Repliku, choose draft mode for the star ratings whose replies you want to check. Read the draft, adjust the wording and publish from Reviews when you are ready. Confirm the business voice so the starting text reflects how you want to communicate.
Rules follow the star rating, not a separate assessment of how sensitive the complaint is. A four-star review can contain a serious concern. If you want to review those replies too, select draft mode for four stars as well. Imported historical reviews are not automatically replied to after the fact.
- Check the facts and remove any unconfirmed explanation.
- Confirm the next step and who will handle it.
- Read the reply as a customer would, then decide whether to publish.