Repeat Contact Rate

What is Repeat Contact Rate?

Repeat Contact Rate (RCR) is a KPI that measures the percentage of customers contacting customer support multiple times within a specified period (typically 24 hours to 30 days) about the same issue or related concerns. The higher this metric, the more likely first-contact resolution failed. In other words, RCR functions as an inverse indicator of “customer satisfaction” and “support quality,” helping identify priority areas for improvement.

In a nutshell: “The percentage of customers contacting us multiple times about the same problem.” Lower is better—it’s proof that first-contact handling worked well.

Key points:

• What it does: Quantitatively measure support quality
• Why it matters: Customers contacting repeatedly signal process or skill issues
• Who uses it: Customer Service managers, QA teams, contact center operators

Calculation Method

RCR = (Number of customers re-contacting about same issue ÷ Total initial contacts) × 100

Concrete example: Out of 1,000 monthly initial inquiries, 120 were re-contacts from the same customers; therefore RCR = 12%

Benchmarks and Standards

Performance varies significantly by industry and issue complexity, so setting appropriate benchmarks based on your organization’s historical data is important.

Why It Matters

High RCR frustrates customers through forced multiple contacts, eroding brand trust. It also increases costs by requiring multiple responses to the same issue, reducing operational efficiency. Conversely, lowering RCR improves both customer satisfaction and support staff workload.

How It Works

RCR measurement requires identifying “whether the contact is from the same customer.” Link multiple touchpoints (phone, email, chat) to a single person using customer database identification. Next, issue classification systems determine “is this the same problem or different?” and set time windows (e.g., within 24 hours) for counting. Automated tracking systems mark instances within the set period as “repeat,” notify supervisors, and enable immediate quality improvements.

Real-World Use Cases

Telecom Support Quality Improvement Discovering high repeat contacts for line trouble issues. Root cause analysis reveals technical staff provide workarounds rather than identifying root causes in single contacts. Strengthened training improves resolution.

Financial Institution Review Process Improvement Discovering “application review status” inquiries comprised most repeat contacts. Implement automatic status update emails for advance notification, and RCR drops from 20% to 8%.

E-commerce Return Process Optimization High repeat rate for return inquiries prompted self-service introduction allowing customers to check return progress directly. Customer service re-contact drops 40%.

Benefits and Considerations

Improving RCR simultaneously increases customer satisfaction and operational efficiency. However, ensure that agents don’t compromise resolution quality just to lower numbers. Parallel evaluation system improvements are critical.

Related Terms

• First Contact Resolution — The inverse indicator of RCR; higher FCR means lower RCR
• Customer Satisfaction — Satisfaction metric correlated with RCR
• Customer Experience — Making customers contact multiple times damages experience
• Process Improvement — Improving issues identified from repeat rates
• Quality Assurance — Continuous monitoring of support quality

Frequently Asked Questions

Q: What period is best for measuring RCR?

A: Depends on issue type. Recommend measuring technical support over 24 hours, general issues over 7 days, and complex cases over 30 days in parallel.

Q: How do we distinguish legitimate re-contact from true repeat?

A: If first response promises “answer within 3 business days,” subsequent progress inquiries should be marked “legitimate re-contact.” Create rules clarifying this.

Q: RCR isn’t improving. What do we do?

A: Determine if issues stem from insufficient staff skills or incomplete knowledge base; root causes require different solutions. Qualitative feedback collection is also important.