Skip to content
Pixeltree

Field notes

Reviews and UGC Email Flow: A Photo-Prompt Sequence That Works

October 24, 2025

Reviews and UGC Email Flow: A Photo-Prompt Sequence That Works

Review request emails are the most ignored flow in DTC retention

Walk into any Klaviyo account and the welcome series has been iterated seven times while the review request flow is the platform default. This is a pattern. Most brands underinvest in the review ask because the immediate revenue impact is low. But reviews drive the social proof that every product page leans on, and photo UGC feeds ads, emails, and the site itself. The long-run compounding is significant.

This guide covers the flow structure we build for DTC brands that want both quantity (review count) and quality (photo content usable across channels).

TL;DR ▸ Time the send to actual use, not delivery. Product category dictates the delay. ▸ Two-email sequence with a photo-prompt variant on the second. ▸ Route low-star reviews to CX before they post publicly, where platform allows. ▸ Measure response rate and photo submission rate separately. Optimize for both.

Step 1: Set the send timing by category

Generic "24 hours after delivery" review requests produce the lowest quality reviews because the customer has not actually used the product yet. They write a review about the unboxing, the shipping speed, or the packaging, which is not what the product page needs.

Better timing by category:

CategorySend after deliveryReason
Apparel7-10 daysEnough wears to have an opinion
Skincare14-21 daysFormulation takes time to show results
Supplements21-30 daysPhysiological effects need a cycle
Consumable food or drink7-14 daysUsed in normal rotation
Home and decor10-14 daysIn place, seen daily
Considered goods (electronics, furniture)30-45 daysReal usage patterns emerge

Pull the send delay from shipping-tracking data so the clock starts on actual delivery, not order date. A customer who waited three weeks for delivery should not get the review request based on order date.

Step 2: The two-email sequence

Email 1: The initial ask (sent at category-appropriate delay)

Subject line: direct and product-specific. "How's the [product name]?" outperforms generic "Share your thoughts".

Body: short, no-friction. Thank the customer, ask a specific question (not just "leave a review"), link to the review submission screen. Include star rating selector inline so the customer can click a rating from the email itself if the platform supports it.

CTA: "Rate and review [product]".

Email 2: The photo prompt reminder (sent 7-10 days after email 1, only to non-responders)

Subject line: "Got a photo?". Photo-specific subject lines double the photo submission rate vs generic reminders in our testing.

Body: acknowledge that written reviews are great but photos help the most. Remind the customer of the incentive if one exists. Make the photo upload obvious.

CTA: "Add your photo" or "Leave a photo review".

Step 3: The incentive structure

A small reward encourages participation without distorting the content.

Text-only review: entry into a monthly drawing, OR a small points award if a loyalty program exists. ▸ Photo review: slightly larger points award, OR a higher drawing entry count. ▸ Video review: the largest of the three rewards, for brands where video matters.

Avoid flat discount offers for reviews. "Get 15% off for a review" produces filler reviews and trains customers to expect a discount for feedback. The signal it sends about the brand is also wrong.

Step 4: Handle low ratings correctly

Most modern review platforms (Junip, Okendo, Yotpo, Loox) support low-star intercepts, where a 1 or 2 star rating routes the customer to a support form instead of a public submission. This is not hiding bad reviews. It is fixing issues before they become public complaints.

When a customer submits a low rating, the flow should:

▸ Route the submission to CX with high priority. ▸ Send a same-day response offering to make the issue right. ▸ If the issue is resolved, ask the customer if they would like to update their review. ▸ Record the pattern so repeat low ratings on a SKU trigger a product review.

Our customer experience service builds these intercept flows as standard. The single biggest driver of review quality is fast CX response on the low ratings.

The PROMPT framework

Every review request email should pass PROMPT:

Product specific: the email references the exact product purchased, not a generic brand message. ▸ Ready to use: timing aligns with when the customer has actually used the product. ▸ One click to submit: rating and photo upload work without jumping through hoops. ▸ Meaningful ask: the email asks a specific question, not a generic "rate us". ▸ Photo path clear: for email 2, photo submission is the primary CTA, not a secondary afterthought. ▸ Thank you on submit: a confirmation email closes the loop.

Step 5: Multi-product orders

A customer who buys three items should get a review request for each, not one email asking for three reviews at once. Multi-product review asks in a single email produce lower response rates and lower photo rates.

The solution: stagger the sends. Request the primary or highest-priced item first. Request the second item 5 days later. Third item 10 days later. Each request is clean and specific.

If the order was all one category, you can batch into a single email with a grid of products, each with its own inline CTA. But three separate CTAs for three products outperforms one CTA asking for three reviews.

Step 6: Photo usage rights

If the goal includes using photos in ads, emails, or on the website, the submission flow needs to capture rights at the moment of upload. A checkbox with clear language works:

"I grant [Brand Name] permission to use this photo on our website, in emails, and in advertising. I confirm this is my photo."

Without this, legal exposure on photo usage is real. With it, the UGC library is a usable asset. Our email marketing service includes this configuration as part of reviews and UGC setup.

Measurement

The metrics that matter:

MetricTargetNote
Review submission rate8-15% of delivered ordersBaseline varies by category
Photo submission share20-35% of reviewsDrives the UGC library
Average ratingabove 4.3Below signals product or fit issues
Time from delivery to reviewvaries by categoryShould match the send-delay design
CX intercept rate3-7% of ratingsBelow 3% usually means intercept is not working

Run a holdout on the review flow for 60 days to measure incremental review volume. Some reviews come in organically, and the flow only captures the ones it moves forward.

Integrating reviews into the broader retention program

Reviews do not stand alone. They feed:

Product pages: the conversion engine. ▸ Email creative: UGC in welcome series, cart recovery, and abandoned browse flows. ▸ Ads: authentic customer photos outperform studio shots in most social ad formats. ▸ VIP recognition: high-volume reviewers are often VIP candidates.

For how reviews feed the cart flow, see Klaviyo abandoned cart sequence. For how UGC integrates into the post-purchase sequence, see klaviyo post-purchase email and post-purchase experience for repeat buyers.

The follow-up loop

Once a review is submitted, the flow should not end. Three follow-up touches that work:

Same day: confirmation email, thank the customer, note the points or entry. ▸ 14 days later: if the review was photo, ask if the customer wants to be featured in social content. ▸ 90 days later: invite the reviewer to a brand community, ambassador program, or early-access list.

Reviewers who engage with the follow-up loop tend to become repeat reviewers and, often, higher LTV customers. This is the seed of referral programs and ambassador structures.

Common failure modes

Generic send timing. A category that needs 21 days of use gets a request at 2 days and produces surface-level reviews.

Multi-product requests stuffed into one email. Lower response rate than staggered sends.

No photo incentive differentiation. Text and photo reviews treated as equivalent. Photo submission rate stays low.

No CX intercept on low ratings. Public low-star reviews that could have been resolved publish as product page decoration.

No rights capture on photo upload. UGC library cannot be used in paid channels without retroactive permission chase.

What to do this week

▸ Audit current review flow timing. If everything sends 24 hours after delivery, rebuild by category. ▸ Split the flow into two emails: initial ask and photo prompt. ▸ Add photo rights capture to the submission form. ▸ Configure CX intercept on 1 and 2 star ratings. ▸ Separate the incentive tier for text vs photo reviews. ▸ Instrument submission rate, photo share, and CX intercept as monthly metrics. ▸ Review ecommerce customer lifetime value to understand how review activity correlates with higher retention cohorts.

One-page resource

Get the Vendor Recovery Checklist.

The 12 steps every displaced maker should take in the next 30 days. Delivered in your inbox.

No spam. Unsubscribe any time.

Ready to put this into motion?

Book a 15-min call