Help me retain a customer without making promises we cannot keep. Use the evidence below to identify the likely retention risk, write an empathetic customer response, and create an internal action plan. Customer and relationship context: [CUSTOMER CONTEXT] What happened and the customer’s words: [ISSUE AND EVIDENCE] Product use, account history, and risk signals: [ACCOUNT SIGNALS] What we can actually offer or change: [APPROVED OPTIONS] Our goal, owner, and timing: [RETENTION GOAL] If a required fact is missing, ask up to 3 clarifying questions. Do not invent product capabilities, timelines, refunds, credits, policy exceptions, customer sentiment, or metrics. Produce five sections: 1. Situation assessment: distinguish confirmed facts from likely causes and list the top three retention risks. 2. Customer message, 120–180 words: acknowledge the specific impact, take appropriate responsibility without speculating, state the next concrete action and its owner, and give a realistic update time. Do not use defensive language or generic apologies. 3. Recovery plan: a table with action, owner, deadline, dependency, and success signal for the next 14 days. 4. Offer decision: recommend the smallest approved remedy that matches the failure, explain why, and state what approval is needed if none is available. 5. Measurement plan: retention outcome, leading behavior signal, customer sentiment check, and date to review. Self-check: every customer-facing statement must be supported by the supplied facts or labeled as a commitment we can fulfill. Ensure the proposed remedy addresses the stated problem rather than only offering a discount. Flag any situation involving security, privacy, billing disputes, discrimination, or contractual commitments for the appropriate internal owner.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [CUSTOMER CONTEXT] | Describe the customer, plan, use case, tenure, key contacts, and relationship history. | Northgate Dental Group, 14-location customer on the Growth plan for 18 months; operations director Maya Chen is the main contact. |
| [ISSUE AND EVIDENCE] | Paste the customer’s message and the verified facts about the incident or concern. | Maya wrote: “Reports were unavailable during Monday’s morning huddle and my managers lost confidence.” Status page confirms a 93-minute reporting outage. |
| [ACCOUNT SIGNALS] | List usage changes, support history, renewal date, NPS or survey feedback, and known competitors if applicable. | Weekly active users down 28% over six weeks; three reporting tickets this quarter; renewal is November 15; no NPS response. |
| [APPROVED OPTIONS] | List remedies you are authorized to offer, such as training, a service credit, an extension, or a product workaround. | We can provide a reporting training session, priority support for 30 days, and up to one month of service credit with director approval. |
| [RETENTION GOAL] | State the desired outcome, accountable owner, and the next deadline or renewal date. | Restore reporting adoption and secure a renewal discussion by October 20. Account owner is Luis Romero. |
How to use
- Paste the customer’s exact language alongside only verified account and incident facts.
- Check the draft message for commitments your team can meet, including the named owner and update time.
- Assign the recovery-plan actions before sending anything so the promised next step is real.
- Follow up with: “Rewrite this for a customer who is polite but has stopped using [FEATURE], without assuming they plan to cancel.”
Variations
Renewal risk brief
Use this when an upcoming renewal needs an internal retention review before outreach.
Create an internal renewal-risk brief for [ACCOUNT]. Use [USAGE AND SUPPORT DATA], [COMMERCIAL TERMS], and [STAKEHOLDER NOTES]. Output: an evidence-only risk summary, a table separating controllable product or service issues from unverified assumptions, recommended outreach sequence, executive-sponsor need, and 30-day actions with owners. Include a renewal forecast with confidence level and reasons, not a fabricated probability. Flag contractual, pricing, or privacy questions for the correct internal team. Ask up to 3 questions only if a necessary input is missing.
Cancellation response
Use this when a customer has submitted a cancellation request.
Draft a response to this cancellation request: [CUSTOMER MESSAGE]. The account background is [ACCOUNT BACKGROUND], and these are our approved retention or offboarding options: [APPROVED OPTIONS]. Write a 130–170 word email that confirms receipt, acknowledges the specific reason, offers one relevant path to resolve it without pressure, and explains the next administrative step if they still leave. Then provide an internal checklist for data export, access removal, billing, feedback capture, and escalation. Do not imply a cancellation is reversed without customer consent.
Low adoption outreach
Use this when usage has declined but the customer has not complained.
Write a low-adoption outreach plan for [CUSTOMER SEGMENT] using [USAGE PATTERN] and [VALUE HYPOTHESIS]. Create a short email under 130 words, a call agenda, and three diagnostic questions that uncover workflow friction without accusing the customer of poor adoption. Recommend one practical intervention from [AVAILABLE INTERVENTIONS], with a success measure and 14-day follow-up date. Do not claim the customer has a problem unless the data supports it, and do not offer discounts as the default solution.
Tips
- Quote the customer’s stated impact in the response, such as a missed reporting meeting, instead of replacing it with a vague apology.
- Separate a proven service failure from a theory about why the account is at risk; the internal team needs both, but they should not be treated as the same thing.
- Make the next update time shorter than the final-resolution time when a fix depends on engineering or another team.
- Use credits only when they match a real failure or commercial strategy; training, a workaround, or executive attention may solve the actual risk better.
FAQ
Should a retention email include a discount?
Only if an approved commercial remedy fits the problem. A discount does not repair a reliability, onboarding, or support failure by itself.
How quickly should I reply to a retention risk?
Acknowledge a serious issue promptly, then give a specific next update time. Do not promise a final resolution before the responsible team has confirmed it.
Can AI identify customers likely to churn?
It can help organize supplied signals, but it should not invent sentiment or causal explanations. Validate its hypotheses against usage, support, billing, and account-team evidence.