Yes, you can ask an unhappy customer for a Google review, as long as you ask for the same reason and in the same way you would ask anyone else. What you cannot do is ask only the people who seem pleased, or make your help depend on what they post. Fixing the problem and inviting a review are two separate acts, and the trouble starts when you tie them together.
What Google's policy actually says
Google's prohibited and restricted content policy lists rating manipulation as a violation. One of the listed behaviours is to "discourage or prohibit negative reviews, or selectively solicit positive reviews from customers", according to the policy text as quoted in search results. The same policy allows merchants to "solicit or encourage the posting of content that does represent a genuine experience", provided there are no incentives and no attempt to influence the rating or the contents.
Read those two together. Asking for an honest review is fine. Choosing who gets asked based on how they feel is not.
Where the line sits
Here is the test: did mood decide who got the invitation?
- Gating: you ask "how was everything?", send the smiling customers to your Google page, and send the frowning ones to a private form with no way to post publicly. The invitation depended on the answer.
- Not gating: you invite every customer who completed a visit, with the same message, whatever happened during it. Some of them will be unhappy. That is the point.
Starting a conversation with an unhappy customer is not gating either. Calling someone back to put a problem right is just good service. It becomes a problem only when the review request is quietly withheld from them, or when the fix is offered in exchange for a rating.
A sequence that stays clean
1. Fix the problem on its own merits. Refund the wrong order, redo the haircut, rebook the appointment. Do this because it is the right thing, not because it buys a review.
2. Never trade the fix for the review. Google's policy also bars offering payment, discounts, or free goods and services in exchange for posting a review, or for revising or removing a negative one. "We'll comp your meal if you change your rating" is out. So is "we'll comp your meal and then we'll ask you for five stars."
3. Let your normal request go out as usual. If your process sends a review link to every customer after a completed job, the customer who complained gets it too. You do not need to hide it from them or push it at them.
4. Do not steer. Do not say "now that we've sorted this, you'll leave us a good review, right?" That is an attempt to influence the rating. Keep the invitation neutral: "If you'd like to share your experience, here's the link."
5. Accept whatever they post. If they leave three stars after a good recovery, that is a real result. Reply publicly, thank them, and move on. Our guide to replying to a negative Google review covers the wording.
What about the customer who is still angry?
Some people will not want a review link at all. You are not obliged to send a second nudge, and following up repeatedly turns an invitation into pressure. One neutral request is enough.
If a customer tells you privately that they are unhappy, do not discourage them from posting publicly. That is the "discourage negative reviews" half of the rule. Listen, fix what you can, and leave the decision with them. For handling the private side of this, see handling negative private feedback.
Why a rating-first flow helps
The cleanest way to avoid the gating trap is to remove the judgment call. When every customer sees the same screen, taps a star rating, and then chooses for themselves whether to post publicly or send a private note, you never decide who gets the option. The customer does.
That is how Starboard's rating flow works: the stars come first, then the customer picks the destination, and the choice looks the same at one star as at five. Private notes land in a private feedback inbox so you can follow up quickly, and nothing is filtered or withheld from a public platform. If you want the full policy picture, our explainer on Google review gating walks through it case by case.
The short version
Ask everyone, or ask no one. Fix problems because they need fixing. Keep the fix and the review request separate, keep the wording neutral, and let the customer decide what to post. An unhappy customer you handled well is worth more than a smooth rating, and a policy violation costs you reviews you worked hard to earn.
If you are building a process that does this by default, start with the numbers: how many customers get asked, and how many of them you can reach privately before they reach Google.