Review request emails
Last updated: November 17, 2026
Most stores collect reviews through automated request emails, sent a set number of days after an order event, with a row of stars for each product that opens the BetterReviews chat. This page has two halves:
- When requests are sent: turning collection on, the trigger and delay, the time of day, and how often one customer is emailed.
- Who is skipped and why: every reason a customer doesn’t get an email, including the marketing-consent rules.
Sending review requests from Klaviyo? If you’ve connected Klaviyo and chosen Klaviyo under Who sends review requests, everything on this page about who gets a request and when still applies. At the moment we’d have sent our email, we send a
BetterReviews - Review Request Eligibleevent to Klaviyo instead, and your Klaviyo flow sends the email. That email, its unsubscribe link and any reminders are yours to manage in Klaviyo: keep it free of incentives and send the same request to every customer. Unsubscribes in Klaviyo don’t reach the BetterReviews suppression list, and opens and clicks show in Klaviyo’s flow reporting, not in our email stats. BetterReviews itself never sends reminders, so a Klaviyo flow is the way to add them. Setup and flow recipes: Send review requests from Klaviyo.
When requests are sent
Turning collection on and off
Collection is off by default on new installs. The usual way to go live is Cutover → Turn on BetterReviews, which turns on collection and the weekly summary email in one step (see Cutover), or the Start collecting step in onboarding. Both ask for a notification email first if we don’t have one for your store.
After that, the Enable collection / Disable collection button lives in Collect → Emails → Review request → Settings, under Status.
- Cancelling a paid plan doesn’t turn collection off. You drop to the Free plan and requests keep going out, with the classic review form instead of the AI chat.
- A Shopify freeze or an uninstall does stop collection. Waiting requests are cancelled, and turning sending back on afterwards is always a deliberate click: we never resume on your behalf, and you see the preview of what will be sent again.
The trigger and the delay
You set both in Collect → Emails → Review request → Settings, under Timing. The delay counts from the event’s real Shopify time, not from when we hear about it: an order paid three days ago with a 7-day delay sends in four days.
Trigger event, which Shopify order event starts the countdown, and the Send request after options for each:
| Trigger | When the countdown starts | Delay options (days) |
|---|---|---|
| Order fulfilled (default, recommended) | At each shipment. The email asks about the products in that shipment. | 3, 5, 7, 14, 30 |
| Order delivered | When the carrier confirms delivery. The most accurate signal when it works; see Delivery fallback. | 0, 1, 3, 7, 14, 30 |
| Order paid | When payment is captured. Useful for pre-orders and dropshipping. | 1, 7, 14, 30, 60 |
| Order created | When the order is placed. Useful for digital or made-to-order products. | 1, 7, 14, 30, 60 |
The bold delay is the recommended one. Each customer gets at most one review request per order: if an order ships in two boxes, the first box to come due sends the email and the second doesn’t send another.
Stores with short-lived excitement (novelty items, food) usually prefer shorter delays. Products with a break-in period (shoes, skincare, kitchenware) do better at 7–14 days. Subscriptions and pre-orders usually pair Order paid with 14–30 days. Order delivered + 3 days is a popular choice for merchants coming from Okendo or Yotpo.
Screenshot of the Timing section with the four-option trigger dropdown and the fallback-days input that appears when “Order delivered” is selected — manual capture, drop in here.
Different timing per product (for example, asking about a sofa later than about a cushion) is rolling out store by store. See When to ask.
Changing the trigger or delay
Saving a new trigger or delay first shows a preview (“X cancelled, Y rescheduled, Z newly overdue”) and asks how to apply it:
- Apply to all requests, including ones already scheduled.
- Trigger change: every request that hasn’t gone out yet is cancelled, because the new trigger picks a different set of orders. To rebuild the queue, click Enable collection again in Collect → Emails → Review request → Settings, under Status. It runs the same preview you saw the first time you turned collection on.
- Delay change only: scheduled requests are re-timed to their original event plus the new delay. Requests already being sent are left alone. A request whose new send time has already passed goes out in that customer’s next send window (below), not all at once.
- Apply to new orders only. Saves the new timing for future orders and leaves every existing request alone.
Past orders that never made it into the queue (for example, because their send date had already passed) aren’t added back in either case.
Time of day
The trigger plus the delay picks the date. The time of day is picked inside a send window, 9am–9pm by default, with a small random spread so emails don’t all go out in the same minute:
- Customer’s shipping address known: the customer’s local 9am–9pm. This covers most shoppers.
- No customer address, store timezone known: your store’s local 9am–9pm. Common for digital products and gift cards.
- Neither known: the email goes out at the time of day the trigger event happened.
You can set your own window (for example 10am–6pm) with send_window_local_start and send_window_local_end, or turn the window off with send_time_strategy: "off", through the Settings API, or ask support to do it for you. There’s no setting for this in the app. On some stores we’re testing a narrower afternoon window (1pm–6pm) for half of customers; a custom window you set always wins over that test.
How often customers are emailed
Repeat buyers (subscribers, collectors, anyone who orders every couple of weeks) could otherwise get several requests a month. To avoid that, BetterReviews may space requests out per customer:
- About one review request per customer every 30 days, per store. If a customer got a request from your store in the last 30 days, their next one may wait until the 30 days are up, then go out in their usual send window.
- Requests due together may be combined into one email listing up to 4 products. The order can vary: we’re testing putting the product with the fewest reviews first. Each product keeps its own row of stars, and each review is still credited to the order it was bought in. A request that doesn’t fit in the 4 slots waits for the next window. Combined requests show as Combined into another email in your email stats.
- We don’t ask more than ~45 days after purchase. If waiting out the 30 days would push a request past that, it isn’t sent and shows as Customer emailed recently — skipped.
Spacing is being rolled out gradually, so some customers may still get one email per order for now. When Klaviyo sends your requests, spacing still decides when each request is handed to Klaviyo, and a combined request arrives as one event listing its products.
What the email contains
- A short message (your heading and body text)
- Each product with a row of stars (“Tap a star to begin”). Tapping a star opens that product’s review chat with the rating already in place, or the classic review form if your store uses it
- Your logo and branding (see Customizing the email template)
- A footer with an unsubscribe link and the BetterReviews business address
Each email’s link carries a unique random token, so anyone with the email can open that customer’s review page. Treat the link as the credential and don’t forward review emails. Links stay valid for 90 days by default; you can change that to 30–180 days through the Settings API (request_token_expiry_days) or by asking support. It isn’t a setting in the app.
Delivery fallback (for the “Order delivered” trigger)
Not every carrier reports delivery. Major US carriers (USPS, UPS, FedEx, DHL Express) are reliable. Many European regional carriers (DPD, Evri, Royal Mail non-tracked, Yodel) and most smaller Latin American and Southeast Asian carriers rarely send a “delivered” status, and international shipments often lose tracking at the border.
So no customer is silently skipped, every shipment waits for its delivery confirmation for a set number of days. If the carrier confirms delivery, the email goes out on time. If it never does, the email goes out anyway once that wait is over. Each shipment waits on its own, but a customer still gets only one email per order.
The wait is 14 days by default, adjustable from 3 to 30 in Collect → Emails → Review request → Settings, under Timing (visible only with the delivered trigger). The shorter it is, the more emails go out without a delivery confirmation.
Carrier reliability: which trigger should you pick?
If you ship mainly with USPS, UPS, FedEx, DHL Express, Canada Post or Australia Post, Order delivered is the best signal.
If your carriers don’t report delivery consistently, stay with Order fulfilled. Otherwise many of your emails go out on the fallback anyway, which defeats the point.
Not sure? Open a few recent orders in your Shopify admin and check the tracking company. If most have no delivered status after a week, use Order fulfilled.
Sending a review request manually
To send a review link outside the automatic flow (say, to a customer who emailed asking to leave a review), create one through the API without sending an email:
curl -X POST https://api.betterreviews.app/api/v1/review-requests/send \
-H "X-API-Key: YOUR_API_KEY" \
-d '{"email": "[email protected]", "product_ids": ["shopify-7125386199075"], "skip_email": true}'
The response includes a hub_url to paste into your reply; it opens the customer review hub. These show as Manual link (no email) in Collect → Review requests. See the API docs for details.
If you include the Shopify order_id, that link counts as the order’s review request, and BetterReviews won’t also send its own email to that customer for that order. Use this when you send review links from another tool (Klaviyo, your helpdesk) for some orders, so the customer is asked once, not twice.
Turning off request emails entirely
Some stores collect reviews only through the widget’s Write a Review button. To stop automated review request emails:
- Open Collect → Emails → Review request → Settings
- Under Status, click Disable collection
- If requests are waiting to send, a confirmation shows how many will be cancelled; confirm with Disable collection
Your widget keeps working, and customers can still start reviews from your product pages. Cancelled requests show as Collection paused in your email stats.
Languages
Review request emails, and the review pages they link to (chat, review form and review hub), are shown in the customer’s language: English, Polish, Spanish, German or French. Polish is live now; Spanish, German and French switch on after a native-speaker review. Anything else falls back down the order below.
The language is chosen per customer, in this order: a language set in the review link, the language their order was placed in, their browser language, your store’s primary language, then English. Emails use the order’s language, then your store’s primary language. Template fields you’ve edited go out word for word in whatever language you wrote them — see Languages. The consent line under the review form is translated too.
Seeing if it’s working
- Collect → Emails → Review request → Performance shows opens, clicks, reviews collected, deliverability and which emails were held back. See Email performance. Requests handed to Klaviyo aren’t in the open, click and deliverability numbers; use your flow’s reporting in Klaviyo, and the
BetterReviews - Review Request Completedevent to see who went on to review. - Collect → Review requests lists recent requests one row per request: the order, the customer (name plus a masked email), the products, when it was scheduled or sent, and a plain-language status such as Scheduled for Jun 20, Awaiting delivery, Sending, Sent, Opened, Clicked, Skipped — customer unsubscribed, or a cancel reason. Requests handed to Klaviyo show as Sent via Klaviyo until the customer starts a review. You can filter by status or date, search by order number or customer email, and cancel a request that hasn’t gone out yet.
Who is skipped and why
When a request is created
A review request is only created when all of these are true:
- Collection is on (see Turning collection on and off).
- Your chosen trigger event happened on the order.
- The order has at least one line item and isn’t a Shopify test order. Orders placed with the Bogus Gateway or in payments test mode never create a request. To preview the email, use Send test email.
- The event is recent enough. If the event is more than ~90 days old, or the send date it gives is already in the past (for example, you install today and the order shipped a month ago with a 7-day delay), the request shows as Skipped instead of being sent. This keeps install day from emailing a month of old orders.
- The customer hasn’t said no to email (see Marketing consent).
- The customer hasn’t already had a request for this order. A later shipment or a reprint never sends a second email, and switching triggers doesn’t double-send. A different person on the same order (for example a gift recipient with their own email) is treated separately.
Checked again right before sending
- The customer is on your suppression list (they unsubscribed, their email bounced, or they marked an email as spam). Checked at send time too, so a customer who unsubscribes while an email is waiting doesn’t get it.
- The customer already reviewed every product in the email through BetterReviews (imported reviews and reviews you rejected don’t count). The email is cancelled. If they reviewed only some products, the email still goes out, and their review page skips the ones already done. If this check can’t run, we send rather than hold the email back.
- A request for the same order already went out, for example from an earlier shipment.
- The email template contains promotional wording (see Marketing consent).
Every email held back shows its reason in Collect → Review requests and in the Where emails stopped list on Email performance, which explains each label.
Marketing consent
You might assume BetterReviews only emails customers who ticked “Email me with news and offers” at checkout. We don’t, and neither do Klaviyo, Loox or Okendo. Here’s why.
By default, review request emails go to every customer who bought from your store, not just those who opted in to marketing. We treat them as transactional: non-promotional, post-purchase, and about the product the customer bought. That classification is recognized under CAN-SPAM (US), PECR’s soft opt-in (UK), CASL §6(6) (Canada) and GDPR Article 6(1)(f) legitimate interest (EU).
It rests on three things, and we enforce all three:
- No promotional content. No discounts, incentives, cross-promotion, rewards or promo codes, in any language. A template with promotional wording (for example “get 20% off your next order”) is rejected when you save it and when you send a test, and an email that somehow still has it is cancelled at send time and shows as Email template contained promotional content.
- A working unsubscribe. Every email has an unsubscribe link. Clicking it adds the customer to your store’s suppression list, and BetterReviews never emails them again, automated or manual.
- Respecting an explicit no. Customers whose Shopify email-marketing status is unsubscribed, redacted (erased under GDPR) or invalid (flagged undeliverable by Shopify) never get a review request, whatever your settings. When a new order arrives with one of those states, that customer’s earlier requests that haven’t gone out yet are cancelled too.
Only customers who opted in: Require marketing consent
If your legal team wants the stricter rule (email only customers who opted in to marketing at checkout), turn on Require marketing consent in Collect → Emails → Review request → Settings, under Audience.
- Only customers whose Shopify status is subscribed get review requests. Everyone else is skipped.
- Turning it on cancels waiting requests for customers who weren’t subscribed when the request was created. The preview shows the count before you confirm, and they show as Marketing consent now required.
- Turning it off cancels nothing; every waiting request is still valid under the looser rule.
- Expect far fewer emails. Typically only 5–15% of customers tick the marketing box at checkout. The badge next to the setting shows your own rate.
Every change to this setting is logged with who made it and when, and each request records the customer’s consent status at the moment we decided whether to email them.
What about EU and UK customers?
The default is sound for EU and UK customers too, as long as the four PECR soft opt-in conditions hold: the contact details came from a sale, the email is about similar products, the customer could opt out when their details were collected, and every message carries an opt-out. All four hold for BetterReviews: Shopify’s checkout offers the marketing checkbox, and our emails carry the unsubscribe link. If your legal team prefers explicit opt-in, turn on Require marketing consent.
When Klaviyo sends your requests
The rules about who gets asked still apply before we hand a request to Klaviyo: unsubscribed, redacted and invalid customers, customers on the BetterReviews suppression list, customers who already reviewed everything in the request, and (with Require marketing consent on) anyone not subscribed are all skipped. Our promotional-content check doesn’t run on your Klaviyo template, so keeping it non-promotional and making sure it has a working unsubscribe link is up to you.
Unsubscribes
Every BetterReviews email has an unsubscribe link, as CAN-SPAM requires. When a customer unsubscribes, they’re added to your store’s suppression list and get no further BetterReviews emails. They can still use a review link you send them yourself (for example from the API, above); unsubscribing only blocks emails. You don’t have to do anything; suppression is automatic.
When Klaviyo sends your requests, Klaviyo’s unsubscribe link and consent settings decide who receives them, and unsubscribing in Klaviyo doesn’t add the customer to our list. Customers already on our list still never get a request event.
Customizing the email
The look and copy of the email (logo, colors, subject, body) are covered in Customizing the email template. When Klaviyo sends your requests, you design the email in Klaviyo instead.
Book a demo