Private feedback and public reviews do different jobs. Private feedback tells you what to fix and reaches only you. Public reviews tell strangers whether to trust you and stay on the internet permanently. A business that collects only one is missing half the picture, and the way you offer both decides whether you stay inside Google's rules.
What each one is for
Public reviews are a sales asset. A prospective customer reads them before choosing between you and the next result. They are written for that reader, whatever the reviewer intended.
Private feedback is an operations asset. It is a note, a rating, or a short form that lands in your inbox. One comparison piece on private feedback versus public reviews describes it as input meant to surface operational issues and service friction before they turn into public complaints.
The two differ on four points:
- Audience. One person on your team versus every future customer.
- Detail. People write candid, specific notes in private. Public reviews skew shorter and more performative.
- Permanence. A private note can be answered and closed. A public review stays on the page.
- Your power to respond. In private you can refund, apologise and fix the problem quietly. In public you can only reply.
Why you need both
If you collect only public reviews, you hear about problems late. A customer who had a bad Tuesday posts on Thursday, and you learn about it when a stranger does.
If you collect only private feedback, you fix things but build no public proof. Your Google profile stays thin, and our post on how many Google reviews you need explains why a thin profile costs you when someone is comparing options.
Each channel catches what the other misses. The private inbox surfaces the awkward truth a happy-but-annoyed customer would never post. The public profile turns your many satisfied customers into visible evidence.
Where the line with Google sits
This is where businesses get into trouble, so it is worth being exact. Google's review policies prohibit selectively soliciting positive reviews and discouraging negative ones. Summaries of the policy, such as this explainer on review gating workflows, describe it the same way: you shouldn't ask only satisfied customers to review, or filter customers before they reach the review platform.
The test is simple. Ask who decides.
- Gating: the business uses a score, or predicted sentiment, to decide who is shown the public review option. Happy customers see Google, unhappy ones see a private form.
- Not gating: every customer gets the same rating prompt, and the customer decides whether their feedback goes public or private.
The second is a choice, and it is the only version you should build. If the private route ever replaces, delays or hides the public option for someone who is unhappy, you have crossed the line. We go through the rules in more detail in Google review gating policy explained.
One consequence: a private route can't be a way to suppress anything. Customers who pick it have chosen it, and customers who want to post publicly always can.
How to set it up so both work
- Show the same screen to everyone. Stars first, then the choice of where it goes. Don't change what a person sees based on their rating.
- Make the private option as easy as the public one. If it takes four taps to reach, you've built a funnel for public reviews and the private channel is decoration.
- Keep the private inbox owned. A note nobody reads is worse than none. Assign an owner and a response window. Handling negative private feedback covers how to triage them.
- Don't pay for either. No discounts, no draws. Incentivised reviews are prohibited, and rewarding private feedback only for good scores recreates the gating problem.
- Read the two together. A theme that shows up in private notes will often show up in public reviews a month later if you ignore it.
A private feedback inbox sits at the end of that flow, and the rating flow is what makes the choice the same for everyone.
What to do with the public side
Private feedback does not remove the need to answer reviews. Reply to everything that is posted, keep replies short, and move any dispute offline. How to reply to a negative Google review has a structure that works.
The short version
Collect private feedback to fix what is broken. Collect public reviews to show strangers what is working. Give every customer the same prompt and let them pick the destination. That keeps both channels honest and keeps you on the right side of Google's rules.
Starboard's flow works this way: stars first, then the customer chooses where their feedback goes. The principle applies whatever tool you use.