Skip to main content
Published: 2026-09-12 · Last reviewed: 2026-09-12 · Reading edit: 2026-09-12 A customer left because an important integration was missing. Now it exists. That gives you a specific reason to ask whether the product is worth another look. A useful win-back conversation begins with what changed and whether it addresses the original reason for leaving.

​
Separate the situations

Distinguish a canceled customer, an inactive user in a healthy account, a failed payment, and a stalled evaluation. They have different owners and needs. Verify contact eligibility and suppression before planning promotional re-engagement.

​
Build a reason to return

  1. Recover the original reason. Use cancellation notes, support history, and direct feedback where appropriately available. Mark unknown reasons as unknown rather than guessing from low usage.
  2. Find a relevant reason to return. A missing integration may now exist; an implementation problem may have been fixed; the customer’s needs may have changed. Verify the change before making the claim.
  3. Select an eligible cohort. Include only accounts for which the change is relevant and contact is appropriate. Exclude unresolved issues that make a return premature.
  4. Write a specific invitation. Acknowledge the prior context without overfamiliarity. Explain the change, its limits, and an optional low-friction way to reassess. Do not imply urgency that does not exist.
  5. Plan reactivation. Check data retention, account restoration, current pricing, migration, and support. Do not promise that old data or settings remain available without verification.
  6. Check whether returning customers keep getting value. Separate replies, restarted trials, paid reactivation, and continued useful adoption. Compare servicing and incentive costs with retained value over an appropriate window.

​
Worked example

A fictional customer canceled because a required accounting connector was unsupported. The connector is now available for the relevant version. The vendor verifies that scope and sends an eligible, concise invitation to review the new compatibility guide. The message does not promise automatic restoration of the old workspace. If the customer returns, onboarding checks current requirements and data availability. Success is sustained useful use, not merely accepting a discounted first month.

​
Win-back brief

​
Know when to stop

Respect refusals and suppression. If the original mismatch remains, record it for product or market learning rather than repeatedly changing the subject line. A clean exit can preserve trust and future relevance better than a sequence with no new reason to engage.

​
Try it with your own work

Pick one former customer whose situation you understand. Verify that something relevant has changed, check whether contact is appropriate, and write a short optional invitation to reassess.

​
Sources and scope

  • Intercom: Series FAQs provides a technical example of re-entry conditions; the business eligibility and win-back method here are original.
The example is fictional; any numbers illustrate the method rather than a benchmark. Adapt the worksheet to your own situation. Revenue churn · Lifecycle email · Customer onboarding Chapter guide · All playbooks
Copyright © 2026 Ivan Xu. All rights reserved. See the copyright and reuse terms. Canonical source: github.com/weilun88313/B2B-Playbook