Review Gating: What It Is and How to Request Reviews Fairly

Recognise the gated journey

The problem is not asking a private question before a public-review action. The problem is changing access according to the answer. If a high score reveals Google while a low score reveals only a support form, the business is selectively soliciting the customers it expects to be positive.

Gating can also happen before the QR code is shown: staff may be told to invite only visibly happy customers, or an automated invitation may be limited to a stage reached only by successful experiences.

• High score → public review, low score → private only
• Review QR shown only to customers selected by staff
• Invitation list filtered by satisfaction or complaint status
• Positive-rating language such as “Give us five stars”

Platform rules focus on fair and genuine invitations

Google Maps policy prohibits discouraging negative reviews or selectively soliciting positive reviews. Trustpilot requires invitations to be fair, neutral and unbiased. Tripadvisor says positive and negative respondents must receive an identical path when an external survey directs people to Tripadvisor.

Policies differ by platform and can change. Check the current rules for every destination you use. The US Federal Trade Commission also regulates fake reviews, sentiment-conditioned incentives and certain forms of review suppression, but platform policy and law are not interchangeable. This guide is operational guidance, not legal advice.

Use one of three honest campaign structures

A direct public-review campaign can make one neutral invitation after a genuine experience. A private-feedback campaign can collect a score and reasons without making a public-review request. A combined campaign can do both when every respondent retains the same public-review action.

Choose the structure by the intended outcome before printing. Do not describe private issue resolution as a mechanism for preventing negative public reviews.

• Public review: one direct, neutral external action
• Private feedback: hosted survey and internal workflow
• Combined: private survey plus equal public-review access

Write a neutral request instead of asking for praise

Use wording such as “Share your experience”, “Leave a review” or “Tell us how the visit went”. Name the genuine experience and let the customer decide what to say.

Avoid “Leave us a five-star review”, “Happy customers: review us” or any reward tied to posting, changing or removing a review. Incentives and employee contests have their own platform restrictions even when every customer sees the invitation.

Keep service recovery separate from review access

A low private score can alert the team and start an internal recovery workflow. That is a valid operational use of feedback. It does not justify hiding the review action, pressuring the customer to change a review or offering compensation on condition that a review is removed.

If the respondent left contact details and separately consented to follow-up, the team can address the reported problem through its own channel. The public-review choice remains the customer’s.

Use product safeguards, but keep human ownership

Mosaqo keeps review destinations at campaign level rather than as questions inside the feedback form. Its policy checks reject known patterns such as a review destination embedded in the form, a reward-for-review prompt or explicit high-rating solicitation.

Automated checks cannot guarantee compliance with every language, context, platform update or local law. The campaign owner must still review the copy, destination and complete mobile journey before publication.

Run a pre-publication fairness check

Test the journey with a low, neutral and high score. The same public-review action should remain available after each response in combined mode. Scan the final printed QR rather than relying only on the editor preview.

Confirm that the invitation is neutral, the destination is correct, no incentive depends on sentiment, private follow-up requires consent and reporting labels outbound clicks as clicks rather than published reviews.

• Same public-review access after every score
• Neutral request tied to a genuine experience
• No reward conditioned on a review or sentiment
• No claim that a click became a published review
• Current destination-platform policy reviewed