A Fair Google Review Request Process for Contractors

Make the request part of a real service closeout

Choose a clear point in the job journey: after the invoice is closed, after the service visit is marked complete, or after the office confirms the requested work is finished. Use a point staff can identify consistently. A completed work order is usually more reliable than a technician’s impression that a customer looked happy.

A plumbing company might send the request after a repair ticket closes. An HVAC office might send it after the service appointment is complete, while an installation may need its own closeout event. Roofing work can have a longer completion and punch-list cycle, so the request should wait until the business has checked that the customer’s work is actually complete.

Separate the feedback invitation from safety, payment, warranty and unresolved-service communications. A customer should not feel that a review is required to receive a receipt, warranty support or a callback.

Invite all eligible customers on the same basis

Write one rule for who receives the invitation, such as all completed jobs that meet the company’s neutral operational criteria. Do not route satisfied customers to Google while sending unhappy customers to a private survey. Google expressly prohibits selectively soliciting positive reviews or discouraging negative ones.

A private service follow-up survey can help the office find and fix a problem, but it should not act as a gate that determines which customers are allowed to see the public review link. If you ask for private feedback and a public review in the same journey, keep the review invitation available regardless of the survey score.

Record exclusions for legitimate operational reasons, such as a duplicate work order or a job canceled before service, and apply them consistently. Do not create an exclusion for ‘customer might leave a bad review.’

Keep the invitation neutral and easy

Use a direct link or a QR code that opens the company’s review form. Google’s guidance allows businesses to remind customers and share a review link. Keep the message short, identify the business, and make clear that writing a review is optional.

Example: ‘Thanks for choosing [Company] for your [service]. If you’d like to share an honest review of your experience, you can do so here: [review link]. Feedback is optional and your service or support is not affected by whether you post.’ Replace the bracketed details with verified information and make sure the URL goes to the correct profile.

Do not ask a customer to include a technician’s name, a five-star score, a keyword, or a specific phrase. A request for honest feedback is different from coaching the substance of the review.

Do not attach a reward to a Google review

Do not offer a discount, gift card, free service, contest entry or other benefit in exchange for leaving, changing or removing a Google review. Google’s policy prohibits incentives for Maps reviews, even though the FTC’s general rule can treat some neutral review incentives differently when there is no required sentiment and the incentive is properly disclosed. A company must follow the platform’s stricter rule for Google reviews.

Do not pay a reputation vendor for a promised volume of positive reviews or use an employee, family member or contractor to create reviews that appear to come from independent customers. Review manipulation can damage trust and may lead to platform consequences.

If an existing customer mentions an incentive in a public review, do not ask the customer to hide the connection. Review the company’s process and remove the problematic incentive rather than trying to edit the customer’s account of their experience.

Set a cadence the office can actually maintain

Decide who triggers the invitation, which channel is approved, how many reminders are allowed and when the sequence stops. A single neutral invitation may be enough. If the customer does not respond, respect that silence rather than sending a recurring series of pressure messages.

Check the chosen channel and consent requirements before sending SMS or email. A request for a review is still a business message; the company should use contact details and permissions according to its own policies and applicable law. Keep promotional offers out of the review request.

When a customer replies with a problem, route it to a person who can help. Do not let an automated review workflow answer an unresolved safety concern or promise a technical fix without the service team’s review.

Handle jobs with more than one visit

A repair that needs a return visit, a roofing project with a punch list, or an HVAC installation with a later inspection should not trigger repeated review requests after every work-order update. Decide which milestone marks the customer’s completed experience, and close the request workflow when the job is reopened or remains unresolved.

If the company has separate stages for visit complete, work complete and invoice closed, document which stage starts the review request. The stage should match the customer experience rather than the software’s default status. Have the office test a multi-visit record before enabling automation across all jobs.

A delayed closeout should not create a burst of old review requests weeks later. Set a reasonable send window and a manual exception queue for unusual records. Staff can then correct the status before a message goes out to someone whose work is still active.

Use a simple message and test the route

For SMS, keep the request short and include the business name so a customer recognizes who is contacting them. For email, use a plain subject such as ‘How did we do on your service visit?’ Avoid subject lines that imply a reward, threaten a consequence or suggest the customer already agreed to post.

Test the link from a phone that is not signed in to the business account. Confirm it opens the correct public profile and that the customer can leave a review without staff assistance. Check that tracking redirects do not break the destination or expose private customer details in the URL.

Keep the actual approved message in the company’s workflow notes. If a vendor changes the copy or adds a second reminder, review it against the same neutral policy before turning it on. A small change in wording can turn an optional invitation into pressure or a sentiment filter.

Keep the request distinct from a marketing opt-in

A customer who leaves a review has not automatically agreed to receive recurring promotions. Keep review-request preferences separate from newsletter, seasonal offer and SMS marketing choices. If a customer opts out of a channel, follow the business’s opt-out process rather than switching the same solicitation to another channel to get around the preference.

For companies using a CRM workflow, label the review message and stop condition clearly. Test a customer who has an active communication restriction, a job that reopens and a record with no approved mobile number. Pause automation if the system cannot distinguish these cases reliably.

Have the owner or counsel confirm how the business handles service-related messages under its own consent and legal requirements. Platform review policy does not answer every communications-law question, so avoid treating a Google review link as universal permission to text.

Assign ownership and handle exceptions

Name a person responsible for checking that the correct customer and job were selected, the link works, and opt-outs or communication preferences are respected. Field staff can explain that feedback is welcome, while the office owns the actual request and any public response.

Pause the sequence for an active dispute, an unresolved callback or a refund discussion if sending the request at that moment would be confusing. Apply the pause consistently to resolve the service issue; do not permanently suppress the customer’s ability to leave an honest public review.

Keep an audit trail of the policy, message version, channel, send date and job status. Do not store review text as proof that the customer accepted future marketing or as a substitute for communication consent.

Review the process, not just the star average

Check whether completed jobs are receiving the same invitation, whether the link reaches the right profile, and whether customers are reporting broken links or confusing wording. The number of reviews is only one input. Read the themes in customer feedback and look for work-order or communication issues the company can fix.

Google says reviews must reflect genuine experiences and that businesses may ask for honest feedback without influencing the rating or content. A fair request process supports that principle while helping an owner learn where service is clear or where the customer handoff needs attention.

Do not set a target for staff to obtain a certain count of five-star reviews. If the office measures process completion, measure whether the neutral request was sent according to policy, not the sentiment the customer chose.

A launch checklist

• Define a neutral completed-job trigger and consistent eligibility rule.
• Use one factual, optional invitation and a verified profile link.
• Send to eligible customers without sentiment filtering.
• Offer no Google-review reward and request no rating or scripted phrase.
• Check SMS/email permission, opt-outs and the chosen send channel.
• Route replies and unresolved service issues to a person.
• Audit the process and correct broken links or inconsistent delivery.