Bizness Growth Association

Opening BGA…

How to ask for customer reviews without filtering out unhappy customers

Build a neutral review-request process, separate support from public feedback and check the difference between FTC rules and Google Maps policy.

Share this guide

LinkedInFacebookX

Make an honest invitation the operating goal

A review request creates a choice for a customer. The owner controls who receives the invitation, what it promises and where the link goes. The customer should control whether to respond and what to say. Before buying reputation software or assigning staff a task, examine those three owner-controlled decisions.

This guide addresses a national customer-acquisition problem, including businesses in the DMV and Delaware. The platform and federal facts below were checked November 18, 2026. The workflow and example are BGA's original operating analysis, not a finding about a particular business or a promise of higher ratings, sales or search visibility.

Keep the federal rule and platform policy separate

FTC staff says the Consumer Reviews and Testimonials Rule took effect October 21, 2024. Its Q&A explains that incentives conditioned on a particular sentiment are prohibited; disclosing payment does not make a paid five-star review permissible. The Q&A also cautions that selectively asking happy customers could violate the FTC Act even though the rule does not specifically prohibit that practice.

Google Maps separately prohibits incentives for any review, selective positive-review solicitation, pressure to review on the premises, requests for specific review content and staff review-solicitation quotas. It permits requests for genuine experiences without incentives or attempts to influence content or rating. Read the destination platform's current policy before designing a request; a distinction in federal guidance is not permission from Google.

Audit the path before choosing a message

Start with a neutral eligibility rule, such as customers who completed a defined service during a stated period. Apply the same rule regardless of whether someone complimented the work or complained. Check channel permission and opt-outs separately: having a completed transaction does not by itself settle every email, text or privacy requirement.

Look for a satisfaction question placed before the public review link. If a high score opens the public link while a low score leads only to a private support form, the workflow filters who receives the public invitation. BGA recommends making support available without using it as a gate to public feedback.

Inspect the actual customer journey, including the low-score branch, on a test configuration. Confirm that the public link belongs to the correct business and location. Do not publish a test review, supply a customer's words, or have AI invent an experience. Keep the test out of live customer messaging.

A fictional routing example

Assume a service business has 40 completed jobs in an illustrative period and permission to use the selected contact channel for all 40 customers. Its current survey routes 30 favorable responses to a public review invitation and 10 unfavorable responses only to support. These are invented counts used to show the routing problem, not BGA client results.

The repair is to remove sentiment-based routing and offer the same optional public invitation to the comparable customers, with support accessible to everyone. It is not to persuade the other 10 customers to change their scores. If some customers lack channel permission or have opted out, exclude them for that reason and document that reason separately from satisfaction.

The example does not establish a review-conversion rate: survey responses, message acceptance, actual delivery and a published review are different events. A review appearing later does not prove that a particular request caused it.

Use neutral wording and a separate support route

An original draft to adapt after checking the platform and contact-channel requirements: Thank you for using [service]. If you would like to share your experience, you can leave an honest review at [verified public review link]. Feedback is optional. Please avoid including private information. For help with your service, contact [support route].

Replace every placeholder, remove incentives and rating suggestions, and test the link without submitting a review. Do not add a request to name an employee or mention a keyword. For Google Maps, do not set a staff quota for soliciting reviews. Train staff to make the invitation optional and to handle service concerns through the support process.

A short invitation has a tradeoff: it gives the owner less control over the resulting story. That is the point of asking for independent customer feedback. A private service-recovery conversation can still resolve a problem without making a benefit depend on changing or deleting a review.

Review the process, then the business evidence

Assign an owner to check routing, permission records, opt-outs, wrong-location links and unresolved support handoffs. Inspect a small sample from different satisfaction outcomes to see whether the same eligibility rule is being applied. Avoid collecting extra personal data just to connect a public reviewer to a customer.

Track only what records support. A sender's accepted receipt is not delivery; observed reviews are not completed sales. Use actual completed inquiries, bookings and collected revenue when assessing business value, and leave unattributed outcomes unattributed. No campaign was sent and no business outcome was measured for this article.

An immediate next step is to draw the current request path on one page and test every branch. If the public invitation disappears after negative feedback, fix that routing before expanding the program. Recheck the linked policies when changing software or platforms; this guide does not resolve every sector-specific or state contact requirement.

Original sources

Share this guide

LinkedInFacebookX