· Notes for owners
How to get more reviews for your restaurant within the rule
Ask for restaurant reviews without breaking the federal review rule: what 16 CFR Part 465 prohibits, a request workflow to set up, and the traps to avoid.
On October 22, 2026, the Federal Trade Commission sued the operators of a government impersonation scheme over deceptive ads, misleading promises and fake reviews. The Commission alleges the scheme deceived travelers seeking passport services, and the press release sets out the charges. For a full-service restaurant, the part that matters is the federal review rule on fake reviews.
How should a full-service restaurant ask for reviews without breaking the federal review rule?
A full-service restaurant's own version of this problem is fake or manipulated reviews. Staff or friends post five-star reviews. A free dessert is offered only to guests who promise a good review. Each of the first two moves is the kind of conduct the federal rule targets. The field is large: 264,800 private full-service restaurants operated in the United States in 2025 (BLS, Quarterly Census of Employment and Wages).
The rule is 16 CFR Part 465, 2026 edition. It makes it an unfair or deceptive act to:
- write, create or sell a fake review;
- give compensation or incentives conditioned on a particular sentiment;
- have an officer or manager write a review without a clear and conspicuous disclosure;
- use threats or intimidation in response to a review.
The list does not name asking for a review. The request is where the second item can slip in, through a reward that depends on what the guest says.
Build the request so it stays inside the rule
The steps below turn the rule into a workflow that someone can run on a busy night.
- Map the request as it runs today. Note who asks, when, where the guest is asked and what words they hear. Find any step where guests are skipped or a reward is attached.
- Ask every guest the same way. Use one script and one review link. Do not choose who gets asked based on how the meal went.
- Keep rewards out of the review step. The rule's limit covers incentives tied to a particular sentiment. The rule as cited does not say whether a reward for leaving a review of any kind is allowed, so the request should carry no reward at all.
- Disclose any connection. If an officer or manager writes a review, it needs a clear and conspicuous disclosure of that role.
- Set one rule for replies. Answer reviews in a steady tone, with no threats and no intimidation.
- Keep a record. Save the date, the channel and the exact wording used for each batch of requests.
Across the country, 74,910 of the 265,527 private full-service restaurants (28 percent) had fewer than 5 employees in the first quarter of 2026 (BLS). A request that depends on memory is easy to skip on a busy night, whatever the size of the team. That is the reason to put it in a fixed step, as the list above describes.
Reviews also build trust
Reviews work as testimonials, and The Marketing Hourglass places video, case studies and testimonials in its trust stage. For a full-service restaurant, that stage comes before the first meal. A review request that stays honest protects that trust.
In New York County, 4,236 private full-service restaurants operated in 2025, at an average annual pay of $52,918 per worker. In the first quarter of 2026, the county counted 4,138 such restaurants, at an average weekly wage of $977 (BLS). With that many restaurants in the county, a clean request step is the part of reviews an owner can control.
Two traps to avoid
- Offering a reward for positive reviews. A discount or dessert tied to a good review breaks the incentive limit in 16 CFR Part 465 directly. Sentiment is the test, so any reward on the request step is the trap to watch for.
- Treating a repeated figure as a finding. A trade source repeats the claim that 87 percent of potential customers will not consider businesses with low ratings. The figure is given without a population or year, so it should not guide a plan.
Our work is to act as a restaurant's technology department: we map the workflow, build the software that fits it, and run it. The first step is to map the request as it runs today, find where it leaks, and decide which step the technology should take over. To start that map, book a discovery call.