Repeat Contact Analysis measures how often customers come back to support after an issue should have been resolved. It helps CX teams understand failed resolutions, unclear communication, broken processes, and product problems that keep customers from completing their goal.

Repeat contact is a strong signal of customer effort. A customer who contacts support three times about one delivery, refund, or account issue is experiencing friction even if each individual interaction receives a passing QA score.

What Repeat Contact Analysis Looks For: - Multiple contacts from the same customer in a defined time window - Related intents across channels - Prior unresolved cases or callbacks - Escalations after failed AI or human support - Contact reasons with high recurrence

Why It Matters: Reducing repeat contacts lowers support cost and improves customer experience. It also reveals where QA, VoC, and operational metrics should be connected rather than reviewed in isolation.

Examples

A customer contacts chat, email, and phone about the same refund within five days.
An AI agent marks an issue resolved, but the customer returns the next day with the same complaint.
A support leader finds that address-change issues have a high repeat contact rate.

FAQs

What causes repeat contacts?

Common causes include incomplete resolution, unclear communication, missing follow-up, broken workflows, inaccurate AI responses, and product or policy friction.

Is repeat contact the same as FCR?

No. FCR measures whether an issue was resolved on the first contact. Repeat contact analysis investigates the patterns and causes behind customers returning after support interactions.