Blog · Board and management reporting · Customer service
Live chat KPIs connect first response, completed resolutions and customer feedback. Calculate a small scorecard from chat exports, keeping missed conversations and unrated sessions visible.
A live chat KPI measures an important service result, such as how long customers wait, how often their issue is resolved and whether they rate the experience positively. Use those measures together: a fast first message is useful only alongside access, resolution and quality.
Start from an export of distinct chat sessions. Define the time window, clock and eligible population before comparing teams or reporting a headline percentage.
The first response clock should begin at the customer's qualifying entry or message and end at the first qualifying agent reply. State whether automated acknowledgments count; for the example below, they do not. The live chat metric definitions distinguish the session's first reply from later replies and from separate agent engagements.
Use the session ID as the unit for customer experience. A transfer may create additional agent records for the same conversation. Those are useful for staffing analysis, but counting them as new customer sessions inflates volume and changes the rates.
| Measure | Calculation | Decision it supports |
|---|---|---|
| Missed rate | Unserved eligible sessions / Eligible arrivals | Whether customers can reach the team |
| Mean first response | Total first-response seconds / Responded sessions | How long answered customers wait |
| Response-target attainment | Eligible sessions answered within target / Eligible arrivals | Whether the access and speed commitment is met |
| In-chat resolution rate | Sessions with a confirmed in-chat resolution / Served sessions | Whether conversations deliver an outcome |
| Satisfaction | Positive ratings / Submitted ratings | How respondents assess the experience |
| Feedback coverage | Rated sessions / Served sessions | How much of the served population the score represents |
Select a KPI because it supports an objective, then keep its definition stable. For a broader multichannel scorecard, the neighboring helpdesk KPI guide covers the wider support view.
Export session ID, start time, first agent response, end time, served status, owning team and linked case ID. Add an explicit outcome field for resolution and a separate feedback field. Keep timestamps in one time zone and use the same definition across shifts.
An ended session is not automatically resolved. Confirm the issue outcome from the case record or a documented resolution field. If the export lacks that evidence, report session completion separately and leave resolution unconfirmed.
For the feedback field, distinguish positive, negative and no response. Unrated sessions belong in coverage; they are neither satisfied nor dissatisfied respondents. Where the survey uses a score scale, document which responses qualify as positive before calculating satisfaction.
A US equipment supplier reviews the following illustrative inbound sessions after every session has ended and outcomes have been checked. The response goal is a first agent reply within 60 seconds for every eligible arrival. All sessions meet the eligibility rules; a dash means no observed value.
| Session | Served? | First response (seconds) | In-chat resolution? | Resolution duration (minutes) | Rating |
|---|---|---|---|---|---|
| C1 | Yes | 20 | Yes | 5 | Positive |
| C2 | Yes | 40 | Yes | 8 | Positive |
| C3 | Yes | 60 | Yes | 12 | Negative |
| C4 | Yes | 80 | Yes | 15 | Unrated |
| C5 | Yes | 100 | Yes | 20 | Positive |
| C6 | Yes | 180 | No; follow-up case | — | Unrated |
| C7 | No | — | No | — | Unrated |
| C8 | No | — | No | — | Unrated |
| Count or total | 6 served | 480 | 5 resolved | 60 | 4 rated |
The duration column runs from the start to the recorded resolution for the sessions resolved during chat. It is not agent handling effort. The follow-up case stays outside that duration average because its resolution has not occurred.
| KPI | Calculation from the session rows | Result |
|---|---|---|
| Served share | 6 / 8 × 100 | 75.0% |
| Missed rate | 2 / 8 × 100 | 25.0% |
| Mean first response | 480 / 6 | 80 seconds |
| Median first response | (60 + 80) / 2 | 70 seconds |
| Response-target attainment | 3 / 8 × 100 | 37.5% |
| In-chat resolution rate | 5 / 6 × 100 | 83.3% |
| Mean in-chat resolution duration | 60 / 5 | 12 minutes |
| Satisfaction | 3 / 4 × 100 | 75.0% |
| Feedback coverage | 4 / 6 × 100 | 66.7% |
Percentages are rounded to one decimal place. The median uses the middle observations after sorting the six response times. The response-target numerator includes C1, C2 and C3 because the limit is inclusive.
The first response average describes answered sessions. Target attainment describes all eligible arrivals, including the missed sessions. Changing that denominator to served sessions would give 3 / 6, or 50.0%, which answers a different question.
The positive-rating denominator is submitted ratings, consistent with the satisfaction and rated-session definitions. A positive score should always travel with its coverage so the service lead sees whose feedback is represented.
Reconcile eight arrivals to six served plus two missed. Reconcile six served sessions to five resolved in chat plus one requiring follow-up. Reconcile the four ratings to three positive plus one negative, and the served population to four rated plus two unrated.
These checks make the next action more specific. Missed sessions direct attention to service availability. A slow response distribution directs attention to waiting within answered chats. Unresolved sessions require an outcome review; satisfaction calls for reading the feedback behind the score.
The service lead owns the scorecard and its improvement priorities. A reporting owner checks session counts, timestamps and rating coverage. Team leads review the conversations behind the figures, keeping the unresolved cases in view when faster replies appear to improve the headline result.
The first response time method covers clock definitions in more detail. Follow the average resolution time calculation for cases that continue after chat, and use customer KPIs to connect service observations with broader customer outcomes without treating correlation as proof.
If checking the table in Excel, leave missing durations blank. The AVERAGE documentation confirms that empty referenced cells are ignored while numeric zeros are included. Covirage is not affiliated with Zendesk or Microsoft.
Upload a session export with outcomes and ratings: Covirage maps the columns, and its tools compute and check the figures. The external AI model explains the response, resolution and quality results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data; account creation takes about a minute.
See self-service analytics for the supporting approach to working from business files.
Start with served and missed sessions, first response time, response-target attainment, resolution rate and customer satisfaction. Show feedback coverage beside satisfaction. The useful selection depends on the service objective, but it should cover access, speed, outcomes and quality.
No. A chat can end while the customer's problem remains unresolved. Chat duration describes the conversation; case resolution time can extend into follow-up work. Link the session to its case before treating an ended chat as a resolved issue.
No. They have no observed agent response, so assigning zero makes service appear faster. Keep them outside the responded-session time average and show them in the missed rate. Include them in target attainment when the target covers all eligible arrivals.