automations.help
Book a teardown

Reviews & UGC

Send a second review request to non-openers

One review email per order leaves most of your reviews uncollected — the majority of customers never act on the first ask. Here's how to wire a single, different second request that goes only to the people who genuinely didn't review, stops at two, and never nags someone who already left a review or sent the item back.

Difficulty
Intermediate
Time to build
2-4 hrs
Updated
  • Klaviyo

The manual way today

The first review email goes out, some people leave a review, and that's where it ends. To chase the rest by hand you'd export everyone who got the first ask, cross out who already reviewed, cross out who returned or refunded, cross out who unsubscribed, and then build a one-off send to whoever's left — for every cohort, every week. Nobody does that. So the first ask is the only ask, and whoever ignored it is gone.

Most customers don't review on the first email — that's normal, not a failure of the email. But it means a single ask collects only a fraction of the reviews you could have. Reviews are the social proof that actually does the converting on a product page, so every uncollected one is a quiet drag on the conversion rate of every shopper who lands there afterward. And it compounds in the worst place: your newest products have the fewest reviews and the most need for them, and a one-and-done ask is slowest to build proof exactly where it matters most.

What running looks like

A week after the first review email, the customer who still hasn't left a review — and hasn't returned the order, unsubscribed, or already been asked twice — gets one more, deliberately different ask. Only that customer. Anyone who already reviewed, refunded, or opted out never sees it, and nobody ever gets a third. The whole thing lives inside the review flow you already run, so it can't double-fire or collide with your other sends.

01The build

How to build it

  1. Decide the gap, the cap, and what 'non-opener' really means

    Needs a human

    Three calls before you build. The gap between the first ask and the second — 5-7 days is the usual sweet spot, long enough that the first email's moment has passed but short enough that the purchase is still fresh. The cap — two asks, full stop; a third reads as nagging and chips at the sender reputation every other Klaviyo send depends on. And the honest one: 'non-opener' should not actually mean 'didn't open,' because email opens are no longer trustworthy. Apple's Mail Privacy Protection pre-loads images and marks a large share of emails 'opened' whether or not a human ever looked. The signal that means something is 'didn't submit a review.' Decide up front to key the second ask off that, with a click (never a bare open) as a soft secondary signal.

  2. Build the second ask into the first flow — not a new one

    Runs itself

    Don't start a fresh flow on a fresh trigger. Extend the review-request flow you already have. After the first review email, add a time delay set to the gap from step one. Keeping the second ask in the same flow means it inherits that flow's state: Klaviyo already knows this profile received email one, so it can't re-enter someone or lose track of how many asks they've had. A separate flow on a separate trigger is exactly how stores end up sending the same customer three review emails.

  3. Split on the real outcome: did they actually review?

    Runs itself

    After the delay, add a conditional split on whether this customer has submitted a review since the first email. Your review platform — Yotpo, Okendo, Judge.me, Loox, Stamped, they all do this — syncs a 'Reviewed Product' or 'Review Submitted' metric into Klaviyo. Split on that metric having occurred since the order's delivery (or first-email) date. Anyone who reviewed exits here. A 'please leave a review' email landing on someone who already left one is the most obviously broken automation a customer can receive, and it's the one this split exists to prevent.

  4. Narrow to the genuinely unengaged — by clicks, not opens

    Runs itself

    For the people who still haven't reviewed, you can narrow further, but split on whether they clicked the first email, not whether they opened it. A click is a real action a person took; opens are inflated by Mail Privacy Protection and image pre-fetching to the point of being noise. A non-reviewer who clicked the first email and then didn't finish probably just needs a nudge; a non-reviewer who never clicked needs a different hook entirely. Branch the message on that if you want two versions — or skip this split and send everyone the same second ask. Either is fine. What's not fine is gating the whole thing on opens, which would silently drop real non-openers and re-ask people who never saw a thing.

  5. Re-run the suppressions right before the send

    Runs itself

    State changes during the wait, so re-check it at the end, not only at the start. Immediately before the second email, split out anyone who opened a return or refund since the first ask (Klaviyo's Shopify integration exposes a 'Refunded Order' metric and the order's tags, both readable in a flow), anyone who unsubscribed during the gap, and anyone already marked as asked twice. Then write a tag like review-request-2-sent onto the Shopify order the moment the second email enqueues. That tag is the idempotency key: a flow edit, a re-publish, or a duplicate entry all see it and skip, so nothing can ever produce a third email.

  6. Make the second email a different email

    Runs itself

    A resend of email one performs like email one did — it's already been ignored once. Change it. Cut it to a single line and a one-tap star rating that drops the customer straight into a review form pre-filled with their product, so the ask costs them one tap instead of a form. Change the subject line, because the first one didn't land and reusing it gets filtered the same way. If you offer an incentive for reviews, the second ask is the right place to lead with it. And for customers who consented to SMS and ignored the email, send the second ask as a text — a different channel is a genuinely different shot, not just a louder version of the same one.

  7. Stop at two and respect a frequency cap

    Runs itself

    After the second email the flow ends. No third branch, no 'last chance' reminder. Turn on Klaviyo's smart sending / frequency cap so the review flow can't pile onto a customer who's already getting a promo or a back-in-stock the same day. Two asks, spaced, then silence — that restraint is the whole point. It's what keeps your review emails from teaching people to tune out everything you send, which is the failure mode that quietly kills response rates on every future flow, not just this one.

02The stack

What it’s built on

Klaviyo
Owns the entire build: the delay after the first email, the 'did they review?' split, the click split, the return/unsubscribe suppressions, the second send, and the frequency cap that stops it colliding with other emails. The review signal it splits on comes from your review platform's native Klaviyo integration (Yotpo, Okendo, Judge.me, Loox, Stamped), which pushes a 'Reviewed Product' metric onto the profile.Klaviyo's free tier is enough to build and test this, and you're almost certainly already running it for email. Any ESP that supports a delayed flow with conditional splits on a custom review metric works the same way — only the split syntax differs.
Shopify
Read through Klaviyo's Shopify integration: the source of the return/refund signal you suppress on, and the order where the review-request-2-sent tag lives so the two-ask cap survives flow edits and re-runs. No custom Shopify code is needed — the integration surfaces the order data and tags inside the flow.

03Questions

Before you build

Isn't a second review email just nagging customers?

Only if you do it the lazy way. This re-asks one time, after a gap, and only the people who genuinely didn't act — reviewers, returners, and the unsubscribed are filtered out before the send. The cap is two emails, full stop. A single well-targeted follow-up to people who never reviewed isn't nagging; resending the same email three times to everyone is, and the hard stop at two is what keeps it on the right side of that line.

Can I trust email opens to find non-openers?

No, and this is the trap most people fall into. Apple's Mail Privacy Protection pre-loads images and marks a large share of emails 'opened' whether or not anyone read them, so 'opened' is no longer a reliable signal and 'didn't open' silently includes people who did. Key the second ask off whether they submitted a review — the actual outcome you care about — and use a click, not an open, if you want a secondary engagement signal.

Should the second email be the same as the first?

No. A resend performs like the first send did, and that one's already been ignored. Change the subject line, cut the body to a single line with a one-tap star rating, and lead with your review incentive if you have one. For customers who consented to SMS, send the second ask as a text instead — a different channel is a real second shot rather than a louder repeat of the first.

How long should I wait before the second ask?

Usually 5-7 days after the first email. That's long enough that the first ask's moment has clearly passed, and short enough that the purchase is still recent enough for a review to feel natural. Tighten it for fast-turnover products and stretch it for things people use slowly — but keep it inside the same flow so the wait is a delay step, not a second trigger.

What stops someone who already reviewed from getting the second ask?

A conditional split on the review metric. Your review platform syncs a 'Reviewed Product' / 'Review Submitted' event into Klaviyo, and the flow checks for it since the order's delivery date right after the delay. Anyone who reviewed exits there. A second suppression pass before the send also drops anyone who returned, refunded, or unsubscribed during the wait, so state that changed mid-flow still gets caught.

Can I build this myself, or should you build it?

Every split, signal, and suppression is spelled out above, so if you're comfortable in Klaviyo and your review platform, an afternoon gets it live. If you'd rather not own the open-tracking gotchas and the return re-checks, we'll build it on the Klaviyo and Shopify accounts you already pay for, document it, and hand you the keys — you own the flow outright, no monthly retainer. It starts with a free 20-minute teardown, not a contract, and you keep the plan either way.

Reviews & UGC

Reward customers with a discount code for reviews

Asking for a review is asking a customer for free work. A small reward for the people who actually do it lifts your response rate without bribing anyone for a five-star. Here's how to mint a unique, single-use discount code the moment a verified customer leaves a review, deliver it through the email you already send, and do it without the legal and abuse traps that come with paying for reviews.

  • Klaviyo
  • Shopify

Intermediate3-5 hrs

Reviews & UGC

Flag negative reviews for follow-up

A one-star review is a customer telling you something's wrong in the most public place they have. This watches every review as it's submitted, catches the low ones, and drops them in a Slack channel with the rating, the product, what they wrote, and who they are — so someone reaches out while it still matters instead of finding it a week later in the app's dashboard. Build it yourself with the steps below, or we build it, wire the routing, and hand you the keys so you own it with no monthly fee. Free teardown of your current review setup first.

  • Slack
  • Klaviyo

Intermediate1-3 hrs

Reviews & UGC

Collect photo and video UGC in Airtable

Your best content is already being made — customers shoot it and drop it in photo reviews, email replies, and DMs, where it dies. This pulls every photo and video into one Airtable library the moment it lands: the file attached, who sent it, which product, which source, and — the part most teams skip — whether you actually have the right to run it in an ad. Build it yourself with the steps below, or we build it on the accounts you already pay for and hand you the keys, so you own the whole thing with no monthly fee. Free teardown of where your UGC is currently leaking first.

  • Airtable
  • Klaviyo
  • n8n

Intermediate4-6 hrs