Most support teams track response time. Some track resolution time. Almost nobody tracks the metric that actually predicts churn: repeat contact rate.
If you run customer support for a growing business, this is worth five minutes of your attention today.
What Repeat Contact Rate Actually Measures
Repeat contact rate is the percentage of customers who contact you again about the same issue within a set window, usually 7 days.
It matters more than the metrics most teams already track, for a few specific reasons:
- A fast response that doesn’t actually fix the problem still counts as “resolved” in most dashboards
- A customer who has to ask twice has already started losing patience, even if neither contact took long to handle
- Repeat contacts are invisible in average handle time, they just look like two separate, unrelated tickets, so the real cost hides in plain sight
What a High Repeat Contact Rate Actually Tells You
A high repeat contact rate is rarely an agent skill problem. In our experience, it’s usually one of three things:
Agents are closing tickets to hit speed targets, not because the issue is actually fixed. When response time is the primary metric being measured, closing fast becomes the incentive, whether or not the underlying issue is genuinely resolved.
The knowledge base is outdated, so agents give confidently wrong answers. A wrong answer delivered quickly and confidently often looks identical to a right one, right up until the customer comes back.
Complex issues need a specialist, but there’s no clear escalation path, so a generalist takes a guess. Without a documented triage system, ambiguous cases get handled by whoever picks up the ticket, regardless of whether they’re actually equipped to solve it.
How to Start Tracking It This Week
You don’t need new software for a first pass at this. A basic first measurement takes under an hour:
- Pull last week’s support tickets
- Flag any customer who contacted you twice about the same topic within 7 days
- Calculate the percentage, that’s your baseline
Once you have a baseline, the more useful question becomes which of the three causes above is actually driving it, and that usually becomes clear after reading through a handful of the repeat-contact tickets themselves, not just the numbers.
Why This Matters More Than It Seems
Response time tells you how fast you replied. Repeat contact rate tells you whether you actually helped. Most support teams have spent years optimizing the wrong number, and the gap between “fast” and “actually helpful” is exactly where customer trust quietly erodes.
This becomes especially important as a business scales. A small team can compensate for missing metrics with institutional memory, everyone roughly knows which issues tend to recur. That advantage disappears as the team grows, new hires join, and volume increases, which is exactly when a measurable repeat contact rate becomes the difference between catching a systemic problem early and discovering it months later through customer churn.
If you want help setting up repeat contact tracking properly, and figuring out which of the three underlying causes is actually driving yours, book a free consultation and we’ll help you get a real baseline in place.