Soft-Nudging vs. Review Gating: Where the Legal Line Actually Sits
The honest distinction between routing customers by satisfaction (legal) and blocking unhappy customers from public platforms (illegal). Six concrete examples on each side of the line, plus the 30-second self-test.
A coffee shop owner in Berlin asked me last month: "Can I show happy customers a Google button and unhappy ones a feedback form? Is that gating?"
The honest answer is "almost." The line between soft-nudging and review gating is one design decision wide. Most small business owners trip over it because the difference looks like a UX preference and is actually a legal distinction. This piece is about where exactly the line sits and how to stay on the right side of it.
If you have not read the back-story on why this matters, our piece on the FTC's $4.2-million review-gating case covers the precedent. This piece is the practical follow-up.
Friction vs. access blocking
The whole legal question collapses into two words: friction and access.
Friction is asking the customer to do extra steps before they reach a public platform. Friction is legal. Common forms:
- Showing a star prompt before the public review form
- Showing a longer feedback form before the platform buttons
- Adding a confirmation screen between the rating and the platform redirect
- Asking for the customer's name or email before the platform buttons (if the form is optional)
Access blocking is preventing the customer from reaching a public platform based on a signal you already have. Access blocking is not legal. Common forms:
- Hiding the public platform buttons when the customer rated 1 to 3 stars
- Routing 1-to-3-star ratings to a "thank you" page with no public option
- Requiring email-to-support before the public platform buttons appear
- Showing a CAPTCHA only to unhappy customers
The simplest reformulation: you can make it harder, you cannot make it impossible. Anything that requires the unhappy customer to leave your funnel and find the public platform on their own is access blocking, even if you frame it as a UX choice.
Six examples on the legal side
Cases I have seen running in 2026 that pass legal scrutiny:
Case 1: A restaurant. Customer scans the QR on the receipt. Sees a 1-to-5 star prompt. Rates 5 stars. Lands on a screen with three buttons: "Google," "Tripadvisor," "Yelp." Rates 1 star. Lands on a screen with a long feedback form, plus the same three platform buttons below the form (collapsed by default, expandable on tap). The platform buttons exist on every path.
Case 2: A dental clinic. Email goes out 24 hours after appointment. Star prompt in the email itself. 5-star clicks open Google directly. 1-to-3-star clicks open a feedback form on the clinic's site, with a footer line that reads "You can also leave a public review on Google here," with a visible link.
Case 3: An e-commerce shop. Order completion email asks for a 1-to-5 star rating. Happy ratings get a Trustpilot link. Unhappy ratings get a feedback form, with a sentence below the form: "Did the issue get resolved? You can also leave a public review on Trustpilot here."
Case 4: A salon. Receipt has two QR codes side by side: one for "Loved your visit? Leave us a review" (Google), one for "Something off? Tell us directly" (private form). Both visible at the same time, before the customer has rated anything.
Case 5: A hotel. Booking.com guest checkout email asks for the rating. Star prompt determines the lead button (Booking.com or Google for happy, feedback form for unhappy), but every email has a footer with three platform links visible regardless of the rating.
Case 6: A home services company. SMS sent two hours after the job. Link opens a star prompt. The page that loads (regardless of rating) shows the platform buttons in a footer that does not get hidden, ever.
The shared pattern: the public platform path is reachable in every flow, even if it is not the primary call-to-action.
Six examples on the wrong side
The same scenarios with a small design change that crosses the line:
Case 1, gated. Same restaurant, but the 1-star path lands on a "Thanks for the feedback, we will reach out" screen with no platform buttons.
Case 2, gated. Same clinic, but the 1-to-3-star feedback form does not include the line about the public Google option. The customer has to remember Google exists.
Case 3, gated. Same shop, but unhappy customers get a "Customer Service Resolution" page that requires them to enter a ticket number before any public platform link appears.
Case 4, gated. Same salon, but the receipt has only the "Loved your visit?" QR code. The "tell us directly" path is verbal-only, undocumented.
Case 5, gated. Same hotel, but the email body changes based on the rating. Unhappy email versions have no platform links anywhere in the email.
Case 6, gated. Same home services company, but the page footer hides the platform buttons via CSS for ratings under 4.
In all six gated examples, the asymmetry comes from one design choice: the public platform stops being visible based on a signal the customer has given. That is what triggers the legal analysis.
The 30-second self-test
Open your review collection funnel in an incognito browser. Click 1 star. From the screen that loads, count how many seconds and how many taps it takes to reach the Google review form for your business.
If it takes under 30 seconds and fewer than 3 taps without leaving the funnel: you are probably soft-nudging.
If it takes longer than 30 seconds, requires you to leave the page, or requires actions like emailing support first: you are probably gating.
The test is not a legal opinion, but it captures what regulators look for in practice. The FTC's enforcement actions have all centered on whether the public path remained reachable. Reachable is the test.
How Review Manager handles this
Honest disclosure: this blog runs on the company that built Review Manager. So I have a perspective.
The way the product handles the line is through a single architectural decision: the PlatformGrid (the component that displays public review platforms in the funnel) is hard-coded to be visible at every star rating from 1 to 5. There is no settings toggle that lets a business owner turn it off for low ratings. We blocked that flexibility in the source code, with a Playwright compliance test that fails the build if any star rating ever produces a screen without a visible platform link. We documented this in our compliance page.
This sounds restrictive. It is. The reason is that we wanted to ship a product that is defensible if it ever gets audited, and the easiest way to make a product defensible is to make the gating mechanic structurally impossible. A toggle that ships with "Off" by default and could be flipped on by a customer is a future legal liability. A constraint that does not exist as a setting cannot be misconfigured.
There is a UX cost to this approach. We give up the ability to ship the gating funnel that some customers ask for. We have heard that pitch from prospects more than once: "Can you just hide the buttons for 1-star ratings? That is the feature I want to pay for." We say no, every time. The trade-off is that the product is defensible for the long run, and the prospects who insist on gating tend to churn from any review tool within 18 months when the regulator catches up.
What to copy from this
If you are designing your own funnel without a tool, the simplest pattern that stays on the legal side:
- Star prompt comes first
- Every star rating leads to a screen that includes the public platform buttons
- Different ratings can vary which button is the primary call-to-action and which is secondary
- Different ratings can vary the additional content shown (e.g., a feedback form for low ratings, a thank-you for high)
- The public platform buttons never disappear
If you are evaluating a tool, ask the vendor: at what star rating does the public platform stop being visible? If the answer is anything other than "never," the tool is built for gating. The price difference between gating tools and compliant tools is usually small. The legal difference is not.