The GET Routine for Automated Review Requests

Doing review requests by feel gives uneven results. Some weeks you ask everyone, some weeks nobody, and replies pile up unread. A short, named routine fixes that. This post gives you one for automated review requests, called GET: Gather, Engage, Thank. It is a working method, not a proven formula, so treat the numbers you collect as the real test.

The routine matches what Lesson 5.5 teaches: pick the right moment, write a short ask, make it one tap, and reply fast. The lesson is here: Get five star reviews without chasing. This post turns it into a weekly habit.

Each week, Gather who finished a job, Engage them with one ask, and Thank every reviewer with a personal reply.

Why a routine beats good intentions for automated review requests

Most review efforts fail on consistency, not on cleverness. A request that goes out to every customer on a fixed day beats a brilliant message sent twice a year. A routine also gives you a record, so after a month you can see what changed.

GET is deliberately small. It has three parts and a ten minute weekly check.

G is for Gather

Gathering means knowing, each week, who has completed a job and has not yet been asked.

What to collect. For each customer: first name, email or phone number you have permission to use, what they bought, the date it was completed, and a column for "asked on" (date or blank).

What counts as complete. Pick one rule. For example: "delivered and three days passed" for products, or "job signed off" for services. Lesson 5.5 uses three days after delivery as its example. Choose your own and keep it fixed.

Why everyone goes in. Gather every completed customer, not only the ones you think are happy. Google's Maps policy says merchants should not selectively solicit positive reviews. If a customer had a problem, you can handle it personally, but do not quietly drop them from the list to protect your rating.

1. List completed jobsPull everyone whose completion date passed your trigger rule this week.
2. Remove duplicatesSkip anyone already marked "asked on" for this purchase.
3. Check the basicsConfirm each name and contact detail is right. A wrong name is worse than no message.
4. Hold known problems for a callIf a customer has an open complaint, resolve it first, then ask them like everyone else once it is closed.

If your customers live in one tidy list, this takes minutes. Lesson 5.1 covers setting that list up.

E is for Engage (the ask)

Engaging means sending the request itself.

One ask, one reminder. Send the first request on the trigger day and a single reminder a week or so later. Then stop.

Three lines. A thank you, an honest ask, the link. For example (illustrative):

Hi Priya, thanks for your order. If you have a minute, an honest review helps others find us. Here is the link: [your Google review link]

The link. Google's help explains how to create a review link or QR code from your Business Profile: Read reviews, then Get more reviews. Test it on your phone before you use it.

What the ask never includes.

• An incentive. Google's pages say incentives for reviews are prohibited on its platform.
• A request for a specific rating or particular wording. Google's policy says merchants should not try to influence the rating or contents.
• Pressure at the point of sale. The policy says not to require or pressure people to review on the premises.
• Any attempt to reward only positive sentiment. The FTC's rule bans incentives conditioned on a particular sentiment.

You can ask AI to write a few versions of the message in your voice. Pick one, check it for the items above, and keep it fixed so you can compare results over time.

T is for Thank

Thanking means replying to every review, positive or negative, within a day or two if you can.

Google's help says your reply is public, the reviewer is notified, and replies are checked against Google's content policies. Its tips are practical:

• Keep it short.
• Use the reviewer's name and mention something specific.
• Do not use the reply as a promotion.
• For negative reviews, acknowledge mistakes, apologise where it is fair, and invite them to continue by phone or email.
• Never share private details.

A reply to a five star review can be two sentences. A reply to a one star review deserves more care, and a pause before you post. If you use AI for a first draft, edit it so it sounds like you. A copy and paste reply on every review looks lazy, and Google's tips specifically suggest not sending the same "thank you" to everyone.

The ten minute weekly check

Pick a fixed time, such as Friday morning. Do this in order:

1. Gather: who completed a job this week? Are they in the list?
2. Engage: did the automation send? Open the sent list and spot check two.
3. Thank: are there new reviews without a reply? Reply to each.
4. Note: write down requests sent and reviews received.

That is the entire routine. Anything that does not fit in ten minutes a week is probably over built.

A short worked example

This is illustrative, not real data. Say you sell printed tote bags online, around 30 orders a week.

• Gather: Your order sheet has a "delivered" date. Every Monday you filter for orders delivered three or more days ago with a blank "asked on".
• Engage: The email tool sends the three line message to that filtered list. You mark the date.
• Thank: On Friday you open your Business Profile, read new reviews, and reply to each in a sentence or two. For a negative one you take longer, offer a fix by email, and do not argue in public.

After a month, you compare requests sent against reviews received, and look at how long replies took. You have a baseline you can improve one change at a time.

When the routine breaks

• Requests going to the wrong people. Check the trigger rule and the "asked on" column.
• Nothing coming in. Check that the link works on a phone and that the message is not landing in spam. Do not respond by adding incentives.
• Many unhappy reviews. Read them as feedback. Pick one repeated issue and fix it.
• You skip the weekly check. Put it in your calendar as a recurring slot. Skipped checks are the main way routines die.

For more on avoiding common errors, see the post on five mistakes that cost time.

Questions people ask

Do I need software to use GET?

No. A spreadsheet and an email tool are enough to begin. Software only helps once volume grows.

How often should I run it?

Weekly for most businesses with steady orders. Monthly can work if you have few customers.

Should unhappy customers be skipped?

No. Google's policy says not to selectively solicit positive reviews. Resolve problems personally, then ask like everyone else.

Can I use AI for the Thank step?

For drafts only. Edit each reply so it is accurate and sounds like you.

Put the routine to work

Write down your trigger rule, copy your review link and add the "asked on" column today. Then block ten minutes a week for the check. If you want help building the automation and the reply workflow, Lesson 5.5 goes through it in order: Get five star reviews without chasing. The step by step setup guide is a good companion read.