Klaviyo Review Request Flow: Why Your Reviews Dried Up

You used to get reviews without thinking about it. Star ratings stacking up on the product page, the odd photo you could screenshot for the grid, a steady drip of proof doing the selling for you.

Then one day you looked up and realised nothing had come in for months.

Nothing broke loudly. There was no error message, no alert, no red flag in the dashboard. Your Klaviyo review request flow, the automated email that asks a customer to rate what they bought, just quietly stopped doing its job while you were busy running the business.

This is the most commonly abandoned automation in ecommerce. Most brands set it up in their first month on Klaviyo, the email and SMS platform built for ecommerce, and then never open it again.

Quick answer

Reviews usually dry up because the review request flow was built once and never touched again. The trigger quietly breaks, the timing no longer matches how long your product takes to arrive and get used, and the ask is buried in a busy template. Fix the trigger, retime the send to real usage, and add a small incentive tied to effort.

Why did my product reviews suddenly stop coming in?

I had this exact conversation on a client call recently. Reviews had fallen off a cliff early in our working relationship, and nobody could point to a single thing that had changed. No site migration, no app swap, no obvious culprit. They just stopped.

That is the part founders find maddening, and it is also the clue. When a flow stops working, nothing tells you.

An email that never sends does not report anything. There is no bad number to spot, because there is no number at all.

In practice it is almost always one of these five.

• The integration went quiet. Your reviews app pushes an event into Klaviyo. If that connection drops, gets reauthorised, or the app changes its event name in an update, the flow sits there waiting for a trigger that no longer arrives.
• The trigger is on the wrong event. Most review flows fire off “order placed” because that is the easiest metric to grab. It is also the one that has almost nothing to do with whether the customer has the product in their hands.
• A filter is silently blocking people. A flow filter added for a good reason two years ago (exclude wholesale, exclude a discontinued line, exclude anyone who bought a sample) can end up excluding most of your customers once the range changes.
• Someone paused it. Usually during a sale or a stock issue, with every intention of switching it back on.
• It fell off the list. This is the honest one. It gets raised in a meeting, everyone agrees it matters, and then something more urgent shows up. On the call I mentioned, the rebuild had been flagged, agreed on, and then lost twice in a row. Not because anyone stopped caring, but because reviews never scream the way a broken checkout does.

The same silent-failure problem hits other automations too. I have written about it in detail in why abandoned cart emails stop converting when the trigger is wrong, and the diagnosis process is nearly identical.

What is a review request flow actually meant to do?

Most people think of it as a way to get stars on a product page. That is one job out of three.

Job one is written proof. Ratings and text on the product page, which lifts conversion for every visitor who lands there afterwards, including the ones who came from paid ads you already spent money on.

Job two is content. Photo and video reviews are the cheapest user generated content you will ever get. A customer showing your product in their kitchen or on their skin does more for your ads and your grid than another studio shot. Brands that lose their review flow usually notice this loss first, because the social content pipeline dries up before the star count looks obviously wrong.

Job three is catching problems. A private reply from an unhappy customer is worth ten public ones. A well-built flow gives people somewhere to tell you before they tell everyone.

The review request belongs in the same tier as the automations everyone actually maintains. If you have not audited yours against the full set, start with the 6 core Klaviyo flows every ecommerce store needs, then treat the review flow as the one that sits directly after the post-purchase sequence.

When should a review request email actually send?

This is where nearly every brand gets it wrong, and it is the single highest-leverage fix in the whole build.

The standard setup sends seven days after the order is placed. Think about what that actually means. Two of those days are processing. Three are in transit. The parcel arrives on day five, sits on the bench, and gets opened on the weekend. Then on day seven you send an email asking what they thought of it.

Ask before someone has used the product and you get a review of your packaging.

Here is the timing formula I use instead.

Fulfilment or delivery date, plus the time it genuinely takes to form an opinion.

Anchor the flow to the fulfilled or delivered event rather than the order event. Then add a delay that matches your category, not a generic seven days.

• Homewares, candles, jewellery, accessories: 7 to 10 days after delivery. They know how they feel almost immediately.
• Apparel: 10 to 14 days after delivery. They need to wear it and wash it once.
• Food, drinks and consumables: 14 to 21 days. Long enough to have used it a few times, short enough that it is still front of mind.
• Skincare, supplements and anything with a claimed result: 4 to 6 weeks. Asking a supplements customer for a review at day seven is asking them to review a bottle.
• Subscription and replenishment products: time it to land before the second charge, so a happy review and a renewal reinforce each other.

Then test it properly. Place a real order, walk through the flow yourself, and check the email lands when you expect it to. Delays behave in ways you do not always predict once conditional splits and time windows are involved, and I have seen flows send weeks early for a slice of customers with nobody noticing until someone complained.

One more timing rule. If you have a long-use product and a short-use product in the same store, do not run them through one flow with one delay. Split them, or you will keep asking half your customers too early and the other half too late.

How many emails should be in the flow?

Three. One is not enough, five is nagging.

1. Email one, the plain ask. Written like it came from you, not from a template. One link, straight to the review form with the product already selected. Every extra click you make them take costs you reviews.
2. Email two, four to five days later. Different angle, not a copy of the first. Ask one specific question instead of a blank star rating (“Did it do what you hoped?” beats “Rate your purchase”). Specific prompts get you reviews with actual detail in them, which is what future buyers read.
3. Email three, the upgrade ask. This is where the incentive lives, and where you ask for a photo or a video rather than text.

Add a flow filter so anyone who has already left a review exits immediately. Nothing damages trust like being chased for feedback you already gave.

Keep the design light. A simple, mostly-text email from the founder outperforms a heavily designed one here, because the request reads like a person asking a favour rather than a brand running a campaign.

Not sure whether your review flow is even sending? A Mini Klaviyo Audit is $69 and gets you a 15-minute personalised video walking through what is live, what is broken, and what is quietly costing you revenue.

Are review incentives worth it, or are you just buying fake praise?

They work, and no, you are not buying praise, as long as you structure them around effort instead of sentiment.

The ladder I recommend looks like this.

• Written review: a small store credit, roughly the value of a shipping cost.
• Photo review: two to three times that.
• Video review: five times that, or more.

Price it against what the content is worth to you, not against what feels generous. A usable customer video costs a fraction of what you would pay a creator for the same thing, and it converts better because it is real.

Use a fixed dollar credit, not a percentage off. This is a small change with a real effect. “$10 off your next order” is concrete and brings them back to the site. “10% off” is vague, rewards big spenders more than loyal small ones, and reads like the discount code they already ignore in their inbox.

Now the honest part, because this is where brands get themselves in trouble.

• Pay for the effort, never the rating. The credit is for taking the photo and writing the words. It is not for saying something nice. Never write “leave us a 5 star review” in the email.
• Say so in the email. A single line does it: “The credit is yours either way, whatever you write.”
• Disclose it. Most review platforms have an incentivised-review flag. Turn it on. Undisclosed paid testimonials are a consumer law problem in Australia, and shoppers can smell a page of suspiciously glowing reviews anyway.
• Never gate the ask. Sending happy customers to the public review form and routing unhappy ones to a private survey is called review gating. Platforms penalise it, and it makes your average rating meaningless.
• Set a quality bar, not a sentiment bar. The photo has to show the product. The video has to be more than five seconds. That is a fair condition. “It has to be positive” is not.

A page of four and five star reviews with one honest three star in the middle sells better than a page of perfect scores. The three star one is what makes the rest believable.

How do you rebuild a Klaviyo review request flow that has gone quiet?

Work through it in this order. It takes an afternoon.

1. Check it is live and check the send volume for the last 30 days. If the number is zero or close to it, you have found your problem and it is upstream of the copy.
2. Check the trigger and the integration. Confirm the event is still firing into Klaviyo and that the event name has not changed.
3. Re-anchor the timing to fulfilment or delivery, then add the usage window for your category.
4. Rewrite all three emails. One link each, one clear ask, written like a person.
5. Add the incentive ladder to email three, with the disclosure line.
6. Add the exit condition so reviewers stop receiving it.
7. Place a test order and walk through the whole thing yourself. Not a preview. A real order.
8. Put a recurring reminder in your calendar to check the flow’s send volume once a month. Thirty seconds. This is the step that stops it happening again.

That last point matters more than any of the copy. Reviews stop coming in because nobody owns checking. Give the job to someone, even if that someone is a monthly reminder on your phone.

The same rule applies to the rest of your post-purchase automation. Most of it is set-and-forget by design, which is exactly why it needs a scheduled look. There is more on this in the Klaviyo retention flows most product brands forget.

Key takeaways

• Review flows fail silently. There is no bad metric to spot, because an email that never sends produces no data at all.
• The most common cause is the wrong trigger. Anchor to fulfilment or delivery, not to the order.
• Timing should match how long your product takes to use, which is 7 days for homewares and 4 to 6 weeks for skincare or supplements.
• Three emails is the right length, with an exit condition for anyone who has already reviewed.
• Incentives work when they reward effort, not a rating. Pay more for photo and video, use a fixed dollar credit, and disclose it.
• Put a monthly check in your calendar. That single habit is what keeps the flow alive.