Here's a setup I see in almost every local-business automation build: a customer finishes a job or an appointment, they get a text asking "How'd we do, 1 to 5?", and the branch logic sends anyone who taps 4 or 5 straight to a Google review link. Everyone who taps 1, 2, or 3 gets routed to a private "tell us what went wrong" form instead.
Owners love it because it looks like it protects the star rating. It also happens to be the exact thing Google, Yelp, and the FTC have spent years trying to stamp out. It has a name — review gating — and it can get your reviews wiped or your profile delisted.
Full disclosure: I work for Ready, an SMS platform. I'm going to lean on timing and automation controls because that's the part local businesses actually get wrong. But the policy problem here is platform-agnostic. You can violate it just as easily in any tool.
What review gating actually is
Review gating is any process that filters who gets asked for a public review based on how they're likely to rate you. The sentiment-branch flow above is the textbook version, but it shows up in subtler forms too:
- Only texting the review link to customers a rep flags as "happy"
- A survey that routes low scores to a private complaint form and high scores to Google
- Offering the review link only after a positive interaction, and skipping it after a negative one
The common thread: you're using predicted sentiment as a gate on the public review request. That's the violation. It doesn't matter whether the gate is a workflow branch, a rep's judgment, or a survey score.
Google's policy is explicit that you shouldn't discourage or prohibit negative reviews or selectively solicit positive ones. Yelp goes further and actively penalizes solicitation of any kind. The FTC's rule on fake reviews and testimonials — which took effect in 2024 — treats suppressing or gating honest reviews as a deceptive practice, with civil penalties attached.
Why the penalties are worse than a bad review
The math that owners run in their head is: "A 3-star review costs me customers, so I'll route it away." The math they don't run is what a policy hit costs.
When Google catches gating, the usual outcomes escalate: individual reviews get removed, then review counts get frozen, and in repeat or egregious cases the whole business profile gets suspended. A suspended profile doesn't show up in Maps or local pack results at all. For a business that gets 60–70% of its calls from Google (a rough but common figure for local service trades), that's not a lost review — that's the phone going quiet.
One legitimately negative 3-star review, sitting in a pile of 4- and 5-stars, barely moves your average. A delisting removes every star at once. You're trading a rounding error for a cliff.
The compliant version: ask everyone, the same way
The fix is boring, which is why nobody wants to hear it. Send the same review request to everyone, regardless of predicted sentiment, and send it to the public platform directly.
That's it. No survey gate. No score branch. No "how'd we do" pre-filter that forks the road. Every customer who completes a transaction gets the same text with the same link.
You can still make it good. You just can't make it selective:
- Ask for a review, not a rating. Skip the internal 1–5 survey. Send them straight to your Google or Yelp link.
- Make it easy to reach you privately too — but offer that path to everyone, in the same message, not only to people you expect to complain. A line like "and if anything fell short, reply here and we'll fix it" is fine because it's not gated on sentiment.
- Time it well. This is where most requests fail, and it's got nothing to do with gating.
A message that goes to all customers might look like:
Hi {name}, thanks for choosing {business} today. If we earned it, a quick Google review means a lot to a small shop like ours: {link}. And if anything wasn't right, just reply here — we read every message.
Everyone gets that. Happy or not. That's the whole compliance standard.
Timing beats gating for actual results
Owners gate because they're trying to control the outcome. But the biggest lever on review quality isn't filtering — it's when you ask.
Send too early and the job isn't finished settling in the customer's mind. Send too late and they've moved on. For most service businesses the sweet spot is a few hours after completion, same day, within permitted local hours. A dentist might send at end of appointment; a home-services crew might send once the tech marks the job complete.
Two automation controls matter here, and they're where the platform earns its keep:
- Trigger off a real completion event, not a fixed time-of-day blast. In a GoHighLevel workflow, that's firing the review text when an opportunity moves to "Won" or an appointment is marked complete — and not stacking it into the same step as an email, which is a separate mistake that doubles your unsub rate.
- Respect quiet hours. A review request that lands at 9:40 PM reads as spam and gets you a reply you didn't want. Ready holds sends outside permitted local hours based on the recipient's area automatically, so a job that closes at 8:50 PM texts the next morning instead of at night.
Timing done well lifts response rates across your whole list. Gating just shrinks the list. One of these is legal.
The consent layer you can't skip
Review-request texts are still texts. The fact that you're not selling anything doesn't exempt you from the rules that govern the channel.
- The customer needs to have opted in to receive texts. A phone number on an invoice isn't automatic consent to be messaged — same principle that applies when a phone field on a donation form isn't consent to text.
- STOP has to work. If someone replies STOP to a review request, they're opted out of everything, and that should propagate so no future campaign hits them. Ready handles STOP automatically and carries the opt-out across campaigns.
- You need registered A2P 10DLC. Unregistered traffic gets carrier-filtered, and a review link that never delivers is worse than useless. If you're new to that, the 10DLC explainer walks through brand and campaign registration.
None of this is optional because you're "just asking for a review." It's the same consent wall as any other program.
What this costs to run
Compliant review requests are cheap, which is the last argument against gating — you're adding legal risk to save nothing.
A single review-request text is one segment if you keep it under 160 characters (drop the emoji — one unicode character cuts the limit to 70 and can split your message into extra billed segments). On Ready's Standard tier that's $0.02 plus the $0.0045 carrier pass-through, so $0.0245 per request.
A shop closing 400 jobs a month:
- 400 × $0.0245 = $9.80/month in send cost.
That's the entire program. There's no version of a review pipeline where gating saves you enough to justify a profile suspension. You can see the full tier breakdown on the Ready pricing page, and if you're wiring this into GHL, the setup guide covers the workflow side.
The practical takeaway
Review gating isn't a clever star-rating hack — it's a policy violation with an escalation ladder that ends in delisting. The compliant build is genuinely simpler: send the same request to every customer, route them straight to the public platform, offer a private reply path to everyone, and win on timing instead of filtering.
Get the trigger and the quiet-hours right and you'll pull more real reviews than the gated flow ever did, without betting your Google profile on it. If you want to set that up, you can start with 2,500 free credits — no card required — at app.tryready.com/signup and build the workflow before you send a single request.