Dealership review requests without rating filters

Audit dealership review requests for rating filters, incentives, and pressure. Use a practical BDC worksheet to invite honest feedback after a visit.

A dealership review request should invite an honest account of a real visit. It should not depend on a customer first giving the store a high survey score. For BDC managers, the work starts with the rule that decides who receives the invitation.

Quick answer: choose an approved visit-based trigger, check contact permissions, and send the same neutral invitation regardless of expected rating. Handle complaints on a separate path. Do not make the public review link a reward for a positive survey response.

This guide is for dealership managers reviewing post-visit follow-up. It offers a workflow to adapt, not legal advice or a promise of more reviews. Have the store's authorized compliance reviewer confirm applicable law, channel rules, and the review platform's current policy.

On this page

Check who receives dealership review requests

Start with the invitation rule, not the wording of the message. A polite request can still sit behind a rating filter.

Google Maps policy says merchants must not discourage negative reviews or selectively solicit positive reviews from customers.3 An invitation path that shows a public review link only after a high private survey score is the kind of selection a manager should look for.

Trace both paths through your survey or follow-up tool. Check what a customer with a low score receives and what a customer with a high score receives. Look for hidden conditions in campaign lists, staff instructions, vendor settings, and manual selection.

A legitimate contact restriction is different from a rating filter. An opt-out, invalid address, or lack of permission may prevent a message. Record that reason. Do not replace it with a vague label that could hide an unhappy customer being excluded.

For related contact controls, review the store's BDC opt-out workflow. A review request is not a reason to bypass a suppression rule.

A customer who reports a problem needs a clear route to someone who can address it. That route should not become a barrier to public feedback.

Let authorized staff work on the complaint without bargaining over a rating. Do not ask the customer to remove a review as the price of receiving help. Google also prohibits incentives for revising or removing a negative review.3

Keep the two records distinct: the complaint and its next owner, and any permitted review invitation. Closing an internal service task does not prove that the customer is satisfied. Nor does a positive rating prove that a promised fix was completed.

If a complaint needs a callback across shifts, use the existing callback handoff worksheet. Keep the customer's promised update visible even if no public review follows.

Ask for the experience, not a star rating

Google permits asking for reviews of genuine experiences without incentives or attempts to influence the rating or contents.3 Use neutral language that leaves the account of the visit to the customer.

A manager-reviewed invitation might read: "Thank you for visiting our dealership. If you would like to share your experience, you can leave an honest review here: [approved review link]." This is draft wording to adapt, not an approved message for any store or channel.

Avoid telling a customer which rating to choose, which employee to name, or which phrases to include. Google's policy also says merchants should not pressure people to review while on the premises.3 Give the customer room to decide whether to respond.

Do not treat federal rules and platform rules as interchangeable. The FTC says its review rule does not prohibit incentives that are not tied to a particular sentiment, but notes that failing to disclose incentives could violate the FTC Act.1 Google's policy is stricter on this point: it prohibits incentives in exchange for reviews.3 For a Google review request, do not offer a reward.

Audit the invitation path before launch

Use a small set of controlled records in an approved test environment. Do not send test requests to real customers. Compare the full path for different feedback scores and contact-permission states.

Check the message, destination link, eligibility rule, and exclusion reason. If a vendor operates the request flow, ask to see those settings rather than accepting a description of the process. A screenshot of the message alone cannot show who was filtered out before it was sent.

Copy this worksheet into the store's approved review process:

Keep customer information out of shared screenshots and public examples. The worksheet should document the process without exposing personal details.

Measure the request process without a rating quota

Review whether eligible customers received the approved invitation and whether exclusions had a documented reason. Separate requests attempted, messages delivered, and reviews actually observed. An attempted send is not proof of delivery or a posted review.

Google's current policy lists staff review quotas among prohibited solicitation practices.3 Do not turn the worksheet into a target that pressures staff to collect a fixed number of reviews. Use it to inspect the invitation path and correct faults.

The useful takeaway is simple: a dealership review request should follow the customer's real experience and contact permissions, not the rating the store hopes to receive. Start by checking whether a low survey score changes access to the public review link.

Frequently asked questions

What is review gating?

Review gating commonly describes a process that routes public review invitations according to expected sentiment, such as showing the link only after a high survey score. Google Maps prohibits selectively soliciting positive reviews. Audit both the survey flow and the rules that build the invitation list.[3]

Can a dealership offer a reward for a Google review?

Google prohibits incentives in exchange for reviews, including payment, discounts, and free goods or services. The FTC rule has a different scope, so a practice that is not prohibited by that rule may still break Google's policy. Have the store's reviewer check both requirements.[1][3]

Should unhappy customers get a different follow-up?

They may need a separate service-recovery conversation with an authorized person. Do not use that help as a substitute for, or condition on, access to public feedback. Keep contact permissions and suppression rules in force, and do not base review eligibility on the desired rating.

What should a BDC manager check before sending review requests?

Check the eligibility trigger, contact permissions, exclusion reasons, exact message, and destination link. Test the path for high and low feedback scores without messaging real customers. Confirm that complaint handling does not depend on a rating, and obtain the store's required policy review before launch.

Sources

Talk with Paramount Lead Solutions about your BDC follow-up workflow. The store's authorized reviewers remain responsible for its legal and platform-policy decisions.