Consider an illustrative two-rooftop dealership group, East and West. Its sales and service teams use separate follow-up messages. A vendor adds an offer: share what you loved about your visit and receive a $25 service credit. The marketing manager spots the problem and changes the request to an honest review. The reward stays. So does the Google link.
The campaign has better manners. It still breaches the destination's incentive policy. The edit addressed one federal-rule question without fixing the Google-bound request.
This is where an established business can get caught: separate approvals for the copy, reward and destination leave their combination unchecked. A useful reputation program preserves genuine customer evidence. Its approval has to cover the full experience behind the message.
Where this fits
A changed request reopens the collection check
- Discovery
- Recommendation
- Foundations
- Review collectionAudience · offer · destination
- Feedback
- Improvement
Recheck
After an audience, offer or destination changes
↺ Back to discovery
Editorial model: the Digital Footprint Loop. Recheck connects the next campaign version to its current destination policy.
Three versions, three different decisions
The FTC's Consumer Review Rule took effect on October 21, 2024. Section 465.4 prohibits incentives expressly or implicitly conditioned on a review expressing a particular sentiment. In the dealership example, the phrase what you loved ties the reward to praise. Calling for an honest review removes that sentiment condition only if the offer and surrounding instructions genuinely do the same.12
Google has a separate policy. It bars incentives for reviews and selectively soliciting positive feedback; it permits genuine, unincentivized requests that leave the customer's opinion independent. Yelp takes a different position again: its policy bars businesses from soliciting Yelp reviews.34
Changing the dealership's Google request therefore takes more than substituting one adjective. Removing the reward addresses the platform's incentive restriction. The selection rule and customer path still matter. Moving that revised message to Yelp would create a different destination problem, even with the reward removed.
Illustrative request versions
Removing the praise condition leaves another decision
Assumptions: each version links to Google; A and B offer a $25 service credit, while C offers a review invitation alone.
| Request shown to the customer | Federal incentive question | Google destination |
|---|---|---|
| Version AShare what you loved about your visit and receive a $25 service credit. | The reward implies positive sentiment. §465.4 prohibits that condition. | A review-linked incentive is barred. |
| Version BShare an honest review of your visit and receive a $25 service credit. | A genuinely sentiment-neutral reward is outside that specific prohibition. Other duties remain. | The incentive restriction still applies. |
| Version CShare a review of your visit.Review invitation only; the customer chooses the rating. | The invitation offers no reward to condition on sentiment. | Still check genuine experience, selection and influence. |
Change the destination to Yelp? Yelp bars business solicitation, including an unrewarded invitation.
Sources: 16 CFR §465.4, FTC staff Q&A, Google policy and Yelp policy, checked October 1, 2026. The highlighted phrase shows where praise enters the offer; the unchanged reward explains why Version B still fails the Google check.
The unit of approval is the whole request path. A template can sound fair while a survey sends only satisfied customers to the public page, a staff script adds a reward, or a vendor swaps the destination. The message shown in an approval email is only one part of what the customer encounters.
Read the federal ceiling in its enforcement context
In December 2025, FTC staff warned ten companies about possible Consumer Review Rule violations. The letters cited civil penalties up to $53,088 per violation. They were warnings; a violation finding would require enforcement. A published notice effective September 15, 2026 retained the 2025 penalty levels during 2026.56
That ceiling is serious enough to belong in the approval conversation. Courts can impose penalties for knowing violations; liability and the legal counting of violations are fact-specific. Estimating exposure requires the facts of the campaign and qualified legal assessment. A contact list tells the operator how many people received a message; an enforcement finding establishes which conduct violated the rule.15
The platform consequence belongs in a different column. Google's published possibilities include a temporary block on new reviews, temporary unpublishing of existing reviews and a profile warning after a fake-engagement determination.7 Those actions affect the public evidence customers use to judge a business.
For the dealership group, the practical stake is the credibility of each location's record when a buyer compares sales teams or a driver chooses a service department. A campaign strengthens that record when it reveals the customer's own judgment.
Each business picks its moment; the honesty standard stays the same
A service customer has collected a repaired car. A vehicle buyer has completed a handover. Those are different events, even inside the same group. A request triggered by a scheduled appointment alone can arrive before the customer has experienced the promised work.
Consider an illustrative specialty-clinic group that introduces an initial consultation before a later procedure. Its vendor retains the old completed-treatment template. The first consultation now triggers a message asking the patient to praise a treatment outcome, although the procedure is still ahead. The clinic manager discovers the mismatch in the first follow-up batch. The relevant clock runs from the changed visit pathway to the next message customers actually receive: revise the event and wording to refer to the consultation experienced, then check that exact patient-facing version. Only a completed treatment establishes a treatment result.
An illustrative restaurant group has a shorter decision window. A new payment-terminal script asks guests for a Google rating while the server is still waiting beside them. Google bars requiring or pressuring customers to review while on the premises.3 The manager removes the requested star score, but the invitation remains part of completing payment. The next shift therefore repeats the pressure that the copy edit missed. The manager separates the optional invitation from payment and checks the next shift's actual interaction. The restaurant's clock is a shift handover; the clinic's is a follow-up batch and the dealership's is vehicle collection.
Across these businesses, the common thread is independence. Useful reviews come from the experience the customer actually had, rather than the rating, timing or wording the business wants to collect. The service journey determines the appropriate event; the platform determines the destination rules.
Private feedback remains valuable. It lets a team investigate a late collection, a confusing follow-up instruction or a billing question. Preserve the public option independently of the customer's satisfaction, alongside that private route. Service recovery and public-review eligibility are separate decisions.
Find the shared setting behind the complaints
Across the dealership group's eight configured paths, a manager selects twelve recent feedback records for a campaign review. Six mention a review request arriving before collection or handover. Four praise a staff member. Two report an unresolved service problem.
Eight paths means two rooftops, each with sales and service messages, each sent by email or text: 2 × 2 × 2. It counts the configurations the manager needs to inspect.
The six early-request comments reveal a trigger problem. Their common link is the scheduled event, rather than confirmation that the customer has collected the car. The two unresolved problems belong with the service manager and the workshop. The four compliments describe staff performance; campaign timing needs evidence from the actual request path.
The resulting decisions are few. The vendor replaces the premature trigger with the agreed completed-service or handover event. The campaign approver removes the review-linked reward from the Google-bound version and inspects the public path for both satisfied and dissatisfied responses. The service manager takes the unresolved cases through normal service recovery.
The team leaves the compliments alone in this campaign repair because they concern staff performance. Keep them for recognition while maintaining the same public-review eligibility for customers who praised the staff and customers who raised a problem.
Illustrative operating record
Eight configurations can share one premature trigger
Assumptions: two dealership rooftops × sales and service × email and text = eight configured paths. Twelve selected feedback records illustrate triage.
East rooftop
- Sales · email
- Sales · text
- Service · email
- Service · text
West rooftop
- Sales · email
- Sales · text
- Service · email
- Service · text
Each configured path is a set of campaign settings to inspect.
Early request
6 of 12 selected records
Pattern → decision
Request arrives before collection or handover. Vendor replaces the scheduled-event trigger with the agreed completion event.
Proof
Observed email/text path, followed by whether early requests recur.
Staff praise
4 of 12 selected records
Leave outside this repair
Keep this evidence for staff recognition. Use the actual request path to assess campaign timing.
Unresolved service
2 of 12 selected records
Escalate separately
Service manager owns the unresolved work. Each issue merits attention according to its service impact.
Proof
The service issue is resolved and the customer receives the next step.
Three customer paths, three different checkpoints
The checkpoint follows each sector's operating change.
Dealership group
- Change
- Vendor adds a scheduled-event request trigger.
- What runs
- The request arrives before collection or handover.
- Checkpoint
- Next completed-service or handover event after repair.
- Proof
- Observed email/text uses that completed experience. Every customer's invitation is unincentivized and independent of satisfaction.
Specialty clinics
- Change
- A consultation now precedes the later procedure.
- What runs
- The retained treatment template asks about an outcome still ahead.
- Checkpoint
- First post-change consultation message.
- Proof
- The event and wording refer specifically to the consultation experienced.
Restaurant group
- Change
- Review invitation enters the payment-terminal script.
- What runs
- Server waits beside the guest while asking for a rating.
- Checkpoint
- Next shift after the manager separates invitation from payment.
- Proof
- Actual interaction keeps the optional invitation separate from completing payment.
Six early-request records point to the shared trigger; four compliments go to recognition and two unresolved cases go to service recovery. Source: selected audit record, 6 + 4 + 2 = 12.
Verification has two parts. A test of the actual email and text paths shows that the new event, offer and destination reached the customer-facing version. Subsequent feedback shows whether early requests still occur. A saved template establishes what was intended; an observed path establishes what ran. The clinic checks the first post-change consultation message; the restaurant checks the next shift's payment interaction. Each check follows the experience its customer actually completed.
The next vendor edit reopens the decision
A reviewed campaign needs a fresh decision whenever a reward, survey branch, location link or staff script changes the request. A shared edit can propagate across departments before anyone notices a local variation.
The operating record needs to keep those connections visible: the approved customer event, eligible audience, offer, destination, live wording and responsible approver. A changed destination calls for that destination's current policy. A changed reward reopens the incentive question. A complaint about service belongs with the team that can change service.
This work sits inside the Digital Footprint Loop: collect genuine feedback, distinguish a recurring defect from unrelated comments, change the relevant instruction, and check what customers now encounter. The negative-review response guide explains the public-reply side; multi-location consistency explains why a shared standard still needs branch-level verification.
How RaveHQ fits
RaveHQ sends timed Google review requests through its connected workflow, respecting contact permission and opt-outs. Private feedback remains additional to the public review path. A weekly report and action queue bring the next reputation task back to the team, while staff focus on the handover, appointment or service experience. Feedback collection becomes a maintained workflow rather than a fresh chase after every visit.
One revealing question
Ask which live customer path the last campaign approval covered. A copy document establishes the intended sentence. Follow it through to the audience rule, reward and destination the customer actually encountered.
For the dealership, the next useful milestone is concrete: customers who have completed the relevant experience receive the approved, unincentivized Google request, whichever way they felt about it. For the clinic, the request names the consultation experienced rather than a treatment outcome still ahead. For the restaurant, the optional invitation sits separately from payment. Each team maintains a different customer path; the shared standard is genuine experience and independent choice. Open the next message or observe the next shift to see whether that standard reached the customer.
Questions owners ask
Does calling a rewarded review honest make the campaign acceptable?
An honest label leaves the reward in place. A genuinely sentiment-neutral incentive is outside the particular prohibition in §465.4, but other FTC Act requirements remain. Google prohibits review incentives regardless of that wording. The destination has to be considered separately.123
Can a disclosure fix an offer for a five-star review?
The violation remains. FTC staff says a reward conditioned on a five-star review still violates §465.4 even when the business discloses the incentive.1
Does private feedback have to disappear?
Keep a useful service-recovery route, while preserving the public option independently of customer satisfaction. A shared inbox and a satisfaction-based gate do different jobs.
Does one late request prove the campaign is broken?
It identifies a path worth checking. In the illustrative record, repeated early requests led to the event-setting repair. A serious individual problem can still merit prompt attention on the strength of its service impact.
Sources and interpretation
- FTC, Consumer Reviews and Testimonials Rule: Questions and Answers, staff guidance published November 8, 2024; refreshed October 1, 2026 UTC. Supports the effective date, sentiment-conditioned incentives, disclosures and knowing-violation penalty mechanism. Part 465 leaves selective requests outside its specific prohibitions, while the FTC Act can still apply. Staff guidance describes the FTC staff's interpretation; a specific campaign needs qualified legal assessment.
- 16 CFR §465.4, Buying positive or negative consumer reviews, eCFR current through September 29, 2026, accessed October 1. Supports the express-or-implied sentiment condition. The eCFR is an authoritative, unofficial presentation of federal regulations. The rule was published August 22, 2024 and took effect October 21, 2024.
- Google Maps, Prohibited and restricted content, accessed October 1, 2026. Supports incentive and selective-solicitation restrictions, genuine unincentivized requests, and the prohibition on pressure to review on the premises. This is Google's platform policy, maintained separately from federal law.
- Yelp's review-request policy, official policy, accessed October 2, 2026. Supports the bar on business solicitation of Yelp reviews. The recommendation-software explanation describes Yelp's approach to requested reviews.
- FTC, warning letters to ten companies, December 22, 2025, accessed October 1, 2026. Supports the $53,088 maximum and the distinction between warning letters and violation findings.
- FTC, Civil Penalty Inflation Adjustments, Federal Register 91 FR 58446–58447, effective September 15, 2026, accessed October 1. Retains 2025 penalty levels during 2026.
- Google Business Profile, restrictions for policy violations, accessed October 1, 2026. Supports the three possible review restrictions described. Google determines their application, notifies businesses and provides an appeal route.
Scope of this guide. The incentive comparison addresses §465.4 and destination policies; a whole-campaign legal assessment also considers other applicable duties. The FTC maximum is a ceiling for fact-specific knowing violations, rather than a charge per message or an estimate of a particular case. Google's restrictions are possible responses to a policy finding; their effect on bookings or ranking depends on circumstances. The dealership, clinic and restaurant records are fictional illustrations. Their quantities count configurations and selected feedback, while their checkpoints follow the stated customer journeys. They supply examples of decisions, rather than population rates, measured sector timings or predicted customer results. Staff guidance supplies an interpretation, rather than a legal safe harbor.