What First Contact Resolution Means for a Help Desk

Tuesday, 10:40, at Tollgate Foods. Sam has been on the desk for three weeks. Dana from payroll rings: the payroll export has failed and the run is due at noon. Sam opens a ticket while she talks and asks her to read the error out. He recognises a locked export file from a runbook he happened to read the week before. He asks her to close the application, clears the lock, and stays on the line while she tries again. It works. Before she hangs up she says, "That is the first time I have only had to ask once." Sam types the sentence into the ticket as a quote, because it seemed like something that should be kept.

Priya, who runs the desk, reads the ticket that afternoon and then opens the monthly report. It has response times, resolution times, volume by week and a chart of tickets by department. It has nothing that measures what Dana just thanked the desk for. First contact resolution, usually shortened to FCR, is the share of tickets the desk fixed completely in the requester's first contact with it. That means one call, one chat, one visit or one e-mail exchange, handled from start to finish by the first person who picked it up. There is nothing for the requester to come back for, and it is still fixed afterwards. It is one count of tickets divided by another, and it is the number closest to how the requester experiences the desk. This article is part of our First Contact Resolution series. The series covers what the number means, how to count it without fooling yourself, and how to raise it honestly. It covers where it can and cannot rise, what it does not see, and how to review it every month.

It covers the definition in plain words and the difference between a contact, a ticket and a reply. We cover the four conditions a ticket meets before it counts and why the number matters more to the requester than any speed figure. Next come what first contact resolution is not and the family of names it travels under. We cover where it sits among the desk's other numbers, then a worked month at a fictional desk. A short war story and the definition card to copy follow, in that order.

The Definition in Plain Words

Every help desk number is a fraction. And the way to understand any of them is to ask what is on the top and what is on the bottom. For first contact resolution the bottom is every ticket the desk handled in the period. That means all of them: easy and hard, phone and e-mail. It includes the ones that went well and the ones that went to the second line and stayed there. The top is the subset that the requester only had to ask about once. Divide the top by the bottom and you have a share. You can write it as a fraction, a percentage or "about two in five". The third form is often the most honest.

A contact is one occasion on which the requester reaches the desk and gets an answer. It is a phone call from dialling to hanging up, one chat session, one visit to the desk, or one e-mail and the reply to it. The first contact is the first of these for a given problem. If the requester has to write again, ring again, come back, or wait to be called, the problem has had a second contact, however good the reason. Contacts are counted from the requester's chair, not the desk's, and that one rule settles most arguments about the number before they start.

Resolved means the requester can do the thing they were trying to do, and agrees that they can. It does not mean a reply was sent. It does not mean the status field says "Resolved". The status is the desk's opinion; resolution is the requester's experience, and the two drift apart more often than anyone likes to admit. A status field has never once asked the requester how it went.

Put the pieces together and the definition is short. First contact resolution is the share of tickets the requester had to ask about once, fixed by the first person who answered, in that one exchange, and still fixed afterwards. Everything else in this series is about the words "once", "first person", "one exchange" and "still fixed". Each of them has an edge, and the edges are where the number is won or lost.

Contact Versus Ticket Versus Reply

Three units get confused, and most bad first contact resolution figures come from mixing them. A ticket is the record the desk keeps of one request from open to close. A contact, as above, is one exchange between the requester and the desk. A reply is one message from the desk to the requester. One ticket can hold several contacts. One contact can hold several replies, as a chat does. And a reply may not be a contact at all, from the requester's side, if it contains nothing they can use. "We are looking into it" is a courtesy, not an exchange.

The phone makes the distinction easy and e-mail blurs it. On the phone one contact is one call, and the requester knows it was one contact because they dialled once. By e-mail, the requester writes, and the desk replies with the fix. The requester tries it and it works. That is one contact carrying two messages. If the desk's reply was "which version are you running?" and the requester had to answer before anything happened, the problem has had two contacts. That is because the requester had to come back. The desk may feel it replied promptly. The requester feels they were asked to do the desk's homework.

This is also why first contact resolution and first response time are cousins rather than the same number. First response time measures how long the requester waited for the first human reply. A desk can have a wonderful first response time and never fix anything the first time, by replying to everything within the hour with a question. The two are related the way most cousins are: they share a grandparent and very little else.

The Four Conditions a Ticket Must Meet

A ticket counts as resolved on first contact when it meets four conditions, in order, and fails the moment it misses one. The first condition is that it was logged as a ticket at all. A walk-up fixed in the corridor and never recorded is not a first contact resolution. It is an unrecorded piece of work, and it drags everything else in this series down with it. That is because a desk that logs only its hard tickets will measure itself as a desk that only has hard tickets. Log every contact, the quick ones included, and the number has something to stand on.

The second condition is that the first person who took the ticket finished it. Any change of owner before the fix, whether a formal escalation or a quiet "can you take this one, I am out of my depth", breaks the chain. The requester may not even notice the change, but the desk should count it, because it is the clearest signal that the first line could not finish the work. That signal is the whole reason the number exists. What escalation is, and how to do it without dumping, belongs to the escalation series in this library; here it is only a line crossed.

The third condition is that the fix happened in the first exchange and left nothing for the requester to come back for. A call-back, a scheduled visit, a "try this and let us know" that requires an answer, a part on order: each of these is a second contact waiting to happen. In each case, the ticket is not first-contact anything until the problem is gone. A workaround counts here only if the requester accepts it as the fix and it holds. If it buys a day and the real repair follows, the ticket had two contacts and should say so.

The fourth condition is that the fix stayed fixed through the desk's reopen window. This is the agreed number of working days after a ticket is marked resolved. During that window, the requester saying "it has come back" is treated as the same problem rather than a new one. A ticket resolved on Tuesday and reopened on Thursday was not resolved on Tuesday; the desk only thought so. The window's length is the desk's choice and should match the confirmation period it already uses between resolved and closed. That is the subject of Resolved vs Closed: the Confirmation Window. In QuerySolv, as in many tools, a requester's reply to a resolved ticket reopens it. That is what makes the fourth condition something you can count rather than guess at. The fresh ticket about the same fault is the case you still catch by hand.

Each condition has edges, and the next article in this series, Measuring First Contact Resolution Honestly, owns them. Those edges include the triage assignment that is not a handoff, the consultation where the owner never changed, the ticket closed because the requester went quiet. For now, the shape is enough. Four gates, in order, and a ticket that passes all four is one the requester asked about once.

Why It Matters More to the User Than Any Speed Number

The requester does not experience the desk in minutes; they experience it in asks. Dana at Tollgate did not know, and would not have cared, that her ticket's resolution time was fourteen minutes. She knew that she had asked once and it was fixed. Had the desk taken four hours to fix the same fault on that one call while she worked on something else, she would still have asked once. Had it taken forty minutes across three exchanges, with a question, a wait, and a call-back, the report would have shown a faster resolution. In that case, she would have had a worse morning.

Every extra contact costs the requester something the report never sees. They tell the story again, often to a new person who has not read the first telling. They wait with the problem unresolved and no idea when it will be. They write the "any update?" message, which nobody enjoys writing, and feel faintly like a nuisance for having done so. They lose the thread of their own work twice instead of once. None of this appears in a resolution time, which measures a clock, not a person.

Every extra contact costs the desk as well, which is the argument that works on people who do not care about Dana. The second technician reads the ticket from the beginning. The second exchange repeats half of the first. Two people have now spent time on a problem that one could have finished. A desk with a low first contact resolution is a desk doing much of its work twice. And the backlog it complains about is partly made of second contacts.

First contact resolution is the metric closest to the one requesters would choose if they ran the desk. Satisfaction asks them how they feel about it; this number counts what they actually lived through. In my experience it is also a number many desks never compute, because the tool does not print it by default. The arithmetic needs two or three rules written down first. Speed numbers are easier, and they are also the desk's favourite because the desk controls them. A desk can halve its first response time by replying "received, thanks" to everything. The requester notices this about the third time.

What First Contact Resolution Is Not

It is not first response time. First response time measures how long the requester waited before a human replied; first contact resolution measures whether that reply finished the job. A desk can be excellent at one and poor at the other. The two targets that usually appear in a service agreement, response and resolution, are explained in Response vs Resolution Targets. First contact resolution is neither of them and should not be written into a service agreement at all, for a reason that comes next.

It is not a promise to the requester. A service level is a commitment the desk makes about the requester's experience. For example, you will hear from us within an hour, and your problem will be fixed within a day. First contact resolution is a measure the desk takes of its own reach. A desk that promises "we will fix it the first time" has promised something it cannot control for every ticket. Some tickets need a part, an approval or a second pair of hands. Keep it inside the desk, where it tells you how the first line is doing, and out of the document that tells the requester what to expect.

It is not "closed on first reply". Some tools, and many spreadsheets, count a ticket as a first-contact success if it was closed after one message from the desk. That measures how quickly the desk is willing to press the close button, which is a different thing and sometimes a worse one. A ticket closed in one reply that fixed nothing is the silent close described in Avoiding the Silent Close. A counting rule that rewards it will get more of it. The reply must have resolved the problem, and the problem must have stayed resolved, or the ticket does not count.

It is not a measure of quality on its own, and it is not a score for a person. A high figure can hide hurried fixes and workarounds presented as repairs, which is why the number is always read beside the reopen rate and the satisfaction score. The fifth article in this series, The Limits of First Contact Resolution, is about exactly that. When a desk does read it per technician, the reading is for coaching rather than ranking, and not from fewer than forty or so tickets of a comparable kind. That article also explains the reasons. A first contact resolution figure on a wall, with names beside it, is a request for the number to be gamed. It will be granted.

The Family of Names It Travels Under

The idea has several names, and they do not all mean the same thing. So when someone quotes a figure it is worth asking which one they counted. First call resolution is the oldest, from the era when the only way to reach a desk was the telephone. It means the same thing as first contact resolution with "call" where "contact" now stands. The word changed because the channels did. A desk that takes e-mail, chat, web forms and walk-ups needs a word that covers all of them, and "contact" is that word. Where you see "first call resolution" in older material, read it as the same number measured on one channel.

First time fix comes from field service, where an engineer travels to the fault. It means the fault was fixed on the first visit without a return trip or a part on order. It is the same idea applied to one kind of contact and it is the right phrase for a desk's hardware technician, whose first contact is a visit. The strict version of first contact resolution and a first time fix figure for the hardware line are compatible. The fourth article in this series, which looks at the number by category, uses that compatibility.

First touch resolution, first reply resolution and one-touch tickets are desk-side names, and they are weaker. They usually count tickets the desk only touched once, or closed after one reply, without asking whether the requester had to come back or whether the fix held. They are easy to compute from a ticket export, which is why they are common. They are the figures that produce a desk with a glowing number and a corridor full of people asking each other for help. This library means the strict version throughout: contact counted from the requester's chair, one person, one exchange, still fixed when the window closes. If a figure is quoted without those four things attached, it is a different number wearing the same name.

Where It Sits Among the Desk's Other Numbers

First contact resolution is one of a small set of measures a desk reads together. The idea of reading them in pairs, so that each one keeps the others honest, belongs to Reading Metrics Together in the metrics series. First contact resolution's partners are the reopen rate, which catches the fix that did not hold, and the satisfaction score, which catches the fix the requester did not like. Rising first contact resolution with a rising reopen rate is not improvement; it is a desk closing faster. Rising first contact resolution with flat satisfaction is a question. Rising first contact resolution with falling reopens and rising satisfaction is the thing itself.

It is not usually one of the first numbers a new desk should track. A desk in its first weeks needs volume, backlog age and response time, which are the three in First Metrics. It needs them because they tell it whether it is drowning. First contact resolution needs a clean record of who owned each ticket and a reopen rule before it means anything. So it belongs in the second or third month, once those are in place. The ownership record is usually there already if the tool keeps one. QuerySolv keeps a complete event history on every ticket, and most tools keep something like it. So the second condition is a filter on who claimed the ticket rather than a test of anyone's memory.

What it tells you that the others do not is the reach of the first line. Volume says how much work arrives, resolution time says how long it takes, and first contact resolution says how much of it the first person who answers can finish. When it is low, one of four things is usually missing at the first touch: knowledge, permission, a tool, or information from the requester. Finding which, and fixing it without cheating, is the third article in this series. The number is a thermometer for the first line's reach, and like a thermometer it is useless if you only read it when you feel well.

A Worked Month at Tollgate Foods

Priya counted a month by hand, which is how every desk should do it the first time. Here is her count. The numbers are Tollgate's, invented for this article, and the only point of them is the method. The desk had logged 388 tickets in the month. She asked each technician how many corridor fixes they had done and not logged. The honest answers added up to about sixty. She logged those fixes after the fact with the source marked as walk-up, bringing the bottom of the fraction to roughly 450. That one question nearly always finds work, and finding it is a relief, not an accusation. It is work the desk did and never got credit for.

Of the roughly 450, she found 231 that had been handled from start to finish by the person who first took them. She did this by reading the ownership history rather than asking anyone. Of those 231, she found 207 that had been fixed in the first exchange. The other twenty-four had needed a call-back, a visit or a reply from the requester before anything could be done. Of the 207, sixteen had been reopened inside the desk's window, which she took from the confirmation period the desk already used. That left 191 tickets on the top of the fraction and about 450 on the bottom: a bit over two in five.

She wrote it as "191 of about 450 tickets, a bit over two in five", not as a percentage to one decimal place. The two counts are the part a reader can check and the share is the part they can misremember. She also wrote down what the number did not say. Around 120 of the 450 were hardware repairs, purchases and access requests needing a manager's approval. None of those could have been first-contact anything, so the desk-wide figure carried that mix inside it. Whether two in five is good or bad is not a question the first count can answer. The first month's number is a photograph, not a verdict.

A Short War Story: Two Numbers at Ashgrove Housing

Dev, who managed IT at Ashgrove Housing, was asked by the operations director in a quarterly meeting what the desk's first contact resolution was. He said he would find out. Two technicians each produced a figure by the next morning. Kirsten counted tickets closed after one reply from the desk and got about four in five. Yusuf counted tickets with no change of owner, one exchange and no reopen and got a little under half. Dev, in a hurry, sent the first number. The director quoted it in a board paper as evidence that the desk did not need the second-line hire it had asked for. When the hire was refused, Dev had to explain in writing that the figure in the paper had counted a reply as a resolution. The honest number took most of a year to be believed. The cost was a delayed hire and twelve months of having every figure from the desk asked about twice. Define the number before anyone counts it, because the first number out of the door is the one people remember.

The FCR Definition Card

The card below is one page, filled in once by the desk lead and whoever else will quote the number, and pinned where the monthly count is done. Its job is to make the four conditions and the edge rulings explicit. That way, two people counting the same month get the same answer. And when the number is quoted a year from now, the rules it was counted under can be produced. Fill every blank, including the edge rulings you think are obvious; the ones that feel obvious are the ones two technicians will decide differently. The counting method that uses this card is in the next article. The card itself does not change unless the desk agrees to change it and writes the date.

FIRST CONTACT RESOLUTION — DEFINITION CARD, ONE PAGE
Desk: ______________________   Agreed by: ______________________   Date agreed: ____________

WHAT WE COUNT
  Denominator: every ticket logged in the period, including walk-ups logged after the fact
  Numerator:   tickets that meet ALL FOUR conditions below
  Period:      calendar month, by the date the ticket was ____________ (opened / closed: pick one)

THE FOUR CONDITIONS
  1. Logged as a ticket ........................................................ yes / no
  2. Handled start to finish by the first person who took it
     (no reassignment, no escalation) ........................................... yes / no
  3. Fixed in the first exchange; the requester had nothing to come back for
     (no call-back, no visit to schedule, no "try this and tell us") ............ yes / no
  4. Still fixed when the reopen window closed ................................. yes / no
     Our reopen window: ____ working days after the ticket is marked resolved

OUR EDGE RULINGS (decide once, write them here)
  A triage assignment that does no work on the ticket .............. is / is not a handoff
  A consultation where the owner stays the same ................... breaks / does not break
  A workaround the requester accepts and that holds ............... counts / does not count
  A ticket closed because the requester never replied ............. counts / does not / own bucket
  A new ticket about the same fault inside the window ............. treated as a reopen: yes / no
  A "how do I" question answered completely in one exchange ....... counts / does not count

HOW WE REPORT IT
  As two counts and a share:  "____ of ____ tickets, about ____"
  Always beside:  reopen rate ______   satisfaction ______
  Never alone; never as a target for one person; never in the service agreement

Priya filled in the card the week after her first count, with Sam and the other two technicians in the room. The edge rulings took longer than the conditions did. The desk disagreed for ten minutes about whether a triage assignment was a handoff. They settled on "is not", because the triager at Tollgate never works a ticket, only sorts it. Sam asked whether Dana's call would have counted under the card. It would have: logged, one owner, one exchange, and still working when the window closed. She had, after all, only had to ask once.

Frequently Asked Questions