# What is First Contact Resolution?

Also called FCR, first touch resolution.

First contact resolution is the share of customer issues fully resolved during the initial interaction, with no follow up, transfer, or callback required. It is a long established support metric that correlates strongly with customer satisfaction. Definitions of the measurement window vary between organizations, which makes benchmark comparison unreliable.

Measurement hinges on the window. Some organizations count a contact as resolved if no related contact arrives within twenty four hours, some use seven days, and some rely on the handling agent marking it resolved. Self-marking inflates the number substantially. The window choice should be stated whenever the figure is reported, and frequently is not.

The metric matters because repeat contact is expensive on both sides. Each additional touch consumes handling capacity and requires the customer to restate their situation, which is the specific experience most strongly associated with dissatisfaction in support research. A modest improvement in first contact resolution typically outperforms a large improvement in raw response speed.

For automated handling the determinants are access and authority. An agent resolves on first contact when it can read the relevant records and is permitted to take the action the resolution requires, such as issuing a credit within a set limit. Read access without action authority produces an informative reply and a second contact, which counts against the metric.

The measure can be gamed and the failure modes are well documented. Closing tickets aggressively, discouraging follow up, or splitting one issue across several ticket records all raise the reported number without improving anything. Reading it alongside repeat contact rate and satisfaction is the standard defense against this.

## Key points

- Share of issues resolved in the initial interaction
- Measurement window varies, so benchmarks rarely compare
- Repeat contact is costly to both sides
- Automated resolution needs record access plus action authority
- Easily gamed by aggressive closing or ticket splitting

## In practice

A software company gives its support agent read access to subscription records and authority to apply a prorated credit up to a fixed cap without approval. Billing questions that previously required a handoff to finance and a next-day callback now close in the first conversation. Anything above the cap, or any request to cancel, still routes to a person immediately.

## Related terms

- [Ticket Deflection](/en/glossary/ticket-deflection)
- [AI in Customer Support](/en/glossary/ai-in-customer-support)
- [Escalation Path](/en/glossary/escalation-path)
- [Agent KPI](/en/glossary/agent-kpi)
- [SLA For Automated Work](/en/glossary/sla-for-automated-work)

[Back to the AI Glossary](/en/glossary)