Your churn warnings are public. You're just not listening.

The cancellation email is the last step of churn, not the first. By the time it arrives, the decision is weeks old, the replacement is shortlisted, and your win-back discount is an insult.

The first step happened somewhere else, and increasingly it happened in public. "Anyone else finding [product] support useless lately?" in a subreddit. "Genuinely considering dropping [product], the new pricing is wild" on X. A thumbs-down in a community your CSM has never heard of. Customers vent publicly before they churn privately, for the same reason they do everything else in those spaces: they want validation and alternatives from peers, not a retention flow from you.

The window between venting and leaving

What makes public venting valuable isn't the sentiment data. It's the timing. Someone complaining about you in public is, definitionally, still your customer, still emotionally invested enough to type a paragraph, and usually asking a question whose subtext is "talk me into staying or out of it." The thread's commenters will happily do the second one. The window where you can do the first is measured in days.

The saves I've seen work all look the same. The company shows up fast, in-thread or via a genuinely human reply, acknowledges the specific complaint without corporate padding, and either fixes the thing or explains the roadmap honestly. Done within a day or two, this converts shockingly well, and it converts in public, where every lurking customer with the same silent complaint watches you handle it.

Done after two weeks, the same reply reads as damage control on a corpse.

Why your CS stack misses this

Health scores are built from product telemetry: logins, feature usage, ticket volume. All real, all lagging. The customer who's quietly furious often looks fine in telemetry right up until they don't, because they're using the product daily while shopping for its replacement.

Meanwhile the leading indicator, a paragraph of first-person frustration with your product's name in it, sits on a public website, unmonitored, because "brand monitoring" belongs to marketing and marketing's firehose channel got muted a year ago (a whole separate failure).

There's also a subtler miss: telling venting apart from everything else that mentions you. A mention could be praise, a feature request, a comparison, a prospect asking if you're any good, or a customer packing their bags. Those need entirely different responses from entirely different teams. When we added audience tagging to our pipeline, "current customer, negative, acute" became its own category precisely because routing it to a sales rep, or letting it ride a daily digest, destroys the value.

A note on product teams

The same threads that warn you about churn are the cheapest roadmap research you'll ever get. People describe what's broken, in their own words, with the emotion intact, next to what they wish existed. Feature requests phrased as complaints. Complaints phrased as questions. A quarter of our own roadmap has come from watching people describe problems adjacent to what we'd already built.

You don't need our product to act on any of this. You need someone, or something, watching the places your customers actually talk, able to tell an upset customer from an upset stranger, fast enough that the thread is still warm when you arrive. That's the whole trick. The cancellation email is silent for months first. The internet usually isn't.