All use cases

Retain / Save

Cancel-flow save for a wellness subscription

She is on the cancel screen of a wellness app, and the reason is almost never the price — it's that she stopped seeing results, lost the habit, or ran out of time.

Close the loopNext best thingBehavioral triggerRisk triggerChatIn-appEmailWellness (B2C apps)Subscription

What it does

Wellness subscriptions are bought on a goal and kept on a habit, so when a member hits cancel the cause is usually specific: the scale stopped moving, the daily streak fell apart, life got busy, or the value stopped feeling worth the price. Most cancel flows answer all four with the same radio-button survey and a coupon, which fixes none of them. The agent turns the cancel screen into a short diagnostic that finds the real reason and offers the save that actually addresses it — a re-personalized lighter plan for someone who feels it stopped fitting, a habit-restart for someone who drifted, a pause for someone short on time, or a recap of the progress she would lose. The cancellation completes cleanly when she means it, but a fixable reason gets fixed at the moment of intent.

How it works

  1. 1
    Trigger. cancel intent on a paid wellness plan — the cancel button is pressed in-app, or "cancel my plan" lands in chat.
  2. 2
    Decision. the agent asks the one reason question and reads the member's own history — logging streak, results trend, recent activity — to classify the reason as price, no results, lost habit, or no time, then selects a wellness-fit save from a policy-bounded ladder. A judge gates tone and the no-dark-patterns rule.
  3. 3
    Action. the matched save is offered in-thread — re-personalize the plan to her current goal, restart the habit with a right-sized first step, pause without losing progress, or recap concrete wins to date — and executes inline, or the cancellation is processed cleanly if she declines.
  4. 4
    Follow-through. the reason and outcome write back to memory for win-back and product; saves are measured as lift over a randomized holdout, and cancellation is always one step away.
Example
CustomerI want to cancel — I'm just not getting anywhere with it.
AgentThanks for being honest. Looking at your last few weeks, your weight's been flat but your logging's been consistent — that flat stretch is normal, and it's usually the cue to change the focus, not to stop. I can rebuild your plan around protein and sleep for the next month instead of cancelling. Want to try that, or still prefer to cancel?
CustomerI didn't realise the plateau was normal. Let's try the new plan.
AgentDone — your plan's updated and your streak stays intact. I'll check in next week to see how the change feels.

Configuration

How the agent is wired for this use case.

Triggercancel intent on a paid plan — a cancel_clicked event from the app backend or "cancel my plan" detected in chat
Tools & actions
  • Messaging channel · open the diagnostic on the cancel screen, in chat, or by follow-up email
  • App backend · read logging streak, results trend, and recent activity to classify the reason
  • Plan/program engine · re-personalize the plan, right-size a habit-restart, or surface a progress recap
  • Billing platform · execute the matched save inline: pause the plan or step down the tier
  • Memory store · recall prior offers and her stated goal; record the diagnosed reason and outcome
Autonomythe diagnostic, the reason classification, and the policy-bounded save ladder run unattended behind judge gating; the agent stays in wellness framing and gives NO medical, diagnostic, or clinical advice; pause and downgrade are money-moving and execute within a bounded billing-action policy; cancellation always stays one step away
Channelschat · in-app · email
Escalationa complaint, a refund dispute, or a distress signal hands off to a human with full context; a member who restates the cancel after one offer is processed without a loop

What you need

The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.

Signals

cancel-button events and cancel intent in chat, auto-renewal status, logging-streak and results-trend state

Data

plan and billing history, stated goal, logging and progress history, prior support and offers, customer memory

Guardrails

cancellation always one step away — no loops, no dark patterns; save ladder capped by policy and not discount-first; judge gating on the conversation; wellness framing only, no medical or clinical claims; human hand-off for complaints and refunds; randomized holdout for save-rate measurement

Metrics it moves

  • save-rateup, by matching the offer to the diagnosed reason — re-personalize, restart, pause, or recap — instead of a survey and a coupon
  • churndown, as the no-results and lost-habit reasons that drive wellness cancellations get addressed at the click
  • ltvup, with members re-engaged on a fitting plan rather than churned at the first plateau

Related use cases

Retain / Save

Cancellation-intercept save flow

the femtech sibling whose trigger is the support queue, not a cancel button

Retain / Save

Weight-plateau coaching intervention

the proactive save for the no-results reason this flow catches at cancel

Retain / Save

Cancel-flow save conversation

the general cancel-button save this specializes for wellness reasons and saves

See it on your own customer journey

Bring one drop-off, one churn cliff, or one silent segment. We will show you what a proactive agent with memory and judgment does with it.

Book a demo