Signals in Email & Slack · 7 signals

The churn signals hiding in email & slack.

Gmail, Outlook, Slack Connect — the relationship layer: reply times, thread participants, ritual engagement.

Why this source matters

Responsiveness is a measurable proxy for priority. You can compute exactly where you rank in a champion's week — and watch the rank change before the contract does. Participation patterns reveal committee dynamics no survey captures.

Email & SlackTypical lead time: 60–120 daysFalse-positive risk: High

Champion reply latency doubles

The champion's median email reply time doubles versus their baseline. Responsiveness is a proxy for priority — you can measure exactly where you rank in their week.

Detection logic

Compute median reply latency per champion per month from email metadata. Flag 2x baseline sustained over 60 days.

When it lies to you

Busy quarters, board prep, and reorgs slow everyone down. Compare against the champion's peers, not just their history.

Email & SlackTypical lead time: 60–120 daysFalse-positive risk: High

Thread participants shrink

Email threads that used to include five colleagues now include one. The buying committee is disbanding — or the conversation moved somewhere you're not invited.

Detection logic

Track average distinct participants per account thread per quarter. Flag 40%+ contraction sustained over a quarter.

When it lies to you

Streamlined communication is sometimes just efficiency. Check whether the missing participants left the company or just the thread.

Email & SlackTypical lead time: 60–120 daysFalse-positive risk: Medium

QBRs and business reviews skipped

QBRs get declined, rescheduled into oblivion, or attended by substitutes. Customers who see value protect the review; customers who don't, don't.

Detection logic

Track QBR/business-review completion rate per account vs plan. Flag 2 consecutive missed or downgraded reviews.

When it lies to you

Calendar collisions are real, especially in December and August. Require the pattern across two quarters before flagging.

Email & SlackTypical lead time: 30–90 daysFalse-positive risk: Medium

Shared Slack channel goes quiet

Messages per week in the shared Slack Connect channel drop 70%+ from baseline. The informal channel dying means the relationship moved — or ended — elsewhere.

Detection logic

Count messages per week in shared channels per account. Flag 70%+ drops sustained 4+ weeks.

When it lies to you

Teams migrate channels, especially after reorgs. Verify the channel is actually the live one before reading silence as signal.

Email & SlackTypical lead time: 30–90 daysFalse-positive risk: High

Unknown evaluator looped into threads

A new address — often from a different department or an unknown domain — starts asking pointed questions in existing threads. Evaluations announce themselves in CC lines before they announce themselves in RFPs.

Detection logic

Flag first-time participants on established account threads whose messages contain evaluation-pattern questions (capabilities, pricing, terms, references).

When it lies to you

New hires genuinely need onboarding. Evaluators ask about commercial terms and alternatives; new users ask about workflows.

Email & SlackTypical lead time: 60–180 daysFalse-positive risk: Medium

Detractor feedback goes unanswered

An NPS detractor or negative CSAT response gets no meaningful follow-up within two weeks. The survey asked for honesty; silence in return teaches the customer that feedback goes nowhere.

Detection logic

Join survey responses to follow-up activities. Flag detractor responses with no logged outreach within 14 days.

When it lies to you

Survey fatigue produces low-effort detractor scores that don't reflect real sentiment. Weight written comments far above bare scores.

Email & SlackTypical lead time: 14–60 daysFalse-positive risk: Low

Renewal conversation moves to procurement only

The commercial thread leaves your users and lands solely with procurement. When the conversation becomes purely about price and terms, the value case has already been lost — or was never made.

Detection logic

Track participant roles on renewal-related threads. Flag when business users drop out and only procurement/finance remain for 3+ exchanges.

When it lies to you

Some companies route all renewals through procurement by policy. Establish the account's normal pattern before flagging the shift.

How to instrument it

Median reply latency per champion per month, distinct participants per thread per quarter, QBR and business-review completion vs plan, and message volume in shared channels. Metadata and patterns — not message content — carry most of the signal.

Common pitfalls

This is the most privacy-sensitive source: analyze metadata and aggregate patterns, be transparent about it, and stay inside your data-processing agreements. Busy quarters slow everyone down — compare champions against their peers, not just their history.

Signals in the other sources

CRM Call transcripts Support tickets Product usage Billing & payments

Get your free Account Risk Snapshot

We run signals like these against your 20 riskiest accounts — before you sign anything.