Win back after cancellation
Goes back to people who cancelled at 30, 60 and 90 days with what has changed, a discount, and a free month, then stops.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon4 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Find recent cancellations
Coming soonBlu builds a step
- 2
Write three win back emails
Coming soonBlu builds a step
- 3
Send at 30, 60 and 90 days
Coming soonBlu builds a step
- 4
See who comes back
Coming soonBlu builds a step
About this recipe
When to use it
Most cancelled users never hear from you again, even though a meaningful share would come back with the right nudge at the right time. This stages that outreach over 30/60/90 days instead of stopping at cancellation.
What it delivers
After a user cancels, fires a staggered 30/60/90-day winback sequence - product updates, win-back incentives, and a final 'one last try' message - to recover formerly-paying customers.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Goes back to people who cancelled at 30, 60 and 90 days with what has changed, a discount, and a free month, then stops.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Find recent cancellationsBuild a segment 'Recently cancelled - last 120 days' capturing users with Subscription canceled in the last 30-120 days AND cancel_reason is NOT 'wrong-fit' or 'company-shutdown' (those won't winback). Excludes users who have already won back (subscribed again) and users who explicitly requested no-marketing in cancel form.
- 02Write three win back emailsGenerate 3-touch winback email content. Touch 1 (Day 30 after cancel): 'A lot has changed since you left: here's what's new.' Lead with 2-3 specific product improvements shipped post-cancel, relevant to their stated cancel reason. Touch 2 (Day 60): 'Come back for [N] months at 50% off': winback discount offer. Personalize the call-out with their prior use case if known. Touch 3 (Day 90, final): 'One last invitation' (softer, more emotional appeal) acknowledges you understand they left for a reason, mentions a free 30-day reactivation try (no charge until they confirm) as the final lever. Send-from: their original CSM if known, else success@ address. Use the result of "Find recent cancellations".
- 03Send at 30, 60 and 90 daysBuild a 3-touch journey triggered when Subscription canceled fired 30+ days ago. Touch 1: Day 30. Touch 2: Day 60. Touch 3: Day 90. Each touch personalized using the prior account context (cancel reason, plan, last-used features). Exit on: Subscription started (won back: record winback_won event), email_replied (warm handoff to sales), unsubscribe, or 120-day timeout (after which user moves to long-term lapsed nurture, separate motion). Use the result of "Find recent cancellations", "Write three win back emails".
- 04See who comes backCompose a winback dashboard: post-cancel winback rate (% of cancellers who re-subscribe within 90 days: baseline benchmark is 5-10%), winback rate by touch (which touch is actually driving recoveries), winback rate by original cancel reason (informs which reasons are recoverable vs. final), ARR recovered via winback this quarter, and time-to-winback distribution (most winbacks happen in the first 60 days; users dormant 90+ days rarely return without a major external trigger). Use the result of "Find recent cancellations", "Write three win back emails", "Send at 30, 60 and 90 days".
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /post-cancel-winback in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 