How to Ask Customers for Google Reviews After a Job

Start with a small, honest invitation.

After finishing a job, it is easy to say “we should ask for a review” and then move on to the next customer. A useful routine is smaller: confirm the work is complete, choose one suitable way to contact the customer and send a short invitation with the right link.

You do not need to write a sales pitch or ask for a particular rating. Give customers an easy way to describe their own experience. The free message pack contains an email, a text alternative, a spoken invitation, one optional reminder and two reply starters. Choose the appropriate message; they are not a sequence to send to everyone.

This is a documented walkthrough with fictional examples. It has not been tested in a customer's account and does not promise more reviews, bookings or higher search positions.

1. Decide when a customer has actually received the service.

Choose a clear point your team can recognise. For a plumbing business it might be the technician marking the repair complete after checking it with the customer. For a salon it might be the end of the appointment. A booking made, quote sent or payment link opened does not necessarily mean the service happened.

Name one owner of the invitation. In the fictional Harbour Plumbing example, Sam reviews the completed jobs at the end of the working day. Sam checks whether an invitation already went out and whether the business may use the selected contact method. The team does not ask only the customers it expects to give a high score.

If a customer has a complaint, give the concern a responsible person as a separate task. Do not make the public review link depend on a private satisfaction question, a successful complaint outcome or a promise to change a review. Google's review policy prohibits incentives and selectively asking for positive reviews. A neutral invitation leaves the rating and wording to the customer.

2. Get the review link for the correct location.

Sign in to the Google account that manages the correct Business Profile. Open Read reviews, then Get more reviews, and copy the link. Google's current instructions also explain the QR-code option.

Open the copied link yourself and check the business name and location. This matters if your account manages several branches. Stop at the review form; do not post a pretend customer review as a test. A customer needs to be signed in to a Google Account to submit a review, so a sign-in prompt does not by itself mean the link is broken.

Keep this verified link with your approved message wording. Use the direct review destination rather than a home page that makes the customer search for the next step. If you print a QR code, scan the printed copy before sharing it. When the business moves or changes its profile, check these destinations again.

3. Adapt one finished message, then read it as the customer.

For an initial email, use the first message in the pack:

Subject: Thank you for choosing [business name]

Hi [first name],

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

Your feedback helps other people understand what to expect. There is no obligation to leave a review.

Thank you,
[sender name]
[business name]

Sam replaces the service description with “repairing your kitchen tap”. The message identifies the work without publishing an address or private job details. Sam checks the recipient and link, signs with a real sender and keeps the invitation short.

The brackets are writing prompts to replace by hand. They are not ready-made HighLevel fields. If you later use automatic personalisation, insert fields using the software's own controls and test a contact whose name is missing. Never send an unfinished “[first name]” or “[Google review link]” prompt.

Do not add a discount, competition entry, requested star rating or suggested review text. The customer writes the review. The pack's text message is an alternative when you have valid SMS permission, not a second message to send just because the email was ignored. Keep the required business identity and opt-out wording; LC Phone's messaging policy explains those requirements.

4. Choose a one-message start or a configured request routine.

The simplest start: send the adapted email once through your existing approved business email account. Paste the verified review link into it and record that the invitation went out. You can use the wording without buying a new platform. A customer asking not to be contacted should not get another invitation.

If you already use HighLevel: its review-request feature can send requests manually or through a workflow. A manual request can still use configured delays and repeat messages. Do not assume that clicking send creates only one message. The sending guide explains these routes.

Before using that feature, check your account's subscription, allowed access and actual email or phone charges. You need a usable sending identity and permission for the chosen channel. Use the platform and usage cost guide as a starting point, then check your own billing. This article does not require WhatsApp, AI or a custom integration.

5. If using HighLevel, check the link, template and repeats.

Open Reputation → Settings. In Review Link, use Custom Link for the verified Google destination. In Email Requests, check the sender, timing and maximum follow-ups before enabling a request routine. HighLevel's settings guide documents those controls.

Create an email template using the adapted wording and add the review-link button. Choose it as the live template through Set Email Templates. Use the email template guide for the current editor.

For an owner-approved routine, an example is one initial email and at most one reminder a week later. This is a proposed operating choice, not a default or a promise that your account offers a one-send setting. Verify the available controls. HighLevel's SMS documentation lists one to five retries, so do not assume zero retries is supported. If you want exactly one invitation and cannot verify a no-repeat HighLevel path, use the ordinary-email start instead.

Check all other workflows for existing review requests. The HighLevel repeat sequence can stop after a detected link click for that channel; a click does not prove a review was posted. Hold an unclear setup rather than rely on an untested stop. Only then select one controlled contact from Reputation → Requests for a test; keep bulk sending out of this first trial.

6. Test the link and message before contacting customers.

Use an inbox or number your team controls. Ask someone who did not write the message to read the complete result and open the link. Confirm the right business appears, the wording is recognisable and no unfinished prompt is left in the message.

If you are testing a HighLevel request routine, check which channel and template actually sent, when it arrived and whether another send is queued. Test the configured stop and opt-out handling with controlled contacts. Do not perform a fake public review to prove that the setup works.

Write down what was observed and what remains untested. Sam approves the exact message and sending route before using it with real customers. If the recipient, location, timing or repeat behavior is wrong, pause further triggers and fix that issue first. A failed status is not an instruction to resend: check the conversation and provider result so an uncertain first attempt does not become two messages.

7. Read the feedback and keep the next action human.

When a review appears, read it before using a reply starter. Acknowledge something the customer actually said, keep the response short and avoid turning it into another promotion. Google's reply guidance recommends a professional response and protecting personal information when dealing with concerns.

Sam might thank a reviewer for mentioning the clear explanation of the repair. If the review describes a problem, Sam checks the facts and invites a private conversation through the business's normal contact route. The reply does not publish the customer's booking details or offer a reward for changing their review.

For a weekly check, count invitations actually sent, failures that need attention and genuine reviews observed. Keep these as different results. Do not label every link click as a review, or a review as a confirmed new customer. Check for repeated invitations and stale links, then choose one useful improvement to the process.

To stop, stop the team's manual sends and hold the relevant automatic steps that start requests or request routine if one is in use. Verify any queued repeats separately; a settings change is not proof that all earlier queued messages disappeared. Give an affected customer one responsible contact rather than switching channels to continue a chase.