Calls Handled
Definition
Calls Handled
Calls handled is the total count of inbound and outbound calls a contact centre finishes in a period, minus those dropping before an agent picks up. It’s the core voice metric behind staffing plans, SLA reports, cost-per-contact math, and daily agent targets.
The metric sounds simple, yet it drives more downstream decisions than almost any other call centre statistic. Workforce planners use it to build shift schedules, and finance teams pair it with average handle time to price client accounts.
Operations leads watch it hourly to spot backlog before service level slips. Finance closes the month against it.
Where it gets interesting: “handled” isn’t the same as “offered”. A call is offered the moment it hits the queue. It only becomes handled once an agent answers and finishes the conversation.
Key takeaways
- Calls handled counts completed inbound plus outbound calls, minus abandons and misroutes.
- The metric feeds workforce planning, cost-per-contact billing, and SLA scoring on every business process outsourcing (BPO) voice contract.
- Industry benchmarks sit around 40–60 handled calls per agent per 8-hour shift in general voice support.
- Deflection through interactive voice response (IVR), chatbots, and self-service cuts total volume but raises the complexity of the calls that survive.
- Global BPOs such as Concentrix, Teleperformance, and TTEC report handled-call volumes in the billions per year.
How it works
Every voice interaction runs the same short pipeline. A call arrives through the PBX or cloud dialler, hits a routing layer, then gets answered, sent to voicemail, or dropped. Only the answered-and-completed calls count toward the handled tally.
The core formula stays simple:
Calls Handled = Inbound Calls Answered + Outbound Calls Connected
Most operations report the two streams separately:
- Inbound calls handled — customer-initiated calls that reach a live agent and complete.
- Outbound calls handled — agent-initiated dials that connect to a real party, not voicemail or a busy tone.
Dispositions decide the edge cases, and that’s where disputes start. A call an agent answers but ends early usually still counts, while a transfer that never reaches a second agent gets stripped out at month-end reconciliation.
A calls-handled figure is only useful next to its cousins: average handle time (AHT), first call resolution (FCR), and call abandonment. Together they show how the queue actually behaved.
| Industry vertical | Median calls handled per agent per day | Typical AHT |
|---|---|---|
| Retail support | 55–70 | 4:00–5:30 |
| Financial services | 35–45 | 6:00–8:00 |
| Healthcare | 40–50 | 5:00–7:00 |
| Utilities | 50–60 | 4:30–6:00 |
| Tech support | 30–40 | 8:00–12:00 |
Sources: the ContactBabel UK Contact Centre Decision-Makers’ Guide 2024 and ICMI contact-centre benchmarks.
A well-run workforce management team pairs those medians with local shrinkage and adherence figures before it sets agent-level targets. Skip that step and the number looks arbitrary to the floor.
Examples
Handled-call volume scales with the size of the operator. The biggest global providers count interactions in the billions each year, while a single mid-market Philippine site reports its output per agent, per shift, on a client scorecard.
- Concentrix, the Newark, California-based BPO, reported handling more than 1.5 billion customer interactions across voice, chat, and email in fiscal 2024, with voice still the single largest share.
- Teleperformance, the Paris-headquartered group, operates roughly 500,000 workstations across 170 markets and reports tens of billions of contacts managed each year in its 2024 annual report.
- TTEC Holdings, the Denver-listed operator, publishes segment revenue tied directly to interaction volume. Its Engage segment serves financial-services and healthcare accounts where handled-call quality tracks tighter than raw volume.
- Foundever, formed from the 2023 Sitel-Sykes merger, runs 170,000 associates across 45 countries and consolidates handled-call reporting per client under one global scorecard.
For a mid-market BPO in Manila or Cebu servicing a US retail brand, a healthy target sits between 50 and 70 calls per agent per 8-hour shift once wrap time and shrinkage are baked in.
Sales-heavy outbound campaigns run lower per agent, because each dial needs longer discovery and objection handling. Score both campaign types on one target and you’ll punish the outbound team for doing the harder job.
Here’s what the invoice teaches you. Clients rarely dispute the handled count itself; they dispute what got excluded from it. That’s why the disposition list belongs in the contract, not in a floor-level cheat sheet.
Related terms
Calls handled sits inside a small family of voice metrics. Each one measures a different slice of the same queue, and reading any of them alone will flatter or punish an operation that doesn’t deserve it.
- Average Handle Time (AHT): the average duration of one handled call, including talk, hold, and wrap.
- First Call Resolution (FCR): the share of handled calls that resolve on first contact, with no callback needed.
- Call Abandonment: the counter-metric to calls handled, tracking callers who hang up before an agent connects.
- Interactive Voice Response (IVR): the routing layer that deflects some calls before they reach the handled pool.
- Occupancy Rate: the share of logged-in time an agent spends on handled calls rather than idle wait.
- Call Center: the operational unit whose daily output is measured first in handled calls.
FAQ
What counts as a calls handled?
A call qualifies as handled once an agent answers an inbound call or connects on an outbound dial and completes the conversation. Voicemail deposits, abandons, and misdirected transfers don’t count. Most platforms flag it in the disposition code.
How is calls handled different from calls offered?
Calls offered is the raw inbound queue volume — every call that hits the switch. Calls handled is the subset that actually reached an agent. The gap between the two equals the abandonment count for that period.
What is a healthy calls-handled number per agent per day?
In general voice support, 40–60 calls per agent per 8-hour shift is typical. Retail lines run higher at 55–70 because AHT is short. Tech-support desks run lower at 30–40, since sessions are longer and more complex.
Does chat or email deflection reduce calls handled?
Yes. A well-tuned IVR, chatbot, or self-service portal can absorb 20–30% of the volume that would otherwise land in the voice queue, per the Salesforce State of Service 2024 report. The calls that do survive tend to be harder and longer.
Who tracks calls handled, the BPO or the client?
Both. The BPO uses the figure for internal workforce planning and agent scoring. The client sees it on the monthly invoice as the billable-volume line, usually next to AHT and FCR in the SLA report.
Is calls handled still relevant with AI and omnichannel routing?
Yes — voice still carries 60–70% of contact volume in most regulated verticals, and calls handled remains the primary billing unit on nearly every BPO voice contract signed in 2025.
Ready to benchmark your own call-handling numbers against vetted providers? Get a free quote from pre-screened contact-centre partners on Outsource Accelerator.
Independent
