How to ask for customer reviews, with simple message templates

Ask after a clear completion point

Choose a moment your team can identify consistently, such as a completed visit or a closed job. Avoid triggering a request simply because a lead was created or a payment link was sent. Those events do not necessarily mean the work is finished.

Check the customer record for duplicate requests and contact preferences. For ongoing work, your team should decide whether the job has reached an appropriate point for feedback.

• Use a completion event your team trusts
• Check for duplicate requests
• Respect contact preferences and opt-outs
• Keep unresolved service issues owned by staff

Use a direct link and neutral wording

Google provides a way for businesses to share a link or QR code that lets customers leave a review. Use the link for the correct profile and location, then test it from a phone before adding it to a message.

Do not add an incentive for a review or ask only customers you expect to be positive. Google’s contribution policy restricts incentivised reviews and selectively soliciting positive feedback.

Hi [first name], thanks for choosing [business]. If you would like to share your experience, you can leave an honest review here: [review link]. We appreciate your feedback. [Approved contact-preference wording]

Keep an email request just as short

An email can include the job or visit context without becoming a long campaign. Identify your business, explain why you are writing, and offer one clear review link. Avoid wording that pressures the recipient or implies that only a positive review is welcome.

For a multi-location business, confirm that the link matches the location that served the customer. A central template still needs location-specific details.

Subject: How was your experience with [business]?

Hi [first name],
Thanks for choosing our team for [visit or job]. If you would like to leave an honest review, here is the link: [review link].
If you still need help with your visit, you can reach us at [support contact].
Thank you,
[business]

Make service recovery a separate responsibility

A review invitation is not a replacement for resolving an unfinished job or an unanswered question. Give customers a normal way to contact the team, and assign a person to handle issues that need follow-up.

Keep that support route separate from filtering who is invited to review. Customers should not have to pass a satisfaction check before seeing a public review link.

Measure the process without promising a rating

Track whether requests are sent to the correct customers, whether the links work, and whether the team is receiving follow-up questions. Reviews themselves remain the customer’s choice.

Agent37 includes review requests in Essentials. During setup, agree on the review destination, completion trigger, message wording, and supported data source. A good process makes feedback easier; it does not guarantee a rating or a number of new reviews.