The scariest churn signal isn't a complaint — it's silence
When a customer sends an angry support ticket, that's actually good news.
They're frustrated. But they're still there. They still think you can fix it. They took the time to write to you.
The customers I worry about are the ones who stop writing altogether.
What silence looks like
Silence doesn't arrive all at once. It creeps in slowly:
- They stopped opening your emails
- They stopped replying to your check-ins
- They haven't submitted a support ticket in weeks — not because everything is fine, but because they gave up trying
- They filled in your last survey with a score and left the comment box empty
Nothing in your dashboard shows this as a problem. Usage might still look normal. They might still be logging in. But in their head, they've already moved on.
Why silence is so hard to catch
Every other churn signal gives you something to look at. A complaint has words. A bad review has a rating. A drop in usage shows up as a number.
Silence has nothing.
There's no ticket to read, no review to respond to, no number that changes. The only signal is something that stopped happening — and it's easy to miss what's no longer there when you're busy watching what is.
This is why churn often comes as a surprise. Not because teams weren't paying attention, but because they were watching for signals that arrive — not signals that disappear.
Three types of silence worth watching
1. Communication silence
A customer who used to reply within a day now takes a week — or doesn't reply at all. One missed reply is nothing. Two in a row is worth noticing.
2. Support silence
They used to submit tickets regularly. Now they've stopped. This can feel like a good sign. Often it isn't. It can mean they've stopped expecting things to improve.
3. Feedback silence
They used to fill in surveys and leave comments. Now they skip them, or just fill in the number and leave the text box blank. When someone stops giving feedback, something has changed.
What you can actually do
Silence is hard to track because there's no event that triggers an alert. But a few simple things help:
Make check-ins shorter and more frequent. A long quarterly survey is easy to ignore. One question — "how's this feeling lately?" — sent more often gets more responses. And the responses are more honest because it takes less effort to answer.
Watch for what stops happening. Set a simple rule: if an active customer hasn't opened an email, submitted a ticket, or replied to anything in 30 days — reach out personally. Not an automated message. A real one.
Notice when themes go quiet. If certain customers used to mention pricing or support problems and suddenly stopped — that's worth checking. They may have accepted it. Or they may have stopped caring.
Silence usually doesn't come out of nowhere
Before a customer goes fully quiet, there's almost always a shift in how they communicate.
Their tickets get shorter. Their survey comments shrink to one line. They stop asking follow-up questions. They reply with "ok" instead of a paragraph.
These are small changes. Easy to miss. But they're the last readable signal before silence arrives — and if you catch them, you still have time to do something.
Most customers don't disappear without warning. The warning is just quieter than we expect.
Silence is the end of the story. The drift that leads to it is where you can still act.
If you want to catch that drift in your own customer feedback, there's a live demo at sentana.se/demo — no signup needed. Or send me a batch of tickets or survey responses and I'll run it through and share what it finds.
Curious whether others have found a good way to track support silence specifically — it feels like the hardest one to catch in practice.
