The architecture rule
A customer who rated five and a customer who rated one must see exactly the same page, with the same two options in the same order. That single rule is what makes the product safe to point at a merchant's own public listing.
It is not a setting, a plan or a compliance mode. There is no configuration in which the screen branches on the rating.
Updated
Each is absolute. There is no plan, flag or partner arrangement in which any of them becomes available.
A one-star rating is stored, counted and delivered exactly like a five-star one. Nothing is screened out on the way to you.
The public step is a button to a listing. The customer writes their own words and presses publish, or closes the tab.
No screen, button, route or delay depends on the score. The page renders identically for every value on the scale.
The word covers more setups than most people expect, and the description used in the sales deck is not what platforms judge.
A survey that shows the public button only to people who rated well. A flow that routes the unhappy into a complaint form and the happy onto Google. A delay applied to low ratings. All of it is gating, and the sanction lands on the merchant's listing — usually with no explanation given.
7Feedback shows the private channel and the public listing to every customer, in the same order, at the same moment. The unhappy customer can publish. The happy one can write to you privately. Which one they pick is genuinely their decision.
Four public destinations, four different rules. The default target is the one whose requirements 7Feedback meets by construction.
The honest version
An unhappy customer with a working private channel more often tells the business first. Fewer of those visits end as a public complaint, and the public average drifts upward. The effect is real and entirely legal.
It is also a consequence, not a feature. The moment it becomes a promise on a landing page, the setup being described is one where the unhappy do not get the public button — which is the thing platforms sanction.
So the claim on this site is the narrow, true one: your customer gets a way to tell you directly. What that does to your public listing is between your team and your customers.
Exactly what a customer sees after a good one. No screen, button or route depends on the rating. Both options — writing to the business and opening the public listing — appear in the same order for a one and for a five.
Google Maps is the default target and TripAdvisor is available on request. Trustpilot only if the invitation is shown to every customer without exception, which is how 7Feedback works anyway. Yelp is never used, because it prohibits asking for reviews in any form.
Not for a public one. Platforms prohibit it, and the moment someone opens a public listing is not an event a reward can be attached to — that link does not exist and will not be built. Rewarding a customer for feedback given to you privately is a different question: ask us and we will walk through what is possible in your country.
It often does, and we will not promise it. The effect is real and legal: an unhappy customer who is given a working private channel more often tells the business first. That is a consequence of convenience, not of filtering — and anyone promising you a rating increase is describing something the platforms prohibit.
Next step
It is the page that answers their questionnaire, and it is easier to read than a contract clause.
