Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Repeat Contact

A customer contacting the business again about the same problem, the clearest sign that the first answer did not end the customer's work.
AnalyticsconceptUpdated

Definition

A repeat contact is a customer contacting the business again about the same problem. The guide to reducing customer effort puts it in effort terms: a customer who comes back about the same problem has spent effort twice, and repeat contacts are the clearest evidence because they show the first contact did not end the customer's work.

Two choices turn the idea into something countable. The first is "the same problem": the contact must be about the issue already raised, not a new question from the same person. The second is the window: the guide to customer service metrics counts customers who get in touch again about the same problem within a set window, which the business chooses and then keeps fixed so the figure can be compared over time. Where the count is expressed as a share of contacts, it is sometimes called the repeat contact rate.

Why repeat contacts expose fast non-answers

Most service dashboards lead with speed, and speed is easy to improve in ways that do not help. A quick acknowledgement that answers nothing, or an automatic message that stops the clock, makes time to first reply look better while the customer waits longer for an answer. The support channels and self-service guide names the trap directly: a fast reply that does not solve the problem starts the clock again, and repeat contacts are the clearest sign of a channel answering quickly but badly.

So the service metrics guide pairs them. Time to first reply is read beside repeat contacts by reason, and time to resolution beside reopened and repeat contacts, because closing a case early shortens resolution and creates repeats. The same logic applies to automation. The guide to AI in customer service rejects deflection as an assistant's measure and judges resolution by the absence of a repeat contact on the same subject within a set window.

A repeat contact has a blind spot. A customer who gives up instead of coming back does not appear in it, so the metrics guide reads it with satisfaction or effort by reason rather than alone.

In practice: counting by original reason

Repeat contacts become useful when they can be traced to a cause. The tutorial on tagging support contacts by reason asks agents to keep the original reason when the same customer comes back about the same problem, so repeat contacts are counted by reason rather than disappearing into general categories. Tagging the second contact as a new reason is the mistake the metrics guide warns against.

Once counted by reason, the question is what happened in between. The effort guide suggests looking for a promised call-back that never came, an answer that did not solve the problem or a transfer that lost the history.

Illustrative example — not a real result

A broadband provider finds the step its saved reply skipped

Prilpove Broadband answered email within 2 hours on average and was pleased with it. But 1,240 customers contacted it about router set-up in a quarter, and 410 of them got in touch again about the same problem within 7 days. Because agents now kept the original reason on returning contacts, router set-up stood out as the reason with the most repeats. Reading a sample showed why: the saved reply for set-up told customers to restart the router but skipped the step of linking it to their account in the app, so the connection never activated. The team added the missing step and a link to the app guide. The next quarter, router set-up repeats within 7 days fell to 120, while first reply time stayed the same.

Contact Rate counts how often customers need help at all; repeat contacts count how often the help did not work. Both are read by Contact Reason, and a repeat keeps the reason of the first contact so it is not mistaken for a new problem. A Saved Reply that leaves out a step can produce repeats at scale, because every agent who uses it sends the same gap.

Common confusions

  • A closed case is a solved case. Closing early shortens resolution time and creates repeats. The customer's return is the test.
  • Any second contact from a customer is a repeat. Only a contact about the same problem counts. A new question is a new contact.
  • Fewer repeats always means better service. Customers who give up do not come back, so repeats are read with satisfaction or effort by reason.
  • A returning contact gets a new reason. Keeping the original reason is what makes repeats countable by cause.
  • Matching duplicate enquiries in a CRM is the same thing. That is a data task about records. A repeat contact is about a customer whose problem was not solved.

More terms to look up

Where this term is used

Related