Repeat Contact Rate
Definition
Repeat Contact Rate
Repeat contact rate is the share of customers who come back about the same issue within a set window. It is the honest counterpart to first contact resolution, because it counts what happened rather than what an agent recorded in the notes.
First contact resolution relies on someone marking a case as solved. Repeat contact rate waits to see whether the customer agrees.
The two rarely match. A team reporting 82% first contact resolution with a 26% repeat rate has a measurement problem — not a performance mystery.
Repeats also cost twice. The second contact consumes handling time that was already paid for once — and it arrives with a more frustrated customer attached.
Key takeaways
- Repeat contact rate counts customers returning about the same issue inside a fixed window.
- It is observed rather than self-reported, so it cannot be marked resolved optimistically.
- Window length changes the number substantially and must be fixed before measuring.
- Matching repeats to an original issue requires linked cases, not just matching customer records.
How it works
Count contacts arriving in a period that relate to an issue the same customer raised earlier, then divide by total contacts. The window decides which returns count, and it has to be set before any measurement begins.
Linking is the hard part. Without case threading, a second contact about the same problem looks identical to a new one.
| Window | What it captures | Best suited to |
|---|---|---|
| 24 hours | Immediate failures and incomplete answers | Live chat and phone support |
| 7 days | Fixes that did not hold | Technical and billing issues |
| 30 days | Recurring underlying faults | Product defects and account problems |
| 90 days | Systemic issues and policy gaps | Executive reporting |
Longer windows always produce higher rates. A team quoting 6% on a 24-hour window and one quoting 19% on 30 days may be performing identically.
Federal service measurement takes the same view of repeat effort. The customer experience programme at Performance.gov treats the burden a service places on people as a measurable quality problem in its own right.
Satisfaction research points the same way. The American Customer Satisfaction Index argues that satisfaction strengthens retention and, through it, financial performance — and nothing erodes satisfaction faster than having to explain the same problem twice.
Examples
Repeat patterns differ by channel, issue type, and how much authority the first agent holds. Four cases show where the returning contacts actually come from.
A Manila billing support desk. First contact resolution was reported at 84% while the seven-day repeat rate sat at 21%. Two thirds of repeats followed answers agents were not authorised to complete.
A broadband technical line. Repeats within 24 hours ran at 11%, almost all from fixes that required a router restart the customer never performed. A follow-up text cut the rate by half.
An insurance claims team. The 30-day window exposed a document requirement never mentioned on the first call. Changing one script line removed 400 repeat contacts a month.
A retail chat channel. Repeats were invisible because chats were not threaded to customer records. Linking them raised the measured rate from 4% to 17% overnight.
Related terms
Repeat contact rate sits beside the resolution measures it is designed to validate. The terms below cover the claims it tests and the costs it exposes.
- First Contact Resolution: the self-reported measure repeats are used to check.
- First Call Resolution: the voice-channel version of the same claim.
- Contacts Resolved on the First Contact: the raw count behind that percentage.
- Cost per Contact: the figure that prices every avoidable repeat.
- Customer Satisfaction Rating (CSAT): the outside signal repeats damage first.
- Escalation: the route many repeat contacts end up taking.
- Key Performance Indicator (KPI): the reporting family the rate belongs to.
FAQ
What is a good repeat contact rate?
Most support operations target below 10% on a seven-day window, with technical support running higher. Always check the window before comparing two figures.
How is it different from first contact resolution?
First contact resolution is recorded by the agent, while repeat contact rate is observed from actual customer behaviour. The second is much harder to game.
What window should be used?
Seven days suits most support work, balancing genuine repeats against unrelated new issues. Fix the window and keep it stable across reporting periods.
How are repeats identified?
By threading cases to a customer record and comparing issue categories. Without linked cases the measure cannot be calculated reliably.
Do repeats always mean poor quality?
No. Some reflect genuinely new questions in the same category, which is why category matching matters as much as customer matching.
Who should own the measure?
Operations owns the result and quality owns the matching rules. Splitting them keeps the definition from drifting.
Compare support teams and their published resolution records across the Outsource Accelerator BPO hubs.
Independent
