First contact resolution, or FCR, is a simple idea from customer service: the customer's problem is solved in the first conversation, without follow-ups, transfers or repeat contacts. It is one of the few service measures that customers feel directly. Nobody enjoys asking the same question three times or being told to call back tomorrow. For a small business, AI chat makes a high FCR realistic for a large share of routine questions, because the assistant answers instantly from your documents at any hour. It also makes it easy to fool yourself: a conversation that ended is not the same as a problem solved. This guide explains what FCR means in a chat setting, which kinds of questions an assistant can genuinely resolve, how to measure resolution without inflating it, what blocks it and how to improve it. Where numbers are suggested, they are yours to gather, not industry promises.
Defining resolution honestly
| Counts as resolved | Does not count |
|---|---|
| Visitor got the opening hours and did not return with the same question | Visitor left after an unhelpful answer |
| Visitor booked an appointment and received a confirmation | Visitor was told to phone and never did |
| Visitor received the address and parking details | Visitor got a vague answer and rephrased three times |
| Visitor's request was handed to staff with full details and answered | A handover with no details that forced them to repeat themselves |
The test is whether the customer got what they came for, not whether the chat closed. A person who abandons in frustration is a lost conversation, not a resolved one.
What an assistant can resolve
- Factual questions: hours, location, services, prices, policies, preparation and aftercare.
- Simple actions: booking, rescheduling through a private link and leaving details for a callback.
- Guidance: which service suits a situation, based on your documented advice.
- Navigation: where to find a form, a page or a document.
Matters that need judgement, access to private records or empathy, such as complaints, disputes and clinical or legal advice, should be handed to a person with the context attached. Resolving them in one contact means the handover works, not that the bot solves them.
How to measure it
- Pick a sample of recent conversations, thirty to fifty.
- For each, decide: resolved, handed over, or unresolved.
- For handovers, check whether staff resolved it and whether the customer had to repeat information.
- Check whether the same visitor came back with the same question within a few days, where you can tell (same contact details or booking).
- Calculate the share resolved without repeat contact.
Keep the definition stable so you can compare months. A rough measure applied consistently beats a precise one used once.
What blocks first contact resolution
| Blocker | Effect | Fix |
|---|---|---|
| Missing information | The assistant cannot answer, visitor leaves | Add the passage; review unanswered questions weekly |
| Outdated information | Wrong answer; repeat contact to correct it | Date content and review monthly |
| Vague answers | Visitor asks again | Give specifics and a next step |
| No booking path | Visitor told to call | Enable booking or callback capture |
| Bad handover | Customer repeats everything | Pass the transcript and details to staff |
| Hard-to-find handover option | Customer gives up | Offer a person clearly when asked |
Improve it in four steps
- Fill the gaps. Use the unanswered list to add missing facts.
- End with the next step. Every answer should say what happens next: book, call, visit or wait for a reply.
- Make handover complete. Send the conversation, name and contact details, so nobody starts over.
- Follow up. For handed-over conversations, reply promptly and confirm the issue was solved.
See handing over from bot to human for a smooth escalation design.
Do not chase the number
- Forcing the assistant to answer everything drives up wrong answers.
- Discouraging handover to boost the metric hurts customers.
- Counting every closed chat as resolved makes the figure meaningless.
- A modest, honest rate you can improve beats an inflated one.
A worked example
A pet groomer reviews forty chats. Twenty-two were simple questions about prices, hours and vaccination rules; the assistant answered them and none returned with the same question, so they count as resolved. Nine ended in a booking. Six were handed to staff with details and were answered the same day. Three were unresolved: a visitor asked about grooming an elderly cat, a service the documents did not mention. The groomer writes a short passage on senior and nervous animals and adds it to the knowledge base. Resolution here rose because a gap was found and filled, not because the metric was redefined.
| Group | Count | Action |
|---|---|---|
| Answered, no return | 22 | Keep documents current |
| Booked | 9 | Check confirmations were sent |
| Handed over and answered | 6 | Confirm the details reached staff |
| Unresolved | 3 | Add the missing passage |
The role of staff in resolution
Resolution is a team result. When the assistant hands over, staff should see the whole conversation so the customer does not repeat anything, and they should reply quickly with a real answer, not a generic acknowledgement. Agree a reply time, such as the same business day, and check it in the weekly review. A fast, informed reply after a handover often leaves the customer happier than an instant answer from a machine, because it shows the business listened.
Finally, remember the customer's view. They do not care which channel solved their problem; they care that it was solved once. Design each answer to end with a clear next step, whether that is a booking, a visit or a promised reply, and check that the promise is kept.
A weekly checklist
- Read the unanswered list and add the top missing facts.
- Check the oldest documents for outdated prices, hours and policies.
- Read three handovers and confirm the customer did not have to repeat anything.
- Look for repeated questions from the same person, a sign the first answer failed.
- Note one improvement for next week.
Small weekly fixes compound. After a couple of months, the same visitors' questions are answered first time, and staff spend their time on the conversations that really need a person.
Signs your resolution is improving
- Fewer repeat questions from the same customers.
- Shorter conversations that end with a booking or a clear next step.
- A shrinking unanswered list from week to week.
- Staff report fewer calls asking for information already on the website.
Note these signs in your monthly review and celebrate progress with the team, since it is their handovers that make the whole approach work.
Frequently asked questions
What is first contact resolution?
Solving the customer's problem during the first conversation, without follow-ups or repeated contacts.
Can an AI chatbot achieve high FCR?
For routine factual questions and simple actions such as booking, yes, when the knowledge base is complete and current.
How do I measure FCR for chat?
Sample recent conversations, classify them as resolved, handed over or unresolved and check for repeat contact.
Is a handover a failure?
No. It is resolution when the handover passes full context and a person answers promptly.
What lowers FCR most?
Missing or outdated information and answers that do not say what happens next.
Should I set an FCR target?
Set a direction for improvement against your own baseline rather than copying vendor benchmarks.
See the AI assistant feature, pricing and the chat analytics playbook. Also read where visitors drop off in chat.
Further reading
- Google Search Central: creating helpful, people-first content: What Google looks for in useful pages.
SVARA ALLA BESÖKARE. BOKA DEM SOM ÄR REDO.
Lägg in Crescelo på din webbplats på 15 minuter
Träna din assistent på dina prislistor, dokument och tjänstevillkor. Aktivera välgrundade svar dygnet runt och bokning av tider direkt i chatten utan krockar.