A Week to Working Automated Review Requests: Worked Example

This is not a case study about automated review requests. I have not run this on a real business and I am not going to invent numbers. What follows is a worked example: a made up small shop, a seven day plan, and the decisions you would face along the way. Every figure is labelled as an example so you can swap in your own.

The aim is to show what it looks like to get automated review requests working in a week, including what tends to go wrong. If you want the underlying method, Lesson 5.5 covers it: Get five star reviews without chasing.

A week is enough to get a simple, rule abiding ask running; it is not enough to judge results.

The example business and its automated review requests

Say you run a small online shop selling dog treats. You ship about 15 orders a week. You have a Google Business Profile that you set up once and forgot, an order spreadsheet, and an email tool you already use for receipts. You have a handful of reviews and have never asked for any.

Everything below, including the "15 orders", is an illustration.

Day 1: Profile and rules

First task: confirm the Google Business Profile is verified. Google's help says you must verify before you can reply to reviews, so this blocks everything else.

Then read the rules, which takes ten minutes. Google's policy says no incentives for reviews, no selectively soliciting positive reviews, and no pressure or requests for specific content. The FTC's reviews rule bans incentives conditioned on a particular sentiment. You decide: no discount for reviews, no five star requests, ask every customer.

You also decide not to point anyone at Yelp, because Yelp's business help says you shouldn't ask customers to post reviews there.

What can go wrong on day 1: the profile verification takes longer than expected. If so, you can still do days 2 to 4 and wait for verification before switching on.

Day 2: The moment and the link

You pick the trigger: three days after delivery, the example timing Lesson 5.5 uses. Your sheet already has a "delivered" date from the courier emails.

You then follow Google's steps to get the review link: Business Profile, Read reviews, Get more reviews, copy the link. You open it on your phone to check it lands on the review form. You also note that customers must be signed in to a Google Account to leave a review, so you accept that some people will drop off at that step.

What can go wrong: you copy a link to your website, not the review form. The phone test catches this.

Day 3: The message

You write the three line ask:

Hi Dan, thanks for ordering. If you have a minute, an honest review helps other dog owners find us. Here is the link: [your Google review link]

You write a one line reminder. You ask AI for two alternative wordings, pick the plainest, and read both for anything that pushes a rating or offers a reward. Neither does.

You add a column called "asked on" to the order sheet, so nobody is asked twice. If your customers are not in one tidy list yet, Lesson 5.1 shows how to set that up.

What can go wrong: the first draft sounds like marketing. If it does, cut it down. The shorter, the better.

Day 4: The automation

In your email tool you build one rule: send the ask to customers whose delivered date was three days ago, then send the reminder seven days later to anyone who was asked and has not been followed up, and stop. If your tool cannot do it automatically, you set a weekly reminder to send a filtered batch, which is a reasonable hybrid.

You send the message to yourself as a test, using a test order. You check the name, the link on your phone, and that the unsubscribe or contact details your email tool requires are in place. For ideas on the wider email setup, see Lesson 5.3.

What can go wrong: the message goes to people whose order was cancelled or refunded. Filter those out before you switch on.

Day 5: Replies

You write three short reply patterns, not scripts:

• For a happy review: thank them by name and mention one detail they raised.
• For a mixed review: thank them, acknowledge the problem, say what you will do.
• For a bad review: apologise where fair, explain what you can and cannot do, and offer to continue by email.

These follow Google's reply tips: short, personal, not promotional, protect privacy, respond promptly. You remember Google's note that replies are public, the reviewer is notified, and replies are checked by Google before they appear, usually within about 10 minutes but sometimes up to 30 days.

What can go wrong: you let AI post replies without reading them. Do not. Read every reply.

Day 6: Switch on, small

You switch the rule on for new deliveries only, not your whole back catalogue. Asking 200 past customers at once is a different kind of request. Some may barely remember you. A sensible alternative is to ask recent customers first, then decide about older ones.

You make a note of the date and the starting numbers in a small table:

Day 7: Review the first week

By day 7 you will have sent only a few requests, because the trigger waits three days after delivery. That is the main lesson of the week: the first results lag the setup. Do not judge anything yet.

Do a quick check instead:

1. Did the first messages send correctly?
2. Did anyone reply by email with a question or a complaint?
3. Are any reviews waiting for a reply?
4. Is anything in the sheet wrong?

Fix problems, not numbers.

What the example does not tell you

A real week would not prove the method works. Several things sit outside your control: how many of your customers have a Google Account they use, how happy they are, the time of year, and chance. A small sample can swing wildly. Be wary of any article, including this one, that shows a neat result from a week of work.

What a week can prove is that the system works mechanically: the message sends, the link opens, replies get written and nobody is asked twice. Results come over months.

What to do in week two

• Read the first reviews and your replies with fresh eyes.
• Check the unsubscribe and complaint rate on the emails, using whatever your email tool reports.
• Decide about older customers.
• Pick one number to track monthly. The post on metrics that matter suggests which.

Questions people ask

Is a week realistic?

For a simple setup with a clean customer list, yes, as a setup time. Results take longer because requests only go out as orders complete.

Should I ask my old customers?

Think about it after the first batch works. Ask them the same way, once, and expect some to have forgotten you.

What if the verification takes longer than a week?

Do the rest of the setup and wait. You can only reply to reviews once your business is verified, according to Google's help.

Are the numbers in this post real?

No. The shop, the order volume and the figures are illustrative. Use your own.

Your turn

Print this plan, replace the example with your business, and block an hour a day for five days. The full walk through, with prompts and templates, is Lesson 5.5: Get five star reviews without chasing. For a longer written guide, try the complete setup guide.