Signals worth tracking
| Signal | What it may mean |
|---|---|
| Falling use of core features | Value is fading |
| Fewer active teammates | Adoption is shrinking inside the account |
| Repeated errors or abandoned flows | A usability or reliability problem |
| Rising support tickets | Frustration, or a feature that does not work as expected |
| No admin activity for a long time | The champion may have left |
| Declining logins before renewal | Low engagement at a critical moment |
Fix the friction, not just the message
Retention emails treat the symptom. The cause is often a stuck onboarding step, a confusing workflow, or a missing feature. Review sessions and tickets from at-risk accounts, find the shared problem, and fix it in the product. One design change can help every customer who hit it.
Reach out with something useful
- Point to a feature they have not tried that matches their goal.
- Offer help setting up something they started but did not finish.
- Share a result: "Your team saved 14 hours this month."
- For larger accounts, have a person reach out, with context from the product.
Build a simple health score
Combine three to five of the signals above into a score per account. Keep it explainable, so the team understands why an account is flagged. Review it against actual cancellations every quarter and adjust the weights.



