Skip to content

Sales

How to ask for a Google review after a job is complete

A neutral review-request email template and a job-complete workflow with duplicate prevention, correct timing and clear stop rules.

The short answer

Ask after real work is complete, thank the customer and include the correct review link. Invite honest feedback without offering rewards or filtering requests by expected rating. Use a verified completion event, keep a record of the request, and prevent a corrected pipeline stage from sending the same request again.

When should the review email send?

Use a completion event your team can verify. Job booked means the work is arranged, not delivered. If the job is rescheduled, cancelled or still in progress, a completion-based message would be confusing.

Choose timing that fits your service and allows the customer to experience the result. An owner can review the timing before enabling the workflow. The exact delay is a business choice to test, not a universal rule.

  • Confirm the job is complete.
  • Check the customer and business identity.
  • Use the review link for the business that did the work.
  • Check whether a request has already been sent for this job.
  • Send only through an approved customer communication process.

What should the review request say?

Make the request understandable and easy to act on. Reference the service without including unnecessary private details. A short, direct invitation works better as a starting point than a long explanation of why your company needs reviews.

Should you only ask customers who seem happy?

No. Use a consistent, neutral request process. Google's fake engagement policy prohibits selectively soliciting positive reviews and offering incentives in exchange for reviews. Do not ask a satisfaction question and send only positive respondents to Google.

Keep the service-recovery channel open to everyone while leaving the public review option available. A complaint needs a real response, not a workflow designed to hide criticism.

  • Do not offer a discount or gift for a review.
  • Do not require a particular star rating.
  • Do not write a review for the customer.
  • Do not reveal private customer or job information in a public reply.

How do you prevent duplicate review requests?

Record the job identifier, completion event and request status. Re-check them before sending. If a team member moves the lead backward to fix a mistake and then returns it to Job complete, the workflow should recognize the earlier request.

For repeat customers, decide what a new completed service means in your system. Review volume alone is not the measure of a successful workflow. Also check whether messages reached the right people, whether links were correct and whether your team handled replies.

Common questions

Can the thank-you and review request be one email?

Yes. Keep the thank-you genuine and the review request optional. A direct link makes the next action clear.

Can I offer a discount for a review?

Do not offer an incentive in exchange for a Google review. Google's policy prohibits that practice, including incentives to change or remove a review.

About this guide

Written for service-business owners by WellRun. The workflows and examples are practical recommendations; example messages are illustrative, not client results. Actual setup depends on your services, team and connected tools.

Sources and further reading

Spotted something that needs correcting? Email WellRun.

Keep reading