A better way to ask for a review after the job

Invite an honest account of the work

The work is finished, the customer has the details they need, and your team is ready to close the job. A review request can be a simple part of that handoff. It should feel like an invitation to describe the experience, with no obligation to reward the business or the person who did the work.

For Google reviews, the platform’s policy matters: it prohibits incentives, discouraging negative reviews, and selectively seeking positive reviews. Build your routine around those boundaries. Do not sort customers into a public-review path for happy responses and a private-only path for unhappy ones. A private service conversation can remain available to everyone alongside the same opportunity to leave a public review.

Choose a moment based on the job, not the expected rating

Pick an operational milestone that makes sense for your work, such as the completion handoff. Apply it consistently to customers with a genuine experience, including those who raised a concern. Do not make the team guess who is likely to leave five stars. If a project has several visits, decide which milestone avoids sending the same request after every small task.

Keep service follow-up separate from rating management. Resolve a reported issue because the customer needs help, without asking for a review to be changed or removed in return. Avoid pressuring someone to write a review while a worker waits beside them. Give them the link and the freedom to decide whether and when to use it.

Write one clear request with one useful link

Use your business name, identify the visit without exposing unnecessary details, and explain what the link does. Keep the language neutral. You do not need to prescribe a star rating, suggest phrases for the review, or ask the customer to mention a staff member. Their account should be their own.

Google’s Business Profile help explains how to share a direct review link or QR code. Test your link on a phone before using it. Confirm that it leads to the right business and location. A customer should not have to search through similarly named businesses to find the place you meant.

Check the request before making it routine

Have someone outside the original job conversation read the message. Does it make sense without additional explanation? Does it identify the business accurately? Could any sentence make the customer feel their service, warranty support, or relationship with the team depends on leaving a positive review? Remove that pressure before the template becomes a habit.

Use a suitable contact channel and honor the customer’s communication preferences and applicable requirements. A review invitation is not a reason to ignore an opt-out or reuse an unrelated list. If your process includes a reminder, keep it modest and stop when the customer declines further contact. More requests are not automatically a better experience.

• The recipient had a genuine experience with this business.
• The selection rule does not depend on a predicted positive rating.
• The message offers no discount, gift, drawing entry, or other incentive.
• The correct location’s review link works on a phone.
• The request asks for honest feedback without suggested review content.
• A customer can still get help without writing a review.

Treat the reply as part of the customer experience

When feedback appears, read it before reaching for a template. A short thank-you can acknowledge the experience without turning a response into an advertisement. If something went wrong, address the concern politely and offer a suitable private channel for the details. Do not publish addresses, account information, or the contents of a private conversation to win an argument.

Avoid promising an outcome before checking the facts. You can say that you would like to understand what happened and explain how the customer can reach the right person. If you believe content breaks Google’s rules, use its reporting process; a negative opinion alone is not a reason to assume a review should disappear.

Review the process without setting a rating target for the crew

Look for practical breakdowns: requests sent to the wrong contact, duplicate invitations, broken links, and unanswered feedback. Give the team responsibility for a considerate handoff and accurate records. Do not turn requests for specific ratings, wording, or review counts into a condition of doing the job well.

Read recurring themes in the feedback as operational clues. If several customers mention unclear arrival updates, improve the update routine. If a particular explanation is helpful, use it more consistently. The checklist and message examples here are our suggested workflow; Google’s current policies and help pages below are the source for its platform rules.