Managing reviews

Review request email: what 78 of our own requests taught us

14 October 2026 · JustReview

A review request email that works is short, personal and sent within a day of a moment when the customer is clearly happy: it says why you are asking this person, contains exactly one link that opens the review form, and is never followed by a chain of reminders. Timing matters more than the wording. When we asked 78 of our own customers for a review in July and August 2026, a request added to a support reply right after the customer thanked us produced a review two times out of five, a standalone email about one time in ten, and every review we could match with certainty arrived within 72 hours.

Below are the numbers behind that, the checks we now run before anyone gets asked, and three templates built from what actually produced reviews.

Where these numbers come from

We sell review widgets, and for years our own profile on the review sites people check before buying software was thin. In the summer of 2026 we started asking. Between 24 July and 29 August we sent 78 requests to 78 different people, all of them customers of ours, and we logged each request with the date, the wording used and the reason that person was chosen. Nobody was offered anything for writing, and apart from one mistake described further down, nobody was asked twice.

The review site emails us whenever a new review appears, so we matched each new review to a request by name, company and timing. Six matches are certain. Two are probable, because the review showed only a first name or a display name, and we flag them as such below. We did not track opens or clicks, so everything here is about the outcome that matters, a published review, not about engagement.

Two caveats before the table. The sample is small, and these are business customers of a software tool, not diners or patients. The pattern is still worth having, because most guides to review request emails show templates, not what came back.

What 78 requests produced

The fastest certain match appeared less than seven hours after the email went out, and three reviews arrived within 16 hours of their request. The slowest took 71.6 hours. After that, nothing: none of the 70 people who had not written by day three has written since, and the oldest of those requests is now more than eleven weeks old.

Lesson one: the moment beats the message

The same product and roughly the same request produced 40% in one setting and under 10% in another. The difference was not the email. It was what the customer had just said.

The five in-thread requests went to people who had just told us, in their own words, that they were happy with the product or with how we had handled their problem. We were already in a conversation with them, the problem they had raised was solved, and the request was one extra paragraph at the bottom of a reply they were going to read anyway. The standalone emails went to people who were satisfied in the sense that they kept using the product, but who had not thought about us that week.

For a local business, the equivalent moment is easy to find. It is the minute the client says the haircut looks great, the evening the delivery arrives intact, the message that says the boiler works again. A request sent then is a continuation of a good conversation. The same request sent three weeks later is a chore.

This is also why the review request email is usually better as a reply than as a campaign. If your booking or support tool lets you send it from the thread where the customer just thanked you, do that. If it has to be a separate email, send it the same day.

Lesson two: there is no long tail, so do not chase

Most guides recommend a reminder after three or seven days. Our data says the reminder lands after the decision has already been made. Every review we could match with certainty arrived within 72 hours, and the people who stayed silent for three days stayed silent for good.

So we stopped planning follow-ups at all. Each person gets one request, and silence closes the topic. Our rule now is at most two requests per person in a lifetime, at least 120 days apart. That costs us a few reviews we might have squeezed out with a reminder. It saves the relationship with everyone else, which is worth more, especially when the same customers renew every year.

If you collect reviews at volume, the same logic applies to the review counts you see later: a spike the week after you send requests, then a quiet stretch, is normal. Our analysis of how fast businesses normally collect reviews shows how uneven healthy profiles look.

Lesson three: ask for a new review, not a copy

We wrote to five customers who had already reviewed us on another software directory and asked them to post the same review on the site where our profile was weakest. None did. That is a small number, but the reason is easy to guess: these people had already done us the favour once, and repeating it felt like admin, not like praise.

If someone has reviewed you on one platform, thank them and leave them alone, or ask for a review of something new a year later. Do not ask them to copy and paste their own words.

Lesson four: batches are cheaper to send and worse in every other way

In August we sent 29 requests in one afternoon to lifetime-deal customers, chosen because they had no renewal at stake. It produced one certain review and one probable one, the weakest rate of any form that produced anything.

It also broke our own pacing. Our inbox assistant is allowed three requests a day and eight a week, so that requests go out only when a customer has just said something positive. Twenty-nine in one day used up that allowance for a full week, and during that week every well-timed request, the kind that converts at 40%, was blocked. A batch can quietly cost you the best moments of the following days.

Check these four things before anyone gets a request

The most embarrassing request we sent was that one mistake, and it is not counted among the 78 above: a second, friendly ask to a customer who had already left us five stars after the first one. After that we put a gate in front of every request. It answers four questions, and a request goes out only if all four answers are right.

1. Has this person already reviewed you? Check by email, and by first name plus company when the platform hides surnames. If the match is uncertain, a human decides.
2. Have you asked them before? Match the person, not the address, because the same customer often writes from a work address and a personal one.
3. Is anything open or broken on their side? An unresolved complaint, a failed payment, or, in our case, a broken review import. Asking for praise in the middle of a problem reads as tone-deaf.
4. Is the link you are about to send the real one? A guessed URL that lands on a search page or an error loses the review and makes you look careless.

The second rule we keep is simple: ask everyone in the same situation the same way. Google’s content policy forbids selectively asking happy customers and forbids offering anything in exchange for a review. In the US the FTC’s 2024 rule goes further on rewards tied to positive sentiment, which we cover in our guide to FTC rules for displaying customer reviews. Our first July email said, half as a joke, that we were “quietly hoping for a positive one”. That is the kind of line review platforms tell you not to write, so leave it out. Asking for an honest review is the request. Hoping for stars in writing is not.

None of this needs bought reviews or review gating, and both backfire. Here is why buying reviews is a trap even before a platform notices.

The anatomy of a review request email that gets reviews

Strip out everything else and a review request email that works comes down to five parts:

• A subject line that names them, not you. “A small favour, [Company]?” or a reply in an existing thread, never “We value your feedback”.
• One sentence on why this person. How long they have been a customer, or what they just said.
• One link that opens the review form itself. Not your profile, not a list of platforms to choose from. For Google, our free Google review link generator builds the direct link and a QR code for print.
• An exit. “If anything is not right, just reply and I will fix it.” It catches the unhappy customer before the review site does.
• A real person’s name at the end. Our July emails were signed by the founder, not by “the team”.

Keep it under 120 words. Customers who are going to write read the first three lines and click.

Three templates

Adapt the names and the link. Each one is built from a form that produced reviews for us.

1. The in-thread reply, after the customer thanks you (our best performer)

Glad that is sorted, and thank you for saying so.

One small ask, only if you have two minutes: an honest review of us
here would help other people find us.
[direct review link]

Either way, thanks for sticking with us.
[Your name]

2. The same-day email after a job or delivery

Subject: How did we do, [First name]?

Hi [First name],

Thanks for choosing us for [the job / your order] today. If you have
two minutes, an honest review would mean a lot to a small team like ours:
[direct review link]

If anything was not right, just reply to this email and I will fix it.

[Your name], [Business]

3. The once-a-year note to a long-time customer

Subject: A small favour, [Company]?

Hi [First name],

You have been with us since [year], which makes you one of the people
we build this for. Could you spare two minutes for an honest review?
[direct review link]

No reminders will follow. And if something is missing on your side,
reply here and I will look at it myself.

[Your name]

Template 3 says “no reminders will follow” on purpose. It is true, it lowers the pressure, and the data above says a reminder would not have helped anyway.

Then put the reviews where people decide

A review request email ends with a review on a platform your customers may never visit. The second half of the job is showing it on your own site, at the point where a visitor is deciding whether to book or buy. Our guide on how to get reviews on your website covers where to place them, and the Google reviews widget pulls new reviews in automatically, so each one your requests produce appears on your pages without anyone copying it over.

The free plan stores up to 100 reviews from Google and Facebook, with no view limit, no domain limit and no card, and the pricing page lists what the paid plans add. If you want to see your own reviews on your site before the next request goes out, create a free account and connect your Google profile.