A practical Switzerland guide to review-gating accusations, selective review requests, Google policy risk, evidence preservation, and measured public response.
Why Review-Gating Accusations Need A Separate File
A review-gating accusation is different from an ordinary false-review dispute because the business has to inspect its own workflow, not only the review text. In Switzerland, the practical question is whether the company used neutral review requests or whether dissatisfied customers were routed into private complaint channels while positive customers were pushed toward Google. That is a process question first, and only later a removal or defamation question.
A disciplined file therefore separates rhetoric from records. A reviewer may overstate what happened, but management should still test the underlying workflow: survey branches, QR codes, follow-up emails, CRM automations, branch scripts, agency instructions, refund offers, and any practice that could discourage negative reviews or selectively solicit positive ones. The business weakens its position if it denies everything publicly before that internal audit is complete.
Evidence Checklist Before Anyone Replies
Preserve the public side first: the full review URL, reviewer profile, rating, exact wording, screenshots, timestamps, visible edits, and any owner reply draft. Then preserve the internal side: review-request templates, survey branching logic, complaint-routing pages, QR destinations, SMS or email campaigns, staff guidance, and a chronology showing what customers were asked to do before and after the accusation was posted.
The key audit question is whether public review access changed by sentiment. Did all eligible customers receive the same opportunity to leave a review. Were unhappy customers invited only to complain privately. Were discounts, goodwill credits, or service recovery tied to review revision or removal. Was staff training framed around asking only happy customers. A short public reply is easier to defend when the internal record already answers those questions calmly.
Google Policy And The Local Consumer-Law Angle
Google policy matters on two levels here. First, the review itself may still be false, provocative, or non-genuine and may justify ordinary reporting if the facts support that route. Second, Google's prohibited and restricted content policy makes clear that merchants must not discourage negative reviews or selectively solicit positive ones. That means the business should not treat the platform report as a substitute for auditing its own solicitation process.
Local legal review should also take account of Swiss Federal Act against Unfair Competition. That source matters because a review-gating accusation can sound like deceptive commercial conduct rather than mere insult. Even if the business ultimately disputes the accusation, the safer posture is to preserve the workflow, classify any real compliance risk, and keep the public wording aligned with what the internal file can support.
What A Measured Public Reply Usually Says
Where a public reply is needed, it is usually safer to acknowledge the concern, say the business is reviewing both the feedback and its review-request practices, and invite the reviewer to a private official contact channel. The reply should not promise that the accusation is impossible unless the business has already audited the workflow that the accusation is actually about.
What the reply should usually avoid is calling the reviewer a liar, scammer, extortionist, criminal, or competitor before the file supports that allegation clearly enough. It should also avoid publishing names, order numbers, screenshots, or internal explanations simply to prove the reviewer wrong. The public response is a risk-control step, not a courtroom submission.
When Escalation Deserves Closer Review
Closer escalation review may be justified when the accusation is repeated across multiple reviews, appears tied to a competitor or former insider, coincides with a broader fake-engagement campaign, or exposes a real internal practice that now creates platform or consumer-protection risk. In those files, the business usually needs both tracks at once: a narrow Google report for the review itself and an internal compliance clean-up that is preserved rather than hidden.
No result should be promised. A careful reply does not guarantee removal, court relief, regulator action, or reputational repair. Its practical value is narrower: it protects the record, reduces avoidable admissions, and keeps the business aligned with the strongest available Google or legal route.
Related PimLegal Reading
For related reading, see our local guide on fake Google reviews, consumer protection and removal strategy and the Switzerland Google review removal page. These two internal links connect public-response drafting with the wider removal and escalation strategy in Switzerland.
Selected Official References
- Swiss Federal Act against Unfair Competition
- Google prohibited and restricted content policy
- Google Business Profile review reporting guidance
- Google Business Profile guidance on managing customer reviews
Practical Conclusion
A review-gating accusation should be handled as a dual inquiry. Test whether the reviewer can support the allegation, but also test whether the business's own review funnel was neutral, documented, and consistent with Google and local consumer-law expectations before any aggressive public or legal escalation.
This article is general information only and not legal advice for a specific dispute in Switzerland. Businesses should seek local advice before sending formal notices or publishing detailed accusations.