Your Review Request Should Not Buy a Five-Star Rating

A five-star review can help a customer choose a plumber, a franchise location, an outdoor product or a nonprofit partner. That makes reviews valuable. It also makes the process used to collect them worth examining.

The risky practices rarely arrive with a label that says fake reviews. They often look like ordinary growth tactics:

• A team offers a gift card only after a customer leaves five stars.
• A survey sends happy customers to Google while unhappy customers stay in a private feedback form.
• A technician stands beside a customer and asks for a specific rating before leaving the job.
• A franchise location asks employees, relatives or vendors to boost a new profile.
• A brand publishes an edited testimonial that changes the customer's meaning.

These shortcuts can violate platform rules, create regulatory exposure and weaken the proof the business was trying to build.

The better approach is not complicated. Ask real customers for honest feedback, ask consistently, document the workflow and use criticism to improve the operation.

Review enforcement is an operating issue, not a fine-print issue.

The Federal Trade Commission's Consumer Review Rule took effect on October 21, 2024. The FTC's Consumer Reviews and Testimonials Rule Q&A explains that the rule addresses fake or false reviews, incentives conditioned on positive or negative sentiment, undisclosed insider reviews, review suppression and fake indicators of social influence.

On December 22, 2025, the FTC warned 10 businesses about possible violations. The letters were not findings that those companies broke the law. They were a clear reminder that the agency can pursue civil penalties when it believes a business knowingly violated the rule.

Google's policies create a second layer of responsibility. Its prohibited and restricted content guidance says businesses cannot offer payment, discounts, free goods or services in exchange for posting, changing or removing a review. Google also prohibits selectively soliciting positive reviews and discouraging negative reviews.

The policies do not mean a business should stop asking for reviews. Google explicitly provides tools and guidance for requesting reviews. The important distinction is that the request should seek an honest account of a genuine experience, not a purchased rating.

This article provides an operational checklist, not legal advice. Businesses facing a specific enforcement, contract or regulatory question should speak with qualified counsel.

Start by mapping the request customers actually receive.

Most owners know the intended process. Fewer have seen every text message, email, leave-behind card, survey branch and employee script that reaches a customer.

Run the audit from the customer's point of view. Collect each active request and write down:

1. The request trigger should be clear. Record whether the message is sent after a completed job, delivered order, support conversation, donation, event or other genuine interaction.
2. The eligible audience should be defined. Record who receives the request and whether the selection changes based on an internal satisfaction score.
3. The exact message should be preserved. Save the text, email, QR card, on-site script and follow-up message as the customer sees it.
4. Every destination should be identified. Note whether the customer is sent to Google, another review platform, a marketplace, the company website or a private survey.
5. Any benefit should be documented. Include discounts, drawings, loyalty points, gifts, donations and employee rewards tied to the request.
6. The owner of the workflow should be named. Identify the person who can change the automation, train the team and respond when a platform flags the profile.

This inventory often finds the real problem quickly. A marketing leader may have approved neutral language while an old automation still promises a discount for five stars. A franchise brand may have a compliant national template while local operators use their own cards and scripts.

Remove rating gates from the workflow.

Review gating happens when a business asks customers how they feel, then encourages only satisfied customers to publish a review. Unhappy customers are routed somewhere private.

Private feedback is useful. The problem is using it to determine who is invited to leave a public review.

A sound workflow can ask every eligible customer for both forms of feedback:

• The customer can share private feedback directly with the business.
• The same customer can choose whether to describe the experience on a public platform.
• The public review invitation does not change based on the customer's survey score.

If the current automation contains a question such as “Were you satisfied?” followed by different review options, inspect the branches carefully. The safer design is a consistent, neutral request sent to a defined group of genuine customers.

Separate appreciation from a required rating.

Businesses use incentives because response rates are hard. The short-term lift is not worth a review program that customers or platforms cannot trust.

Google prohibits incentives in exchange for reviews. The FTC rule specifically prohibits compensation or incentives that are expressly or implicitly conditioned on a review expressing a particular positive or negative sentiment.

That means these messages should be removed:

• “Leave five stars and receive ten percent off your next service.”
• “Show us your positive review for a free upgrade.”
• “Update your rating and we will resolve the charge.”
• “Employees receive a bonus for every five-star review that names them.”

Employee recognition can still focus on service quality. Use verified customer-retention, first-time resolution, response time or broad satisfaction measures instead of paying for a particular public rating.

If a team wants to thank customers for research participation, keep that research program separate from public review solicitation. Make the terms clear, collect useful private feedback and do not require a public review or a particular sentiment.

Give employees a neutral script they can use comfortably.

Frontline teams often create policy risk because the approved language feels awkward in a real conversation. A short, natural script works better.

For example:

Thank you for trusting us with the work. We will send a link where you can share honest feedback about your experience. Your comments help future customers know what to expect and help our team improve.

The script does not ask for five stars. It does not hover over the customer while the review is written. It does not suggest what the customer should say.

Train employees to avoid pressure when the customer is on the premises or when the technician is still in the home. The customer should have time and space to decide whether to respond.

For home-service teams, add the neutral script to the closeout checklist. Our local SEO checklist for home-service businesses explains how review operations fit with profile accuracy, service-area pages and local proof.

Multi-location brands need one policy and local visibility.

Franchise systems have a specific challenge. The brand can provide compliant tools, but the customer interaction happens locally.

The national or regional owner should establish:

• A single approved request template should be available for each major customer journey.
• Local operators should know which incentives, filtering rules and employee requests are prohibited.
• The system should record which location sent the request and which profile received the review.
• A regular spot check should compare the approved workflow with messages actually used in the field.
• Escalation instructions should explain what to do when reviews disappear, a profile is restricted or an operator discovers a questionable campaign.

This is not about removing local judgment. It is about protecting every location from a shortcut used by one location. The local SEO guide for franchise brands covers the broader system for ownership, listings, local pages and reporting.

Respond to criticism without trying to erase it.

A negative review is not automatically a reputation crisis. A defensive, revealing or manipulative response can turn it into one.

Use a response process that protects the customer and the business:

1. Acknowledge the concern without arguing about every detail. The public response should show that the business is listening.
2. Do not disclose private customer or account information. Move the detailed conversation to a secure channel.
3. Offer a specific next step. Give the customer a named contact, phone number or support path.
4. Document the operational issue internally. Classify themes such as scheduling, communication, product quality, billing or follow-up.
5. Do not trade resolution for removal. Resolve the problem because it is the right customer action, not because the customer promises to delete or revise a review.

If the content violates a platform policy, use the platform's reporting process and keep a record of the submission. Do not mass-report legitimate criticism simply because the rating is uncomfortable.

Treat review data as customer-experience research.

The best review program does more than improve an average rating. It produces a steady stream of customer language and operational evidence.

Once a month, review the themes across public reviews, private feedback and contact-center notes. Look for:

• The reasons customers say they chose the business.
• The promises customers repeat when the experience goes well.
• The handoffs or delays that create frustration.
• The locations, services or products with different patterns.
• The questions that marketing content should answer before a customer contacts the team.

Share those findings with operations, sales and marketing. A recurring complaint may point to a broken process. A recurring phrase from satisfied customers may reveal a positioning idea that is more credible than a brainstormed slogan.

This is where reputation management becomes part of strategy. Reviews should inform service improvements, local content, sales conversations and the proof displayed on the website.

Use a 30-day cleanup plan.

A focused month is enough to replace risky shortcuts with a useful operating system.

Week one should document the current process.

Collect every request, survey branch, incentive, employee script and vendor workflow. Identify who can change each one.

Week two should correct the language and targeting.

Remove rating gates, sentiment requirements, review-linked benefits and requests from people without genuine experience. Write a neutral template for each customer journey.

Week three should train the team and locations.

Give employees a short script, examples of prohibited pressure and a clear escalation path. Confirm that franchisees, agencies and software vendors use the approved process.

Week four should connect reviews to improvement.

Create a basic monthly report that covers request volume, response rate, review themes, response time and operational follow-up. Do not judge success by star average alone.

Honest reviews are stronger proof.

A reputation cannot be manufactured into durability. It has to be earned, requested fairly and maintained through the way the business responds.

The practical standard is straightforward. Ask real customers consistently. Ask for an honest account. Do not buy the sentiment. Do not hide criticism. Give the team a workflow it can explain without embarrassment.

That approach may feel slower than a five-star shortcut. It produces proof that is more useful to customers, safer for the business and more valuable over time.

Build a review program that earns trust.

Strats & Roadmaps helps local and multi-location teams connect customer experience, local search, reputation management and practical follow-up. Review the reputation-management approach or start a conversation to audit your review workflow and build a stronger system for customer proof.