The challenge
Cancellations and returns could easily become a transactional processing queue. The business needed a clearer view of why customers were leaving, which customers were still recoverable, what had already been attempted, and which issues reflected larger operational patterns.
What I saw
- Cancellations were processed accurately and analyzed rarely.
- There was no visible distinction between a customer who was gone and a customer who was still deciding.
- Intervention attempts lived in individual notes, so the team could not tell what had already been tried.
- Pending returns sat in a blind spot between the customer decision and the physical logistics.
- Recurring drivers were discussed anecdotally rather than counted.
What I designed or implemented
- 01
A recurring Order Health and Retention update
A regular update covering at-risk orders, active cancellations, pending returns, and outcomes, written so operations and leadership read the same picture.
- 02
Separation of finalized losses from active salvage
Finalized cancellations were reported separately from customers still in an open conversation, so effort went where it could still change the result.
- 03
Categorized cancellation and return reasons
A consistent reason taxonomy covering wait time, installation space, financial hardship, product fit, relocation, technical concerns, and customer-service experience.
- 04
Intervention and outcome tracking
Each at-risk customer carried the intervention attempted and the resulting state: retained, still negotiating, declined, or proceeding with the return.
- 05
Pattern reporting back to the business
Recurring drivers were routed to the teams that owned the underlying cause rather than absorbed by the recovery workflow.
How the system worked
The update was not a status list. Each open case carried an intervention, an owner, and an expected outcome date.
A customer leaving over wait time needs a different response than a customer leaving over product fit. The reason taxonomy drove the strategy.
Recording the result of each intervention told us which strategies actually worked and which were being repeated out of habit.
Retention strategies in use
The range of interventions available to the team, applied based on the cancellation reason and the customer's situation.
- Accelerated scheduling
- Shipping credits
- Subscription or app access
- Trial extensions
- Fee waivers
- Product education or trainer demonstrations
- Proactive calls
- Alternative installation discussions
- Future re-engagement planning
Engagement & Advocacy
Customer health shouldn't stop at identifying risk. The same signals that tell you when someone may need intervention can also tell you when someone is engaged, satisfied, and ready to advocate.
That creates another opportunity: use customer health not only as a recovery system, but as a lifecycle growth system. The recovery half ran in production. Everything in this section was designed and proposed. None of it launched.
A referral experience built into the product
Rather than asking every customer for a referral and hoping some of them are happy, use engagement and satisfaction signals to identify likely promoters and reach them at the moment advocacy is natural: after a milestone, after a recovered issue, after a stretch of consistent use. The ask lives inside the product rather than in a campaign.
- Eligibility driven by health state, not by list membership
- Timed to a moment the customer already feels good about
- Tracked as an outcome of health, so the model can be corrected
Rewards tied to behavior, not to spend
The principle was to reward the behaviors that increase engagement and long-term value rather than rewarding another purchase. A customer who keeps a streak going is worth more than one who buys an accessory, and the reward system should say so.
- Completing workout milestones
- Maintaining engagement streaks
- Referring someone who stays
- Giving feedback the team actually uses
- Participating in community activity
- Joining beta or early-access programs
One framework, more than one direction
The operational point is simple. A health model that only looks for risk is doing half the work. The same read that tells you who to call also tells you who to celebrate, who to invite, and who to ask. Each state routes somewhere different.
This section is written as it stood: designed, argued for, and not built. The recovery workflow earlier in this case study is the part that ran.
Outcome and business value
Turned cancellations and returns from a passive processing queue into a visible customer-recovery workflow.
- The team could distinguish unavoidable loss from operationally driven risk.
- Recoverable customers were identified while the conversation was still open.
- Customers who needed a different intervention were routed rather than re-pitched.
- Broader product and fulfillment patterns became visible to the teams that owned them.
- Individual retained customers were reported as individual outcomes. No cumulative company-wide retention rate is claimed here.
What was executed versus what remained proposed
- Recurring Order Health and Retention update
- Cancellation and return reason taxonomy
- Pending-return tracking
- Intervention and outcome tracking per at-risk customer
- Pattern reporting into product, fulfillment, and support
- A predictive at-risk score to flag customers before they initiate a cancellation
- Automated intervention prompts tied to reason category
- A referral experience triggered by engagement and satisfaction signals
- A rewards model built around engagement behavior rather than spend
- Community and advocacy programs for customers already at the top of the health model