Asking customers for Google reviews is allowed. Trying to control who gets the Google link, what rating they leave, or what they write is where contractors get into trouble.
That distinction matters because a lot of review software is built around a tempting idea: ask customers to rate you privately, send the happy ones to Google, and route the unhappy ones to a private form. It sounds clever. It is also the exact kind of selective solicitation Google says merchants cannot do.
You do not need to stop asking for reviews. You need a clean rule, a neutral message, and the discipline to let real customers say what they actually think.
The policy in plain English
Google’s Maps policy on rating manipulation allows businesses to ask for reviews that reflect a genuine experience. The request cannot include an incentive or try to influence the rating or contents of the review.
The same policy says merchants cannot discourage negative reviews or selectively solicit positive ones. It also says businesses should not pressure customers to review while they are on the premises, ask for specific wording, or tell employees to collect a certain number of reviews.
For a contractor, that rules out several common tactics:
- Giving a discount, gift card, raffle entry, free service, or other benefit for a review
- Asking “Were you happy?” and sharing the Google link only when the answer is yes
- Sending four- and five-star customers to Google while keeping lower ratings on a private feedback page
- Asking a customer to mention a technician’s name, service, or city in the review
- Standing over the homeowner while they post it
- Giving technicians a quota for reviews collected
Google’s Business Profile review guidance is much simpler. Businesses can share a direct review link or QR code, remind real customers to leave a review, reply to reviews, and value honest feedback.
No tricks needed.
Pick an objective rule for who gets the request
The safest workflow asks every eligible customer based on an event you can prove, not on how happy you think the customer is.
A reasonable rule for many home-service companies is: send the request after the job is marked complete and the final invoice is paid. That works for a plumbing repair, HVAC service call, roof replacement, or finished remodeling project because the customer has experienced the work.
Your trigger may need to change by trade.
A weekly pool-service customer may not need a request after every visit. Ask after the first 30 or 60 days, then exclude anyone who already reviewed the company. For a long remodel, the final walkthrough may be a better trigger than payment if retainage remains open. For warranty work, wait until the issue is resolved instead of firing another request because somebody closed a ticket.
Write the rule down. The important part is that the rule applies without checking whether the customer praised the crew, complained to the office, tipped the technician, or clicked a private star rating first.
You can exclude spam, duplicate records, vendors, employees, applicants, and people who never became customers. You can also suppress repeat requests to the same customer. Those are record-quality decisions, not attempts to shape your rating.
Send a neutral message with one clear action
A review request should identify the business, connect to a real completed job, and give the customer the direct Google review link. It should not ask for five stars or suggest what to say.
For example:
Hi Maria, this is Ridgeview Roofing. Thanks for trusting us with your roof repair. If you have a minute, would you share an honest review of your experience on Google? [direct review link]
That is enough.
“Please leave us a five-star review” is not neutral. Neither is “If we earned five stars, tell Google. If not, call us first.” Both try to steer the outcome.
You can send one reminder if the customer does not act, but give it a stop rule. Stop after a review is recorded, the customer replies, the customer opts out, or the reminder limit is reached. Nobody should receive six review texts because an automation forgot how to quit.
Google also lets a business create a direct review link or QR code. Put the QR code on a receipt, leave-behind card, or invoice email if that matches how your customers communicate. Do not turn the kitchen table into a checkout line where the homeowner feels watched until the review is done.
Handle unhappy customers without hiding the Google link
Service recovery and review solicitation can run at the same time, but one should not block the other.
If a customer reports a leak after a roof repair, assign the problem to a person, acknowledge it, schedule the inspection, and document the resolution. Do that because it is good operations. Do not make private feedback a gate the customer has to pass before getting access to Google.
The clean setup has two separate paths:
- Every eligible customer receives the same neutral Google review request.
- Every complaint, low private survey score, callback, or warranty issue creates a service-recovery task for a named person.
The contractor still gets a chance to fix the problem. The customer still keeps the choice to review the experience. If the resolution changes their opinion, they can update the review on their own. Do not offer money, free work, or a discount in exchange for changing or removing it.
When a negative review appears, reply like an adult. Keep the response short. Protect the customer’s private information. Acknowledge what you can verify, explain the next step, and move the detailed conversation to phone or email. Google’s own guidance recommends professional replies and warns against personal attacks or sharing private information.
A calm response often tells the next homeowner more about your company than another generic five-star rating does.
Measure the process, not each employee’s star count
Review quotas create bad incentives. A technician who needs three reviews by Friday may pressure customers, ask only the happiest ones, or script the wording. Google specifically lists staff review quotas and requests for content that identifies an employee as prohibited examples.
Measure the operation instead:
- Completed jobs eligible for a request
- Requests actually sent
- Delivery failures and bad contact records
- Customers accidentally asked more than once
- Complaints assigned and resolved
- Public reviews received, without tying compensation to a required rating
The useful number is request coverage. If 80 jobs were eligible and only 31 requests went out, the system is broken. Fix the trigger, records, or owner. Do not hand the crew a five-star contest.
Also watch for sudden review bursts. Google’s policy flags unusual volumes or patterns that suggest rating manipulation. A normal automated process should follow the pace of completed jobs, not produce 70 reviews in a weekend because somebody uploaded an old customer list and blasted everyone at once.
Audit your current review funnel this week
Run one customer record through your process from beginning to end.
Check the job-completion trigger. Read the exact text. Click every button. Test what happens after a low private rating. Confirm that the Google link is available without first choosing a high score. Check whether an incentive, five-star language, employee name request, or on-site pressure has slipped into the script.
Then inspect the stop conditions. A customer who already reviewed, opted out, complained, or entered an active service conversation should not keep receiving canned reminders.
This is worth doing because the downside is bigger than losing a few reviews. Google says suspicious activity or policy violations can lead to removed reviews, temporary posting restrictions, hidden reviews, or a warning banner on the Business Profile. Google explains those possible actions in its consumer alerts guidance.
The rule is not complicated. Ask real customers. Ask them consistently. Do not pay them, filter them, pressure them, or tell them what to write.
That gives you a review profile you can defend and feedback you can use.
If your customer records, completed jobs, and review requests live in separate tools, start by mapping the trigger and stop conditions. You can review the tools Contractor Systems connects with and see the customer workflow in action, then compare it against the audit above before changing your process.
