First response time is the most measured number in customer communication, and for support queues it is a reasonable one. A stranger with a broken thing wants speed above almost everything, and the dashboards in tools like Front, Hiver, and Help Scout are built to report exactly that one number. The trouble starts when account teams, whose job is relationships rather than resolutions, inherit the same scoreboard because it came with the tool.
Here is the uncomfortable scenario every account lead recognizes: a team answering every email within the hour, hitting green on every SLA, while an account slides toward the exit. Fast replies to the emails that arrive say nothing about the promise made three weeks ago, the question nobody addressed, or the client who stopped writing altogether. You can sprint to every ball that comes over the net and still lose the match on the balls that never came.
What does reply speed actually measure?
It measures reactive throughput: how quickly the team processes inbound. That is a real operational quality, and account teams should not be slow. But retention does not hinge on throughput. It hinges on whether the client feels remembered, whether commitments land, and whether the relationship has forward motion. None of that appears in a response-time histogram, and a team optimizing the histogram can drift into exactly the behavior that loses accounts: shallow, fast replies that close threads without closing loops.
A better scoreboard: three relationship metrics
- Commitment follow-through rate. Of the promises the team made in email this month, how many landed on time? This is trust, quantified. Most teams have never seen their number, and the first measurement is usually sobering.
- Open question age. How many client questions are currently unanswered, and how old is the oldest? Not threads awaiting reply, questions, including the ones buried inside threads that look handled.
- Cadence health. For each named account, how does current contact rhythm compare to that relationship's own baseline, and is the relationship warming up or cooling down? The count of accounts running meaningfully below their normal rhythm is the closest thing to a churn early-warning number that exists.
Notice what these have in common: none of them can be gamed by replying faster, and all of them measure the outbound half of the relationship, which reply-time metrics ignore entirely.
The measurement problem, and the honest answer
The obvious objection is that these three numbers are brutal to compute by hand. Commitments live in prose, open questions hide inside answered threads, and cadence baselines require history nobody has time to reconstruct. That objection is correct, and it is why the metrics stayed unmeasured for two decades while reply speed, which falls out of timestamps for free, became the industry scoreboard. We measure what is easy, then manage what we measure.
It is also, transparently, why we built Sektra the way we did. Because it reads the team's shared Gmail, it extracts the commitments, tracks the questions, and knows each account's rhythm, which makes the three relationship metrics fall out as a byproduct of the inbox rather than a reporting project. The morning digest is effectively this scoreboard turned into a to-do list: what is due, what is aging, who has gone quiet, ranked with reasons.
Keep answering fast. Speed is politeness. Just stop pretending it is the score. The score is whether Friday's promise arrived on Friday, and whether anyone noticed the client who stopped calling.
