Churn Save Conversation

Cancellation acknowledged within 30 minutes. Real reason captured. Save play offered or declined. Outcome logged. Feedback aggregated for product/marketing/support teams.

Before you start

Approved retention playbook with offers and concession guardrails
Customer context: usage, tickets, billing history
CSM/AE involvement on save plays >$5k ACV
Cancellation request (subject, body, customer email)
Customer account: plan, MRR, contract end, usage trend
Recent support history

The steps

Acknowledge the cancellation respectfully — First reply within 30 minutes: thank them for letting us know, confirm we'll process if that's their decision, and ask if they're open to a quick conversation to make sure we understand. Tone: respectful, not desperate.
Probe for the real reason — Ask 1-2 questions: 'What's driving the change?' and 'Is there anything specific that pushed you toward this?'. Real reasons often differ from stated reasons — give them room to articulate it.
Categorize the cancellation reason — Map to: pricing, missing feature, switched competitor, internal change (lost champion, layoff, refocus), no longer needed, support quality, onboarding failure. Each category has a different play.
Match to the right save play — Pricing: adjusted plan or pause option. Missing feature: roadmap commitment + temporary workaround. Switched competitor: migration assistance, retention offer. Internal change: pause/downgrade option. Support quality: escalation to leadership. Don't apply pricing concessions to feature-driven cancellations — wrong fix.
Offer the matched play with clarity — Present the offer concretely: 'Given X, here's what I can do: [offer]. No pressure either way.' Avoid stacking multiple offers — confuses the customer and signals desperation. Single, fitting offer.
Honor the cancellation if they decline — If they don't accept, process the cancellation cleanly. Confirm the date, prorate or not per policy, send a final summary. Offer a 'we'll check in 90 days in case anything changes' line — but not aggressively.
Log the outcome and feed back to the org — Log: stated reason, real reason, save play attempted, outcome (saved, lost, paused). Aggregate weekly: top cancellation reasons feed product, marketing, and support inputs. Patterns matter more than individual cases.

If it goes wrong

Customer feels pressured by save attempts

Single offer, no escalation if declined. The save attempt should feel like care, not a sales push.

Save plays succeed short-term, customer churns again 60-90 days later

Track 90-day retention post-save. If <50%, the save isn't working — it's deferring churn. Reroute those cohorts to deeper success engagement.

Categorization is gamed to make 'pricing' the easy answer

Audit save outcomes against actual product/process changes. If 'pricing' dominates but pricing isn't the issue, recalibrate the categorization rubric.

All OpenLabor playbooks