The best time to ask for a review is right after a customer has experienced your product — but not so soon that they haven't formed an opinion. The worst time is when they're annoyed by yet another marketing email.
This guide covers when to send, what to say, and how to structure your review request emails for maximum response rates. Every template is based on patterns that consistently outperform generic "please leave us a review" messages.
# The golden rules of review request emails
Before the templates, three principles that determine whether your emails get opened — or deleted:
# 1. One ask, one action
Your email has exactly one job: get the customer to click the review link. Don't cross-sell. Don't ask them to follow you on social media. Don't include three different CTAs. One email, one link, one action.
Emails with a single CTA increase click-through rates by 42% compared to emails with multiple CTAs (Campaign Monitor, 2023).
# 2. The subject line is everything
Most review request emails die in the inbox. Your subject line needs to:
- Be from a recognizable sender (your brand name or founder name)
- Not look like marketing ("Your order #1234 — quick question")
- Be short (under 50 characters for mobile)
"Quick question about your order" consistently outperforms "Please review your purchase" by 2–3× on open rates.
# 3. Timing matters more than copy
The best-written email sent at the wrong time will get ignored. The rules:
| Product type | When to send | Why |
|---|---|---|
| Digital products | Same day or next day | Immediate value delivery |
| Physical products | 3–7 days after delivery | Time to unbox and use |
| SaaS / subscriptions | 14–30 days after signup | Time to experience the product |
| Services (consulting, etc.) | Within 48 hours of completion | Fresh impression, not yet stale |
| Consumables / food | 5–10 days after delivery | Time to try the product |
Never send a review request before the customer has received the product. This is the single most common mistake, and it's the one that got SiteJabber in trouble with the FTC in 2024. Sending a review request at checkout — before the customer has the product — generates reviews about expectations, not experience. Those reviews are misleading, and they're now a regulatory risk.
# Template 1: E-commerce — physical products
Subject: How was your [Product Name]?
Hi [First Name],
Your [Product Name] arrived [X days] ago — hope it's everything you expected.
When you have a moment, we'd love to hear how it's working out. Your review helps other customers make better decisions, and it helps us make better products.
[Leave a review →]
Honest feedback only, please — good, bad, or in-between. We read every one.
Thanks, [Founder Name / Brand Name]
Why it works: Short, personal, and explicitly invites honest feedback. "Good, bad, or in-between" signals that you're not fishing for 5-star reviews, which increases both response rate and review authenticity. The founder's name as the sender (rather than a generic brand email) increases open rates.
# Template 2: SaaS — subscription products
Subject: [X] days in — how's it going?
Hi [First Name],
You've been using [Product Name] for about [X] days now. We built it to [solve specific problem], and we genuinely want to know: is it working for you?
If you have 2 minutes, a quick review would mean a lot: [Leave a review →]
No pressure, no incentive — just honest feedback from a real user. It helps other [industry/role] professionals decide if [Product Name] is right for them.
Thanks for giving us a try, [Founder Name]
P.S. If something isn't working, reply to this email. It goes directly to me, and I'll make sure it gets fixed.
Why it works: The P.S. is the highest-read element of any email. Making it a direct line to the founder converts people who wouldn't leave a review but might report a problem — reducing churn and negative reviews simultaneously. The "we built it to [specific problem]" line reminds them of the value proposition without being salesy.
# Template 3: Services / freelancers / agencies
Subject: Thanks for trusting us with [project/engagement]
Hi [First Name],
Working with you on [specific project] was a pleasure — thank you for trusting us with it.
If you're happy with how it turned out, a quick review helps us enormously. Most of our new clients find us through reviews from people like you.
[Leave a review →]
And if anything fell short, please tell me directly. I'll make it right.
Best, [Your Name]
Why it works: Services are personal. The review request should be personal too — from the specific person they worked with, referencing the specific project. Generic service review requests ("Please review our company") get ignored. Specific ones get responses.
# Template 4: Short follow-up (for non-responders)
Subject: One quick question
Hi [First Name],
No worries if you're busy — just one quick question:
Would you recommend [Product Name] to a friend?
[Yes, absolutely →] [Not really →]
That's it. Takes two seconds.
Thanks, [Founder Name]
Why it works: The binary question reduces friction to near zero. "Yes" clickers can be routed to a review form pre-loaded with a positive sentiment; "Not really" clickers can be routed to private feedback. This is sometimes called a "sentiment gate" and can increase review submission rates by 40–60% compared to a direct review link.
⚠️ Important: If you route "yes" clickers to a review form, you must also give "not really" clickers a path to leave a review. Otherwise you're review gating — funneling happy customers to public reviews and unhappy ones to private feedback — which is an FTC compliance risk under the 2024 rule.
# Template 5: Delivery-triggered (physical products)
Subject: Your [Product Name] was just delivered
Hi [First Name],
According to [carrier], your [Product Name] just arrived. Here's a quick question while it's fresh:
[Leave a review →]
We ask after delivery — not before — because we want reviews from people who've actually used the product. No rush. When you've had a chance to try it, we'd love to hear what you think.
Thanks, [Brand Name]
Why it works: The delivery trigger is the most accurate timing for physical products. And explicitly saying "we ask after delivery, not before" signals integrity — it tells the customer you're not one of those companies collecting reviews at checkout. This builds trust even before they write the review.
# What to avoid
# Don't incentivize positive reviews
The FTC's 2024 rule explicitly prohibits incentives conditioned on sentiment. "Leave a 5-star review and get 10% off" is illegal. "Leave a review and get 10% off" is still allowed — but your email copy must make the distinction clear.
# Don't send more than 2 reminders
One initial request + one follow-up, max. A third email is spam. If the customer hasn't responded after two attempts, they're not going to — and continuing to email them damages your brand.
# Don't ask for reviews at the wrong time
- Immediately after a support ticket is resolved? Yes (fresh relief/gratitude).
- Immediately after a billing issue? No.
- After a feature request you haven't built yet? No.
- On a customer's billing anniversary? Yes (moment of reflection).
# Don't use no-reply addresses
A no-reply sender address says "we want your opinion but not your conversation." It depresses response rates and damages brand perception. Use a real address, even if it's just a team alias.
# How Stripe-native review collection changes the equation
If you process payments through Stripe, you can automate all of this. Every charge triggers a review invitation automatically. The timing rules above are configurable — same-day, delayed, or delivery-triggered. And because the invitation is tied to the Stripe transaction, the review is processor-attested: verified independently by Stripe, not just matched to an order in your system.
The templates still matter. The timing still matters. But the automation removes the operational overhead — and the independent verification makes every review more credible once it arrives.
Further reading: How to Collect Verified Customer Reviews · Stripe Verified Reviews · How Stripe Review Verification Works