War-game a winback campaign by testing whether eligibility rules, offer caps, and pause paths still protect margin when cancelled customers reappear on multiple lists and the quarter needs recovery numbers.
Winback campaigns fail when "eligible" is undefined, when discount codes dual-count the same customer across channels, and when suppression after a hard unsubscribe lives only as tribal knowledge. The review needs one written eligibility definition, one owner who can deny a send, and a documented consequence when a complaint fires without a pause.
Freeze the winback proposal
Write the cancel and dormant definitions, lookback windows, offer ladder, channel sequence, suppression sources, and billing exclusions. Attach the last three winback flights with reactivation rates, margin impact, and complaint counts. Identify exclusions in plain language. If billing-hold customers are omitted from the block list, show how that omission affects risk rather than leaving it as a footnote.
Name the approval choice and the conditions that force a hold. Include the CRM fields that compute eligibility so two reviewers can reproduce the same allow or deny label from the same packet.
Seat the campaign from both sides
- Lifecycle marketing
- Defends why the sequence must ship and what recovery harm a delay would cause.
- Finance
- Challenges offer depth, stacked discounts, and whether reactivation revenue is net of refund risk.
- Support
- Tests whether winback promises match what agents can honor on the phone.
- Billing ops
- Checks whether cancelled or disputed accounts stay out of the send.
- Skeptic
- Finds the strongest reactivation claim with the weakest suppression evidence.
Run pressure cases on the offer form
Use Pingpong to walk through a customer who cancelled after a price hike, a partner list that wants the same code, a support queue already overloaded by prior winbacks, and a request to waive preference sync because the ESP already looked clean. For each case, start from the documented winback language. Ask who can expand the segment and which evidence is required to reverse a deny. Any step that depends on an unnamed person becomes a campaign condition.
Ask the room to replay one historical winback under the proposed rules. If the historical case would have paid a deep discount while later showing quick re-churn, revise the campaign before treating it as standard.
Compare the proposal with the lifecycle marketer seat and an email preference center stress test. If survey language feeds the segment, review a churn survey rewrite. More operating decisions live in the war-game decisions hub.
Publish the winback path only after a dry run can reproduce the same allow or deny label from the stored CRM fields without manual reinterpretation.