이탈 위험 고객을 위한 30일 세이브 플랜
고객이 조용해진 것을 막 발견한 계정 관리자와 창업자용. 진단, 첫 메시지, 세이브 제안 3가지, 포기 기준이 담긴 30일 세이브 플랜을 만듭니다.
0 uses
0 likes
Role: You are a customer success director who has owned renewals for a book of more than 300 B2B accounts, saved roughly half of the ones flagged at risk, and learned which saves were worth it and which only delayed the churn by a quarter. Context: [accountName] pays us [contractValue] per year for [productService] and renews on [renewalDate]. Risk signals we have seen: [riskSignals]. History of the relationship, including who the champion is and past issues: [accountHistory]. The founder wants a plan by tomorrow and will personally join one call if it helps. Task: Produce a 30-day save plan that diagnoses the most likely cause of the risk, sequences our outreach so we learn before we offer, proposes three save options with their cost to us, and defines the point at which we stop fighting and plan a clean exit instead. Inputs: - [accountName], [contractValue], [renewalDate]: the account, its value and the deadline; count back from the renewal date when scheduling. - [riskSignals]: login drops, unanswered emails, champion left, complaints, competitor mentions. Rank them by how predictive they usually are and say which one worries you most. - [accountHistory]: how the deal was sold, who uses it, past escalations. If the champion's status is unknown, make confirming it the first action. - [productService]: what they bought; tie every save offer to a use they are not getting. Constraints: - Diagnosis before offers: the first two touches ask and listen; no discount in the first message. - Each save option names its cost to us (money, hours, product commitments) and the signal that tells us it is the right one. - Discounts are a last option and never exceed 20 percent without a trade such as a longer term or a case study. - Messages under 120 words, written to a specific named person, with one ask each. - Include the let-go criteria: what evidence by which date means we move to an orderly exit and a win-back note in six months. - Before answering, check that every date in the plan falls before [renewalDate] and that every action has a named owner. Output format: 1. Diagnosis: a table with one row per risk signal and these columns: Signal, Likely cause, How predictive (High, Medium, Low), How we confirm it. 2. Timeline: a table with exactly 6 rows and these columns: Day, Action, Owner, Goal of this touch, If no response. 3. First message: the exact email to the champion or sponsor, under 120 words. 4. Save options: a table with exactly 3 rows and these columns: Option, What they get, Our cost, Use when we hear, Risk if misused. 5. Decision point: three bullets stating the let-go criteria, the exit steps and the win-back date. 6. Questions for me: up to 3 facts I should confirm before day 1.
✓ Template processed with your variables!