Ask for an honest review without scripting the customer's answer

TL;DR

• Ask for a genuine review without a reward, a preferred rating or instructions about what the customer should say.
• Do not send public-review invitations only to customers who first tell you they are happy. Check your software's selection rules.
• Avoid employee review quotas and pressure during a visit. Audit the request process rather than requiring a number of reviews.
• Give one person responsibility for checking invitations across tools. A technician, office message and automated email can otherwise repeat the same ask.

A technician mentions a review at the end of a visit. The office texts a link after the invoice, and the CRM emails another request that evening. No one intended to pressure the homeowner, but three parts of the business acted without seeing the others.

A useful review process starts with what the customer experiences. It should give them a straightforward, optional way to describe the work, in their own words.

Read the rules before changing the script

Google's current Maps fake-engagement policy prohibits review incentives and selective solicitation of positive reviews. It also prohibits pressure, prescribed review content and asking staff to solicit a certain number of reviews. The policy gives requesting a staff member's name in the review as an example of prohibited content direction.

Google's Business Profile guide allows genuine requests through a review link or QR code and explains that rewards for reviews, revisions or removals are prohibited. Those are platform rules, not a promise of visibility or a complete statement of applicable law.

That changes how you should assess common suggestions. A discount in exchange for a review is still an incentive when the customer is allowed to be honest. Asking for a particular rating or named technician still directs the response when the rest of the wording sounds polite.

Choose a consistent point in a real customer experience

For this proposed workflow, use a documented service-completion event as the point to consider an invitation. It is a practical design choice for a service shop, not a Google requirement or permission to use any contact channel.

Check that the work record belongs to an actual customer experience, that the selected communication is appropriate and permitted, and that the customer has not already received the request for this experience. Keep customer preferences and suppression records available to the people operating the process.

Do not make the public link depend on a positive satisfaction answer. If your software first asks how the visit went, inspect where each response leads. A flow that directs only happy respondents to Google while routing others away from public review is a selection problem, even when the office calls it a service survey.

Handle complaints through your normal service process. Resolving a problem should not depend on a promise to remove, revise or withhold a review.

Use a short invitation with no desired answer

An original example for a permitted customer message is:

Thank you for choosing [Business]. If you would like to share your experience, you can leave an honest Google review here: [review link].

Replace the placeholders with the actual business name and its verified profile's review link. The customer chooses whether to respond and what to write. Keep any channel-specific requirements separate; this sentence alone does not establish consent to send a text or email.

Avoid adding instructions to mention the city, service, technician or a particular number of stars. Do not supply a finished review for the homeowner to paste. You can explain how to reach the review page without composing their experience for them.

Use Google's official instructions to obtain the link or QR code, then test its destination yourself. Confirm it opens the correct business, especially when the company operates several locations. A short link that opens the wrong profile creates a customer problem before anyone writes a word.

Check what every tool sends

Walk through the actual sequence with a non-customer test record where your system safely supports testing. Inspect the content, timing and selection conditions. A template in the settings page does not prove which message was sent in a real workflow.

The reference can stay in your existing CRM. You do not need a new spreadsheet containing copies of customer messages. If the system's behavior is unknown, assign someone to inspect it instead of marking the check complete.

Give the process an owner without setting a review quota

Choose who maintains the template and who can change automation settings. Make sure technicians know that the customer's rating and wording are the customer's choices.

A manager can inspect whether the request process follows its documented rules. Avoid turning that into a requirement for each employee to collect a number of reviews or named mentions. That invites the pressure and content direction the policy addresses.

Keep review counts out of the sales ledger. A public review does not establish which advertising channel produced a customer, whether a job was profitable or whether an agency caused the outcome. Your marketing report review needs separate evidence for those questions.

Reply without exposing the job record

Read a public response as if the customer and the next homeowner will both see it. Acknowledge the issue you can discuss publicly, keep private account or service details out, and offer an appropriate way to continue the conversation when needed.

Do not make a refund, fix or other remedy conditional on deleting or improving a review. The service-resolution decision and the public feedback decision belong in separate parts of your process.

A reply also needs a responsible person. An automated draft can be wrong about a visit, so check its content against the record before posting. This is a proposed operating safeguard, not a claim that a particular response will improve ranking.

What this doesn't cover

This article describes a proposed workflow under the Google pages read on October 16, 2026. Policies can change. It does not establish Business Profile eligibility, provide permission for customer messaging, guarantee review publication or promise search placement. It concerns eligible home service businesses; Lonta's own fully online service is not being presented as an eligible local listing.

Questions owners ask

Can we reward a review if it can be positive or negative?

Google prohibits incentives for reviews. Allowing an honest rating does not make a reward acceptable under that policy. Keep discounts and customer feedback requests independent.

Can the office ask only the customers a technician recommends?

Check the selection basis. Choosing people because they are expected to leave positive feedback is selective solicitation. Use a neutral process for actual customer experiences and respect contact preferences.

Does every customer need a reminder?

No universal reminder schedule is proposed here. Inspect prior requests, customer preferences and the actual experience before adding another message. More automation can create repeated asks rather than useful feedback.

Sources and method

• Google Business Profile: Tips to get more reviews, read October 16, 2026.
• Google Maps: Prohibited and restricted content, the fake-engagement section, read October 16, 2026. Read the current policy before implementing changes.
• The invitation text, audit table and operating workflow are original Lonta proposals, not a tested review-growth program or client case.

Lonta AI provides managed advertising. A strategy review can separate advertising measurement from the shop's customer-feedback process. The workflow above is available to use with your existing office and providers, without buying a service.