Definition
Customer Recontact Reason is the recorded explanation for why a customer contacts support again about an earlier question, request, or problem. Common reasons include an incomplete answer, a new issue, unclear instructions, or a promised follow-up that has not happened.
Why It Matters
Recording the reason for recontact helps managers distinguish between unresolved problems and genuinely new requests. Teams can use these patterns to improve replies, update internal guidance, refine routing, and give agents better context when a customer returns.
Real-Life Use Case
Online store support: A customer returns to live chat because an order-status answer did not explain a delivery delay. The agent records “unclear delivery explanation,” checks the latest order details, and gives a specific next step. The support team later uses similar records to improve its delivery responses.
FAQs
What is the difference between a recontact reason and a customer question?
A customer question describes what the customer asks now. A recontact reason explains why the new conversation happened in relation to an earlier interaction.
Who should record the customer recontact reason?
The agent handling the conversation can record it during or after the interaction, using a consistent set of reason categories.
Can one conversation have more than one recontact reason?
Yes. For example, a customer may return because the first answer was unclear and because the underlying issue remains unresolved. Teams should follow their chosen reporting rules when selecting primary and secondary reasons.
How can teams use this information?
Managers can review recurring reasons to identify coaching opportunities, unclear processes, missing information, or cases that need better follow-up.