The review request email no one opens.

Open a Klaviyo dashboard and the open-rate benchmark for post-purchase transactional flows sits at 40 to 45 percent across the consumer-goods cohort. Klaviyo publishes these numbers in their quarterly benchmark report; the 2025 Q4 edition put apparel post-purchase at 43.2 percent, beauty at 44.8 percent, food and beverage at 41.1 percent. The review-request email is technically a post-purchase email. It rides the same brand-buyer relationship and benefits from the same transactional context.

Pull the open rate on the review-request email specifically, separate from the broader post-purchase flow, and the numbers fall apart. Beauty review-request flows commonly run at 23 to 30 percent open rate. Apparel review-request flows run at 25 to 32. Food and beverage runs lower, in the high teens. The drop is 15 to 25 percentage points against the cohort average for post-purchase email of any other type.

The drop is consistent enough across categories and platforms that it is not a quality problem at any one brand. It is a category-level failure mode. The review-request email, as it exists in the default templates of every major platform, is the most templated, lowest-craft customer touchpoint in DTC commerce. The buyer sees the subject line and skips it. The brand sends the email and reports the bounce. The flow stays on, year over year, producing a corpus thinner than the buyer base would otherwise yield.

A typical review-request email arrives 14 days after delivery from `noreply@brand.com` or `hello@brand.com`. The from-name reads "Brand Name." The subject line is one of about six templated variants:

"How did we do?" "Leave a review." "Share your thoughts." "We'd love your feedback." "Tell us what you think." "Rate your recent purchase."

These six subject lines account for roughly 70 percent of review-request emails we have read across a corpus of 240 brands sampled in Q1 2026. None of them references the product. None of them references the buyer. None of them offers the buyer a reason to open beyond the implicit ask. Every one of them reads as a request for the buyer's time on the brand's behalf.

The post-purchase email that runs at 44 percent reads differently. A shipping-confirmation subject line is specific ("Your order is on the way") and informational. An upsell email is specific ("The matching shorts to the t-shirt you bought"). The buyer has a reason to open. The review-request email has no reason. It is, in inbox-economy terms, a deposit on the brand's side of the relationship with no withdrawal from the buyer's side.

Every review platform ships a default request flow with a default email template. The defaults are written by product marketers at the platform, not by content writers at the brand. The templates are designed to be neutral enough to ship across the category without modification, because the brand that has to write its own email is the brand that does not run the flow.

The neutral subject line is the safest possible business decision for the platform. It cannot offend. It cannot be off-brand for any specific merchant. It can also not be remembered or opened. The platform optimises for ship rate. The brand inherits the open rate.

Klaviyo, Yotpo, Okendo, Junip, Stamped, Loox, and Reviews.io all ship near-identical default templates. The convergence is not coordination. It is convergence on the lowest-risk artifact each platform can hand the merchant. The merchant does not write the email; the merchant accepts the template. The corpus thins accordingly. This is the dashboard-shaped version of email: the platform displays an open-rate widget and a click-through widget and a flow-builder widget. The actual writing of the email is offstage. The platform has no view of it because the platform did not write it.

We have read enough A/B variants to be relatively sure about four properties of an email that runs at 35 to 45 percent open rate on the review request specifically. Each property has a default behavior that suppresses opens, and a craft alternative that lifts them.

Specificity in the subject line. The default subject "How did we do?" references nothing the buyer cares about. The craft alternative references the product the buyer ordered, by name. "The cardigan you ordered in March." "How is the moisturiser working out?" "Your boots, two weeks in." The buyer reading their inbox at 9pm on a Wednesday recognises the product before they recognise the brand. The subject line is doing the work the from-name cannot.

A from-name that is a person. The default from-name is the brand. The craft alternative is a human at the brand. "Sara at Brand." "Anders from Brand." The from-name change alone lifts open rate 8 to 12 percent in nearly every A/B test we have seen, with no other variable touched. The inbox is a personal medium. A brand name reads as marketing. A human name reads as correspondence. Glossier's early-era founder-team emails ran this format. Pattern's growing roster of small DTC brands uses it. The platform default does not, because the platform does not know which human at the brand should sign.

A body that references the order. The default body is templated. "Hi {{ first_name }}, thanks for shopping with us! We'd love to hear your thoughts on your recent purchase." The craft alternative names the specific items, the date, and the use case if known. "Hi Lena. You ordered the merino crewneck and the wool socks on March 14. The crewneck has been our most-asked-about piece this season. We are curious how you're getting on with it." The body is doing the work of demonstrating that the brand knows who the buyer is. The buyer reads the first sentence and the body reads as a continuation of the order experience, not a pivot to a new ask.

A form that does not punish length. The default form has one text box and a five-star slider. The craft alternative has two to three short prompts. "What were you trying to fix?" "How is it going so far?" "What would you change about the product itself?" Each prompt is a sentence. Each field is a textarea. The form takes longer to complete; the buyer who completes it produces a paragraph worth quoting rather than a star rating with three words of caption.

Four properties. Each property is a content decision the operator makes, not a platform feature the operator buys. The platform exposes the surfaces. The operator writes the email.

A real before-and-after, from a Pacific Northwest knitwear brand in early 2026. The brand was running the default Klaviyo template with no modifications. Open rate on the review request was 26.4 percent over a six-month baseline. Click-through was 7.1 percent. Review-completion rate from click-through was 41 percent. Net: of every 1,000 buyers who hit the flow, 264 opened, 19 clicked, 8 wrote a review. The corpus added eight paragraphs per 1,000 buyers.

The operator did not change the platform. The operator changed the email. Three changes:

The from-name changed from "Brand Name" to "Maya at Brand Name." Maya was a real person in customer service. The from-name was authentic; emails replying to the request hit Maya's inbox.

The subject line changed from "How did we do?" to a templated reference to the product, populated dynamically: "The {{ primary_item }} you ordered in {{ order_month }}." For Lena, who bought the merino crewneck in March, the subject line read "The merino crewneck you ordered in March."

The body changed from the generic templated paragraph to a three-sentence email from Maya. "Hi Lena. You ordered the merino crewneck and the wool socks on March 14. The crewneck has been our most-asked-about piece this season, and we're curious whether the fit through the shoulder is working for you." The CTA dropped from "Leave a review" to "Tell us how it's going."

Open rate on the next 1,000 sends: 41.8 percent. Click-through: 14.2 percent. Review-completion rate from click-through: 38 percent (slightly lower because more marginal buyers were clicking through). Net: 418 opened, 142 clicked, 54 wrote a review. The corpus added 54 paragraphs per 1,000 buyers, against a baseline of 8. A 6.75x improvement, on no software change, on three edits to the email.

The math is not a one-off. We have watched the same pattern repeat across about a dozen brands that swapped the default template for a written email. The lift is rarely smaller than 4x. The lift is sometimes 8x. The platform was never the bottleneck; the writing was.

A review written in response to the default email reads, on average, 22 to 38 words. A review written in response to the craft email reads 110 to 220 words. The length difference is not random. The buyer who received a personal email writes a personal reply. The buyer who received a templated request gives a templated answer.

The buyer answers the shape of the question they were asked.

The longer review is the citable review. The 22-word review averages one or zero quotable sentences. The 180-word review averages three or four. The first-person-dated-signed sentence the answer engine reaches for is statistically more likely to exist inside the longer review. The corpus that ranks for citation queries is the corpus assembled from longer reviews. The longer reviews come from better-written request emails.

The platform can ship the open-rate dashboard and the click-through dashboard. The platform cannot ship the email that produces the cited paragraph. That email is written by the brand, in the brand's voice, to a buyer the brand knows by name. It is, in this small specific way, the kind of correspondence the hardware store conducted in 1968 without thinking of it as marketing.

Five edits to the flow that take a Tuesday afternoon and lift the corpus contribution per buyer by a factor of three to six.

Change the from-name to a real human at the brand. Pick someone who can plausibly handle the replies. The replies are themselves a corpus and a research artifact; they tell the brand what buyers want to write about that they cannot fit into the review form. This requires software that remembers who that human is, what the buyer ordered, and where the reply should land. Most platforms do this poorly; the operator usually has to manually forward.

Change the subject line to reference the specific product the buyer ordered. Dynamic insertion through the platform's merge tags. The subject line is the single highest-impact edit in the flow. Subject line specificity, over six months of A/B testing in our hands, accounts for 60 to 70 percent of the open-rate lift.

Change the body to reference the order, the date, and the use case if any of these are stored in the customer record. Three sentences. Conversational. No CTA button at the top; the CTA can be a text link at the bottom.

Change the form to ask two or three specific questions rather than presenting a single textarea. The prompts are the brief; the brief is what makes the buyer write a paragraph rather than a sentence.

Change the timing per category. The 14-day default is wrong for skincare, electronics, apparel, supplements, and food. The right window is a per-category decision. We argued this at length in a separate piece.

Total operator time: four hours, including writing the new email copy. Total platform changes: zero. The flow stays on the same platform with the same dashboards. The buyer receives a different email and writes a different review. The corpus, six months later, looks different.

Every review platform ships an open-rate widget on its dashboard. Every brand reads the widget. Most brands accept the number on the widget as the open rate the email can achieve. The widget reports on an email written by the platform, sent through the brand, in a voice that belongs to neither. The number is the floor, not the ceiling.

The brand that writes its own email, in a real human voice, to a buyer it knows by name, produces a different number. The number is invariably better. The corpus is invariably richer. The work is invariably writing rather than configuring. The most templated touchpoint in DTC commerce is also the most rewarding to write by hand. The platform's default exists so the email can ship without being written. The brand's job is to write it anyway.