A customer thanks your cleaning crew for a job well done. Another customer tells a plumbing technician that the repair went smoothly. Should you ask them to leave a Google review? Yes—but the wording, timing, and selection process matter more than many small businesses realize.

A review request should give a real customer an easy, voluntary way to describe an actual experience. It should not steer that customer toward five stars, reward a specific rating, or screen out people who might have concerns. The distinction is especially important for a business using automated follow-up software, where one poorly written template can be sent to every customer.

There are two sets of rules to understand: U.S. federal standards enforced by the Federal Trade Commission (FTC) and the policies of the platform where the review will appear. Following one does not automatically mean you comply with the other.

Understand the difference between FTC rules and Google policy

The FTC's Consumer Reviews and Testimonials Rule took effect on October 21, 2024. It addresses practices such as fake or false reviews, incentives conditioned on positive or negative sentiment, undisclosed insider reviews in specified circumstances, and certain forms of review suppression. The FTC's official questions and answers also emphasize that its rule is not a complete guide to every practice that might violate the broader FTC Act.

One particularly important distinction concerns incentives. The FTC rule does not categorically ban an incentive for a review when there is no express or implied requirement that the review express a particular sentiment. But an incentive can still require disclosure, and the circumstances can still be deceptive under the FTC Act.

Google Maps applies a stricter platform standard: businesses may not offer payment, discounts, free services, or similar benefits in exchange for a review, regardless of whether they demand a positive rating. Google's user-generated content policy also prohibits selectively soliciting positive reviews and pressuring customers to include specified content.

For a business asking for Google reviews, the simpler operating rule is to offer nothing in return. It is unnecessary to build an incentive program just to ask customers to share their experiences.

Ask customers based on a consistent event, not their mood

A common mistake is to ask for reviews only when a customer says, "That was fantastic," while sending dissatisfied customers somewhere else. That can distort the public picture of service quality.

Instead, define an ordinary operational trigger: a completed and confirmed service appointment, a closed work order, or an appropriate follow-up after the customer has had a chance to experience the result. Make the request available to eligible customers regardless of whether their feedback is likely to be favorable.

A landscaping company might send one review invitation after a completed maintenance visit. An HVAC business may prefer to wait until a service ticket is closed and any immediate follow-up is resolved. A handyman operation could include a request in its usual post-job email. The right moment depends on what a customer can reasonably evaluate, not on how likely the owner thinks a five-star rating will be.

Keep legitimate service recovery separate from review selection. If a customer reports an unresolved problem, address it promptly. Do not make assistance conditional on their leaving a review, withdrawing a complaint, or changing what they wrote.

This does not mean every possible customer must receive an identical message at the same second. It means the process should use defensible, neutral criteria rather than filtering people by predicted sentiment.

Give customers an uncomplicated way to leave a Google review

Google Business Profile provides a review link and QR code that a business can share. Google's instructions for creating a review link or QR code describe uses such as receipts and thank-you messages.

The request itself can be brief:

After-service email example

"Thank you for choosing us for your recent service. If you'd like to share your experience, you can leave an honest Google review here: [review link]. Your feedback helps other customers understand what working with us is like. Thank you for your time."

Invoice or receipt example

"How did we do? You're welcome to share your experience in a Google review using this link or QR code. Reviews are optional, and we appreciate candid feedback."

Verbal example

"If you have a moment later, we'd appreciate an honest review of your experience. There's a link on your receipt."

These are editorial templates, not legal safe-harbor language. Adapt them to the business, check the platform's latest policy, and avoid inserting a reward, a desired rating, or a required keyword. Don't ask customers to name a particular technician to meet an internal contest or quota: Google specifically identifies pressure for staff-name mentions and specified review content as rating manipulation concerns.

There is no need to ask a homeowner to post while a technician watches. In fact, Google advises merchants not to pressure customers to leave ratings or reviews on the premises. Let the customer decide if, when, and what to write.

Keep private feedback separate without hiding the public option

Businesses need a way to learn about problems before they become repeated complaints. A post-service survey can help identify missed appointments, confusing estimates, or poor communication. But using that survey as a filter for public reviews is a different matter.

Consider a workflow that asks, "Were you satisfied?" and shows the Google review link only to customers who answer yes. Everyone else is routed privately to customer service. That is a classic selective-solicitation pattern and conflicts with Google's policy against soliciting only positive reviews.

A better design makes two options clear to everyone: share a public review if they wish, and contact the business directly if they need assistance. The private support path must not replace or obstruct the public review path for people who report problems.

If your review software labels customers as promoters or detractors, inspect the actual email logic—not just the vendor's sales description. Ask to see who receives a public review invitation, what happens after a low survey score, and whether the software offers any rewards. The business remains responsible for evaluating the workflow it approves.

Avoid family, employee, and fabricated reviews

A real review must reflect a genuine customer experience. Business owners should never write reviews from customer accounts, hire a service to generate fabricated testimonials, or ask staff to pretend they are independent customers.

Connections matter. The FTC rule addresses undisclosed insider relationships in specified situations, while Google treats current or former employment, consulting arrangements, family relationships, and other conflicts of interest as potential grounds for disallowed review content. A relationship disclosure that may matter under federal law does not automatically make a conflicted Google review acceptable.

For Google reviews, keep employee and family advocacy out of the review-request program. Rely on real customers who can independently describe the service they received. If a vendor promises a batch of five-star reviews, don't assume those are legitimate because the vendor calls them "verified."

The same rule applies to website testimonials. Do not invent a quote, turn a customer's private message into an attributed testimonial without appropriate permission, or edit a review so substantially that its meaning changes. A carefully selected quotation can still mislead if the editing conceals essential context.

Handle complaints without trading favors for review changes

A negative review may contain an honest account of a frustrating experience, a factual dispute, or material that violates the platform's rules. These are different situations and require different responses.

If the customer reports a legitimate issue, investigate the service and offer an appropriate remedy based on the merits of the complaint. Do not say, "We'll issue the refund if you delete your review." Google prohibits incentives in exchange for revisions or removal of negative reviews, and the FTC warns that paying for changes or removal of truthful negative reviews may be deceptive under broader law.

If a review contains prohibited material, use the platform's reporting mechanism instead of pressuring the customer. If the concern needs a public response, keep the reply factual, brief, and respectful. Never reveal private customer addresses, billing records, or service details to win an online argument.

A review program that welcomes honest criticism also creates an operational benefit: recurring complaints can identify weaknesses in scheduling, estimates, and communication that deserve attention beyond marketing.

Review your automated messages before sending another batch

Small service businesses often combine booking software, invoicing tools, text messaging, and reputation-management platforms. That can make requests easier to send, but it can also hide an outdated script or an unauthorized incentive.

Before approving a workflow, check these questions:

  • Does the invitation go to customers selected by neutral, documented criteria rather than expected star ratings?
  • Is the request voluntary and written in neutral language, with no prize, discount, or other benefit for Google reviews?
  • Can a customer share negative feedback publicly without being routed away from the review link?
  • Does the system avoid asking for five stars, staff names, keywords, or a review while the customer is being watched?
  • Are customer contact details used in accordance with applicable privacy and messaging requirements?
  • Can the owner inspect and stop the automation, including messages sent by an outside agency?

For text messages, review any applicable consent and telemarketing requirements separately. Review-platform compliance alone does not establish that an automated SMS campaign is lawful.

Keep the review link current, save the approved message template, assign someone to monitor replies, and periodically sample what customers actually received. A modest, consistent process is easier to supervise than a complex funnel designed to maximize a star rating at any cost.

Judge the program by trust and usefulness, not just review count

The purpose of a review system is not to manufacture an impressive score. It is to make honest experiences easier for prospective customers to find while giving the business an opportunity to learn.

Look at whether review requests are reaching real customers, whether customers can speak candidly, and whether repeated feedback highlights improvements the business can make. Do not assume that more reviews guarantee higher rankings, more phone calls, or more booked jobs. Google describes reviews as one of several signals associated with local prominence, not a promise of a particular result.

When an owner is deciding whether to spend more on review software or agency support, the first question should be simple: Does this process collect authentic feedback without manipulating it? If the answer is unclear, fix the process before increasing its reach.

Federal rules, state laws, messaging requirements, and individual review platforms may impose different obligations. The examples here are general operational guidance, not legal advice; seek qualified counsel for a disputed enforcement or compliance question.

Sources and Further Reading