Skip to content
Lines open
Map my coverage

Call operations research

Measuring first-call resolution for a virtual receptionist

A measurement protocol for first-call resolution that defines resolution by the caller outcome rather than by the receptionist closing the call.

Measuring first-call resolution for a virtual receptionist
Table of contents

First-call resolution sounds simple until a team tries to define it. A call can be closed at the desk and still leave the caller without an answer. This review sets out a measure that follows the caller outcome and credits a correct transfer. The aim is a fair number that a supervisor can use for coaching rather than a scoreboard.

Key takeaways

  • Define resolution from the caller outcome, not the call disposition.
  • Separate a resolved call from a call that was correctly transferred.
  • Check the record against a sample of callers where possible.
  • Report resolution by call type and by team.

Research question and scope

This review asks what share of calls handled by a virtual receptionist are resolved on the first contact. The unit is one inbound call that reaches a receptionist or the team. The review measures whether the caller got what they needed without calling again about the same issue. It does not measure how pleasant the call was, though that can be a separate review.

The scope covers service, booking, and information calls handled by a receptionist for a small business. It excludes sales calls with a separate conversion goal and internal calls between staff. It also excludes emergency calls that follow a clinical or safety protocol. The scope should be fixed before the sample is drawn.

The review separates a call that was resolved from a call that was correctly transferred. A transfer can be the right outcome even though the receptionist did not resolve the issue alone. The measure should credit a correct transfer as a successful first contact when the caller reaches the right person. A definition that credits only calls closed at the desk will punish good routing.

Record the call type because resolution means different things for a booking and a complaint. A booking is resolved when the appointment is confirmed, while a complaint may be resolved when a plan and a date are agreed. A single resolution definition across all types will hide the difference. Use a short type-specific definition.

Definitions and unit of analysis

Define first-call resolution as the caller receiving a complete answer, a confirmed next step, or a correct transfer on the first contact. A promise to call back is not a resolution unless the promise is kept within the stated window and the caller confirms the outcome. The definition should be written with examples and applied consistently. Keep the examples beside the scoring sheet during the review.

The unit is the call, not the caller. A caller with two unrelated issues has two calls for this measure. A caller who calls back about the same issue is a repeat contact and should be linked to the first call. Record the link so the analysis can avoid counting the second call as a new resolution opportunity.

Define an unresolved call as one where the caller needs another contact to get the answer, and the second contact is about the same issue. A call that was correctly transferred is resolved if the receiving team handles it. A call that was transferred to a queue with no answer is not resolved. The outcome, not the transfer, decides the score.

Decide before collection how to treat a call where the caller hangs up before the end. If the issue was answered before the hang-up, score it as resolved and note the early end. If the answer was incomplete, score it as unresolved. The decision should be written down and applied to every case.

Sampling and data dictionary

Draw the sample from the call records for a fixed period. Include every call that meets the scope, or a random sample if volume is high. Record the export date, the queue, and the row count. Keep the raw export with the report so the sample can be rebuilt.

For each call, capture the time, the caller, the call type, the disposition, and the next step. Add the agent, the duration, and any linked follow-up call. These fields let the reviewer see the outcome without reading every note. A short data dictionary keeps the scoring consistent.

Score the outcome from the call note and the linked follow-up, not from the disposition code alone. A disposition can say resolved while the note shows a pending question. Use the disposition as a hint, not as the answer. A second reviewer should check a small overlap sample.

Include calls from every agent and every shift so the result is not dominated by one person. If one agent handles most of a call type, report that agent separately as well as in the total. A team with a good average can still have a weak process for one type. The split gives the supervisor a fair view.

Measuring resolution and repeat contact

Report the share of calls resolved on the first contact, by count and by call type. Also report the share of calls that were correctly transferred and handled. A single resolution rate can make a routing team look worse than it is. Show the two outcomes separately.

Report the repeat contact rate for the same issue within a fixed window, such as seven days. A high repeat rate can show that a resolution was recorded too early. A low rate can show that the first contact was strong. The window should be stated and kept the same across reviews.

Break the result down by agent, shift, and call type. A gap in one type may reflect a knowledge gap rather than a skill gap. A gap in one shift may reflect staffing or system access. The breakdown should lead to a specific coaching or process change, not a general score.

Check a sample of calls against the caller record where the business has permission to follow up. A short survey or a call-back to a few callers can confirm whether the answer was complete. The sample does not need to be large. A small check is better than assuming that a closed disposition means a resolved caller.

Analysis and limitations

The call record cannot show whether the caller understood the answer. A caller may say thank you and still leave confused. The review should treat the record as one source and the follow-up as another. Note any complaint that arrives after a call marked resolved. That note is a useful correction to the measure.

A resolution rate can be improved by closing calls too early. The repeat contact measure is a check on that behavior. If the resolution rate rises while the repeat rate also rises, the team may be marking calls resolved without solving the issue. Report both numbers together.

The review cannot control for the complexity of the call. A simple booking is easier to resolve than a complaint with a policy question. Record a simple complexity label and compare within it. A fair comparison is more useful than an overall score that mixes different calls.

Give the finding to the team with one testable change, such as a short resolution checklist for the most common call type. Record the change date and repeat the review with the same definitions. A second sample shows whether the change reached the caller. It also protects the team from judging a new checklist on its first busy week.

Repeating the review

Repeat the observation with the same call types and the same repeat-contact window. A change in the window can move the rate without any change in performance. Report the window beside the number. The reader should be able to see whether the same question was asked both times.

Keep the scoring examples in the appendix so a new reviewer can apply the same standard. A measure that depends on one supervisor is fragile. Write the examples into the operations note. The method should survive a staff change.

Agree on the next review date and the person who owns the call export. Put the date in the quality calendar. A review that is not repeated becomes a one-time story. The next review should ask whether the checklist is still in use, not only whether the rate moved.

Use the result to improve the first contact, not to add another dashboard. A short knowledge note, a named backup, and a clear transfer rule are often enough. Ask the agents which question they cannot answer at the desk. Fix that gap before asking for a higher score.

Sources

Map the first queue

GIVE MISSED CALLS A WAY BACK IN.

Share your call types, hours, tools, and escalation rules. We will turn them into a practical coverage plan with a clear first week.

Book a free consultation ↗See the call lanes