WooCommerce

Write a WooCommerce post-purchase review-request email sequence

A scenario prompt for timing review requests to actual product usage rather than delivery date, and routing recent returns or complaints away from the request instead of risking a public bad review.

Works with Claude / GPT1,150 uses 4.5

The prompt

woocommerce-review-request-email-sequence
Write a post-purchase review-request sequence for a WooCommerce home goods store:

PRODUCT CATEGORY: [cast iron cookware], typical time before a customer has really used
it enough to review it: [10-14 days after delivery, not immediately]
INCENTIVE POLICY: [a $5 store credit for leaving any review, positive or negative,
never an incentive tied to a positive rating specifically]
EXCLUDE: [any order with an open support ticket or a return/refund filed in the last 30
days]

Write the sequence:

1. Email 1, sent 12 days after delivery, not immediately at delivery, since a review
   requested the day a cast iron pan arrives is a review of the unboxing, not the
   product, and asking too early produces shallow reviews that don't help future buyers
   decide.
2. Frame the ask around a specific, useful question ("how's the seasoning holding up
   after a few uses" or "any trouble with sticking") rather than a generic "how did we
   do," since a specific prompt produces a more useful review for future shoppers and
   also feels less like a form email.
3. State the incentive clearly and note explicitly that it applies regardless of star
   rating, since an incentive that's only paid out for 5-star reviews is both against
   most marketplace and ad platform policies and produces reviews that read as fake to
   other shoppers, undermining the exact trust signal a review section is supposed to
   provide.
4. Email 2, a single follow-up at day 21 for non-responders only, with no further
   escalation after that, since more than two review requests starts to read as
   pressure rather than a reminder.

Judgment call already applied: this segment excludes anyone with an open support ticket
or a recent return, since inviting someone who just went through a bad experience to
publicly review the product either produces a review that damages trust unfairly (if
their specific issue was already resolved) or, worse, invites a negative review from
someone who should be getting personal customer service attention first, not a review
request.

Replace the bracketed product category, timing, and incentive with your own.

Delaying the request until the product has actually been used, and excluding anyone with an open ticket, are the two changes that separate a review sequence that produces genuinely useful reviews from one that just produces volume.