We tracked what happened to customers who never contacted support. The results were uncomfortable.
Last quarter we did something we hadn't done before.
We looked at all the customers who churned in Q3.
Then we checked: how many of them had contacted support in the 60 days before churning?
Answer: 23%.
Which means 77% of churned customers had a problem — or lost connection with the product — without ever telling us.
We had no idea they were struggling.
Then we looked at customers who had contacted support in the 60 days before their renewal.
Retention rate for that group: 89%.
Retention rate for customers who never contacted support: 61%.
Counterintuitive takeaway: customers who ask for help retain better than customers who don't.
Not because support is magic. But because reaching out is a signal of engagement. Of still caring enough to try.
The customers who go quiet — who stop asking questions, stop reporting bugs, stop requesting features — those are the ones already mentally moving on.
What we changed after this:
We started a simple proactive check-in sequence. If a customer hadn't logged in for 10 days and hadn't contacted support, they got a personal email from a human. Not automated. Not templated.
Just: "Hey, noticed you haven't been around. Anything we can help with?"
Response rate: 34%.
Of those who responded: 71% mentioned a specific problem they'd never raised.
The support ticket they didn't send was the one that mattered most.
Has anyone else done this kind of analysis on silent churners? Curious what others found.
The 61% vs 89% retention split is one of the starkest numbers I've seen on this. There's a behavioral economics angle worth noting — when someone invests effort into reaching out, they're implicitly telling themselves "this product is worth my time to fix." That micro-commitment compounds. It's the same reason customers who go through a slightly annoying onboarding process often retain better than those who breeze through.
The 10-day inactivity threshold is interesting. Did you experiment with different windows before landing on that? For daily-use tools, 10 days is practically a goodbye. For tools with a weekly or monthly cadence, 10 days might be normal usage. Getting the threshold wrong in either direction risks either missing churners or annoying your most satisfied quiet users.
Also really curious about the 71% who mentioned a specific problem — was it mostly product issues (bugs, missing features) or confusion about features that already existed? That distinction changes the intervention completely: one is a product problem, the other is an onboarding/education problem. In my experience building SaaS, the "I didn't know that feature existed" bucket is surprisingly large and much cheaper to fix.
Thanks for such a thoughtful breakdown — really appreciate it!
You're spot on about the behavioral economics angle. That micro-commitment of “I bothered to write in” seems to create real psychological ownership. We saw it play out exactly like you described.
On the 10-day threshold: we actually tested 7, 10, and 14 days. For our customer base (mostly daily/weekly-use B2B tools), 10 days gave the best signal-to-noise ratio. Below 7 days we started annoying active users; above 14 days we missed too many at-risk ones. Curious if you’ve seen different sweet spots in your SaaS experience?
And yes — of the 71% who mentioned a specific problem when we reached out, \~65% was “I didn’t know this feature existed” or “I didn’t realise I could do X”. Only \~35% were actual bugs/missing features. The education/onboarding bucket was surprisingly large and cheap to fix once we saw the pattern.
Really interesting to hear your take — have you run anything similar in your own products?