Feedback Gate for Review Collection: What It Is and Why It's Banned

A feedback gate asks a customer how their experience went before deciding whether to show them a public review link — happy-sounding answers get the ask, everyone else gets quietly routed to a private form instead. It's marketed as smart risk management. Legally, in the US, it's the textbook example of banned review gating under the FTC's rule on consumer reviews (16 CFR Part 465). If a review-generation vendor pitches "smart routing based on sentiment" as a feature, that's exposure your client is buying along with the software, not an edge.

Last updated: September 2026

We're not writing this from a safe distance. An earlier version of DFY Hub's own Review Request Campaigns worked exactly this way — sentiment question first, then branch. We pulled it and rebuilt the flow to show every customer the same thing, specifically because of this rule. If you've seen an older description of our product (ours or a competitor's) that describes gating as a feature, that's the part to be skeptical of.

What a feedback gate actually does, mechanically

The pattern has three steps: ask a quick sentiment question ("how did we do?"), branch on the answer, and only surface the public review platform link to customers who signaled a good experience. Customers who signal anything less get a private feedback form and nothing pointing at Google or Yelp.

The pitch for building it is intuitive — dissatisfied customers write reviews more often than satisfied ones do, so a program that asks everyone the same way will surface some bad ones. A gate looks like it solves that.

Why it's banned, not just risky

The FTC's rule on consumer reviews and testimonials, finalized in 2024, prohibits soliciting reviews from customers in a way that the business knows or should know will result in reviews that misrepresent the seller's overall reputation — and it names sentiment-based routing directly as an example of that. Suppressing negative reviews while soliciting positive ones isn't a gray area under the rule; it's the specific behavior the rule was written to stop. Google's own review policies separately prohibit selectively soliciting reviews based on expected sentiment, so a gate breaks two sets of rules at once, not one.

"Structurally risky" undersells it. This is a compliance violation with your client's name on it, running automatically, every time the campaign sends.

What a compliant flow looks like instead

Every customer who opens a DFY Hub review request email lands on the same page: a public review link (Google, and Yelp if configured) and a private feedback box, shown together, with no sentiment question in front of either one. Nobody sees a different version based on how they're predicted to feel. The customer decides — public, private, both, or neither.

In practice, a fair number of dissatisfied customers pick the private box anyway, because it's sitting right there and doesn't require writing something public. That's a real outcome, just not an engineered one. Private feedback that comes in gets flagged for a person on the account to read and respond to directly — DFY Hub's Confirmation Required Flow keeps a human in that loop rather than auto-acknowledging it and filing it away. For the actual copy — the ask, the reminder, and the reply to a customer who used the private box — see review request email templates for contractors.

The volume argument doesn't actually need a gate

The real fix for "dissatisfied customers write reviews more" isn't hiding the ask from them — it's asking everyone, fast, and having a real plan for what shows up. How to get more Google reviews covers building request volume the compliant way, timed to within 48 hours of the job closing. And when a negative review does land publicly, how to respond to negative reviews covers what to actually do about it — a fast, specific, public response does more for a client's reputation than any routing trick would have.

Platform policies go further than the FTC rule

Even outside gating specifically, Google, Yelp, and Trustpilot each have their own solicitation policies — what you can offer in exchange for a review, how you can time a request, what a business can and can't say. Those policies change more often than federal rules do. Read the current version yourself before you write anything into a client's scope of work; don't take a vendor's summary of it as current, including this one.

Frequently asked questions

What is a "feedback gate" in a review request campaign?

A design that asks for sentiment before showing a review ask, then only surfaces the public review platform link to customers predicted to leave a positive review. Everyone else gets routed to a private form instead of the public option.

Is a feedback gate actually illegal, or just against platform rules?

Both. The FTC's rule on consumer reviews (16 CFR Part 465) prohibits soliciting reviews in a way designed to suppress negative sentiment and surface only positive sentiment — a feedback gate is a direct example of that. Google's solicitation policy separately bans selectively asking based on expected sentiment. It's a violation of federal rule and platform policy at the same time.

Does skipping the gate mean more bad reviews end up public?

Not meaningfully, and it's the wrong problem to solve for. Asking everyone the same way, fast and consistently, produces more total reviews — the honest way to hold the average up is with real service and fast, specific public responses to the negative ones, not by hiding the ask from people who might say something unflattering.

What does DFY Hub do instead of gating?

Every customer sees the same public review link and private feedback box on the same page, with no sentiment question deciding what they see. They choose. Private feedback still gets read and answered by a person on the account — it just isn't the only option shown to anyone.