A negative review can feel unfair, especially when the team remembers the situation differently. The first public reply still needs to be useful to the person who wrote it and to everyone else evaluating the business.
When deciding how to respond to negative reviews, separate what you know from what you need to investigate. A calm reply can acknowledge the concern, explain the next step and protect private details without admitting facts that have not been established.
Acknowledge the issue the customer raised
Before writing the public reply, put the concern into one neutral sentence. “The customer says nobody explained the delay” is a more useful starting point than “This review is unfair.” Then work through three checks:
- Identify what the customer actually reported, without adding motives or assumptions.
- Establish which facts your team can confirm and which still need checking.
- Choose a next step someone in the business can carry out, including a genuine contact route where needed.
For example: “We are sorry the appointment did not go as you expected. We would like to check what happened with the booking. Please contact the service team through our website so we can look into it.” Use a more direct acknowledgement when your team has confirmed its mistake.
Use a more specific acknowledgement when the facts are confirmed. If your team knows it failed to notify the customer of a delay, say so plainly and explain the appropriate next step.
Business.gov.au's guidance on online reviews recommends responding professionally and using feedback to improve the business. That is more useful than treating every critical review as an argument to win.
Move private details to a private conversation
An order number, appointment history or personal circumstances may help resolve the issue, but they do not belong in a public reply. Invite the customer to a genuine contact route and make sure someone is responsible for responding there.
Do not ask people to post their phone number or other identifying information in the review thread. Avoid revealing details from your records to prove that the customer is wrong.
Baymard's research on responses to negative user reviews illustrates that readers consider the business's handling of criticism while evaluating a product. A public response should therefore make responsibility and next steps visible without turning the conversation into a spectacle.
Explain disagreement without attacking the reviewer
Sometimes you cannot match the review to a known transaction. State that limitation carefully: “We have not been able to identify the visit from the information here. Please contact us with the relevant details so we can check.” That is different from publicly declaring that the person is lying.
If a factual correction is important, keep it brief and verifiable. Do not publish a long account of the customer's behaviour or use sarcasm to signal that the business is annoyed.
Trustpilot's best-practice guidance on review responses offers another reference for professional public replies. Follow the original platform's rules when a review appears to violate its content policy; disagreement alone does not establish a violation.
Let the resolution change the business
When several customers describe the same problem, investigate the process behind it. Rewriting the apology will not fix an unclear cancellation policy or repeated scheduling error. Record the issue, assign responsibility and check whether the change worked.
Mirror App's Reviews Widget provides a way to display supported reviews on your website. Replying and resolving the underlying issue happen through the source platform and your own service process. A selected website display should not be presented as evidence that criticism never occurs.
Adapt the response to what has actually happened
The following replies are fictional starting points, not statements about real customers. Their purpose is to show how the wording changes with the facts. A reply should not promise a refund, investigation or service change unless the business can follow through.
If a delay is confirmed, the response can be direct: “We did not let you know about the revised delivery time when we should have, and we are sorry for the inconvenience this caused. Our service team would like to review the order with you and discuss the available next steps. Please use the contact details on our website and ask for the delivery team.” This acknowledges the failure without publishing the order history. It also tells the customer which team will handle the conversation.
If the complaint concerns a preference, the business can recognise the mismatch without arguing about taste: “Thank you for explaining your experience. We understand that the atmosphere was different from what you were looking for. We will review how we describe the evening service so guests have a clearer idea before booking.” That is appropriate only if the team intends to review the description. Avoid using it as a polished way to say that the guest should have known better.
If you cannot identify the transaction, keep that uncertainty visible: “We have not been able to match the details here to a booking. We would like to understand the concern, so please contact the team through our website with the date and relevant reference.” A missing match in your records is a reason to ask for information, not proof that the review is fabricated.
If the team is still investigating, a brief initial response may be more accurate than a confident explanation. Say what you are checking, provide a genuine contact route and avoid guessing publicly. When you later have a confirmed outcome, consider whether the original response needs an update, while keeping private details out of it.
Check the reply before it goes public
Read the draft as someone who knows nothing about the dispute. Can they see the concern, what the business has established and what happens next? Remove background details that serve mainly to demonstrate how unreasonable the reviewer was. They rarely make the response more useful to a prospective customer.
Check the handover as carefully as the wording. If you invite the person to contact support, make sure support can recognise the issue and has the authority or route needed to help. Asking someone to retell the whole story to an unattended inbox turns a reasonable public reply into another frustrating experience.
Do not make the resolution conditional on deleting or changing the review. Handle the service issue on its own merits and follow the source platform's rules. If the customer later chooses to update their account, that is their decision. Your team's job is to provide a fair response and address what it can actually change.
