When you ask customers for reviews, the request itself is legal, useful, and expected. What gets US sellers in trouble is everything around the request: who you send it to, what you promise in exchange, and what you do with the answer you did not want. The FTC’s Rule on the Use of Consumer Reviews and Testimonials (16 CFR Part 465) took effect in October 2024, and it applies to a one-person shop exactly the way it applies to a national brand.
This is an operations problem, not a legal theory problem. Below is what the rule bans, and the concrete workflow that stays inside it.
What the FTC Rule Actually Bans
The rule is short and specific. Read it once and you can run from memory. It prohibits:
- Creating, buying, or selling reviews from people who never used the product or never existed.
- Insider reviews — you, your staff, your family — presented as ordinary customer feedback without disclosing the relationship.
- Providing anything of value conditioned on the sentiment of the review. „Five stars gets you a $10 credit“ is the textbook violation.
- Suppressing reviews through unfounded legal threats, intimidation, or false accusations, or displaying a hand-picked subset while implying it represents everything you received.
- Buying followers, likes, or view counts to misrepresent your influence.
Violations carry civil penalties assessed per violation, and the maximum is adjusted annually for inflation. There is no small-seller exemption.
Nothing in the rule stops you from asking, reminding, or making the request one click long. The compliant lane is narrower than most email templates assume, but it is wide enough to build a real review base.
Why Review Gating Fails, Even the Polite Version
Gating is the two-step funnel: ask „How did we do?“ first, send the 4s and 5s to Google or Trustpilot, and route the 1s and 2s to a private support form. It looks like customer care. Functionally it is a filter that turns your public rating into an average of pre-approved opinions.
That creates two separate exposures. First, the FTC’s suppression provision reaches conduct that keeps negative reviews out of a set you present as genuine customer feedback. Second, the platforms ban it outright in policy: Google’s contribution policies prohibit discouraging or filtering out negative reviews, and enforcement usually means review removal or a penalized profile, not a warning.
Keep the instinct, drop the filter. Send every eligible customer the same message, with the same public review link, at the same trigger. If you want a private feedback channel, offer it in addition to the review link for everyone, never as a substitute for people who look unhappy. The test is simple: if a customer’s predicted rating changes which link they see, you are gating.
When and How to Ask Customers for Reviews
Ask after the customer has experienced the outcome, not after the payment clears. A request that arrives before real use produces either silence or a review about your checkout page.
Workable triggers by product type:
- Digital download or template: 7 to 10 days after delivery, and only to buyers who actually downloaded the file.
- Service engagement: within 48 hours of the final deliverable being accepted, while the specifics are still fresh.
- Subscription or software: after the second successful billing cycle, or after a defined milestone — first report exported, tenth invoice sent.
- Physical product: after the return window closes.
Send one ask and one reminder six days later, then stop. Two touches is a request; five is harassment that shows up in the review you eventually get.
The one exclusion that is defensible: skip customers with an open, unresolved support ticket, and add them back to the queue when the ticket closes — regardless of how it was resolved. That is a timing decision, not sentiment filtering, and you should be able to show that people whose problems ended badly still received the request.
A request that reads like a person wrote it:
You downloaded the pricing workbook ten days ago. If you have run your numbers through it, a short public review helps other buyers decide whether it fits their situation. Two lines is plenty — what you were trying to fix, and whether it worked. Honest criticism is genuinely more useful to us than praise. [Review link]
Note what is missing: no stars mentioned, no „if you’re happy,“ no reward. Asking only satisfied customers is itself a form of gating, so write the message so it works for a mixed audience.
Disclosing Incentives Without Turning Them Into Bribes
Incentives are allowed under the FTC’s approach, but only when both conditions hold: the reward is not conditioned on what the review says, and the material connection is disclosed clearly and conspicuously where readers see it.
Practical rules:
- The offer must be identical for every reviewer. Never write „positive,“ „five stars,“ or „if you loved it“ anywhere in the offer.
- Pay out on a one-star review the same day you pay out on a five-star review. If your process cannot do that, do not run the incentive.
- The disclosure belongs inside the review text, not on your landing page. Ask for a line such as: „I received a $10 store credit for writing this review.“
- A sweepstakes entry, free upgrade, or extended trial is an incentive too. Same rules apply.
- Check platform policy before you offer anything. Google prohibits incentivized reviews, Amazon prohibits them outside its own program, and Yelp asks businesses not to solicit reviews at all. Platform bans stack on top of the federal rule.
Given the constraints, incentives are usually not worth it for small catalogs. Timing and a well-written ask reliably outperform a $10 credit that creates a compliance surface.
Responding to Negative Reviews Without Threats
This is where solo operators create liability under pressure. These responses are off the table: „We have forwarded this to our attorney,“ „This review violates our terms,“ refunding only on condition of deletion, or asking the customer to sign a nondisparagement clause in exchange for a fix. Unfounded legal threats and intimidation aimed at getting a review removed sit squarely in the suppression provision, and the Consumer Review Fairness Act separately voids form-contract clauses that bar customers from reviewing you.
Use a four-line structure instead:
- Name the specific problem back, in their words, without disputing it.
- State what you changed or are changing, with a date.
- Give one contact channel for the resolution.
- Stop typing.
Example: „You’re right that the Excel model didn’t open in Numbers — that wasn’t documented. The download page now lists the compatible versions, updated this week. Email support@ and we’ll get you a working file.“ Do not ask them to update or remove the review. If they revise it on their own, fine.
If a review is genuinely fabricated — no matching order, no support history — report it through the platform’s dispute process with your records attached. Contesting a factual claim through the official channel is not suppression. Threatening the reviewer directly is.
A Weekly Review Operation That Takes 20 Minutes
Make the whole thing a recurring block on one day of the week:
- Pull the list of customers who crossed the trigger since last week and remove only those with open tickets.
- Send the request and log the send date, so reminders fire once and never twice.
- Read every new review and respond to anything below four stars within 72 hours.
- Tag each negative review with a root cause: product gap, expectation gap, delivery, or support.
- Monthly, count the tags. If two customers name the same confusion in one month, the fix is a product or copy change, not a better reply.
Track five numbers of your own: requests sent, reviews received, response rate, median time to respond, and open themes. Those are the only review metrics you can actually verify — treat anyone quoting industry benchmarks at you with suspicion.
If you are starting from an empty review page, sequencing matters more than volume, which is the same logic behind building trust when nobody has heard of your brand yet. Ten specific, unfiltered reviews with visible replies do more work than fifty vague ones.
If you would rather not build the cadence, disclosure language, and reply scripts from scratch, the Ethical Review & Referral Engine collects them into a 14-page guide, an 8-sheet Excel workbook, and 14 ready-to-send templates; the rest of the operations workbooks live in the Cursiqa shop. This article is operational guidance rather than legal advice — read the current rule text and your platform’s policies before you launch a campaign.