Post-purchase review request email

Use when you need more reviews and want an ask that is timed to when the customer actually has an opinion.

post-purchase-review-request.md

Download .md

You are a retention email copywriter. Write a two-email review request flow.

Product or service: {{PRODUCT}}
Time until a customer can fairly judge it: {{TIME_TO_VALUE}}
Where the review should be left: {{REVIEW_PLATFORM}}
What I do with negative feedback: {{NEGATIVE_FEEDBACK_ROUTE}}

Output: Email | Send delay after purchase or delivery | Subject | Preheader | Body under 120 words | Call to action | Fallback path for an unhappy customer

Requirements:
- Time the first ask to the time to value above, not to the order date.
- Make the ask small and specific. Say roughly how long it takes and what to write about.
- Give an unhappy customer an obvious route to reply or contact support before any public review link, without hiding or gating the review link.
- No incentive that would breach review platform rules. If an incentive is mentioned, note the rule risk.
- No em dashes, no flattery openers, no closing summary paragraph.

Then give three subject line options for email 1 and say which reads least like an automated request.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{PRODUCT}}
{{TIME_TO_VALUE}}
{{REVIEW_PLATFORM}}
{{NEGATIVE_FEEDBACK_ROUTE}}

Getting a better result

Ask after the customer has used the thing, not after the parcel is scanned as delivered.
Naming what to write about lifts response rates. A blank "leave a review" ask gets ignored.
Route unhappy customers to a human, but never make the review link conditional on being happy - most platforms ban that.

Questions about this prompt

Why two emails rather than one review request after delivery?

Because there is usually a gap between delivery and the customer having an opinion, which is what the time to value field captures. Ask on the delivery scan and you get reviews of the packaging. Two sends also give you a second chance without the first one having to arrive early.

What do I need decided before running it?

An honest time to value, the platform the review should land on, and a settled route for negative feedback. That last one is not optional. Without it the model has nowhere to send an unhappy customer, and the flow either gates the review link or ignores the problem entirely.

What does the two-email flow return?

Two emails under 120 words each with send delay, subject, preheader, body, call to action and a fallback path for an unhappy customer, then three subject options for email 1 and which reads least like an automated request. The fallback column is the one to check line by line.

What gets a review programme in trouble?

Making the review link conditional on the customer saying they are happy. Most platforms ban that gating outright and the prompt will not build it, though routing unhappy customers to a human alongside the link is fine. Incentives are the other risk, since platform rules on them differ.