Automated review requests: timing, wording and the rules
Short answer: The best automated review request goes out soon after the job is done or the order arrives, links straight to your Google review form, asks once with one polite reminder, and goes to every customer, not only the happy ones. Google's policies prohibit incentives for reviews and selectively asking satisfied customers while steering unhappy ones away, so keep the automation simple and even-handed. A personal line from the person who did the work tends to read better than a marketing blast.
Most local businesses know reviews matter and almost none ask consistently. Automation fixes the consistency; the timing and wording decide whether customers act. Here's a sequenced plan, from setting up the link to keeping the process fair.
The rules to build around
Google's Business Profile help page on getting more reviews says reviews and other contributions must reflect a genuine experience, and that offering incentives such as free or discounted goods or services in exchange for posting, changing or removing reviews is considered fake and misleading content and is strictly prohibited. It suggests reminding customers to leave reviews via a Google link or QR code, replying to reviews, and valuing all reviews, noting a mix of positive and negative often feels more trustworthy. It also mentions that customers must be signed in to a Google Account to leave a review.
Google Maps' user-contributed content policy adds that merchants must not discourage or prohibit negative reviews, or selectively solicit positive reviews. It says merchants shouldn't require or pressure customers to leave reviews while on the premises, or request specific content, and gives examples such as asking staff to collect a set number of reviews or reviews naming a staff member. It explicitly allows soliciting reviews that represent a genuine experience, without incentives.
The practical upshot: ask everyone, the same way, with no reward attached.
Before automating: day 0
- Get your review link or QR code. Google's help page links to instructions for creating a Google link or QR code that takes customers straight to your review form. Test it on a phone while signed out and signed in.
- Decide the trigger. What event in your systems means "the customer has experienced the service"? Common choices: a job marked complete in your job-management tool, an order marked delivered, an appointment checked out in your booking system, an invoice paid.
- Pick the channel. Email works for most; SMS gets attention but should be used sparingly and only where customers expect texts from you. Check the rules where you operate before sending marketing-style messages.
The sequence
Same day to 48 hours after completion: the request
Send while the experience is fresh, but not before the customer has had a chance to see the result. For a renovation, that might be a day after final walkthrough; for a takeout order, a few hours; for a delivered product, a day or two after delivery.
What to include:
- The customer's name and what you did ("your furnace service on Tuesday")
- A one-sentence ask
- The direct review link as a clear button
- A note that it takes a minute
- A sign-off from a real person
Hypothetical example:
Hi Priya, thanks for having us out to service your furnace on Tuesday. If you have a minute, would you share how it went on Google? It helps other people in Saskatoon find a technician they can trust. [Leave a review] — Mark, Northside Heating
Five to seven days later: one reminder
Only to people who haven't left a review, if your tools can tell (many can't, in which case keep the reminder gentle and acknowledge they may have already). Shorter than the first message. Then stop.
No third message
Two contacts are plenty. More starts to feel like pressure, which Google's policy asks merchants to avoid.
What not to automate
- "Happy? Review us on Google. Unhappy? Email us." Routing only satisfied customers to Google is the selective soliciting that Google's policy prohibits. It's fine to give everyone a way to contact you, but don't make the review link conditional on a rating.
- Discounts, prize draws or loyalty points for reviews. Prohibited under Google's incentives rule.
- Staff targets for review counts. Google's policy names this as an example of what not to do.
- Requests while the customer is still at the counter on a staff-held tablet. Asking is fine; pressuring isn't.
Setting it up with your tools
Most setups fall into one of these:
- Built-in features in booking, job-management, e-commerce or point-of-sale software that send a follow-up after an appointment or order.
- An automation tool connecting your system's "job complete" event to an email or SMS step.
- A review-management service that handles sending and tracking.
Whichever you use, check that it lets you send to all customers, set the delay, stop after one reminder and exclude people who've asked not to be contacted.
Responding is part of the loop
Google's guidance encourages replying to reviews. Make sure someone owns replies, especially to negative ones, and that replies are polite, specific and not promotional, in line with its tips on review replies.
Measuring the process
- How many requests went out each month
- How many new reviews arrived
- Average time from request to review
- Any spike in complaints about the messages
If reviews barely move, test timing first, then wording.
FAQ
How soon after a job should I ask for a review?
Usually within a day or two, once the customer has seen the result. For delivered products, wait until after delivery.
Can I offer a discount for leaving a Google review?
No. Google prohibits incentives in exchange for posting, changing or removing reviews.
Can I send review requests only to happy customers?
No. Google's policy prohibits selectively soliciting positive reviews. Ask everyone the same way.
Do customers need a Google account to review?
Yes. Google's help notes they must be signed in to a Google Account, which can use a non-Gmail email address.
Asking for reviews only when you remember? Tell us what software you use to run jobs or orders, and we'll suggest how to automate a fair request sequence.