Verified against ChatGPT · 2026-08-11
Write a post-purchase email that gets a new buyer to first successful use, not just a thank-you
Produces a post-purchase onboarding email focused on getting the buyer to a working first experience with the product, aimed at cutting the return rate that comes from people never actually using what they bought.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Write one post-purchase email whose actual job is getting the buyer to a successful first use of the product they just bought — not a generic thank-you, and not a review request, since a buyer who hasn't used the product yet has nothing honest to review. PRODUCT A cold-brew coffee maker with a removable steel mesh filter. COMMON FIRST-USE MISTAKE Using a fine drip-grind coffee instead of a coarse grind, which clogs the mesh filter and makes the brew taste bitter and muddy. WHAT 'SUCCESSFUL FIRST USE' LOOKS LIKE A smooth, non-bitter cold brew concentrate ready in 12-18 hours, filter easy to rinse clean afterward. SEND TIMING The morning after the delivery confirmation, assuming a 1-day unboxing lag. SUPPORT CHANNEL A reply-to email routed to the actual support inbox, monitored same-day. RULES Open by naming the specific first-use moment, not the purchase itself — the buyer already knows they bought it; thanking them for buying is wasted words in the first line. Include one clear instruction or tip that directly prevents the common first-use mistake given — state it as a positive action to take, not just a warning about what goes wrong. Define success in the buyer's terms (what they should notice or be able to do) rather than in the brand's terms (what the product's spec sheet claims). Include exactly one path to help if something isn't working, pointing to the actual support channel given — do not list multiple contact options, which dilutes which one to actually use. Do not ask for a review, a photo, or a referral anywhere in this email — those requests belong in a later email once success is confirmed, and asking before that point gets reviews from people who haven't really used the thing yet. WHAT NOT TO DO Do not open with "Thank you for your order" or "Your package is on its way" — both are already covered by the shipping confirmation email and repeating them here wastes the one email actually meant to drive usage. Do not pad the email with unrelated product recommendations. OUTPUT FORMAT Subject line, then the full email body, under 150 words — this email should be short enough to read on a phone in the time it takes to unbox the product.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Explicitly banning the review or referral ask forces a separation that GPT-5.1 doesn't make on its own: asked generically for a 'post-purchase email,' it defaults to a template that thanks the buyer, nudges a review, and suggests related products all in one message, because that's the most common shape of post-purchase email in its training distribution, and that shape treats the purchase itself as the success event rather than actual product use — for anything with a real first-use learning curve, that conflation is the direct cause of both bad early reviews (written before the buyer figured out the coarse-grind requirement) and unnecessary returns (from buyers who never got a good result and assumed the product was defective rather than misused). Requiring the common mistake to be addressed as a positive instruction rather than a warning matters mechanically: warnings phrased as 'don't do X' get skimmed and ignored at a higher rate in transactional email, whereas 'use a coarse grind, roughly the texture of raw sugar' gives the buyer something concrete to act on during the moment they're actually unboxing and about to make the mistake. Restricting the email to a single support channel, rather than the multi-channel list a model defaults to when asked to be 'helpful,' removes the decision-paralysis cost of a confused new buyer having to guess which of three listed channels actually gets a fast response — a single clear path converts a would-be return into a resolved support ticket instead.
What you get back
Subject: "Before your first cold brew: one grind size makes all the difference" — body opens on the grind tip, states what a good 12-18 hour result should taste and look like, and closes with a single reply-to line for help, no review ask.
Verified against
ChatGPT GPT-5.1 · 2026-08-11
Changelog
- 2026-08-11 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
