Most review-request automations are built on the order date because delivery webhooks feel like extra plumbing, but that sends the email while the package is still in transit half the time. This prompt makes the delivery-confirmed dependency explicit so you catch that mismatch before launch.
Automation
Request a product review a few days after delivery
A scenario prompt that converts a described post-delivery review-request workflow into a recipe, resolving delivery-confirmation and multi-item-order ambiguity.
Works with Claude / GPT460 uses★ 4.1
The prompt
automation-review-request-after-delivery
A store owner describes their process like this: "Three days after an order is delivered, I want an email sent asking the customer to leave a review, with a direct link to the product review form, but I don't want to ask again if they already left one." AVAILABLE TOOLS: [WooCommerce + ShipStation delivery webhook (trigger), Uncanny Automator, email/SMTP, WooCommerce product reviews] Turn this into an implementation-ready automation recipe, thinking through what the plain description leaves ambiguous: 1. Trigger: "three days after delivery" needs an actual delivery-confirmed timestamp from the carrier webhook, not the order date, since ship times vary. Decide what happens if the carrier never sends a delivery-confirmed event at all, which carriers sometimes fail to do. 2. Conditions: for an order with five different products, decide whether one review request email covers all five items with individual review links, or five separate emails, and justify the choice against likely open and unsubscribe rates. 3. Actions in order: check for an existing review from that customer on that product before sending (to satisfy the "don't ask again" rule), then send the templated email with the review link, then log the send so a manual resend doesn't double-email the customer. 4. Failure handling: if the delivery webhook never fires for an order (lost in transit, or the carrier integration drops the event), should there be a fallback timer based on estimated delivery date plus a buffer, so the request still goes out eventually. 5. One edge case specific to this exact workflow: an order that was partially refunded or returned before the three-day window closes. Decide whether the review request should still go out for the item that was kept. Replace the workflow description and available tools with your own.