When should a review-request email be sent?

After the product has been used, not after it has been delivered. Set the gap by category: roughly a week for a consumable, three to four weeks for a durable good, longer for anything seasonal. Delivery triggers collect impressions of the packaging, which is the one thing you did not want feedback on.

What subject line works best for a review request?

A plain one that names the product and asks a single question. Curiosity subject lines raise opens and lower submissions, because the person who opened was expecting something else. Name the item, keep it under about six words, and let the ask be visible before the message is opened.

How long should a review-request email be?

Short enough that the rating control is visible without scrolling. Two sentences and a row of stars outperforms a well-written paragraph almost every time, because the decision being made is whether to spend thirty seconds, and a long message is evidence that it will take longer than that.

Should a review request offer an incentive?

Only after the free changes are in place, and only as a neutral reward offered to everyone regardless of what they write. An incentive tied to a positive review is non-compliant on every major platform and corrupts the data you were collecting. Most stores reach for this first and gain volume they would have had anyway.

How many reminders should a review request have?

One, sent three to five days later, ideally by a different channel from the first ask. A single reminder typically adds about a third again to the response. A second adds very little, and it converts a request into a nuisance for the people who had already decided not to write.

Should the same email go to every customer?

No, and the split that matters most is not demographic. Send a different message to a first-time buyer, a repeat buyer, a customer who contacted support, and a customer who bought a product with no reviews yet. Those four situations change what you should ask for and how much you are entitled to ask.

8 Review-Request Email Templates That Convert

Eight review-request email templates, each matched to the moment it is sent, with the subject lines, the wording that works and why each one performs.

The Brandfeel Team

Published: September 24, 2026Updated: September 24, 2026

An extreme close-up under warm raking light of a short stack of letterpress-printed reply cards fanned on pale warm paper, the deeply impressed type on the top two cards catching the light along its edges

Quick Answer

A review-request email converts when it arrives after the product has been used, asks for the smallest useful thing, and makes the first click possible inside the message itself. Almost every template below is a variation on those three rules applied to a different moment: the first purchase, the repeat purchase, the product nobody has reviewed, the customer who complained and was looked after. The wording matters less than most teams expect and the timing matters more. What separates a message that gets a response from one that does not is rarely persuasion. It is whether the person can see, without opening anything else, exactly how long this is going to take them.

Key Takeaways

Send after use, not after delivery: the delivery trigger collects opinions of the box.
Ask for the smallest useful thing first, then offer the photo after the rating is submitted.
Put the rating control in the email so the first click happens before any page loads.
Four situations deserve four different messages, and none of the splits are demographic.
One reminder, on a different channel, adds about a third again. A second adds almost nothing.

A review-request email is the message that asks a customer to rate or describe something they bought, and it is the most rewritten and least tested asset in most eCommerce programmes. Teams rewrite the copy because copy is the part they can see. The response rate usually moves for reasons that have nothing to do with the words. Last updated: September 2026.

Omniconvert has measured how stores collect and display customer feedback across the CROBenchmark dataset of 7,000+ websites in 15+ industries, against 248+ audit criteria, over 13 years in eCommerce. The pattern is consistent: the stores with the strongest review coverage are rarely the ones with the best-written requests. They are the ones whose requests arrive at the right moment and ask for less.

What follows is eight templates, each tied to the moment it belongs to, with the reason each shape works. For the machinery around them, see how to build a Review-Generation system. For the three levers at a general level, see how to get more product reviews. For the quarter plan they sit inside, there is 12 ways to get more reviews this quarter.

What makes a review-request email convert

Three things, in order of size: when it arrives, how much it asks for, and whether the first click is possible inside the message. Everything else, including the copy every team spends its time on, sits well below those three and usually moves the rate by a few percent rather than by a multiple.

Timing is first because it is the only one that changes what the customer has to say. A request that arrives on the day of delivery reaches someone who has opened a box and formed no opinion of the product, so it collects either silence or a review of the packaging. The same request three weeks later reaches someone with something to report.

Size of ask is second. Every required field removes a share of the people who were willing a moment ago: a title, a nickname, a category breakdown, an account. The version that performs asks for a rating and one optional sentence and stops there.

Placement of the first click is third and the most often missed. If the stars are rendered in the email and clicking one carries the rating through to the form, the customer has already committed before any page loads. If the email contains a button that opens a blank form, the decision happens on a page they have to wait for.

The Request Ladder: ask for the smallest useful thing

Rank what you could ask for by the effort it costs the customer, then pick the lowest rung that still gives you something worth having. Most programmes ask two or three rungs too high and read the resulting silence as disinterest rather than as a price they set.

The rungs, from cheapest to most expensive: a single tap on a star rating, a rating plus one optional line, a written review, a written review with a photograph, a video. Each step up costs you a meaningful share of respondents and buys you a more useful artefact.

The productive move is to climb the ladder across messages rather than inside one. Ask for the rating, accept it, and then offer the photograph on the thank-you screen to the people who just demonstrated they are willing. You keep the ratings you would have lost and still collect a useful share of images.

The eight templates

Each one is a moment rather than a style. The subject lines are deliberately plain, the bodies are deliberately short, and the square brackets mark the only parts that change. If a template reads as though it could have been sent to anybody, it is the wrong template for that moment.

1. The first ask, after use. Subject: How is the [product] working out? Body: one line naming what they bought and when, one question, and the star row. This is the workhorse and it carries most of your volume. Send it at the category-appropriate gap after delivery, never on the delivery event itself.

2. The single reminder. Subject: Thirty seconds on the [product]? Body: one sentence acknowledging the first message, the same star row, nothing new. Send three to five days later, ideally by SMS if you have consent, because a different channel behaves like a different message rather than like a repeat.

3. The uncovered product. Subject: You are the first to try the [product] Body: say plainly that this item has no reviews yet and that theirs would be the first. This is the highest-performing template in the set by response rate, because it converts the request from a favour into a contribution, and it is the one that moves coverage rather than volume.

4. The repeat buyer. Subject: Your [nth] order of [product] Body: name the repeat, ask what keeps them coming back, and offer a single line rather than a form. A customer who has bought the same thing three times has the most credible review available to you and is rarely asked for it.

5. The recovered complaint. Subject: Did we get that sorted? Body: reference the issue, confirm the resolution, then ask. Send it a week after the ticket closes, never on the same day. A publicly resolved problem is more persuasive to the next reader than an untroubled purchase, and most stores suppress exactly these customers out of nervousness.

6. The backlog request. Subject: You bought the [product] last year Body: be honest that this is an old order and that you never asked. Send once, to delivered orders from before the programme existed. The rate is lower than a fresh request and the base is vastly larger, which makes this the biggest one-off win most stores have available.

7. The photo follow-up. Subject: Would you add a photo? Body: thank them for the rating they already left, then ask for the image on its own. Send only to people who submitted, only after they submitted, and never as a field inside the original form.

8. The experience split. Subject: How was the delivery? Body: ask about the service rather than the product, in one question. Send it to customers who are neutral on the item itself. It recovers responses from people who had nothing to say about a sock and plenty to say about when it arrived.

What each template is actually worth

Response rate is the obvious column and the least useful one on its own. The one that decides where to spend effort is the last: whether the template moves your total review count or moves the share of your catalogue that carries any reviews at all, which are different problems with different fixes.

The third row is the one worth arguing about internally. Routing requests to products with no reviews barely changes the number in your dashboard and substantially changes what a shopper meets on a product page, which makes it a hard sell against a reporting line and the right decision anyway.

Four mistakes that cost more than the copy

Sending on delivery, asking for everything at once, hiding the rating behind a page load, and treating a complaint as a reason to stay quiet. Each is a structural choice rather than a wording choice, which is why rewriting the email never fixes any of them.

Sending on delivery is the most common and the most expensive. It is also the default in most tools, because delivery is the event the system can see most easily. Convenience for the sender has quietly set the trigger for half of eCommerce.

Asking for everything at once converts a thirty-second favour into a five-minute task, and the customer prices it correctly. Baymard Institute's long-running work on checkout has shown for years how reliably each additional required field costs completions, and a review form obeys the same arithmetic with none of the purchase motivation behind it [Baymard Institute].

Hiding the rating behind a page load wastes the moment of highest willingness. The person was ready in the inbox and is asked to be ready again somewhere else.

Suppressing customers who complained is understandable and backwards. Bain and Company's work with Fred Reichheld holds that a five percent improvement in retention can raise profits by twenty-five to ninety-five percent, and a recovered complaint is one of the few moments where goodwill is measurably higher than it was before the problem [Bain and Company].

What to do this week

Four actions, none of which need a new tool, all finishable inside five working days. The point is to have the structural changes live before anyone schedules a meeting about subject lines, because the structural changes are worth more and take less time.

Move your trigger. From delivery to a category-appropriate gap after delivery. One setting, and usually the largest single change available.
Put the stars in the email. If clicking a rating in the inbox does not carry through to the form, fix that before touching any wording.
Cut one required field. Whichever is least necessary. Then cut a second one next week.
Count your un-asked orders. Delivered orders that never received a request. That number is template six, and it is a one-afternoon win.

Where the harder question is what the reviews are telling you rather than how many arrived, that is a sentiment problem rather than a volume one. Brandfeel, Omniconvert's sentiment-intelligence layer, aggregates reviews, NPS and support-ticket themes to surface what customers keep saying, and that signal feeds Nexus by Omniconvert, an AI for eCommerce growth engine that unifies commerce data, ranks experiments by True Profit, and generates campaigns and creative you approve before they go live. To see how your review coverage compares with the brands you compete against, the where you stand on reviews guide covers the competitive read.

The bottom line

The reason review-request emails get rewritten so often is that the copy is the only part most teams can change without asking anyone. It is also the part that matters least. Every template above is really a claim about a moment: that this customer, at this point in their relationship with the thing they bought, has something specific to say and can be asked for it cheaply. Get the moment right and mediocre wording performs. Get the moment wrong and no amount of craft recovers it, because you are asking somebody to describe an experience they have not had yet. So change the trigger first, shrink the ask second, and move the first click into the inbox third. Then, if you still want to spend an afternoon on subject lines, you will at least be optimising something that is already working.

Source: Omniconvert, review-request templates by sending moment and by which target each one moves
Template	When it is sent	Moves volume	Moves coverage
First ask, after use	1 to 4 weeks post-delivery	Large, ongoing	Small
Single reminder	3 to 5 days after the first	Moderate, ongoing	Small
Uncovered product	Same gap, routed by review count	Small	Large
Repeat buyer	On the second or third order	Small	Moderate
Recovered complaint	A week after the ticket closes	Small	Small
Backlog request	Once, to historical orders	Large, once	Moderate
Photo follow-up	Immediately after submission	Protects volume	None
Experience split	To neutral respondents	Moderate	None