All articles

How do I ask customers for Google reviews automatically?

A business systems guide from Lattice Management, covering practical software and operational decisions.

October 16, 2026

Office manager reviewing completed service appointments on a laptop with a smartphone beside the keyboard

You can ask customers for Google reviews automatically by having your customer system send a short email or text when a job or appointment is marked complete. The message should include your Google review link and invite an honest review, without offering a reward or screening customers by satisfaction.

This guide covers the sending rules, message wording, safeguards, and reporting that make automated google review requests useful without creating another task for the office.

In short:

  • Start with a reliable completed-service record, not an estimate or booking confirmation.
  • Use the review link from the correct Google Business Profile.
  • Apply the same invitation rules regardless of expected feedback.
  • Check communication permission and prevent duplicate requests.
  • Track delivery and activity, but do not treat a link click as a published review.

What do you need to automate Google review requests?

You need a Google review link, a reliable record that service happened, and a system that can send an approved message. You also need rules for who receives it, which channel to use, and when sending must stop.

Google explains how to get and share your business-specific review link in its guidance on getting more Google reviews. Use that link rather than asking customers to search for your business and find the right listing themselves.

For a business with multiple locations, keep the correct link attached to each location. A customer served by one office should not receive a request for another office simply because its link was copied into the default message.

The customer record should contain:

  • The customer's name and usable contact details.
  • The completed job or appointment and its location.
  • The communication permissions and opt-out status relevant to the message.
  • The last review request sent, including its date and channel.
  • Any pending reminder, so staff can cancel it when necessary.

If those details live in separate spreadsheets and inboxes, the first job is organizing the customer records. Automation cannot reliably decide whether to send if nobody can tell which job is finished or whether the customer already received a request.

Eligibility must not depend on satisfaction. Google's fake engagement policy prohibits incentives for reviews, discouraging negative reviews, and selectively soliciting positive reviews. Do not ask customers to rate their experience privately and send only the happy respondents to Google.

You can provide a way to contact the office about a problem. That support route should not replace or hide the public review option for dissatisfied customers.

When should the request and reminder go out?

Send the request after the customer has experienced the service and your team has confirmed completion. Choose the timing around the actual work, not whichever record happens to change first.

For a routine service visit, marking the visit complete may be enough. For a longer project, use the final handover rather than the deposit payment. A booking confirmation is too early because the customer has not yet received the service.

Use this sequence:

  1. Confirm completion. The responsible staff member closes the job or appointment using a clear, shared definition of finished.
  2. Check eligibility. Confirm the contact details, communication permission, location, and recent request history.
  3. Send the invitation. Use the customer's permitted channel and send during reasonable local hours.
  4. Consider a reminder. If you use one, leave a few days between messages and keep it brief.
  5. End the sequence. Stop after the planned reminder, an opt-out, or a confirmed review. Do not keep asking until the customer responds.

The delay is an operating choice, not a universal best time. A photographer may reasonably wait until the finished images are delivered. A plumbing business may use the completed service visit. The important point is that the customer has something meaningful to review.

Decide how to handle recurring customers before launch. A customer with frequent appointments should not receive a fresh invitation after every visit. Set a repeat-request interval that suits the relationship, and record the most recent request against the customer, not just the appointment.

Do not exclude completed jobs because someone complained or might leave a low rating. If work is genuinely unfinished, apply the same completion rule to every job, regardless of sentiment.

Pro tip: Check what happens when staff reopen and then close a job. That routine correction should update the record, not send another review request.

Text messages need particular care. Store the permission that supports the message, honor opt-outs, and avoid assuming that permission for appointment updates automatically covers every other message. Your business text messaging setup should enforce those rules rather than leave them to staff memory.

What should an automatic review request say?

A good request identifies the business, refers briefly to the completed service, and gives the customer a direct link. Ask for an honest review without suggesting a rating or supplying words for the customer to post.

Keep the message focused. Adding a promotion, referral offer, and booking link turns a simple request into a marketing bundle and makes its purpose less clear.

Use these templates after replacing the bracketed fields.

Email request

Subject: How was your experience with [Business name]?

Hi [First name], thank you for choosing [Business name]. If you'd like to share your experience, you can leave an honest Google review here: [Google review link]. We appreciate your feedback.

Text request

Hi [First name], this is [Business name]. Thanks for choosing us. Would you like to share your experience in a Google review? Here's the link: [Google review link].

Optional reminder

Hi [First name], a quick follow-up from [Business name]. If you'd like to leave a Google review about your recent experience, here's the link: [Google review link]. If you've already reviewed us, thank you. No action is needed.

For texts, include the sender identification and opt-out wording required for your sending method and circumstances. Treat the templates as message copy, not as a complete compliance setup.

Avoid phrases such as “Please give us a five-star review” or “If you were happy, review us on Google.” Also avoid discounts, prize entries, or gifts in exchange for posting a review. The request should not pressure the customer to support the business with a particular rating.

Keep sensitive details out of the message. A review invitation does not need to name a legal matter, describe financial work, or mention a private health concern. This matters especially when a family shares an email address or a message appears on a phone's lock screen.

Pro tip: Test the message with a missing first name. It should fall back to a normal greeting, not send “Hi [First name]” or expose a blank field to the customer.

How do you know whether the automation is working?

Track whether eligible customers receive the request and whether review activity follows. Keep sending performance separate from published reviews, because a delivered message or clicked link does not prove that someone posted.

Start with these measures:

  • Eligible completed jobs compared with requests sent. A gap can reveal missing contact details, permission restrictions, or a broken completion rule. Some exclusions are correct, so record the reason rather than treating every unsent message as a failure.
  • Delivered requests compared with failed deliveries. Delivery failures point to contact-data or sending problems. Fix those before rewriting the message to make it more persuasive.
  • Review-link clicks, where available. Clicks can indicate interest, but tracking methods can be imperfect. Use this as a directional signal, not a customer-by-customer list of who reviewed you.
  • New Google reviews during the reporting period. Read this alongside request volume. Some reviews arrive without an invitation, and some customers post later, so the totals will not match neatly.

You do not need an impressive-looking dashboard to start. A weekly view of these counts, with the reasons for skipped messages, is more useful than an unexplained success score. If reporting already sits elsewhere, include review activity in your business reporting rather than creating another report nobody checks.

Name an owner for the process. Someone should check delivery failures, handle replies, and review whether the completion rule is still correct when your service process changes.

Also test the stopping rules. An opt-out must prevent the reminder. A duplicate customer record should not produce duplicate invitations. If your system cannot reliably match a published review to a customer, do not pretend it can. Keep reminders limited and provide a straightforward way for staff to stop them when a customer confirms they have already reviewed.

How does LATTICE build this into the whole system?

We build review requests around the record of work performed, so the office does not have to remember a separate follow-up task. Our review automation service connects completion, customer details, permitted messaging, and reporting through a shared set of rules.

We start by identifying where your team records that work is finished. Then we define eligibility, choose the correct location link, write the messages, and set duplicate checks and stopping conditions. We also decide where replies go and who handles exceptions.

The goal is not to send the largest possible batch. It is to make a reasonable request consistently, while preserving the context your office needs to answer a customer.

A practical first-week checklist looks like this:

  1. Document the completion rule. Write down the exact event that starts the process and who is responsible for recording it.
  2. Verify the review link. Open it on a phone and confirm that it leads to the correct business and location.
  3. Check customer records. Review contact details, communication permissions, duplicate records, and existing opt-outs.
  4. Approve the wording. Use a neutral invitation and decide whether a reminder is appropriate.
  5. Test without posting reviews. Use internal test records to check sending, missing information, duplicate prevention, replies, and opt-outs. Do not submit test reviews to Google.
  6. Launch with oversight. Watch the first completed jobs move through the process and inspect any skipped or repeated messages.
  7. Assign ongoing ownership. Give a named role responsibility for checking failures and maintaining the rules.

Once these basics are dependable, automated google review requests become part of closing out a job, not a separate campaign the office has to restart whenever things get busy.

FAQ

Can Google send review requests automatically for my business?

Google provides a review link you can share, but that link alone does not connect completed jobs to outgoing messages. To send requests when work finishes, you need your booking or customer system to support that process, or a separate service connected to those records.

Should I ask every customer for a Google review?

Use consistent, neutral eligibility rules for customers who have had a genuine experience with your business. You can exclude records with no permitted contact method or prevent repeated requests, but you should not exclude customers because you expect negative feedback. Do not use a satisfaction survey to decide who gets the Google link.

Can I offer a discount for leaving a review?

No. Google's fake engagement policy prohibits offering incentives in exchange for reviews. Keep discounts, gifts, and prize entries separate from review requests, even if you say the review can be honest.

Can the system tell who has already left a review?

Not always, because a Google display name may not reliably match the customer record. A link click is not confirmation that a review was published. Use confirmed matches where available, allow staff to stop reminders, and keep the follow-up sequence limited.

Sources