Separate the public reply from the work behind it.
A review says, “I asked for an estimate and never heard back.” Your team remembers sending something. Replying that the customer is wrong would turn an uncertain record into a public argument. Saying the problem is fixed would create a different problem if nobody has checked it yet.
A useful response has two jobs: acknowledge what the person describes, and offer an appropriate next step. The investigation has its own job: establish what happened and what the team can do. A reply being published is not evidence that the complaint has been resolved.
This guide is for ordinary service feedback. Sensitive, regulated or safety-related matters need the appropriate responsible person and process. Do not use a public reply to reveal a customer relationship, private history, account details or disputed evidence.
Decide which kind of response is needed.
On a small screen, swipe or scroll sideways to read the full table.
| What the review contains | Public response | Work behind the response |
|---|---|---|
| A positive experience | A short, relevant thank-you. | Keep private service details out of the reply. Do not turn thanks into a sales pitch. |
| An unclear or disputed service issue | Acknowledge the concern and offer your verified private contact route. | Assign someone to review the relevant records without presuming which account is correct. |
| A factual issue the team has confirmed | Recognize the issue in terms safe to make public. | Agree the actual next action. Describe a remedy only if it is authorized and accurately stated. |
| Content you think violates the platform’s rules | Avoid a public accusation or repeating harmful/private details. | Review the platform’s current policy and reporting process. A report does not guarantee removal. |
Disagreeing with an opinion does not by itself establish a policy violation. Keep the customer-service decision separate from any platform report. Do not offer a benefit or withhold help to make a person change their review.
Work through an unanswered-estimate example.
Fictional example: a painting business receives the estimate complaint above. The office can see an estimate was prepared. It has not yet established whether the customer received the current version or whether a reply went to a different conversation.
A public draft might be: “Thank you for flagging this. We’re sorry the next step has been unclear. Please contact our office through the contact page on our website so we can check the estimate with you.” Use this only when that route works and the office is ready to handle the inquiry.
Notice what the reply leaves out: the customer’s address, job scope, price, contact details and any claim about fault. It also avoids promising an immediate answer or a particular remedy before the team knows what is possible.
Behind the scenes, the office owner checks the current estimate, the communication record and any existing follow-up. They verify the request through the business’s normal private process. If another teammate is already handling it, they coordinate the next action instead of sending conflicting replies.
If the record shows that a revised estimate is still waiting for an internal answer, say so privately and agree a realistic next update. Use the customer progress-update guide when an answer is still pending.
Review the draft before posting.
- Can each factual statement be supported? “We sent it” and “you received it” are different claims. Do not guess intent or blame.
- Is every detail appropriate for a public audience? Other readers do not need the customer’s private record to understand that your team will help.
- Does the next step work? Verify the contact destination and the person responsible before pointing someone there.
- Does the wording promise more than the team agreed? Remove invented time limits, refunds, guarantees or claims that the issue is already resolved.
- Is it short enough to read? Answer this review, rather than pasting a long generic defense of the business.
If you use an AI-written draft, the team still owns those checks. The AI reply review guide explains how to examine claims and commitments before a draft becomes a message.
Track the actual outcome, not just the posted reply.
Download the blank public-review response worksheet (CSV). Use a review reference rather than copying the reviewer’s name, full text or private job details into a general sheet. Keep sensitive investigation notes in the business’s approved private record.
Record the public-safe response, private follow-up owner, next check and observed outcome separately. “Drafted,” “submitted,” “visible to the public,” “investigation pending” and “resolution confirmed” describe different things. A platform may review a reply before showing it. Check the actual public result instead of treating submission as completion.
If the person does not contact you, record that the outcome is unknown. Do not mark the issue resolved because the review was edited, removed or left unanswered. Where a private conversation does establish a resolution, record what was confirmed and by whom without republishing it.
For current platform guidance, see Google’s advice for writing review replies and how Google reviews and publishes replies. This worksheet is a suggested working method, not a review-management feature or an included BusinessOS service. If you want to invite future feedback, use the separate honest review-request guide.
Explore Make the public version match the real business. for related questions and a useful starting point.