How Mobile Detailers Can Ask for Honest Google Reviews

Ask for a genuine account of the customer's experience, without a reward, a rating requirement, or a filter that sends only satisfied customers to Google. Google permits authentic review requests but prohibits incentives and selective solicitation of positive reviews. (Google review-content policy)

Check both the law and the destination platform

The FTC's Consumer Reviews and Testimonials Rule prohibits compensation or other incentives expressly or implicitly conditioned on a particular review sentiment. Its guidance explains that the rule does not categorically prohibit every incentive for every review, while other FTC Act concerns and disclosure obligations can still apply. (FTC rule questions and answers)

Google's platform policy is stricter on this point: it prohibits offering payment, discounts, free goods, or services in exchange for any review. Disclosure of an incentive does not make a Google review request acceptable under that prohibition. (Google review-content policy)

The practical policy for Google requests is straightforward: offer no reward and do not try to influence the rating or content. Do not generalize that workflow into a legal conclusion about every review platform or testimonial arrangement.

Do not send only happy customers to Google

Google prohibits discouraging negative reviews and selectively soliciting positive ones. A process that asks for a satisfaction score and shows the Google review invitation only to high scorers is the kind of selective routing Rinse recommends avoiding. (Google review-content policy)

The FTC also advises businesses not to request reviews only from customers they believe will leave positive ones. Its rule FAQ distinguishes that concern from the rule's specific prohibitions, noting that the practice can implicate the FTC Act rather than claiming the rule contains a dedicated blanket review-gating provision. (FTC solicitation guidance, FTC rule questions and answers)

Private feedback is still useful. As an operating recommendation, make the support route available to everyone and keep access to the public review invitation independent of whether their feedback is favorable.

Use neutral request language

Google allows requests for genuine reviews without incentives or attempts to influence the rating or contents. It also prohibits pressuring users to leave reviews on the premises and requesting specific content in the review. (Google review-content policy)

The following are proposed templates, not messages already sent to customers. Replace the placeholders and use only a communication channel for which your business has the appropriate permission.

Email or receipt note

> Thank you for choosing [business]. If you would like to share your experience, you can leave an honest Google review here: [review URL]. Your feedback is optional and helps us understand our service. For a question or concern about the job, contact [support contact].

The invitation does not prescribe a score or a topic. The support route is available regardless of whether the customer leaves a review.

Short message

> Thank you for choosing [business]. You're welcome to share an honest review of your experience: [review URL]. For help with the job, contact [support contact].

This is copy only, not an approval to send automated texts. Check applicable consent, opt-out, and provider requirements before implementing SMS.

Optional follow-up

> A quick follow-up after your recent service: if you would like to share an honest review, the link is [review URL]. No action is needed if you would rather not.

Use restraint and honor communication preferences. This guide does not assert that a particular number of reminders is universally lawful, effective, or welcome.

Avoid shortcuts that change the request

• “Leave five stars for a discount”: The reward is tied to a positive sentiment and also violates Google's prohibition on review incentives. Do not use it even if the customer agrees to disclose the discount. (FTC rule questions and answers, Google policy)
• “Review us for any rating and get a free add-on”: Removing the rating requirement does not remove Google's ban on incentives for reviews. A broader FTC analysis is not permission to ignore the platform policy. (Google policy, FTC rule questions and answers)
• “Happy? Go to Google. Unhappy? Contact us instead”: This can selectively route positive reviewers to the public platform. Offer assistance to everyone without using satisfaction to determine who sees the invitation. (Google policy)
• “Mention our technician by name”: Google prohibits requesting specific review content, including content identifying a staff member. Ask for the customer's own experience instead. (Google policy)
• “We will refund you if you delete the review”: Google prohibits incentives for removing or revising reviews. Keep service recovery separate from review bargaining. (Google policy)
• “Have friends or staff help us get started”: Google prohibits conflict-of-interest content, which can include employment, family, contractual, and professional relationships. Do not manufacture a customer review base from those relationships. (Google policy)

A proposed review-request workflow

Use a neutral eligibility policy tied to real service experiences and valid communication permissions. Do not select recipients by whether the operator expects a favorable review.

• Complete the record: Confirm the actual service occurrence and use the correct customer contact record.
• Check communication permission: Apply channel preferences and applicable opt-out handling before sending.
• Select neutrally: Use a documented rule that does not depend on a satisfaction score, praise, or an expected star rating.
• Send the invitation: Use neutral wording, no incentives, and the correct destination.
• Offer support: Make the same support route available without requiring a private complaint before a public review.
• Limit repetition: Avoid duplicate invitations and stop follow-ups when appropriate.
• Audit changes: Test whether edits to the workflow, staff targets, or third-party tools introduce prohibited routing or pressure.

These are proposed implementation controls rather than a statement that Rinse currently automates them. Validate the actual product behavior before making a feature claim.

Measure the process, not just the star average

As an editorial recommendation, monitor neutral invitation coverage, delivery issues, duplicate sends, opt-outs, and customer complaints about the request process. Do not instruct staff to hit a Google review-request quota; Google's policy specifically prohibits merchants requesting that staff solicit a certain number of reviews. (Google policy)

An optional internal audit can inspect whether the same rules are applied across positive and negative feedback. Do not use the audit to identify and exclude customers likely to criticize the service.

Scope and limitations

This guide addresses selected Google policy and U.S. FTC guidance, not every platform, country, or messaging law. Policies change, so recheck the linked documents before changing an automated workflow.