The users who never raise their hand

There's a pattern we keep seeing in journey data that almost no one talks about: the accounts generating the most consistent engagement are frequently the ones with zero support tickets, zero sales replies, and zero feedback submissions.

They show up. They read. They click into pricing twice a month. They revisit the docs on a Thursday night. And they never, ever reach out.

If you look at most engagement dashboards, these people register as healthy. Green dot, high score, moving through the funnel. But if you ask the sales team who their warmest leads are, these names rarely come up. The warmest leads, according to the team, are the ones who reply to emails, book calls, ask questions in chat. Activity that makes noise.

We looked at a set of about 1,200 mid-funnel journeys across a few B2B products last quarter. Of the accounts that eventually converted, 34% had never initiated a single human interaction before signing. No demo request, no support thread, no reply to an outbound sequence. They read, they compared, they decided. The entire arc was silent.

Meanwhile, many of the loudest accounts — the ones filing feature requests, scheduling second and third calls, asking for custom proposals — churned within 90 days. Not all of them. But enough to notice that volume of contact and likelihood of success were less correlated than most teams assume.

The obvious read is that silent users are self-serve customers, and this is just a segmentation issue. Route them differently, build better onboarding, maybe add a chatbot. That framing isn't wrong, but it misses something important.

Silence isn't a channel preference. It's a posture. The person reading your changelog at 11pm on a Tuesday is doing something specific: they're evaluating without exposing themselves to a sales process. They've learned — probably from experience — that raising a hand means getting grabbed. So they stay quiet and watch. The silence is not passivity. It's protection.

When teams treat silence as an absence of signal, they do predictable things. They send re-engagement emails to people who are already engaged. They flag quiet accounts as at-risk when those accounts are simply deciding on their own schedule. They build scoring models that reward noise and penalize patience. The whole system starts to optimize for the wrong behavior — not usage, not understanding, but contact.

And contact is easy to generate. Anyone who's run outbound knows that. Getting someone to reply is a craft, but it's a craft that selects for responsiveness, not readiness. The person who replies "sure, let's chat" in four minutes is not necessarily closer to buying than the person who has quietly read every case study on your site.

One smaller thing worth noting: this pattern has a sharp edge. Some silent users are genuinely disengaged — they signed up, poked around, left. The difference is in the texture of the journey, not just the volume. A disengaged user's sessions are short, shallow, and clustered at the beginning. An engaged-but-silent user's sessions are spaced out, deeper, and often revisit the same high-stakes pages — pricing, integrations, security. The shape of the reading tells you what the silence means. A dashboard that only counts events can't distinguish between the two.

If your system doesn't know the difference between someone who's gone quiet and someone who's quietly paying close attention, it will treat both the same way. And the one paying attention will notice.