Increasing review volume
Getting more reviews out of the order volume you already have, in order of what actually works.
7 min read
On this page
Response rate is the lever. If you send a thousand requests and 3% respond, doubling that to 6% is worth as much as doubling your order volume — and is very much cheaper.
Here is what moves it, roughly in order of effect.
1. Deliverability
Nothing else matters as much. A request that lands in spam has a response rate of zero and looks identical in your dashboard to one that landed and was ignored.
- Authenticate a sending subdomain. Not your root domain — a subdomain, so review-request reputation stays separate from your order confirmations.
- Check your DMARC policy. If it is enforcing, unaligned mail fails hard.
- Never send from a free-mail address.
See Sending domain & deliverability.
2. Template style
Switch a step to the minimal template and watch what happens. Minimal templates look like mail a person sent, and reach Gmail’s Primary tab far more reliably than image-heavy HTML with one big button.
This is a two-minute change and is frequently worth more than a week of copy work.
3. Timing
The delay should answer “has the customer actually used this yet?”
| What you sell | Typical delay |
|---|---|
| Consumables, apparel | 7 days after shipping |
| Homewares, accessories | 10–14 days |
| Anything with setup or a learning curve | 21–30 days |
| Products with a genuine trial period | Match the period |
Asking too early gets you reviews of the packaging. Asking too late gets you nothing, because the purchase has left their mind.
Remember the clock starts at the status change, not the order date, so a slow-shipping order is not penalised.
4. One reminder
A single reminder five to seven days after the first request typically adds 30–50% on top of the first email’s yield.
Skip anyone who has already reviewed. A second reminder adds far less and costs deliverability — measure before you add one, and delete it if it is not earning.
5. Ask for less
Response rate is inversely proportional to how much work the request looks like.
- Link straight to a form that already knows the order and products. The hosted form does this — the customer never signs in or searches for what they bought.
- Ask about one product, not seven. A multi-product order asking for seven reviews gets zero.
- Make the star rating the first and largest thing. Many people will rate and write nothing, and a rating still counts.
6. Subject lines that are not about you
The request is a favour. Ask like it is one.
What tends to work: the product name in the subject, a first name, and a question. “How are the Merino Runners, Dana?” outperforms “Leave a review and get 10% off” in most stores, because the second one reads as marketing and gets filed as such.
What tends not to work: exclamation marks, “we’d love your feedback”, and leading with the incentive.
7. Incentives, deliberately
Incentives raise volume. Past a point they lower trust, so use them as a bootstrap rather than a permanent fixture.
- Tier them: little for text, more for photos, most for video.
- Disclose them. It is usually required, and shoppers work it out anyway.
- Consider loyalty points instead of a coupon — they cost nothing until redeemed and pull the customer back rather than discounting the next order unconditionally.
- Turn them off once coverage is healthy.
See Review incentives.
8. Ask on the site as well
The email is not the only channel. A review form widget on the product page catches the customer who is already back on your site — often the most motivated person you will get.
Post-purchase pages, order-status pages and packaging inserts with a short URL all work for the same reason.
9. Route through your email platform
If you already run Klaviyo, Omnisend or Mailchimp, connect it. Evident fires an event at the moment the request is due, and your platform sends it — inheriting your templates, your send-time optimisation, your suppression rules and your deliverability reputation.
That last one is usually the win: an established sending domain with good reputation beats a new one.
Do not add a delay in your flow. Evident already held the event for the configured delay; another one stacks. See Review request emails.
What to measure
- Response rate per step, so you can tell whether a follow-up is earning.
- Photo share of reviews, because that is what actually persuades.
- Coverage — products with at least five reviews — rather than total count.
- Reviews per product on the long tail, which is where incentives and reminders pay.
What not to do
- Do not filter by rating before asking. Sending requests only to customers you expect to be happy is both dishonest and detectable.
- Do not blast your back catalogue. Requests are capped to orders under 30 days old partly to stop this. A sudden send to thousands of old addresses is the classic reputation own-goal.
- Do not add a fourth email. It is not the reason your volume is low.
Something missing or out of date? Email [email protected] — docs corrections go straight to the team that builds the feature.