By The Tool Trial Editorial Team
A reply that goes up an hour later and holds up beats one posted in five minutes and walked back. Speed is the easiest thing to get right, and the least important.
It matters because replies to Google reviews are public. Google states that a business reply is posted publicly under the review. There is no draft state, no private preview.
This checklist does one job: it lets a person decide whether a drafted reply is ready before anyone posts it. Whoever wrote the draft — owner, staff, or AI — a human still says yes.
It is practical editorial guidance. It is not legal advice and does not guarantee compliance with Google’s policies or any law.
Why review replies need an approval step
Most bad replies are not badly written. They are fluent, well-meaning, and wrong in a specific way: they confirm someone was a customer when that was not ours to confirm, accept blame for something nobody checked, offer a refund nobody authorized, or argue with a claim that may be false.
Rereading for typos catches none of it. A different set of questions, asked in order before the reply goes out, does.
The three possible outcomes: Approve, Revise, or Escalate
Every check ends in one of three places.
- APPROVE — the reply passes every applicable check and an authorized human approves it for manual posting.
- REVISE — it has a correctable clarity, tone, privacy, factual, or authorization problem. Fix it and run the checklist again.
- ESCALATE — it involves uncertainty or risk that an appropriate authorized person should review before anything is posted.
The outcome is the most serious one any single check produces — nine APPROVEs and one ESCALATE is an ESCALATE. And if editing cannot fix the problem, it is not a REVISE.
ESCALATE does not automatically mean a lawyer. The right reviewer depends on the issue: the owner, whoever holds the service records, whoever handles staffing, or an outside professional. Escalating is not a verdict on the review — it means not this person, not right now.
Before reviewing the draft
Have three things open: the review, the drafted reply, and the internal record covering the visit or job.
If you cannot find a record, that is information, not a reason to skip ahead. It tells you which checks you cannot clear.
The 10-step Google review reply approval checklist
1. Confirm the correct review and business location
Inspect: which review the draft answers, and on which location.
Why it matters: replying to the wrong review or profile is public and hard to undo.
APPROVE: the draft answers this review, on this location. REVISE: it names the wrong location, service, or date. ESCALATE: you cannot tell which visit it refers to, so guessing means inventing.
Ask: does this reply belong to this review, on this profile?
2. Separate reviewer claims from verified business facts
Inspect: every factual statement: reviewer claim, confirmed record, or unchecked.
Why it matters: repeating an unverified claim as fact makes it your statement, permanently.
APPROVE: every statement is verified or clearly framed as the reviewer’s account. REVISE: it states something unverified as fact and can be reworded. ESCALATE: the review carries an accusation you cannot verify and cannot responsibly ignore.
Ask: which sentences am I asserting, and can I support each one?
3. Remove private, sensitive, or unnecessary identifying details
Inspect: anything identifying a person — names, appointment details, account references, the service received.
Why it matters: as an editorial safeguard, remove private, sensitive, or unnecessary identifying information before approval. A public reply can also confirm someone was a customer, which is itself a disclosure in some businesses.
APPROVE: nothing private, and nothing confirmed that should not be. REVISE: a detail can be removed without breaking the reply. ESCALATE: you are unsure whether you may confirm or disclose something publicly.
Ask: what would a stranger learn about the reviewer here?
4. Check tone, professionalism, and defensiveness
Inspect: how the reply reads cold, to someone with no context or sympathy either way.
Why it matters: a reply should remain calm, professional, and non-defensive. Never use it to insult, threaten, or attack the reviewer — harassment and threats are prohibited under Google’s Maps content policy. Defensiveness reads as guilt to some, arrogance to others.
APPROVE: calm, professional, free of sarcasm or blame. REVISE: content is fine but the tone is defensive, curt, or over-apologetic. ESCALATE: the draft attacks the reviewer, or the writer is too close to judge.
Ask: would this sound reasonable to someone who has not read the thread?
5. Check accuracy and supporting records
Inspect: each verifiable statement against the record — dates, services, what was agreed.
Why it matters: a wrong checkable detail hands the reviewer a second, better complaint.
APPROVE: every checkable statement matches the record. REVISE: a detail is wrong and the record shows the right one. ESCALATE: record and review disagree in a way that matters, and resolving it needs more authority than you have.
Ask: can I point to where each detail is written down?
6. Check promises, compensation, and employee authority
Inspect: anything the reply offers or implies — refunds, credits, discounts, replacements, revisits, callbacks, timelines.
Why it matters: this is where small businesses get hurt most. A public offer is hard to retract, and the writer often is not entitled to make it.
APPROVE: no commitment, or only one the writer is authorized to make. REVISE: an unauthorized offer can be removed and the reply still works. ESCALATE: the situation calls for a commitment nobody present can give.
Ask: am I allowed to promise this, and can we deliver it?
7. Decide whether the conversation should move to an official private channel
Inspect: whether resolving this needs details that should not be public.
Why it matters: some cases need a private conversation. Many do not, and pushing every complaint offline reads as evasion.
Point only to a channel the business already owns and controls — the contact details on your profile or website. Do not invent a phone number, email address, form, or staff contact. Never ask for sensitive details in public.
APPROVE: no private channel is needed, or the reply points to a real one you control.
REVISE: it names a channel that does not exist, or asks for sensitive details in public.
ESCALATE: you are unsure whether this should be discussed publicly at all.
Ask: is a private conversation needed, and does the channel exist?
8. Check for high-risk or specialist-review issues
Inspect: review and draft against the stop list below.
Why it matters: these carry consequences a public reply can worsen and cannot fix.
APPROVE: nothing from the stop list is present. REVISE: a high-risk element appears only in the draft and removing it resolves the problem. ESCALATE: any stop-list category is genuinely in play.
Ask: is this bigger than a customer-service reply?
9. Keep the reply clear, relevant, and reasonably concise
Inspect: length, focus, and whether it addresses this review or a generic one.
Why it matters: for readability, keep the reply clear, relevant, and no longer than needed. A long reply invites line-by-line rebuttal and buries the point.
APPROVE: short, specific, easy to read once. REVISE: padded, generic, or drifting into marketing. ESCALATE: rarely applies — if the draft must be long because the situation is complicated, that complication belongs in check 8.
Ask: could someone skim this and get the point?
10. Obtain final approval from an authorized human
Inspect: who is approving, and whether they may.
Why it matters: a checklist run by someone without authority to approve produces a recommendation, not a decision.
APPROVE: an authorized person read and approved that exact text. REVISE: wording changed after approval. ESCALATE: no authorized person is available and the reply supposedly cannot wait.
Ask: who is accountable if this reply is wrong?
Stop and escalate when
Do not post. Route the draft to an appropriate person when the review or reply involves:
- Unverified factual accusations
- Threats or hostile language
- Personal or sensitive information
- Health or medical details
- Payment, account, or financial details
- Discrimination allegations
- Safety incidents
- Legal threats or an active dispute
- Employee allegations needing internal review
- Refunds, credits, discounts, replacements, or commitments the writer cannot authorize
- Any uncertainty about whether the business may disclose or confirm something publicly
This list is not legal guidance and does not tell you what any of these situations means for your business. It marks cases where a public reply written under time pressure is the wrong instrument. Who reviews them depends on the issue and your setup.
While a case is escalated: do not admit fault, and do not deny the allegation — not without verified facts and the authority to say either one.
A Quick Final Review
Once a draft clears the ten checks, run this pass before posting.
| # | Final check | Yes / No |
|---|---|---|
| 1 | Correct review, correct location | ☐ |
| 2 | No invented facts, dates, or details | ☐ |
| 3 | No private or sensitive information | ☐ |
| 4 | Tone is professional and not defensive | ☐ |
| 5 | No unauthorized commitment | ☐ |
| 6 | Any named private channel exists and we control it | ☐ |
| 7 | An authorized person approved this exact wording | ☐ |
Any “No” sends the draft back to REVISE or ESCALATE.
A simple approval record
Keep a short record of what was approved and by whom. Six fields:
- Review identifier or internal reference
- Draft version
- Outcome — Approve, Revise, or Escalate
- Approver role
- Approval date
- Brief reason, or the change requested
Record only what you need. Do not copy the review text, the reviewer’s name, or any customer detail into the log. An internal reference does the same job without creating another home for personal data.
Synthetic examples
The three examples below are fictional. No real business, customer, review, transaction, or location is involved, and none is evidence of how this checklist performs in practice.
Example 1 — APPROVE. A fictional landscaping business gets a three-star review saying the crew did good work but left later than expected. The draft acknowledges the job ran past the estimated window, blames nobody, offers nothing, and points to the contact details already on the profile. It clears all ten checks, and the owner approved the wording. APPROVE.
Example 2 — REVISE. A fictional appliance repair shop gets a one-star review about a return visit. The draft is polite and accurate, but ends by offering to cover the second call at no charge — written by a technician with no authority to waive a charge. Removing the offer fixes it without weakening the reply. REVISE, on check 6.
Example 3 — ESCALATE. A fictional dental practice gets a review about how a front-desk conversation was handled. The courteous, apologetic draft confirms the reviewer’s visit and what was discussed. The practice may not be free to disclose that publicly, and no rewording removes the uncertainty. ESCALATE, on checks 3 and 8.
How to use this checklist with AI-assisted drafts
AI can help here. It can produce a first draft quickly, and can apply this checklist to flag likely problems before a person looks.
What it cannot do is decide. AI may misunderstand context, invent a plausible detail, apologize for something that never happened, promise what nobody authorized, or produce a reply so generic it fits any business. None of that is obvious in a fluent paragraph.
So: treat AI output as a draft, never as verified fact. A person compares it against the review and the actual records, runs the ten checks, and an authorized human makes the final call.
The Tool Trial does not automatically publish replies to Google or any platform. Everything here ends with a person posting manually, on purpose.
Final takeaway
The reply you can defend beats the reply you posted first. Ten checks, three outcomes, and a stop rule will not make every review easy — but they keep the easy ones from getting expensive.
For the wider workflow: Review Replies pillar page — planned, not yet published. How we develop our guidance: Methodology page — planned, not yet published. The standards behind it: Editorial Policy page — planned, not yet published.
Sources
- Google Business Profile — Manage customer reviews:
https://support.google.com/business/answer/3474050?hl=en - Google Maps User-Generated Content Policy:
https://support.google.com/contributionpolicy/answer/7400114?hl=en
Both pages were checked on 2026-08-14.
These two official sources inform the factual and policy context above: replies are posted publicly and must follow Google’s content policies, and harassment, threats, doxxing, misrepresentation, and fake or misleading content are prohibited.
The approval framework, the ten checks, the three outcomes, and the operational safeguards are editorial guidance developed by The Tool Trial — not Google instructions, and not quoted from either page.
The Tool Trial is not affiliated with or endorsed by Google. Platform guidance can change; check these pages again before publication.