Timing is the single largest variable in review-collection response rates. Send the request too early and the customer hasn't formed an opinion. Send it too late and the purchase is a distant memory. This guide breaks down the optimal timing for every business type, backed by what we've observed across thousands of review invitations.
# The golden rule: ask when the experience is complete
The universal principle: don't ask for a review until the customer has received and experienced what they paid for. Obvious, but widely violated. E-commerce stores that send review requests 24 hours after ordering — before the product has shipped — get low response rates and worse reviews, because the customer hasn't used the product yet.
For every business type, the question is: when has the customer experienced enough to have a meaningful opinion?
# By business type
# Digital products & SaaS
| Product type | Optimal timing | Why |
|---|---|---|
| Instant-access digital product (e-book, course, template) | 3–7 days after purchase | Enough time to consume, not so long the purchase feels distant |
| SaaS (free trial) | 7–14 days into the trial or immediately after first "aha moment" | Capture impression while engaged, but after the product has delivered value |
| SaaS (paid subscription) | 30–60 days after first payment | Give time for onboarding + habitual use; renewal is a natural trigger |
| Software update / new feature | 14 days after feature adoption | User has integrated the change into their workflow |
The SaaS nuance: Subscription businesses have recurring verification opportunities. Don't just ask once — every renewal payment is a new transaction and a new chance to ask. A customer who's been subscribed for 12 months has a fundamentally different perspective than one who's been subscribed for 2.
# Physical products
| Product type | Optimal timing | Why |
|---|---|---|
| Standard e-commerce (in-stock) | 7–14 days after delivery | Product received + used + opinion formed |
| Made-to-order / custom | 14–21 days after delivery | Longer experience curve before the product is "lived with" |
| Clothing / fashion | 5–10 days after delivery | Quick opinion formation, but allow for returns window awareness |
| Electronics / high-consideration | 14–30 days after delivery | Takes time to evaluate; early reviews skew superficial |
| Consumables (food, supplements) | 7–14 days after delivery | Quick consumption cycle |
The delivery trigger: If you have access to tracking data, the ideal trigger is N days after the carrier confirms delivery — not N days after the order is placed. A product that takes 10 days to ship shouldn't trigger a review request on day 3.
# Services
| Service type | Optimal timing | Why |
|---|---|---|
| One-off service (cleaning, repair, consulting session) | 24–72 hours after service completion | Fresh but not raw; immediate post-service asks feel pushy |
| Recurring service (monthly cleaning, ongoing consulting) | After the 2nd or 3rd engagement | First session isn't representative; give the relationship time to stabilize |
| Professional services (legal, accounting, agency) | At project milestone or completion | Natural breakpoints, not calendar-arbitrary dates |
# Day of week and time of day
Across e-commerce and SaaS, the data converges on a few patterns:
- Best days: Tuesday through Thursday. Monday is catch-up day; Friday afternoon through Sunday is low-engagement.
- Best time of day: 10am–2pm in the recipient's timezone. Morning inbox processing is done, but it's before the afternoon slump.
- Avoid: Friday afternoon (review request goes into the weekend void), Monday before 10am (buried in weekend backlog), and late-night sends (feels automated and impersonal).
# Reminder cadence
Most people don't write a review on the first request. A structured reminder sequence dramatically increases total response rate without annoying customers:
| Send | Timing | Notes |
|---|---|---|
| Initial request | Optimal window (per chart above) | Friendly, personalized, clear CTA |
| First reminder | +3 days | "In case you missed this" — light, no guilt |
| Second reminder | +7 days (10 days total) | Final ask. "Last chance" framing. After this, stop. |
Stop after 2 reminders. Three or more reminders annoys customers and generates negative sentiment — exactly the opposite of what you want. If someone hasn't reviewed after 10 days and two reminders, they're not going to.
# Transaction-verified: why timing matters even more
With processor-attested (Level 4) verification, review requests are tied to specific Stripe charges. That means:
- You can't send a request without a real charge. No "batch-invite everyone in my customer list." Every invitation traces back to a confirmed transaction.
- Timing is deterministic. The invitation fires when the charge settles — not when you remember to send it. For physical products, configure a delivery delay.
- Refunds auto-hide reviews. If a customer requests a refund after leaving a review, the review is hidden automatically. So you don't need to worry about reviews from customers who ultimately weren't satisfied.
The net effect: processor-attested review collection encourages you to get the timing right upfront, because you can't retroactively invite or exclude customers. The system is neutral — it sends to every paying customer, at the right time, without you curating the list.
# What NOT to do
- Don't ask before the experience is complete. Pre-delivery review requests generate low response rates and lower-quality reviews.
- Don't send more than 2 reminders. Three+ reminders feels like harassment.
- Don't gate reminders behind positive sentiment. Selectively reminding only happy customers is invitation bias, and the FTC's 2024 rule makes it legally risky.
- Don't offer incentives for positive reviews. Incentives for writing a review are generally fine (if disclosed). Incentives for writing a positive review are not.
- Don't batch-send to your entire customer list at once. Staggered, transaction-triggered sends get higher response rates and feel personal.
# The bottom line
The best time to ask for a review is when the customer has experienced the full value of their purchase — which varies by what you sell — and on a Tuesday or Wednesday between 10am and 2pm. Send once, remind twice, stop. And whenever possible, tie the invitation to the transaction itself, so every paying customer is asked at the right time without you having to manage the timing manually.
Further reading:
- Post-Purchase Review Email Templates — ready-to-use email copy for every timing scenario
- How to Collect Verified Customer Reviews — the complete guide
- How Stripe Review Verification Works — how transaction-triggered invitations work technically