Call center metrics are the numbers that show how fast, how well and at what cost your team handles phone calls. The twelve that matter most are service level, average speed of answer, abandonment rate, average handle time, first call resolution, occupancy, call volume, missed calls, CSAT, NPS or CES, cost per call, and repeat or transfer rate. This guide gives the formula, a worked example and a sourced benchmark for each. It also shows which call center KPIs a small team can pull straight from a phone system and which need a CRM, surveys or finance data.
Key takeaways
- SQM Group's 2024 benchmark, published February 6, 2025, found an average first call resolution rate of 69% across industries, with individual call centers ranging from 43% to 88%.
- The traditional voice service level standard is 80% of calls answered within 20 seconds, and some centers now target 90% in 15 seconds, according to a 2019 Call Centre Helper survey.
- Average handle time equals (talk time + hold time + after-call work) / calls handled. Call Centre Helper reports an average of 6 minutes 3 seconds, drawn from 190,702 Erlang Calculator entries.
- A phone system alone can report call volume, answer time, abandonment, talk time, missed calls, voicemail and service level. First call resolution, CSAT, NPS and cost per call need CRM, survey or finance data.
- Teams of one to five agents should track four or five metrics, not twelve, and review them as weekly rolling averages because low call volume makes daily numbers swing.
What are call center metrics, and how do they differ from contact center metrics?
Call center metrics measure how a phone team handles calls, covering speed, efficiency, quality and cost. Contact center metrics use many of the same formulas but add channels such as email, chat and SMS, so call center metrics are the voice-only slice of a contact center view.
Most published lists group metrics into three families:
- Agent productivity: average handle time, occupancy, utilization, calls per agent.
- Operational or queue: service level, average speed of answer, abandonment, call volume, missed calls.
- Customer experience: first call resolution, CSAT, NPS, CES, repeat calls.
How we picked these 12 KPIs
We chose metrics that a team of 3 to 30 people can calculate without a workforce management suite. Each one answers a practical question: are callers reaching us, are we resolving their problem, and what does it cost? Cost per call and repeat rate are included because they connect service quality to money.
How to read each entry
Every KPI below has a one-line definition, a formula, a worked example with invented round numbers, a benchmark where a dated source exists, and a "watch out" line. Benchmarks are directional.
The SQM figure covers 2024 data and was published February 6, 2025. The Call Centre Helper page was last modified January 23, 2026, but its service level figure comes from a 2019 survey and its AHT average comes from undated calculator entries. Where no sourced benchmark exists, we say so and label any target as our own starting point.
Queue and agent metrics at a glance:
| Metric | Formula | Typical target |
|---|---|---|
| Service level | Answered within threshold / offered x 100 | 80% in 20 seconds |
| Average speed of answer | Total wait time / answered calls | 20-30 seconds (our starting point) |
| Abandonment rate | Abandoned / offered x 100 | Under 8% (our starting point) |
| Average handle time | (Talk + hold + ACW) / handled | Your own baseline; 6:03 average |
| Occupancy | Handling time / logged-in time x 100 | 75-90%, by team |
| Call volume | Calls offered per interval | Drives staffing |
Customer, resolution and cost metrics at a glance:
| Metric | Formula | Typical target |
|---|---|---|
| First call resolution | Resolved on first contact / total x 100 | 69% average; 70-75% cited |
| Missed call rate | Missed / inbound x 100 | Under 10% in hours (our starting point) |
| CSAT | Satisfied responses / total responses x 100 | 80%+ (our starting point) |
| NPS | % promoters - % detractors | Track the trend |
| Cost per call | Total operating cost / calls handled | Track the trend |
| Repeat call rate | Repeat callers / total callers x 100 | Falls as FCR rises |
What are the 12 call center KPIs, with formulas and benchmarks?
The 12 call center KPIs are service level, average speed of answer, abandonment, average handle time, first call resolution, occupancy, call volume, missed calls, CSAT, NPS or CES, cost per call, and repeat or transfer rate. Each one has a formula below you can run in a spreadsheet today.
1. Service level
Service level is the percentage of offered calls answered within a set number of seconds.
Service level = (calls answered within threshold / calls offered) x 100
Example: 400 calls offered, 332 answered within 20 seconds. 332 / 400 = 83%.
Benchmark: the classic standard is 80/20, meaning 80% of calls answered in 20 seconds. A 2019 Call Centre Helper survey found some centers now aim for 90% in 15 seconds.
Watch out: always state the threshold. "85% service level" means nothing without the seconds.
2. Average speed of answer (ASA)
Average speed of answer is the mean time callers wait in queue before an agent picks up.
ASA = total wait time of answered calls / number of answered calls
Example: 6,000 seconds of total wait across 300 answered calls = 20 seconds.
Benchmark: no well-sourced universal figure exists. We suggest 20 to 30 seconds as a starting point for small teams.
Watch out: ASA hides the long tail. A 20-second average can include a few callers who waited three minutes, so pair it with service level.
3. Call abandonment rate
Abandonment rate is the share of offered calls where the caller hangs up before reaching an agent.
Abandonment rate = (abandoned calls / calls offered) x 100
Example: 500 calls offered, 35 abandoned. 35 / 500 = 7%.
Benchmark: no authoritative standard is published, and ranges vary widely. We suggest staying under about 8% as a starting point.
Watch out: divide by offered calls, not handled calls, or the rate looks artificially high. Many teams exclude abandons shorter than a few seconds, since those are often misdials. Pick a threshold, write it down and keep it fixed.
4. Average handle time (AHT)
Average handle time is the average total time an agent spends on one call, including talk, hold and after-call work (ACW), which is the wrap-up and notes done after the caller hangs up.
AHT = (talk time + hold time + after-call work) / calls handled
Example: 200 calls, 1,000 talk minutes, 100 hold minutes, 200 ACW minutes. 1,300 / 200 = 6.5 minutes, or 6:30.
Benchmark: Call Centre Helper reports an average of 6 minutes 3 seconds from 190,702 Erlang Calculator entries (undated). It also cites a Cornell University report with sector figures: telecommunications 528 seconds, retail 324 seconds, and business and IT services and financial services 282 seconds each.
Watch out: AHT is a measure, not a goal. Pushing it down without watching resolution raises repeat calls.
5. First call resolution (FCR) formula
First call resolution is the share of customer issues solved on the first contact, with no follow-up needed.
FCR = (issues resolved on first contact / total issues) x 100
Example: 1,000 calls, 700 resolved on first contact. FCR = 70%.
The hard part is defining "resolved." Three common methods give different answers:
- System-inferred: no repeat call from the same number on the same topic within 24 hours or 7 days.
- Customer-reported: a survey asks "Was your issue resolved today?"
- Agent-flagged: the agent selects a disposition such as "resolved" or "follow-up needed."
Benchmark: SQM's 2024 study found a 69% average, with centers from 43% to 88%. Call Centre Helper gives 70-75% and warns that results depend on the measurement method.
Watch out: do not compare your FCR to another company's unless the definition matches. Compare against your own trend.
6. Occupancy and agent utilization
Occupancy is the share of an agent's logged-in time spent handling calls. Utilization is the share of total paid time spent on productive work.
Occupancy = (talk + hold + ACW time) / logged-in available time x 100
Utilization = handling time / total paid time x 100
Example: an 8-hour paid shift (480 minutes), 420 minutes logged in, 330 minutes handling calls. Occupancy = 330 / 420 = 78.6%. Utilization = 330 / 480 = 68.8%.
Benchmark: Call Centre Helper lists 83.3% from its calculator data and says occupancy is best kept between 85% and 90%. Sources differ, so treat roughly 75% to 90% as the working band.
Watch out: sustained occupancy near the top of that band leaves no recovery time between calls.
7. Call volume and peak-hour traffic
Call volume is the number of calls offered in a period, and peak-hour traffic is the share of calls landing in your busiest hour.
Peak-hour share = (calls in busiest hour / total daily calls) x 100
Example: 40 of 200 daily calls arrive between 10:00 and 11:00. Peak-hour share = 20%.
Benchmark: none applies. Your own hourly pattern is the benchmark, and it drives staffing. Larger teams feed it into an Erlang calculator, a staffing formula that estimates how many agents a given call load needs.
Watch out: schedule agents against the hourly curve, not the daily average.
8. Missed call and voicemail rate
Missed call rate is the share of inbound calls that nobody answered, and voicemail rate is the share that ended in a message.
Missed call rate = (unanswered inbound calls / total inbound calls) x 100
Example: 250 inbound calls, 20 unanswered. 20 / 250 = 8%.
Benchmark: no published standard. We suggest under 10% during business hours, tracked separately from after-hours calls.
Watch out: a high voicemail rate during staffed hours signals a coverage problem, not a customer preference.
9. CSAT
Customer satisfaction score (CSAT) is the percentage of surveyed customers who rate an interaction as satisfactory.
CSAT = (satisfied responses / total responses) x 100
Example: on a 5-point scale, count 4s and 5s as satisfied. 90 of 120 responses are 4 or 5. CSAT = 75%.
Collection: a post-call SMS or IVR prompt, or an email, sent within minutes of the call.
Watch out: low response rates skew results. Track the number of responses next to the score.
10. NPS or CES
Net Promoter Score (NPS) measures loyalty, and Customer Effort Score (CES) measures how easy it was to get help.
NPS = % promoters (scores 9-10) - % detractors (scores 0-6)
CES = average rating of "It was easy to get my issue handled" (1-7)
Example: 50% promoters and 20% detractors give an NPS of +30.
Collection: a survey question, after the call for CES and quarterly or after key events for NPS.
Watch out: SQM finds each 1% improvement in FCR raises interactional NPS by 1.4 points on average, so NPS movement often traces back to resolution.
11. Cost per call
Cost per call is your total call operation cost divided by calls handled.
Cost per call = total operating cost / calls handled
Example: $42,000 monthly cost (wages, software, telecom, management) across 3,000 calls = $14 per call.
Benchmark: depends on your cost structure, so track your own trend. SQM estimates that every 1% FCR improvement saves a typical midsize call center about $286,000 a year.
Watch out: cutting cost per call by rushing calls usually increases the number of calls.
12. Repeat call rate or transfer rate
Repeat call rate is the share of callers who contact you again about the same issue. Transfer rate is the share of calls moved to another person.
Repeat call rate = (repeat callers within X days / total callers) x 100
Transfer rate = (transferred calls / calls handled) x 100
Example: 1,000 calls, 120 repeats = 12%. 90 transfers = 9%.
Benchmark: none sourced. Repeat rate is roughly the mirror image of system-inferred FCR.
Watch out: a high transfer rate often points to a routing problem. Fix the menu or queue setup before blaming agents.
Which call center metrics can a phone system report on its own?
A phone system reports the metrics based on call events: volume, answer time, abandonment, talk time, missed calls, voicemail and service level. It cannot report metrics that depend on outcomes or opinions, such as FCR, CSAT or cost per call, because those need data from a CRM, surveys or finance.
| Metric | Phone system alone? | What else you need |
|---|---|---|
| Call volume, peak hours | Yes | Nothing |
| Answer time, ASA | Yes | Nothing |
| Abandonment, service level | Yes | Queue or ring-group reporting |
| Talk time, AHT (partial) | Mostly | After-call work time from agent status or CRM |
| Missed calls, voicemail | Yes | Nothing |
| FCR, repeat calls | No | CRM or helpdesk tickets, dispositions |
| CSAT, NPS, CES | No | Survey tool or post-call prompt |
| Cost per call | No | Payroll, software and telecom costs |
Pulled directly from the phone system
Call logs give you volume, timestamps, duration, answered versus missed, and voicemails. If your system supports queues or ring groups, it can also compute wait time and abandonment. For a setup walkthrough, see our guide to a small call center phone system.
Needs CRM or helpdesk data
FCR and repeat rate need to know whether the issue was solved. That means a disposition field or a ticket status. Voicalyst's AI call summaries write up each call, and the HubSpot calling integration logs calls to contact records, which gives you a place to capture outcomes without manual notes. Our AI call summary guide covers how to turn those summaries into resolution tags.
Needs surveys
CSAT, NPS and CES exist only if you ask. A one-question text or IVR prompt after the call is the lightest way to start.
Needs finance or HR inputs
Cost per call and utilization need wages, software fees, telecom charges and paid hours. Pull these monthly from accounting and payroll. If you are still choosing tools, see call center software for small business.
What call center targets should you set by team size?
Small teams should track fewer metrics with looser targets, while larger teams add queue and cost metrics. The targets below are our recommended starting points, derived from the cited benchmarks. They are not published industry standards, so adjust them after four weeks of your own data.
| Team size | Track first | Starting targets (ours) |
|---|---|---|
| Solo to 5 agents | Missed call rate, abandonment, AHT, CSAT | Missed calls under 10%, abandonment under 8%, CSAT 80%+, AHT set from your baseline |
| 6 to 20 agents | Add service level, ASA, FCR, occupancy | 80/20 service level, ASA 20-30 seconds, FCR 70%, occupancy 75-85% |
| 20+ agents | Add NPS or CES, cost per call, repeat and transfer rate | FCR at or above 70-75%, occupancy 80-90%, track cost per call monthly |
Solo to 5 agents
At this size, one sick day or one long call changes the numbers. Use weekly rolling averages, not daily figures, and focus on whether callers reach a person.
6 to 20 agents
Queues start to matter. Add service level and ASA, and begin recording a resolution disposition on every call so FCR becomes measurable.
20+ agents
Variance smooths out, so you can set individual targets and run occupancy against the Call Centre Helper band. Add survey metrics and monthly cost per call.
How do call center metrics conflict, and what guardrails help?
Call center metrics conflict because improving one often hurts another: faster calls can lower resolution, and high occupancy can drive burnout. The fix is to pair every speed metric with a quality metric and review them together.
AHT vs FCR
Cutting average handle time pushes agents to end calls early, which creates repeat calls. SQM's data shows what is at stake: each 1% of FCR is worth about $286,000 a year to a typical midsize center, and 95% of customers stay when FCR is achieved. Guardrail: never evaluate agents on AHT alone, and flag AHT only when FCR is steady or falling.
Occupancy vs burnout
At 90% occupancy, agents get almost no gap between calls. Guardrail: cap target occupancy for small teams around 85% and watch ACW time for signs agents are skipping notes.
Abandonment vs staffing
Abandonment falls when you add staff, but idle time rises. Guardrail: staff to the hourly volume curve and use routing menus to move simple requests away from live agents. See our notes on IVR call routing.
Speed vs quality in sales calls
Reps measured on dials per day tend to rush conversations. Guardrail: pair activity metrics with conversion or next-step rates.
Which metrics matter for sales and outbound teams?
Sales and outbound teams should track connect rate, talk time per rep, speed to lead and calls per rep per day. Most call center KPI lists assume inbound support, so these four fill the gap. We do not give benchmarks here because we have no sourced figures.
Connect rate
Connect rate = (calls reaching a live person / total dials) x 100
Example: 60 connects from 300 dials = 20%.
Talk time per rep
Talk time per rep = total talk minutes / reps / days
Example: 4,800 minutes across 8 reps over 5 days = 120 minutes per rep per day.
Speed to lead
Speed to lead = time of first call attempt - time lead was created
Track the median, not the average, since one forgotten lead skews the mean.
Calls per rep per day
Calls per rep per day = total outbound dials / (reps x working days)
A power dialer automates dialing and logging, which makes these four numbers easier to capture cleanly.
How do you start tracking call center metrics this week?
You can start tracking call center metrics in one week by writing down definitions, choosing four or five KPIs, setting a weekly review and automating data capture. Do not wait for a full dashboard, because a spreadsheet and call log export are enough to establish a baseline.
Set definitions in writing
Document the threshold for service level, the short-abandon rule, the repeat-call window and what counts as "resolved." One shared definition prevents the FCR comparison problem described above.
Pick 4-5 starter KPIs
Use the team-size table. For most small support teams that means missed call rate, abandonment, AHT, FCR and CSAT.
Build a weekly review routine
Pick one 30-minute slot a week. Review a four-week rolling trend, list two outliers, and assign one action.
Automate capture with call logs, summaries and CRM sync
Manual logging breaks first. Use call logs for volume and answer data, AI summaries for outcome notes, and CRM sync for dispositions. Our manager review workflow shows how to audit those summaries in about 15 minutes a week. If you want one place for call logs, summaries and HubSpot sync, Voicalyst is built for small support and sales teams.
Frequently Asked Questions
What are the 5 key call center metrics?
The five most useful are service level, average handle time, first call resolution, abandonment rate and CSAT. Together they cover speed, efficiency, resolution, lost demand and customer opinion. Small teams can swap service level for missed call rate if their phone system does not report queue thresholds. Add occupancy and cost per call as the team grows.
What is a good first call resolution rate?
SQM Group's 2024 benchmark found a 69% average across industries, with individual centers ranging from 43% to 88%. Call Centre Helper cites 70-75%. Because companies define resolved differently, compare yourself to your own trend first, using one consistent definition, and aim to gain a few points per quarter.
How do you calculate average handle time?
Add talk time, hold time and after-call work for all handled calls, then divide by the number of calls handled. For example, 1,300 total minutes across 200 calls gives 6.5 minutes. Exclude abandoned and unanswered calls, and use the same date range for both numbers.
What is a good call abandonment rate?
No single sourced standard exists, and ranges vary by industry and by whether very short abandons are excluded. As a starting point, we suggest keeping abandonment under about 8% of offered calls for small teams and investigating any week that jumps. Always divide by offered calls and document your short-abandon rule.
What is the most important call center KPI?
For most support teams it is first call resolution, because it ties to cost and loyalty. SQM reports that when FCR is achieved, 95% of customers continue doing business with the organization. Sales teams should watch connect rate and speed to lead instead. Always pair a speed metric with a quality metric.