Customer Win-Back Automation Churned customers re-engaged with a reason, not a discount
Churned customers hear from you when the thing that made them leave has changed — with one approved offer, from their owner.
- Run for you$197/month
- Custom build · this process$2,000–3,500 one-time
- Starts whenSchedule Trigger (weekly) + product/release event
Covers up to 5,000 churned accounts and four trigger types. Custom triggers from your own product data are a custom build. Custom builds start at $2,000 site-wide; this band is for this process and its integrations.
Customer Win-Back Automation is an automation Agentmelt installs in your own tools. The free template is a file you import yourself; the kit ($49) adds the setup guide and prompts. Installed for you costs $249 one-time and is live within two working days of access, with a recorded walkthrough and 30 days of fixes. Run for you costs $197/month, with setup and maintenance included. A custom build of this process is $2,000–3,500 one-time; custom builds start at $2,000 site-wide. No call is needed for any option. Written by Max Zeshut; last revised 2026-09-21.
Reference stack: Claude + n8n. Node names are on each step; the file is under the template.
Founder at Agentmelt
Reviews every build before it goes live; the workflow escalates to a person, never past one.
What is customer win-back?
Customer win-back automation replaces the discount blasted at everyone who ever cancelled with a message that has a reason: churned customers are segmented by exit reason and value, the workflow waits for a trigger that makes a return plausible — the feature they asked for shipped, their season started, a pricing change, a year since they left — drafts a short message that names the reason and carries one approved offer, sends it from a person’s address after approval for high-value accounts, routes replies, and tracks reactivations by segment and trigger so you learn what actually brings customers back. Segments can be paused in one click.
- Win-back is a 30%-off email to everyone who ever cancelled, twice a year.
- We never recorded why customers left, so every message is generic.
- The feature the churned customers asked for shipped and nobody told them.
- High-value accounts get the same blast as the free-tier dropouts.
- Nobody can say which win-back message brought anyone back.
If two of these are yours, this is the process to look at first. Free audit — or read on.
What it looks like once it runs.
Most win-back email is a discount blasted at everyone who ever cancelled. The workflow segments churned customers by exit reason and value, waits for a trigger that makes a return plausible — a feature they asked for shipped, their season started, a pricing change — and sends a specific message with one approved offer. Reactivations are tracked to the segment and trigger so you learn what actually brings people back.
- Monday 7:00 Cancelled and lapsed accounts are pulled with the reason they gave.
- 7:05 Reasons are grouped; a missing-feature churn waits for that feature to ship, a price churn for a plan change.
- When a trigger fires A short message naming the reason and what changed is drafted, with one offer.
- Large accounts wait for the owner's approval; the rest send from the owner's address. Reactivations are tracked to the message.
Churned customers get one generic “we miss you” email and are then forgotten. Nobody uses the cancellation reason that was recorded. Discounts are offered to people who left for reasons a discount does not fix.
Every churned account sits in a segment with a reason and a value, and gets a message only when there is something true to say. Reactivation rate rises because the message is relevant; discount spend falls because it is offered only where price was the reason.
Trigger, then 7 steps.
Six of the seven steps run without anyone. Step 05 waits for a person.
Schedule Trigger (weekly) + product/release event
Build the churned segment
Cancelled and lapsed accounts from billing and CRM with tenure, last plan, revenue, cancellation reason and any exit-survey text.
Classify the reason
Exit reasons normalised into categories — price, missing feature, poor fit, switched to competitor, business closed, unresponsive — from the survey text and support history.
Match triggers to segments
Rules: missing-feature churn waits for that feature to ship; price churn waits for a plan change or an annual-discount window; seasonal churn waits for the season; poor-fit and closed-business are excluded.
Draft the message
A short, specific message referencing the reason they gave and the thing that changed, with one approved offer from the finance-owned set, in the account owner's voice.
Approve high-value sends
Accounts above a revenue threshold pause for the owner's approval; the rest send automatically within the frequency cap.
Send and route replies
Sent from the account owner; replies create a task for them with the account history; unsubscribes are honoured across all lists.
Track reactivation
Reactivations matched to the message, segment, trigger and offer, so the rules and offers can be tuned quarterly.
Every churned account sits in a segment with a reason and a value, and gets a message only when there is something true to say
Every churned account sits in a segment with a reason and a value, and gets a message only when there is something true to say.
One decision, at step 05. Six steps ran without you.
Each pattern page explains it in plain words and lists every automation that uses it.
The template is built on n8n (how the n8n AI Agent node works); the same steps run on Make, Zapier or plain code. The tool is chosen to fit your accounts, you own the result, and the template comes in all three formats.
Data it touches
- Billing (cancellations, lapsed subscriptions)
- CRM and exit-survey text
- Release notes / product changelog
- Finance-approved offer set
Guardrails
- Excluded segments (business closed, requested no contact, poor fit) never receive win-back messages.
- One win-back message per account per quarter unless they reply.
- Offers come only from the approved set; the agent picks, it never invents a discount.
- High-value accounts require owner approval before sending.
A reason, a trigger, one offer
Win-back works when the message is true: “you left because X was missing; X shipped last week.” That requires knowing why they left (the exit reason, classified), knowing what changed (the trigger), and having something to offer that fits (the approved set). The workflow assembles those three and does nothing when any is missing — which is why the reactivation rate on the messages it does send is several times that of a blast.
Measuring it
Reactivation rate by segment and trigger; revenue reactivated vs discount cost; and the share of churned accounts that never qualified for a message, which tells you whether your triggers are too narrow. Review quarterly and retire triggers that do not convert.
What it connects to.
| Tool | Role in this workflow |
|---|---|
| n8n | Segmentation, triggers, sending, tracking |
| Claude | Reason classification and message drafts |
| Stripe / Chargebee + HubSpot | Churn data and CRM |
| Gmail / Customer.io | Delivery |
Want this running without building it?
$197/month
We set it up in your tools, run it on our servershost it on our n8n cloud (or deploy it to your own n8n, Make or Zapier), watch it, and fix it when something changes. Setup included, cancel monthly; the automation stays yours if you leave.
$2,000–3,500 one-time
Your systems, your rules, your edge cases. A one-off build delivered into your accounts to keepon Claude and n8n, delivered into your accounts to keep, with documentation and a recorded walkthrough.
Covers up to 5,000 churned accounts and four trigger types. Custom triggers from your own product data are a custom build.
One-time, in your own accounts
Do it yourself $49 — the workflow file for your automation toolthe n8n workflow and the Make blueprint with the setup guide, prompts, message templates and test checklist; you import it. Installed for you $249 — we put it into your accounts within $two working days of access, in your voice, with 30 days of fixes. The first is credited in full against the second for 30 days. No call for either.
When this becomes a custom build.
The subscription covers the standard version — $197/month, setup and maintenance included. Three things move it to a custom build ($2,000–3,500 one-time), delivered into your accounts to keep. If one of them is you, say so on the audit and the plan prices both.
Triggers from your own product data — a feature shipped, a usage signal — beyond the four standard types.
More than 5,000 churned accounts, or several products with different reasons for leaving.
Offers that are applied inside your billing system automatically when the customer accepts.
Running the standard version first is the usual path: the exceptions it logs in the first month are the scope of the custom build, with your own numbers. How custom builds work.
Frequently asked questions.
What if we did not record cancellation reasons?
The classifier infers reasons from support history, usage before cancellation and any survey text; accounts with no signal go into an “unknown” segment that gets a lighter, question-led message instead of an offer.
Does it work for e-commerce lapsed customers?
Yes — lapsed is defined by purchase recency per category, and triggers include restocks, new arrivals in a category they bought, and price drops on items they viewed.
Can it pause messaging to a whole segment?
Yes, per segment or per trigger, from the rules sheet, without touching the workflow.
What if we did not record cancellation reasons?
The workflow infers a likely reason from the last support tickets, the usage pattern before leaving and the plan history, and labels it as inferred; the first win-back messages ask, lightly, and the answers become the recorded reason. Segments built on inferred reasons start in approval mode.
Does win-back automation work for lapsed e-commerce customers?
Yes, with purchase-based triggers instead of product ones: a replenishment cycle, a new arrival in a category they bought, a seasonal reason. The same rules apply — one message, one reason, one approved offer, and the sequence stops on a purchase or a reply.
How many messages does a churned customer get?
One per trigger, never more than one a quarter, and none after a reply, a return or an opt-out. A win-back that turns into a drip is the thing customers remember about a brand, and not favourably.
What this blueprint is built on.
Vendor documentation the steps rely on, and the rules the guardrails are written against.
- Stripe — Subscriptions API docs.stripe.com/api/subscriptions
- HubSpot — API overview developers.hubspot.com/docs/api-reference/latest/overview
- FTC — CAN-SPAM Act compliance guide www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business