Repeat Contact Rate Calculator
Measure how many inbound contacts are customers coming back about the same issue. Then see how much handling work those repeats represent.
A free tool for contact center teams. Also useful for measuring repeat call rate or recontact rate, provided you use the same definition. No signup required.
How many contacts are repeats?
Enter your total incoming contacts and the number that were follow-ups about the same issue. Use the same reporting period for both figures.
1,500 of 10,000 incoming contacts are repeat interactions about the same issue, using a 7-day lookback window.
Lookback or channel selection changed. The entered counts were not filtered. Make sure both figures reflect this selection.
What do repeat contacts mean for workload?All inbound channels · 7-day lookback
Enter an average handle time or cost per contact on the left to quantify the workload associated with these repeats.
These figures describe recorded repeat-contact workload, not preventable time or guaranteed cash savings.
Count the incoming repeat contact, not the initial contact or separate transfer legs. Compare like-for-like periods.
How to calculate repeat contact rate
Choose a reporting period, then flag each incoming interaction as a repeat if the same customer previously contacted you about the same issue within the selected lookback window.
Use a consistent denominator. A transferred call is not automatically a second customer contact. Look back before the start of the reporting period so early-period repeats are not missed.
Repeat contact rate formula
Repeat contact rate (%) = same-issue repeat inbound contacts ÷ total inbound contacts × 100
This is the share of contact volume that is repeated work. It is not the percentage of resolved cases that later recontact you, and it is not simply 100 minus FCR. Decide whether your report includes voice only or all inbound channels.
| Input | Value |
|---|---|
| Total inbound contacts | 10,000 |
| Same-issue repeats received | 1,500 |
| Lookback window | 7 days |
| Non-repeat inbound contacts | 8,500 |
| Repeat contact rate | 15.0% |
1,500 ÷ 10,000 × 100 = 15%. This example is illustrative and is not presented as an industry benchmark.
Repeat-contact benchmarks
There isn’t a single benchmark that fits every contact center. Rates depend on which channels you include, how you identify a repeat, and how far back you look.
Compare results using consistent rules, then investigate the customer journeys driving repeat demand.
Why do customers need to contact you again?
Select one common reason your customers return. See which part of the journey to review and what a team could verify before deciding on an improvement.
Visual guidance can be useful when customers cannot show, understand or complete a task. It is not a substitute for fixing broken handoffs or delayed decisions.
Select a reason to explore
Choose the cause that best matches the repeat contacts in your data. You'll see a starting point for an operational review.
This is a quick review guide, not an automated diagnosis. Actual causes need to be checked against real customer journeys.
What do repeat contacts add to the workload?
Repeat contacts consume time that could otherwise go toward new issues. Add your real handling time or cost in Advanced mode to quantify that workload, rather than assuming every repeat is preventable.
The work behind the repeat rate
These are incoming contacts your team handled more than once for the same issue. Some may be necessary follow-ups. Review why they occurred before labeling them avoidable.
Add your average handle time in Advanced mode to estimate the handling hours associated with repeats.
How to find repeat contacts in your CRM data
Start with your contact history, not a target percentage. You need a consistent way to connect interactions to the same customer and issue, including when someone switches channels.
Link incoming interactions to a customer
Use a stable CRM customer ID or approved matching method and a timestamp. Account for a customer who starts on chat then calls back. Avoid using names alone where duplicates are possible.
Match the same issue across channels
Compare ticket or case IDs and contact reasons. A new question from the same customer is not a repeat of the original issue. Cross-channel linkage matters.
Apply a consistent lookback window
Check whether an earlier same-issue contact occurred within 7 days, or another window suitable for your process. Include contacts from before the reporting period so early repeats aren’t missed.
Review a sample and count the resulting repeats
Exclude internal transfers and duplicate event records. Separate planned follow-ups from unresolved work. Count flagged inbound repeat interactions, then divide by total inbound interactions in the period.
Example: Monday chat about a faulty router = initial contact. Wednesday call about the same router fault = one repeat. Thursday question about a new invoice = a different issue, not another repeat of the router fault. Count all three inbound interactions in the reporting period if they fall inside it.
Repeat contact rate, recontact rate and other names
These terms overlap, but their denominators, lookback windows and matching rules differ. Check what your CRM or contact center platform actually reports before comparing percentages.
Repeat contact rate / repeat call rate
Repeat contact rate usually covers incoming interactions across channels. Repeat call rate or call repeat rate applies the same idea to phone calls only. Peopleware and Zoom use the repeat-call terminology.
Recontact rate and repeat caller rate
Recontact rate may mean resolved cases that generated another same-issue contact, rather than repeat interactions divided by all incoming contacts. Repeat caller rate can count unique customers, not every repeated interaction.
Next contact avoidance (NCA)
Genesys tracks whether a customer makes any subsequent contact within seven days, even about a different issue. Its Next Contact Avoidance percentage is therefore not the inverse of this calculator’s same-issue repeat-contact rate.
Ticket reopen rate and FCR
Ticket reopen rate counts records reopened after being solved; a customer may create a new ticket instead. Some Sprinklr configurations define RCR as 100 − FCR. That is a product-specific method, not a substitute for counting observed same-issue repeat contacts.
Repeat contact rate FAQs
Definitions vary between reporting tools. These answers explain what this calculator counts and where another system may differ.
What is the difference between repeat contact rate and repeat call rate?
Repeat call rate applies to phone calls. Repeat contact rate can include phone, chat, messaging and other inbound channels when those interactions are linked to the same customer and issue.
Is repeat contact rate the same as 100% minus first contact resolution?
Not necessarily. FCR is usually measured around resolution on the initial contact, and vendor definitions differ. This calculator measures the proportion of all incoming interactions that were same-issue follow-ups within a selected lookback window.
How long should a repeat-contact lookback window be?
Seven days is a practical example, not a universal standard. Select a window appropriate for the journey and use it consistently; equipment replacements or complex processes may need longer periods.
Do transferred calls and unrelated customer questions count as repeats?
No. A transfer is not automatically another inbound customer contact. A later contact about a separate issue is not a same-issue repeat.
Does a high repeat contact rate mean all those contacts could be avoided?
No. Some follow-ups are planned or necessary. Check real customer interactions to separate unresolved tasks, process delays and intentional next steps before estimating avoidable work.
Related tools
Measure first-contact resolution separately. It answers a different question than observed repeat volume.
Understand handling time for repeat issues, including talk, hold and wrap-up.
See what an inbound call costs before estimating the value of repeat work.
Methodology and sources
Grypp calculation: same-issue repeat inbound interactions recorded in the reporting period ÷ all inbound interactions in that period × 100. The repeat indicator is based on your own records matching each contact to a prior contact from the same customer about the same issue inside a fixed lookback window. Changing the displayed window or channel selector does not filter or retrieve records; enter source counts that already match those rules. For contacts early in the reporting period, include earlier interaction history. Do not count call transfers as separate inbound customer contacts or unrelated issues as repeats.
Definition references: Call Centre Helper, repeat call measurement; Sprinklr, FCR and RCR configuration; Genesys, Next Contact Avoidance; Zendesk, reopened tickets. Handling hours and contact costs are calculations from user-supplied inputs, not predicted savings or Grypp performance.
Diagnostic: the interactive reasons and review suggestions are illustrative, not automatically detected root causes or evidence of preventable contacts. This page does not transmit entered figures to Grypp; the copy feature produces a local text summary for you to share if you choose.