Clients go quiet, and nobody notices until it's late.

Service businesses and account teams that talk to clients across email, WhatsApp and Slack, and only notice a quiet client when they cancel or stop paying.

Usually seen inAgencies and account-managed businesses

First testWhen each client last heard from you

PracticeGTM

What you're probably seeing

If this sounds familiar, you're in the right place.

A client cancels, and looking back, they'd been quiet for weeks.
Conversations happen in WhatsApp groups, email and Slack, and nobody sees all of them.
Follow-ups depend on someone remembering.
Account managers can't say which clients need attention this week.
The CRM says one thing, and the chat history says another.

The usual ways out

What teams usually try. Each works somewhere. None works everywhere.

The way	Works when	The catch
Reminders in each person's calendar	There are few clients per person	Depends on people setting them, and keeping them
A CRM with tasks	The team logs every conversation	Most conversations never reach the CRM
A weekly account review	The team is small enough to cover everyone	Takes time, and looks back rather than ahead
A customer success platform	You have product usage data to score	Doesn't see chat-based relationships
An agent that watches your channels and flags silence	Clients talk to you in group chats	Needs care with privacy and with what it reads
Regular check-in messages to every client	Clients welcome contact	Feels automated if it isn't personal

What other companies did. Their published results, not ours.

We read each company's own write-up and asked one question: would our diagnostic's tests have led to the same call? We judge the approach, not the result.

Company	What they did	What they published	Source
GitLabPublic DevOps platform company whose customer success team publishes its process in an open handbook.	Built a health score in Gainsight (a customer success platform) in which 10% is engagement. Half of that is meeting cadence, based on how recently the last call or meeting with the customer took place. Limits differ by account priority: for top-priority accounts, more than 60 days since the last meeting is red; for the next tier, more than 90 days.	Not stated.They noted: CSM sentiment and timeline entries are manual inputs. Stale sentiment is cleared after 120 days, with a warning at 90. Several planned measures (events, NPS, CSAT) are not started yet.	Customer Health ScoringAug 2026
PostHogProduct analytics company with a customer success team. Scores paying or trialling accounts; accounts that have paid for under 4 months are not scored.	Computes a daily relationship score (0–100) from how recently each customer contacted it across Slack, support tickets, meetings and email (relative weights 30, 25, 25 and 25), banded from Strong to Dormant. Separately flags any product an active account has stopped using as 'went silent', meaning contact them this week.	Not stated.They noted: Contact is not sentiment: a customer who writes often but angrily still scores high. Accounts with few signals get unstable scores, and the relationship score is kept out of the main health score.	Customer health tracking - Handbook - PostHogUndated
ConsumerAffairsConsumer review marketplace with business clients. Customer data sat in a web of spreadsheets and other sources.	Moved to a customer success platform (ChurnZero) with real-time alerts for health changes and for accounts due a touchpoint, a simpler scoring method, and segments so smaller accounts got automated plays.	10% increase in retention year over year since implementation. Account-to-CSM ratio up 100%.They noted: Earlier customer success platforms were seen as cumbersome and hard to use.	ConsumerAffairs case study (ChurnZero)Apr 2024 · vendor story
HightouchCustomer data platform company, 201–500 employees, with over 300 shared Slack channels with customers.	Synced its customer Slack channels into its support tool (Intercom) through Pylon, so every question lands in one queue with response-time tracking while customers stay in Slack.	100 hours a month saved finding and tracking customer questions across Slack channels. 100% of support questions routed to one queue. 75% increase in the rate of customers self-serving into support from Slack. Timeframe not stated.They noted: Before the change, Slack conversations did not feed the team's reports, and engineering and sales could not see support issues.	How Hightouch scaled to over 300+ customer Slack channelsUndated · vendor story

Our read

Same call. Teams that handle this well measure the last contact on every channel and set different 'too quiet' limits for different accounts, which is what our tests check.

PostHog scores how recently each customer reached it across Slack, tickets, meetings and email, and GitLab sets 60- or 90-day limits by account priority; both match the tests on channels, last-contact dates and per-client limits. Hightouch's first step was getting 300+ Slack channels into one view. The weak spot in their own write-ups is capture: GitLab's CSM sentiment and timeline entries are manual inputs, and none of the pages says what the system may read, which we would still test.

What we would test first: Map where client conversations actually happen, channel by channel, and the last date of contact on each.

What the diagnostic would test

The tests that rule the wrong ways out.

On your own systems and data, read-only first. The number of tests sets the diagnostic's price, quoted before it starts.

1
Where client conversations actually happen, channel by channel.
2
The date each client last heard from you, and you from them.
3
What 'too quiet' means for different kinds of client.
4
Where the team would act on a reminder: Slack, email or the CRM.
5
What the system may read, and what it must not.

This week, without us

Three things you can do yourself.

1
List your clients and the date of your last real conversation with each.
2
Mark the ones you haven't spoken to in longer than your usual rhythm.
3
Message the three quietest today.

Sound like you? Bring it to a 30-minute call. We'll tell you which tests your case needs, and what they cost.

Back to every case

This page describes what teams in this situation commonly face. It is not a client story.