Skip to content
Kaagazo.
FreeSUPPORT EFFICIENCY

First Contact Resolution Rate

Calculate what percentage of support issues are resolved on the first interaction.

100% client-side. Nothing you type is uploaded or stored on a server.

A customer who has to message three times about one problem remembers the problem, not the fix. First contact resolution (FCR) is the share of support issues resolved in the first interaction — one call, one chat, one visit — with no follow-up needed. It is the support metric most closely tied to satisfaction and to cost: every unresolved contact is a second contact your staff must handle. This calculator computes FCR from ticket counts, shows the cost of repeat contacts, and helps you segment by issue type and channel.

The formula

FCR = Issues resolved on first contact ÷ Total issues × 100.

A mobile-repair shop handled 220 support contacts in a month; 165 were fully resolved the first time, 55 needed a follow-up call or visit → FCR = 75%. At roughly ₹60 of staff time per contact, the 55 repeats cost ₹3,300 plus the goodwill.

Define "resolved" from the customer's view: no repeat contact about the same issue within 7 days (or ask "did this solve your problem?" at the end). Counting only what staff mark as closed inflates the number.

How to use the calculator

  1. Enter total issues and those resolved on first contact for the period.
  2. Enter the average handling cost per contact to see the cost of repeats.
  3. Segment by issue type (delivery, billing, product defect, how-to) and channel (WhatsApp, phone, walk-in).
  4. Track monthly; a falling FCR usually follows a product change, a new staff member, or a policy the front line cannot apply.
  5. Pair with CSAT — a rising FCR should lift it within a month.

Raising FCR in a small business

  • Empower the front line: let staff refund up to ₹500, replace a defective item, or waive a delivery fee without asking the owner. Policies that need an approval guarantee a second contact.
  • Write down the top 10 issues and their fixes; most repeat contacts are about the same five things.
  • Fix the cause: billing questions often mean the GST invoice is unclear; delivery questions mean tracking was not shared — send the AWB from the shipping label proactively.
  • Ask "anything else?" before closing.
  • Callback within the hour when something genuinely needs escalation; a scheduled callback that happens still counts as one contact in the customer's mind.
  • Speed is separate from resolution — track first response time too; fast-but-unresolved is the worst combination.

FCR and the numbers around it

  • Contacts per order: total contacts ÷ orders; a rising ratio with steady FCR means the product or process is generating issues.
  • Cost to serve: contacts × cost per contact ÷ orders — often 2–5% of revenue in e-commerce.
  • Retention: customers with an unresolved first contact churn at multiples of the base rate; the retention rate calculator will show it a quarter later.

Clear, published policies are what let staff resolve issues on the spot; the disclosure rules for online sellers are in DPDP Rules 2025 and the e-commerce checklist, and the messaging norms in TRAI's new anti-spam rules.

Frequently asked questions

What is a good FCR rate?

70–80% is typical; above 85% is excellent. Complex products (electronics, custom furniture) run lower; simple retail higher.

How do I decide if an issue was resolved on first contact?

No further contact about the same issue within a set window (7 days is common), or a "yes" to "did this resolve your issue?" at the end of the interaction.

Does a scheduled callback count as first contact?

If the callback happens as promised and resolves the issue, most businesses count it as one contact. If the customer has to chase, it does not.

Why is FCR more important than response time?

Speed without resolution creates repeat contacts. Both matter, but FCR tracks the cost and satisfaction impact more directly.

How do I track this on WhatsApp?

Label conversations (WhatsApp Business labels) as "resolved" or "follow-up", and count them weekly. A spreadsheet with date, issue type and resolution status works.