Getting Reviews: A System for Asking Customers
Most businesses handle reviews one of two ways. They never ask, hoping a happy customer volunteers a write-up on their own. Or they ask occasionally, whenever someone remembers, with no consistency in who gets asked or when. Neither approach builds a review count that keeps growing.
How reviews turn into star ratings in Google's local pack and knowledge panel is a display and schema question, and Brass-SEO covered that ground already in Getting Reviews That Show Up in Search. This post is about the part that produces the reviews in the first place: a repeatable system for asking, built around timing, a low-friction ask, and a plan for what happens after someone responds.
Quick Navigation
- Why Random Asking Fails
- When to Ask: Timing the Request
- The Ask: Make It One Click
- Building the System: A Repeatable Process
- What Google Prohibits: Incentives and Gating
- Responding to Reviews
- Frequently Asked Questions
Why Random Asking Fails
A review request that depends on someone remembering to send it will get sent inconsistently, and an inconsistent ask produces an inconsistent review count. The businesses with steady, growing review counts have turned the ask into a step in their process, not a favor someone does when they think of it.
Picture two shops with identical work quality. One asks every customer, at the same point, every time. The other asks whenever the owner has a good day and remembers. A year later, the first shop has a review count the second one can't catch up to, and the work behind both shops was the same. The difference was never the quality of service. It was whether asking happened by design or by accident.
This matters because most satisfied customers will not leave a review unprompted. They meant to. They got busy. A system closes that gap by making the ask happen automatically, every time, without relying on anyone's memory.
When to Ask: Timing the Request
The best time to ask for a review is right after the customer experiences the result they came for, while the satisfaction is still fresh. Wait a week and you're asking someone to reconstruct a feeling instead of report one.
That "right after" moment looks different depending on the business. A repair shop's moment is when the customer picks up the finished car and pays the bill. A restaurant's moment is the end of the meal. A consultant's moment is project delivery. A retailer shipping product has to wait for delivery, since asking before the item arrives means asking before there's anything to review. In every case, the target is the same: catch the customer at peak satisfaction, not weeks later when the detail has faded and the motivation to type anything has faded with it.
| Business Type | Trigger Moment | Timing Window |
|---|---|---|
| Restaurant or retail (in-person) | Payment at checkout | Same visit |
| Home services (repair, cleaning, HVAC) | Job completed, invoice paid | Within 24 hours |
| Professional services (legal, accounting, consulting) | Engagement or project completion | Within 24 to 48 hours |
| E-commerce | Delivery confirmed | 3 to 5 days after delivery, once the product's been used |
Set the trigger once, per business type, and every request fires from the same starting point. That consistency is what turns an occasional ask into a system.
The Ask: Make It One Click
A review request needs to travel a customer from "yes, I'd be happy to" to a submitted review in under a minute, or most of them will never finish it. Friction is the reason satisfied customers who agree to leave a review often don't.
Google Business Profile has a built-in way to remove that friction. From the profile's "Get more reviews" option, you can generate a short link that opens the review box directly, skipping the step where a customer has to search for your business and pick the right listing from a results page. That link is the mechanism. Everything else in the ask is about getting it in front of the customer at the right moment.
Email. If a receipt, invoice, or delivery confirmation already goes out by email, the review link belongs in that same message rather than a separate one. One extra line does the job: a short thank-you, one sentence explaining that reviews help, and the link.
Text message. For service businesses that already text appointment confirmations or job completion notices, a follow-up text with the review link performs well because it arrives on the same device, in the same channel, the customer already checks.
Receipt or in-person. A printed QR code on a receipt or at a checkout counter works for foot-traffic businesses, especially paired with a verbal ask from staff. A staff member saying "if you were happy with the work, a Google review really helps us" and pointing to the QR code closes more of the gap than either alone.
Keep the message short. One line of thanks, one line asking, one link. A long paragraph explaining why reviews matter to your business reads as begging, and it buries the one thing you need the customer to click.
Building the System: A Repeatable Process
A review system is four decisions made once and then repeated without rethinking them: the trigger, the channel, the message, and the follow-up. Make those decisions once, write them down, and the system runs without your attention.
Pick the trigger. Use the table above as a starting point. The trigger has to be a specific, observable event: invoice paid, order delivered, appointment closed out. Not "sometime after the job."
Pick the channel. Use whatever channel you already communicate through for that trigger. If you text appointment reminders, text the review request. If you email invoices, email the request. Don't add a new channel just for reviews; ride the one the customer already expects to hear from you on.
Write the message once. A short template, reused every time, removes the decision fatigue that causes requests to get skipped when someone's busy. Save it somewhere the whole team can find it.
Track who's been asked. Even a simple checklist prevents two failure modes: asking the same customer twice in a short window, which reads as pushy, and forgetting to ask at all because nobody was sure if it had already happened.
Send one follow-up, then stop. If a customer hasn't responded within a week, one polite reminder is reasonable. A second reminder is not. Repeated requests annoy the people you're trying to build goodwill with, and the annoyance outweighs whatever review it might produce.
Once those four decisions are made, the system needs almost no ongoing thought. The trigger fires, the channel is fixed, the message is templated, and the tracking catches the edge cases. That's what separates a business that asks consistently from one that asks whenever someone remembers.
What Google Prohibits: Incentives and Gating
Google's Business Profile policy bans two specific review-solicitation tactics: paying or discounting for a review, and selectively asking only the customers you expect to leave a good one. Both fall under what Google calls rating manipulation, and both carry real risk to a profile that gets caught doing them.
The first is straightforward. Offering a discount, a gift card, a free item, or any other incentive in exchange for posting a review is prohibited, whether the incentive is tied to a positive review specifically or to any review at all. Google's prohibited and restricted content policy lists this explicitly under rating manipulation, alongside a related ban on paying to have a negative review revised or removed.
The second is subtler and easier to fall into by accident: review gating. This is the practice of screening customers first, often through a private survey or a staff member's judgment, and only sending the public review link to the ones who seem happy. Customers who seem dissatisfied get filtered out before they ever reach Google. Google's policy directly prohibits soliciting reviews selectively based on expected sentiment, along with related tactics like instructing staff to solicit a specific number of reviews or reviews that include specific content.
The fix is simple: ask everyone who completes the triggering event, using the same message, sent through the same channel. Don't pre-screen for happiness and don't dangle an incentive. A profile found manipulating ratings can lose the ability to receive new reviews for a period, or have existing reviews unpublished, which does more damage than a handful of genuine three-star reviews ever would.
Responding to Reviews
Responding to reviews is the follow-through half of the system, distinct from the solicitation step but just as much a habit worth building. Asking gets the review; responding is what a prospective customer sees when they read it later.
Make review responses a weekly task, not something that happens only when someone happens to notice a new review. A five-minute check-in once a week catches everything and keeps responses timely, which matters because a reply that shows up two months late reads as neglect regardless of what it says.
Positive reviews get a short, specific thank-you. Naming the actual service or detail the customer mentioned shows you read what they wrote instead of pasting a form response: "Thanks for the kind words about the tune-up, James — glad we got you back on the road same day."
Negative reviews get a calmer version of the same treatment. Acknowledge what went wrong, state what you'll do about it, and offer to continue the conversation off the platform rather than arguing in the replies. Future customers read how you handled the complaint more closely than they read the complaint itself.
Responding to reviews also feeds the ranking side of local SEO, since review activity is one of the signals that factors into local pack placement. Brass-SEO's guide to what actually moves local pack rankings covers where review signals fit alongside the rest of that picture.
Asking for reviews is manual work. No tool sends the text message or hands the customer the QR code for you. What a tool can do is show whether the reviews you're earning are translating into search visibility, and whether the local searches you're competing for are actually finding your pages. Brass-SEO connects to both Google Search Console and Google Analytics 4, which are both required, and answers questions like these in plain English instead of a stack of dashboards. For the full picture on local search beyond reviews, see the local SEO playbook. You can start a 3-day free trial from the dashboard for $25/month after.
Frequently Asked Questions
When is the best time to ask a customer for a review?
Right after the customer experiences the result they came for: payment at checkout for in-person businesses, within 24 hours of a completed job for home services, within 24 to 48 hours of project delivery for professional services, and a few days after delivery for e-commerce once the customer has used the product. Waiting longer than a few days lets the satisfaction fade, and the request starts competing with everything else in the customer's week.
What's the best way to send a review request?
Use a direct link that opens the review box in one click, generated from your Google Business Profile's "Get more reviews" option, sent through whatever channel you already use to communicate with that customer at that trigger point. A business that already emails receipts puts the link there; one that texts appointment confirmations puts it in the follow-up text. Foot-traffic businesses pair a printed QR code with a verbal ask from staff. One line of thanks, one link.
Is it okay to offer a discount for a review?
No. Google's Business Profile policy explicitly prohibits offering payment, discounts, or free goods or services in exchange for posting a review, revising a review, or removing a negative one. This falls under Google's rating manipulation rules, and a profile caught doing it risks losing the ability to receive new reviews or having existing reviews unpublished.
What is review gating and why is it against Google's policy?
Review gating is screening customers before asking for a review, often through a private survey, and only sending the public review link to the ones who seem satisfied, filtering out anyone who might leave a negative one. Google's policy prohibits soliciting reviews selectively based on expected sentiment. The fix is to ask every customer who hits the trigger point, using the same message, regardless of how the interaction seemed to go.
Do I need to respond to every review?
Responding to every review, positive and negative, is the practice worth building into a weekly habit. Positive reviews get a short, specific thank-you naming what the customer mentioned. Negative reviews get a calm acknowledgment, a statement of what you'll do, and an offer to continue the conversation off the platform. Review responses also factor into local pack ranking signals, so the habit pays off in visibility, not just goodwill.