What is first contact resolution?
First contact resolution (FCR) is the percentage of customer support tickets that are fully resolved on the first interaction — without the customer needing to follow up or reopen the issue. An FCR of 80% means 8 out of 10 customers get their issue fully resolved the first time they reach out.
FCR is distinct from first response time (which only measures speed of initial reply) and CSAT (which measures satisfaction). FCR measures completeness and accuracy: did the customer actually get what they needed?
Measuring FCR requires some care. The most common method is to track tickets that are closed without being reopened by the customer within 48–72 hours. A simpler proxy is to measure the percentage of tickets that generate no follow-up contact. Some platforms also offer post-resolution surveys ('Was your issue resolved?') which give a cleaner signal.
Ecommerce FCR typically ranges from 65–80% across the industry. Strong performers reach 82–88%. With AI handling the automated-category tickets, FCR often climbs to 85–92% because AI doesn't send 'let me check on that and get back to you' responses that generate follow-ups.
FCR benchmarks for ecommerce
Shipping issues and complex disputes have structurally lower FCR because they often require carrier investigation or back-and-forth. Improving FCR on these categories requires either faster carrier data access or better intake processes (getting all the needed information in the first message), not just better responses.
| Ticket type | Typical FCR range | Strong FCR |
|---|---|---|
| Order status (WISMO) | 85–95% | 95%+ |
| Return eligibility questions | 75–88% | 88–93% |
| Shipping issues / lost packages | 60–75% | 78–84% |
| Product questions | 78–88% | 88–94% |
| Billing and refund requests | 65–78% | 80–87% |
| Account issues | 72–85% | 86–92% |
| Complex disputes / damaged goods | 50–68% | 70–80% |
| Overall blended FCR | 65–80% | 82–88% |
What drives FCR up
High FCR is a product of having the right information available at the moment of first response — both agent knowledge and customer data. Several factors consistently improve FCR:
- Access to real-time order data at the moment of first response — agents and AI that can see the actual order, shipping status, and history give complete answers immediately.
- Clear policies — return, refund, and exchange policies that are documented, unambiguous, and accessible mean agents can answer definitively rather than escalating for a policy check.
- Good intake: gathering enough context up front. A ticket that arrives with only 'my order is wrong' requires follow-up; a ticket that arrives with order number, item description, and photos can often be resolved immediately.
- Agent knowledge quality: comprehensive internal knowledge bases, updated regularly, mean agents don't need to check with a manager before answering.
- Empowered agents: agents who can issue refunds up to a certain amount, initiate returns, and offer credits without approval cycles resolve issues on first contact instead of creating escalation chains.
- Avoiding the 'I'll look into this and get back to you' habit: any response that defers action rather than taking it is an FCR failure, even if it's technically polite.
What tanks FCR
Low FCR is usually caused by a small number of systemic issues that, once identified, can be fixed relatively quickly:
- Missing information: agents don't have order data, carrier updates, or policy access at the moment of first response — they have to go find it, which either takes time or creates a second message.
- Vague policies: policies that say 'we evaluate each case individually' can't be applied consistently, leading to follow-up for internal approvals that didn't need to exist.
- Agent empowerment gaps: agents who can't take any action without manager approval create unnecessary back-and-forth on transactions that should be resolved instantly.
- Poorly scoped first response: agents who answer part of the question (tracking says delivered) without addressing the whole issue (customer says they didn't receive it) create inevitable follow-ups.
- High ticket volume without adequate staffing: when agents are rushed, they give incomplete answers — time pressure is one of the most reliable predictors of low FCR.
How AI affects FCR
AI typically improves FCR for the ticket categories it handles. The primary reason is that AI agents don't resort to 'I'll check on this and follow up' — they either answer from the available data immediately or escalate to a human with full context. There's no intermediate 'acknowledged but not resolved' state that generates follow-ups.
For order status tickets, AI FCR approaches 95%+ when connected to live order data. The answer is always available immediately. For return eligibility, AI FCR is high when policies are documented clearly — the AI applies the rules without needing an approval.
The categories where AI FCR can be lower than human FCR: complex disputes where judgment and negotiation are required, and situations where the customer's issue spans multiple systems that the AI isn't connected to. These are the cases where AI should escalate to a human with context, rather than attempt a resolution.
Bookbag's approach is to give AI agents a clear scope with honest confidence thresholds: handle what they can resolve completely and accurately; escalate with full context when they can't. This approach produces higher FCR on AI-handled tickets and better human FCR on escalations (because the human has all the context they need).
| Category | Human FCR | AI FCR (well-configured) | Notes |
|---|---|---|---|
| Order status / WISMO | 88–94% | 94–98% | AI has live data access — more reliable |
| Return eligibility | 75–85% | 82–90% | AI applies policy consistently |
| Product questions | 78–87% | 80–88% | Depends on catalog data quality |
| Billing disputes | 65–78% | 60–72% | AI is more conservative — escalates edge cases |
| Complex complaints | 55–68% | Escalates to human | Right call — don't automate judgment |
Key takeaways
- Ecommerce FCR benchmark: 65–80% typical, 82–88% strong, 85–92%+ with AI on automated categories.
- FCR varies significantly by ticket type — WISMO FCR should be 90%+; complex disputes are structurally lower.
- The most common FCR killers: missing order data, vague policies, and agents without action authority.
- AI improves FCR on data-grounded categories by giving complete, accurate first responses without deferral.
- Measure FCR by ticket type — the variation tells you exactly where to invest improvement effort.