How to win back churned customers on Zuora
How to run win-back campaigns for Zuora subscriptions: finding churned accounts, what Zuora can and cannot reopen, return offers and timing by cancel reason.
By Florian
Customers who cancelled are some of the cheapest customers to bring back. They already know the product, they have an account in your billing system, and many left for reasons that change over time: budget, timing, a missing feature you have since shipped. Zuora holds most of what a win-back campaign needs, but it does not send win-back campaigns itself.
This guide covers how to find churned customers in Zuora, what Zuora lets you do when they come back, and a campaign structure you can run with any email tool. Zuora details come from its own documentation: Subscription statuses, Subscriptions resumption, Customer accounts cancelation and deletion, Cancel subscriptions (developer tutorial), Zuora custom events for Orders, Analytics metric glossary and Standard booking reports (all accessed November 2026).
Step 1: know who churned, and when
A win-back campaign starts with a reliable list of cancellations and their dates. Zuora gives you three ways to get it.
Events, as they happen
Zuora’s Cancel Subscription event, one of the custom events for Orders tied to Order Action Processed, fires when a subscription is cancelled. Zuora’s docs say enabling Orders and these events goes through Zuora Global Support. Attach a notification with callout delivery so your system records each cancellation the day it happens. This is the best trigger for a win-back sequence, because the timing of the first email depends on the cancellation date.
Reports, for the backlog
Zuora’s standard booking reports include a Cancelled subscriptions report (subscriptions cancelled each month) and Cancelled CMRR (contracted MRR lost to cancellations). Use them to build your first list of past churners before the event-driven flow is live. Note that Cancelled CMRR only counts charges whose end date is aligned to the subscription end.
Analytics, for account-level churn
The Zuora Analytics metric glossary defines a churned subscriber as an account that had an effective rate plan charge in the previous period and has none at the end of the current one. That is a different, account-level view: a customer who cancels one of two subscriptions is not churned by this definition. For win-back, you usually want the account-level view: people with no active subscription at all.
Step 2: record why they left
Win-back emails work far better when they answer the reason the customer gave. Zuora’s cancel operation records the dates and policy of a cancellation; the reason is something you need to capture yourself, typically in your cancel flow, and store against the Zuora account and subscription numbers. If cancellations also happen through support or sales, give those teams the same short list of reasons. See how to add a cancel flow to Zuora for the flow itself.
Also distinguish voluntary cancellations from subscriptions cancelled after failed payments. Customers who churned because a card failed need a “your card failed, here is how to restart” message, not a “here is what is new” message.
Step 3: understand what Zuora can reopen
This matters for the “come back” button in your emails.
- Resume is for suspended subscriptions. Zuora’s resumption docs describe returning a suspended subscription to active status. Cancelled is a separate status.
- Cancelled accounts can be reactivated. Zuora’s account documentation says a customer account that has been cancelled can be reactivated if needed. That is the billing account, not a subscription.
- Cancellation is per subscription, as the developer tutorial points out; there is no account-level cancellation.
The Zuora pages we reviewed do not describe reopening a cancelled subscription. The safe design is to treat a returning customer as a new subscription on the existing account, created through an order. That keeps the customer’s history, payment methods and account number, and gives you a clean start date for the new term. Confirm with Zuora support if your tenant offers another path.
Before creating the subscription, check that the account has a usable default payment method. A card stored months ago may have expired; see how to handle expiring cards in Zuora. If it has, send the customer through a hosted payment page to add a new one first.
Step 4: choose the return offer
Zuora’s discount charges can back a return offer, added to the new subscription through the order (rate plan or subscription scope; see discount scope). Keep offers simple and tied to the reason:
| Cancel reason | Win-back angle | Offer |
|---|---|---|
| Too expensive | A cheaper plan or a limited discount | Discount for the first months back, or a smaller plan |
| Not using it enough | What changed, how others use it | Usually none; a guided restart |
| Missing feature | The feature now exists | None needed if it shipped |
| Moved to a competitor | Specific improvements since they left | Optional discount |
| Payment failed | Easy restart, same plan | None; fix the payment method |
| Business closed or project ended | Nothing | Do not email |
Create a dedicated win-back discount in your product catalog, so revenue from returning customers can be reported separately from new sales.
Step 5: time the sequence
Space emails out so they arrive when circumstances may have changed. A simple, reason-based schedule:
- Day 30: a short note tied to the cancel reason. No hard sell.
- Day 60: what is new since they left, especially anything related to their reason.
- Day 90: the offer, if there is one, with a clear end date.
Stop the sequence as soon as a new subscription is created on the account, and suppress it entirely for customers who said they closed their business or asked not to be contacted. For copy ideas, see win-back email examples.
Step 6: measure what came back
Track, per cancel reason and per email:
- how many churned accounts got a new subscription within 120 days of cancelling;
- the MRR of those subscriptions, net of win-back discounts;
- how many returning customers are still active three months later.
Zuora’s Net MRR changes in Analytics separate expansion, contraction and churn; tagging win-back subscriptions with their own rate plan or discount makes them easy to isolate. For a full measurement setup, see how to measure churn in Zuora.
Common mistakes
- Emailing everyone the same day. A customer who left last week and one who left last year need different messages.
- Sending payment-failure churners a marketing email. They did not choose to leave.
- A “come back” link that leads to a generic sign-up. It should land on a page that knows the account and only asks for what is missing.
- Discounts that never end. Set a duration on every win-back discount.
Doing this with NoChurn
Zuora keeps the account, the new subscription, invoicing and payment runs. NoChurn follows Zuora notifications, records the reason from its cancel flow, and sends win-back emails at day 30, 60 and 90 written from that reason, with a link to come back. Recovery emails for failed payments and a churn score from 0 to 100 sit on the same customer record. See NoChurn + Zuora.