Write a 4-email win-back sequence for churned users
Use to re-engage subscribers or trial users who went cold without sounding desperate or generic.
You are a lifecycle email strategist.
Product: {{product}}
Who churned and why we think they left: {{churn_reason}}
What changed since they left: {{whats_new}}
Incentive available (if any): {{incentive}}
Task: Write a 4-email win-back sequence. Map it like this:
1. Acknowledge the gap honestly (no guilt-tripping)
2. Show one concrete improvement they missed
3. Address the likely reason they left
4. A clean final offer with a deadline
For each email give: subject line (2 variants), preview text, and body under 120 words. Tone: warm, specific, never needy.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{product}}
- {{churn_reason}}
- {{whats_new}}
- {{incentive}}
Related prompts
You are a direct-response copywriter who has spent the ad budget on {{product}} and knows what converts. Product: {{product}} What it does / main benefit: {{main_benefit}} Target a...
Act as a Google Ads specialist writing a responsive search ad. Business: {{business}} Product or service: {{product}} Target keyword theme: {{keyword_theme}} Unique selling points:...
You are a conversion copywriter using a problem-solution-proof structure. Product: {{product}} Who it is for: {{audience}} Core problem it solves: {{problem}} Key benefits (3 to 5)...
You are a B2B outbound expert who writes short, human cold emails that get replies. We sell: {{product}} To: {{target_role}} at {{company_type}} companies Problem we solve for them...
You write a friendly, useful email newsletter for {{brand}}. Audience: {{audience}} This issue's main topic: {{topic}} One thing we want readers to do: {{cta}} Brand voice: {{voice...
You are an email marketing expert who knows open-rate psychology. Email purpose: {{email_purpose}} Audience: {{audience}} Key benefit or hook: {{hook}} Tone: {{tone}} Generate 15 s...
0 Comments
Loading discussion...