Should a customer complaint stay public or move to a private conversation?
A public complaint creates two conversations at once.
One is with the customer who had the problem.
The other is with everyone else reading the review and your reply.
That is why “take it offline” is not enough by itself. If the business immediately moves everything into a private conversation, future customers may see no public acknowledgement of the issue. If the business tries to resolve every detail publicly, it may expose personal information, argue over disputed facts or turn a service complaint into a long public exchange.
The useful question is:
What should be acknowledged publicly, and what details should be handled privately?
Short answer
Keep the acknowledgement public.
Move personal, account-specific or complex resolution details to phone, email or another appropriate private channel.
Google’s own guidance on review replies says businesses should protect privacy and, when a situation is complex, politely ask the reviewer to contact the business by phone or email so the issue can be resolved privately.
That does not mean the public reply should say only “Call us.”
A useful public reply should still show that the business:
- read the complaint;
- understands the issue being raised;
- is not exposing private details;
- knows what the next step is;
- is willing to continue the conversation.
What should stay public?
The public reply should contain only information that is useful, safe and appropriate for anyone to read.
That can include:
- acknowledgement of the customer’s experience;
- a brief apology where appropriate;
- a confirmed public fact;
- a correction to inaccurate public information, if it can be stated without exposing private data;
- a short explanation of a real limitation;
- the next contact step.
For example, if a customer complains that the branch was unexpectedly closed, the business can publicly acknowledge the inconvenience and explain a confirmed hours correction.
It does not need to publish the customer’s booking record, private correspondence or internal notes.
What should move to a private conversation?
Move details private when resolution depends on information that should not be published.
Typical examples include:
- booking or order details;
- account identifiers;
- payment information;
- health or medical information;
- private correspondence;
- personal contact details;
- staff disciplinary matters;
- detailed compensation discussions;
- disputed facts that require private records to investigate.
Google’s guidance tells businesses to protect privacy in review replies.
For complex situations, Google recommends asking the reviewer to continue by phone or email.
Does moving the conversation private mean the complaint should disappear?
No.
Moving the details private is not the same as suppressing the existence of the complaint.
The public reply can still show:
- that the issue was acknowledged;
- that the business wants to investigate or resolve it;
- where the customer can continue the conversation.
Do not make help conditional on the reviewer deleting or changing the review.
Google’s contribution policies prohibit incentives for changing or removing reviews. The same boundary means service recovery should remain separate from pressure around the public review.
Should the business explain who was right?
Usually not in detail.
A public review thread is a poor place to conduct a full factual dispute.
If a simple public fact is wrong, a concise correction may help.
But if the disagreement depends on records, private messages, payment details or internal evidence, arguing point by point in public often creates more risk than clarity.
A safer public boundary is:
- acknowledge the issue;
- state any safe confirmed fact that matters;
- explain what the business can do next;
- move private details to the appropriate channel.
This is a practical recommendation, not a Google-mandated script.
When can most of the answer stay public?
Some complaints can be answered almost entirely in public because they concern public facts.
Examples include:
- published opening hours;
- whether a service is offered;
- a temporary closure;
- a publicly stated booking rule;
- a known system outage.
Even then, do not expose the customer’s own private details.
The test is not whether the business is embarrassed by the complaint.
The test is whether the information needed to answer it is appropriate for public disclosure.
When should the public reply be especially short?
Keep the public part especially short when the review raises:
- personal medical information;
- financial details;
- a legal dispute;
- allegations about an identifiable employee;
- a safety investigation;
- fraud or identity claims;
- a complex compensation dispute.
The business can acknowledge the concern without publishing private evidence or reaching legal conclusions.
Should the reply ask for a phone call or email?
Yes, when private information or detailed investigation is necessary.
But give the customer a specific route.
“Contact us” is less useful than:
- the existing customer-service email;
- the branch phone number;
- a named support channel;
- an existing complaint form.
Do not ask the reviewer to publish an order number, email address or other personal information in the review thread.
What if the reviewer never contacts you privately?
The public reply still matters.
Future customers can see whether the business acknowledged the issue professionally and offered a reasonable next step.
Do not keep posting repeated public messages demanding private contact.
One clear invitation is usually enough unless there is a genuine new public update.
Should you say the problem was resolved?
Only when you know it was.
Do not publish “resolved” simply because the business sent an email or created an internal case.
A business can use neutral status wording such as:
- “Thank you for raising your concern.”
- “To protect privacy, we cannot discuss individual circumstances here.”
- “Please contact [existing support route] so the appropriate team can review your concern privately.”
- “We have corrected the published hours.” — only when that public fact is confirmed.
For healthcare and other sensitive services, a public acknowledgement should not confirm a patient or client relationship, even when the reviewer has mentioned it themselves. Acknowledge the concern without confirming appointments, visits or other individual circumstances.
This is a Madloba Consult confidentiality boundary for public replies, not a quote, separate Google rule or legal conclusion.
“Everything is fixed” is a stronger claim and should be used only when the underlying issue is actually resolved.
What if the complaint is abusive or violates policy?
That is a separate question.
Google’s content policies govern whether contributed content violates platform rules.
Do not move a legitimate complaint private merely because it is negative.
Likewise, do not assume a negative review is removable because the business disputes it.
This article does not promise review removal or a particular platform outcome.
A practical public/private split
A public reply can answer four questions:
- Did we understand the complaint?
- What can we safely acknowledge publicly?
- What next step are we offering?
- Which details need a private channel?
Then stop.
The private conversation can handle records, identities, compensation, evidence and detailed resolution.
Example structure
A useful structure might be:
Thank you for raising your concern. To protect privacy, we cannot discuss individual circumstances here. Please contact [existing support route] so the appropriate team can review your concern privately.
The exact wording should fit the business and the facts.
The important feature is the boundary: public acknowledgement, private details.
What should a business owner check?
Before publishing a reply to a complaint, ask:
- What part of the complaint can be safely acknowledged in public?
- Am I about to disclose personal or account-specific information?
- Is there a confirmed public fact worth correcting?
- Does the issue require private records or investigation?
- What exact private route can the customer use next?
- Would a future customer understand from the public reply that the business took the issue seriously?
If the reply fails those questions, it may be either too vague or too revealing.
Discuss review management with Madloba Consult
FAQ
Does Google recommend moving complex review complaints to a private channel?
Google’s review-reply guidance says businesses should protect privacy and, for complex situations, politely ask the reviewer to contact the business by phone or email so the issue can be resolved privately.
Should the whole complaint be handled privately?
Not necessarily. The complaint is already public. A useful practical approach is to acknowledge the issue publicly while moving personal, account-specific or complex resolution details private.
Can we publish customer records to prove the review is wrong?
Do not publish personal information in a review reply. Correct safe public facts if necessary, but keep private records and account details out of the public response.
Should we ask the reviewer to delete the review before helping?
No. Service resolution should not be conditional on deleting or changing a review. Google’s policies also prohibit incentives tied to changing or removing reviews.
Does moving the conversation private guarantee the review will be removed or changed?
No. Moving details private is about handling the complaint responsibly. It does not guarantee any change to the review or any platform outcome.
Can we say a complaint is resolved after sending an email?
Only if the underlying issue has actually been resolved. Sending a message or opening an internal case is not the same as resolving the customer’s complaint.