Review reply approval register
Build a review-reply process with source checks, approval ownership and publication evidence. Includes a practical reply register.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Review reference | Issue to address | Facts verified | Draft owner | Approval reference | Publication check |
|---|---|---|---|---|---|
| Review-example-01 | Pickup explanation | Invoice checked privately | Service manager | Pending | Not published |
- Starting values are fictional examples, not customer records.
- Keep confidential evidence in your approved business systems. Record only a reference here.
- Complete each row from observed evidence. A completed worksheet does not certify legal compliance or provider compatibility.
- Export your CSV to approved storage before leaving this page.
A reply under your Google review is a public statement from your shop. Treat the approval with the same care as a written estimate. The person drafting needs the facts, and the person publishing needs authority. Sometimes the owner does both jobs, but don’t skip either one just because software produced a polished paragraph.
Use with this guide
review management workspace
Continue with review management workspace.
business dashboard
Continue with business dashboard.
Ask for repair-shop reviews after every eligible completed visit
Check whether eligible visits received a neutral request. Do not select customers by satisfaction or treat message delivery as a published review.
Decide what the reply needs to accomplish
Read the full review before you draft a reply. First, name the customer's concern in plain words: an unexplained diagnostic charge, a missed update, or a pickup time nobody confirmed. A workmanship reply won't fix a complaint about communication. And don't turn your response into a service list or an ad for the next visit.
Google says to keep replies useful and professional, and cautions against sharing private information. So what should you say publicly? Acknowledge the concern, explain what the shop is checking, and give the customer a way to contact the business. Discuss detailed invoice history in a private conversation. A customer naming a repair publicly doesn't make every internal note appropriate for publication.
Sources for this section: Google: review requests and public replies · Google Maps: genuine reviews, incentives and rating manipulation
Separate drafting from publication
Find the review in the review management workspace, check the theme, and draft your answer. With BlueFinch's Google workflow, you have to review the reply and explicitly approve it for publication. Saving a draft doesn’t post it. Check the selected business location and connected Google account before approving, especially if one manager handles two storefronts.
For an illustrative example, a customer says nobody called before closing. But the advisor’s notes show one attempted call and no successful conversation. Writing “we kept you fully informed” goes beyond the evidence. Say the team is reviewing the missed handoff, and invite the customer to speak with the manager. Don’t invent a resolution or promise a refund before someone authorized approves it.
Sources for this section: Google: review requests and public replies · Google Maps: genuine reviews, incentives and rating manipulation · BlueFinch: review management
Use a short approval register
The worksheet tracks the review reference, issue, verified facts, draft owner, approval, and publication check. Keep customer names, phone numbers, and invoices in your shop system. The public worksheet needs only internal references. Record the approved wording or document reference so another employee can see which version was cleared.
Pick one person to review routine replies, and name an escalation owner for threats, insurance disputes, injury allegations, or sensitive disclosures. This is a practical assignment, not a substitute for professional advice on a serious dispute. If the manager is unavailable, leave the draft pending. Don't let every employee improvise a public response.
Verify the result and close the underlying task
Once it’s published, check the live review on the right profile. Make sure the full approved reply is there, not an earlier draft. Record the date and result. If publication fails, keep the draft and investigate the connection instead of submitting more versions. One verified answer is easier to manage than a trail of inconsistent attempts.
A published reply does not establish that the operational fix is complete. The front desk might post an acknowledgment today, while the callback procedure needs another week of observation. Start the owner review in the business dashboard, then open the original issue. Track unresolved service tasks separately from unpublished replies. Otherwise, a nice-looking response rate can hide work customers still need you to finish.
Check the register every week. Clear out obsolete drafts, confirm who owns overdue cases, and sample published answers for factual accuracy. The useful result is a repeatable public response process with fewer unsupported statements, not a promise that every unhappy reviewer will change their rating.
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
- Google: review requests and public replies
- Google Maps: genuine reviews, incentives and rating manipulation
- BlueFinch: review management
Use this page for general business information. It is not legal, tax, or accounting advice.