Ready-to-use prompt
The prompt
Copy it as-is, then swap the bracketed placeholders for your own details before running it.
Role: You are a lifecycle marketer writing an abandoned cart flow.
Context:
- Store and what it sells: {{store}}
- Typical cart value: {{cart_value}}
- Products most often abandoned: {{products}}
- Known friction points at checkout: {{friction}}
- Shipping, returns and guarantee terms: {{policies}}
- Discount policy: {{discount_policy}}
- Brand voice: {{brand_voice}}
- Channels available: {{channels}}
Task: Write a three-message sequence. For each message give:
1. Send timing after abandonment, with the reason for that delay
2. Channel
3. Abandonment reason it targets (distraction, price hesitation, trust, shipping cost, comparison shopping)
4. Three subject line variants with the angle of each
5. Preview text
6. Body copy in the brand voice, under 120 words
7. A single call to action
8. What to do if the shopper does not convert after this message
Rules:
- Message one must never include a discount.
- Only introduce a discount if the discount policy allows it, and say what it costs in margin terms.
- Address a different reason in each message, do not resend the same appeal.
- Never use fake scarcity or a countdown that is not real.
Finish with: the suppression rules, so repeat buyers and recent purchasers do not receive the flow.Estimated results
Editor's note
Why this prompt matters
A shopper who leaves because delivery costs appeared late needs a different answer from someone who simply closed a browser tab. Yet cart recovery often repeats one reminder, changes the subject line, and eventually adds an incentive. This prompt helps you plan three distinct interventions rather than three versions of the same sales pitch.
Before running it, collect your actual checkout friction, shipping terms, returns policy, available channels, and discount limits. Put evidence into {{friction}}: support questions, checkout feedback, or observed drop-off points. Label suspected causes as hypotheses; abandonment alone does not reveal a shopper’s motive.
The result is a draft for your lifecycle platform, not an automated diagnosis or a launch-ready campaign. Review the copy against your policies, connect each CTA to the correct cart, and implement the suppression logic. The useful decision is not just what to say next, but whether another message—or any incentive—is appropriate.
Anatomy
Prompt engineering breakdown
Role
Lifecycle marketer, not coupon generator.
Context
Store facts anchor objection handling.
Goal
Three messages, three distinct reasons.
Constraints
Protect margin and factual accuracy.
Output format
Timed message blocks plus suppression.
Why this structure works
Separates persuasion, sequencing, and eligibility.
What you'll get
Expected output
What the draft should contain
Expect three message blocks with timing rationale, channel, distinct objection, three subject variants and their angles, preview text, body under 120 words, one CTA, and a next step. Timing is a starting hypothesis, not a proven optimum. For SMS, request concise copy; label subjects and preview text as email-only rather than inserting them into a text.
Worked example
Assume an email-only kitchenware store: $80 carts, frequently abandoned pans, shipping disclosed late, $6 delivery, free delivery above $100, and unused-item returns within 30 days. Discounts are prohibited. These are illustrative inputs, not suggested store policies.
1. One hour: distraction
The short delay allows shoppers to resume without immediately interrupting checkout.
- Subjects: “Your pan is still in your cart” (reminder); “Pick up where you left off” (continuity); “Return to your cart” (direct).
- Preview: “Review your selection whenever you’re ready.”
- Body: “Still considering that pan? Your selection is saved so you can review it without starting again.”
- CTA: “Return to cart.”
- Next: Check purchase status before message two.
2. Twenty-four hours: shipping cost
Allow time before explaining the delivery terms.
- Subjects: “Delivery, explained” (clarity); “About the shipping charge” (objection); “Check your delivery options” (utility).
- Preview: “Standard delivery costs $6.”
- Body: “Standard delivery is $6; orders above $100 ship free. No need to add extras unless you want them.”
- CTA: “Review cart.”
- Next: Recheck eligibility.
3. Seventy-two hours: trust
Give shoppers space before addressing purchase risk.
- Subjects: “Questions about returns?” (reassurance); “Before you decide” (support); “Our returns terms” (transparency).
- Preview: “Unused items qualify within 30 days.”
- Body: “Unsure? Unused items can be returned within 30 days.”
- CTA: “Review cart.”
- Next: End recovery; suppress repeat buyers and recent purchasers.
Under the hood
Why this prompt works
The Role establishes a lifecycle-marketing perspective: each message belongs to a sequence, not an isolated promotion. Context ties persuasion to store facts. {{policies}} supplies answers to delivery and trust objections, while {{discount_policy}} prevents the model from treating coupons as a default solution.
The Task makes decisions inspectable. Requiring timing reasons, subject angles, one CTA, and nonconversion steps exposes repetitive appeals and unclear handoffs. Different abandonment reasons create different editorial jobs, although they remain hypotheses unless shopper data supports them.
The Rules constrain tempting shortcuts: no first-message discount, no invented urgency, and an explicit margin discussion when incentives are allowed. Missing cost inputs should produce a clarification request, not fabricated profitability. Finally, suppression requirements connect copywriting to audience eligibility. They remind the operator that even accurate, persuasive copy becomes inappropriate once the shopper has purchased.
Model fit
Best AI models for this prompt
ChatGPT
Use it for consistent message blocks and subject-angle variants. Check that every nonconversion step specifies an action.
Claude
Use it to edit reassurance copy against supplied policies. Ask it to flag promises the inputs cannot support.
Gemini
Use it to compare an existing sequence with checkout-friction notes. Require separation of observed evidence from inferred motives.
Grok
Use it to explore contrasting subject-line angles. Specify restrained language and reject unsupported claims about shoppers or urgency.
When to use
- Building your first recovery sequence.
- Replacing repetitive reminder emails.
- Updating messaging after shipping-policy changes.
- Revisiting objections surfaced by support.
When not to use
- Checkout or payment processing is broken.
- Contact permissions remain unverified.
- Purchase events cannot trigger suppression reliably.
- Regulated claims need specialist review.
Get more from it
Pro tips
- 1
Separate observed friction from hypotheses.
- 2
Verify saved-cart links before sending.
- 3
Define repeat-buyer eligibility explicitly.
- 4
Apply SMS-specific permission and frequency checks.
- 5
Supply costs before requesting margin calculations.
- 6
Recheck suppression before every send.
Don't ship this
Common mistakes
✗ Treating timing as universal.
Fix — Test against your purchase cycle.
✗ Calling discount value profit loss.
Fix — State cost assumptions and contribution impact.
✗ Duplicating email in SMS.
Fix — Shorten and coordinate channel frequency.
People also ask
Frequently asked questions
Q.How many messages should a cart recovery flow have?
Three is the reliable default: a reminder, an objection-handling message and a final close. More than four tends to raise unsubscribes faster than it raises recovered revenue.
Q.When should I include a discount?
Only in the final message, only if your margin allows it, and never in the first. Discounting early teaches shoppers to abandon carts deliberately, which is expensive and hard to reverse.
Q.Should the flow send SMS as well as email?
Only where you have explicit consent for that channel and the cart value justifies it. SMS recovers well but tolerance for it is low, so it belongs on one message, not all three.