In short: Recurring customer contacts — customers calling about the same problem multiple times — are one of the most costly patterns in customer service. They’re caused by incorrect diagnosis, incomplete resolution, or an underlying problem that customer service can’t fix. Here’s how telecom companies identify which cause it is, and what they do about it.
A customer calling for the second time about the same problem isn’t dissatisfied with the agent. They’re dissatisfied that the problem didn’t get resolved. And every time they call again, frustration increases — and so does the probability of churn.
Research shows that customer satisfaction drops from 86% to 42% when a case requires a repeat contact rather than being resolved at first contact. (Source: SQM Group, 2025) In telecom, with long contract periods and low switching costs, the difference shows up directly in churn figures.
Yet it’s one of the least analyzed challenges in the industry.
*Källa: Source: SQM Group, 2025
What is a repeat contact, and why does it matter?
A repeat contact is when a customer reaches out about substantially the same issue more than once within a short period — typically 14–30 days. It could be the exact same question. It could be an escalation of a case that was considered resolved but wasn’t.
Repeat contacts are problematic for three reasons:
-
The cost is double. Every extra contact is agent time that wouldn’t have been needed if the underlying problem had been solved on the first occasion.
-
NPS and CSAT decline. Customers who call multiple times about the same issue give systematically lower satisfaction scores, regardless of how well the individual conversation was handled.
-
Churn probability increases. A customer who repeatedly doesn’t get their problem resolved is a customer who is actively considering switching providers.
Every conversation reveals a pattern
Lina Bjelkmar, CEO of Indicate me, described this same principle in a column in Techtidningen about why customer insights are becoming increasingly important:
"That's because every conversation reveals a pattern. Maybe it's a recurring question about billing, or a recurring fault in a product. Maybe it shows that customers are dissatisfied with a new service, or that something in the process isn't quite working."
Read the full column in Techtidningen
This is exactly the logic that makes repeat contacts worth analyzing systematically. A single call doesn't say much. But ten, fifty, or a hundred calls about the same issue, seen together, point to exactly where the process is breaking down, whether that's a diagnosis that keeps missing the mark, a fix that isn't implemented correctly, or a root cause that CS alone can't resolve.
How AI analysis reveals the causes
There are three main causes of repeat contacts in telecom. They often look the same on the surface but require completely different actions.
Cause 1: Incorrect diagnosis on the first contact. The agent identified the wrong problem and resolved it. The real problem persisted. This isn’t visible in the case logs, but it’s visible in the next call if you look at what the customer actually describes.
Cause 2: The solution wasn’t implemented correctly. The problem was identified correctly, but the technical action — configuration change, activation, or setting — went wrong or took too long. The customer calls back when they notice nothing has changed.
Cause 3: The underlying problem can’t be resolved by customer service. The real problem lies in a technical system, a service limitation, or a product shortcoming that customer service can’t fix. The customer contacts again and again hoping for a different solution.
Cause 3 is the most important to identify, and the one AI analysis is best at catching. If ten customers in a row call about a specific mobile service and none of them get a lasting resolution, that’s a pattern signaling a product or network problem. The customer service manager should flag it to IT.
How do you reduce repeat contacts systematically?
It’s not enough to ask agents to “resolve problems better on the first contact”. That individualizes a structural problem.
Systematic reduction requires:
- Identify which case types generate the most repeat contacts. Not all categories are equally prone. Billing questions are often resolved at first contact. Technical problems rarely are.
- Analyze the specific causes for each case type. Is it caused by diagnosis errors, implementation problems, or an unresolvable underlying problem?
- Adapt the action to the cause. Diagnosis errors are solved with better training and decision support for agents. Implementation problems are solved with better processes and verification steps. Unresolvable underlying problems are escalated to IT or product.
- Measure the effect. Repeat contact rate per case category should decrease if the actions are correct.
What it requires of the customer service manager
The customer service manager who wants to reduce repeat contacts systematically needs to be able to answer one question: which cases are “chronically unresolved” — cases that customers return about regardless of what customer service does?
These are the cases that require escalation up in the organization. And it’s in that escalation that the customer service manager exercises influence beyond their own department.
Identifying and flagging structurally unresolvable issues is one of the most strategic things a customer service manager can do. It affects the customer experience, cost control, and the manager’s position in the organization.
FAQ
How do you define “repeat contact” in customer service?
The most common definition is a customer who contacts about substantially the same issue more than once within 30 days. The exact definition should be adapted to the industry and typical case cycle. For telecom, 14 days may be more relevant.
What is a normal repeat contact rate in telecom?
It varies significantly depending on the company and case mix, but around 10–20% is common. Companies with a strong first-contact resolution culture can be below 10%. Repeat rates above 25% indicate structural problems.
Can AI directly prevent repeat contacts?
AI can flag calls with a high probability of generating follow-up contacts, based on patterns in the conversation. This gives the agent the opportunity to proactively address underlying issues during the call, rather than waiting for the customer to call back.
Want to know which cases are driving your repeat contacts and why?
