Solved on First Contact
Definition
Solved on First Contact
Solved on first contact describes an enquiry fully resolved in a single interaction, with no callback, transfer, or follow up needed. It is one contact, one resolution, judged from the customer’s side of the conversation rather than from the agent’s notes.
The phrase is the plain English form of first contact resolution. Support teams use both, and the underlying measure is the same.
Its appeal is simple — every repeat contact costs money twice and erodes trust once.
The difficulty is verification — an agent marking their own work as solved is the weakest possible evidence that it was.
Key takeaways
- Solved on first contact means one interaction fully resolved the customer’s issue.
- Verification through a repeat contact window beats agent self reporting every time.
- A window of seven days is the common standard across support operations.
- Rates above 90% usually indicate a measurement problem rather than excellent service.
How it works
Count contacts resolved without any further contact from the same customer about the same issue inside a defined window, then divide by total contacts. Seven days is the usual window, long enough to catch a failed fix and short enough to keep reporting current.
Issue matching is the hard part. A customer calling back about something genuinely different should not count against the first contact.
| Element | What it sets | Common practice |
|---|---|---|
| Window | Time allowed for a repeat | 7 days across most operations |
| Matching rule | What counts as the same issue | Same case reference or same reason code |
| Channel scope | Which channels are counted | All channels, matched by customer identity |
| Verification | How resolution is confirmed | System data, not agent self marking |
Government service work treats this as central. Digital.gov frames customer experience as the sum of the public’s interactions with a service, which makes repeat contact a direct measure of failure.
Satisfaction data provides the outside check. The American Customer Satisfaction Index is the only national cross industry satisfaction measure in the United States, and a first contact figure that rises while satisfaction falls is not telling the truth.
Verification is worth what it costs. Teams moving from self reporting to system matching almost always see the number fall first, and that drop is a measurement correction rather than a decline in service.
Set the window once and hold it. Changing from seven days to three lifts the reported rate immediately, which is why the window belongs in the reporting definition rather than in a manager’s discretion.
Examples
Resolution measurement breaks down in predictable ways, and the failures show up across voice, chat, and technical support alike. Four cases show what to watch for.
A Cebu customer service team. Agent self reported resolution sat at 88%. Verified against a seven day repeat window it fell to 71%, and the gap was almost entirely password issues.
A telecoms provider. Cross channel matching revealed customers calling after an unresolved chat. Channel level figures looked healthy while the true rate was eleven points lower.
A software support desk. Giving agents refund authority up to $200 lifted verified resolution from 68% to 79% in one quarter — a permissions fix rather than a training one.
A utility contact centre. Reason code matching was too coarse, so unrelated repeat calls counted as failures. Refining the codes recovered four points of measured performance.
Related terms
The measure sits among the other resolution metrics and the quality processes that verify them. The terms below cover its close neighbours and the outcome it drives.
- First Contact Resolution: the formal name for the same measure.
- First Call Resolution: the voice only version of the metric.
- Contacts Resolved on the First Contact: the raw count behind the percentage.
- Resolution Time: the elapsed measure that runs alongside it.
- Escalation: the path taken when first contact resolution fails.
- Call Quality Monitoring: the review process that checks resolution claims.
- Customer Satisfaction Rating (CSAT): the outcome measure this should track against.
FAQ
What is a good first contact resolution rate?
Between 70% and 80% verified for most support operations. Figures above 90% almost always mean self reporting rather than verification.
How long should the repeat contact window be?
Seven days is the common standard. Shorter windows flatter the number and longer ones make reporting too slow to act on.
Does a transfer break first contact resolution?
Not necessarily. A warm transfer that resolves the issue within the same interaction still counts as one contact.
Should agents mark their own contacts as resolved?
Use it as a signal, never as the measure. Verify against actual repeat contact data.
How does it relate to repeat contact rate?
They are two views of the same behaviour. One counts successes and the other counts failures.
What raises the rate fastest?
Widening agent authority to act without approval. Permissions changes usually beat additional training.
Find support delivery partners in the Outsource Accelerator BPO hubs.
Independent
