Repeat Contact Rate

The percentage of customers who reach out more than once about the same unresolved issue within a defined window.

What Is Repeat Contact Rate?

Repeat contact rate is the percentage of customers who contact support more than once within a defined time window about the same unresolved issue. It is the direct inverse of first contact resolution (FCR): if an organization's FCR rate is 70%, its repeat contact rate is approximately 30%.

The measurement window is typically 7 to 30 days. A customer who calls Monday about a billing error and calls again Thursday about the same billing error represents a repeat contact. A customer who calls Monday about a billing error and calls three months later about a shipping problem does not.

Repeat contact rate is one of the most operationally consequential metrics in customer service because it simultaneously affects customer experience, agent workload, and unit economics. Every repeat contact means a customer had a problem that was not resolved on the first attempt, generating dissatisfaction and additional cost.

How Repeat Contact Rate Is Calculated

Formula: Repeat Contact Rate = (Repeat contacts within the defined window / Total contacts in the period) x 100. Accurate calculation requires linking contacts to individual customers and tagging them by issue type or case ID. Contact centers that lack customer identity resolution across channels often undercount repeat contacts.

Research shows that the industry average FCR rate is approximately 70%, implying a repeat contact rate of roughly 30%. That means nearly one in three contacts is a repeat, representing a significant opportunity for cost reduction and satisfaction improvement.

Root Causes of High Repeat Contact Rate

Root CauseWhat It IndicatesFix Category
Agent lacked the knowledge to resolve the issueTraining or knowledge base gap; agent gave incomplete or incorrect informationTraining / knowledge management
Customer was unclear on next steps after the interactionCommunication gap; resolution was delivered but not effectively explainedCommunication quality / scripting
Promised follow-up was not completed on timeProcess gap; callback, email, or action item fell through the cracksWorkflow / case management
The issue recurred after an initial fixProduct or systemic defect; root cause was not addressed, only the symptomProduct / engineering escalation
Customer self-resolved differently but contacted to confirmSelf-service gap; customers lack confidence in available self-service resourcesSelf-service / knowledge base

Why Repeat Contact Rate Matters

Each repeat contact effectively doubles the per-issue cost. A contact that costs eight dollars to handle generates sixteen dollars of cost when it requires a second interaction. Across thousands of daily contacts, the cumulative expense is substantial. Reducing repeat contact rate is one of the highest-ROI initiatives available to a contact center operations team.

Repeat contact rate also reveals where cost per contact calculations understate true issue resolution cost. A metric that measures cost per contact without accounting for repeat contacts will systematically underestimate the resource investment required to fully close customer issues.

How to Reduce Repeat Contact Rate

Repeat contacts rarely have a single cause. These four interventions target the most common failure points across knowledge, communication, workflow, and product quality.

1. Improve Agent Knowledge Access

Invest in a well-structured, up-to-date knowledge base that surfaces relevant articles during active interactions, reducing the frequency of incorrect or incomplete resolutions.

2. Confirm Resolution Before Closing Cases

Train agents to verify, not assume, that the customer's issue is resolved before closing the interaction. A simple closing confirmation question reduces premature case closures that generate callbacks.

3. Build and Enforce Follow-Up Workflows

When resolution requires a follow-up action, the case should not close until that action is complete. Automated task tracking and reminder workflows ensure committed actions are not lost between handoffs.

4. Route Systemic Root Causes to Product and Engineering

If repeat contact analysis reveals that a specific product feature or process step is generating a disproportionate share of repeat contacts, that finding belongs in a product or operations review, not just a coaching session.

Repeat Contact Rate and AI

AI reduces repeat contact rate through two primary mechanisms: improving first-contact resolution quality and enabling proactive outreach before customers need to call back. On the resolution quality side, AI-powered agent assist surfaces relevant knowledge, recommends next best actions, and flags when an agent's proposed resolution is inconsistent with established procedures.

Gartner predicts that agentic AI will autonomously resolve 80% of common customer service issues without human intervention by 2029, which would dramatically reduce both repeat contact volume and the resolution variability that drives it.

Related Terms

Related Terms

  • Call Routing

    Call routing is the process of directing inbound calls to the most appropriate agent, team, or automated system based on rules defined by the contact center. Effective routing reduces wait times, improves first contact resolution, and ensures customers reach someone with the right skills to help them.

  • Customer Churn Rate

    The percentage of customers who stop doing business with a company over a defined period; the most direct measure of retention failure and a leading indicator of revenue erosion.

  • Customer Retention Rate

    Customer retention rate measures the percentage of customers a business keeps over a defined time period, relative to the number it had at the start. It is one of the most direct indicators of customer satisfaction and long-term business health, with even small improvements compounding into significant revenue gains.

  • Service Desk

    A centralized function that acts as the primary point of contact between an organization and its internal or external users for managing incidents, service requests, and information needs is more formal in scope than a basic help desk. Rooted in ITIL (Information Technology Infrastructure Library) principles, this model emphasizes structured processes, service catalogues, and defined response commitments rather than ad-hoc issue resolution. Understanding where this model fits, and where it doesn't, is essential for any organization designing its support function.

See these concepts in action with Kustomer.

Request a Demo