Accepted Service Factor

Accepted service factor (ASF) is the share of calls a contact centre answers inside a set time. It’s written as a pair, like 80/20: 80 percent of calls answered within 20 seconds. Most teams just call it service level, or telephone service factor.

The pairing matters. A target of 80/20 and a target of 90/15 both sound reasonable, yet they need very different headcount. The threshold does most of the work, and the percentage does the rest.

ASF also carries money. In most outsourcing contracts it’s the number that triggers a service credit when it’s missed, so it shapes both the staffing plan and the commercial terms you sign.

Key takeaways

• ASF is a paired target: a percentage of contacts answered inside a stated number of seconds.
• The name overlaps with service level and telephone service factor — the maths behind all three is the same.
• Erlang models turn the target into headcount, so a tighter threshold costs more agents.
• Contracts usually attach service credits to ASF, which makes it the most audited number on the floor.

How it works

ASF works by counting two things: how many contacts arrived, and how many of those were answered before the clock passed the threshold. Divide the second by the first, express it as a percentage, and you have the factor.

The clock usually starts when the contact enters the queue, after the automated menu. Some contracts start it at first ring. That single definition choice can move a reported figure by several points, so pin it down in writing.

Abandoned contacts are the second argument. Counting a caller who hung up after five seconds as a failure makes the number look worse than the service felt. Most teams exclude short abandons and say so in the definition.

Once the target is fixed, staffing maths takes over. Erlang models convert forecast contact volume, average handling time and the threshold into a required number of agents per interval.

Those numbers land in a workforce management plan — schedules, shrinkage allowances and intraday adjustments. Miss the plan by a few agents in a peak half-hour and the day’s ASF rarely recovers.

Staffing is the hard part because the base keeps moving. The U.S. Bureau of Labor Statistics puts the median hourly wage for customer service representatives at $20.59 in May 2024.

The same handbook projects employment falling 5 percent from 2024 to 2034, yet about 341,700 openings a year, all of them replacing people who leave. You’re holding a target against a base that never stops turning over.

Reporting interval matters too. A month that averages 80/20 can hide a fortnight in the 60s, so most delivery teams track ASF by half-hour and by day, then roll it up.

Interval choice is where the disagreements start. A 15-minute grain punishes short spikes; a daily grain smooths them away. Pick one, write it into the reporting spec, and stop renegotiating it every month.

There’s a ceiling worth knowing about. Pushing past roughly 90 percent answered in 20 seconds buys tiny gains in caller experience for large jumps in headcount, because you’re paying agents to wait.

Channel mix changes the shape as well. Chat and email queues borrow the same paired format, but the thresholds stretch into minutes and hours, and concurrency changes the staffing maths underneath.

Two centres can report the same factor and deliver a different experience. That isn’t dishonesty, it’s definition drift, and it’s why the audit clause deserves as much attention as the target itself.

Examples

ASF shows up wherever a queue has a promise attached to it. Banks, airlines, healthcare payers and government helplines all publish or negotiate one, and the number chosen says a lot about what the service is worth to the buyer.

In offshore outsourcing, 80/20 remains the default opening position. A Philippine or Indian delivery team will price a pilot against it, then quote a premium for 90/15 because the tighter threshold needs more agents idle and waiting.

Named markets matter too. Manila, Cebu and Bengaluru floors treat 80/20 as the standard quote, and buyers who want 90/15 pay for the extra seats rather than getting them absorbed.

Public services set standards as well. Performance.gov runs the U.S. federal customer experience programme under Executive Order 14058, which names High Impact Service Providers and publishes what people should expect from them.

That matters for anyone arguing service targets are a private-sector habit. When a government publishes expectations for its own helplines, a commercial 80/20 stops looking like an arbitrary number.

Retail and travel show the seasonal version. A team can sit comfortably above target through August, then miss badly across a Black Friday weekend when volume triples and the roster doesn’t.

Utilities give the clearest cost example. Winter outage weeks blow through any factor built on average volume, so many run a separate storm target and staff a surge bench against it.

Healthcare payers often run two factors on one floor — a tight one for clinical lines, a looser one for billing. Splitting the queues is cheaper than holding every caller to the strictest promise.

Banks show the compliance angle. Fraud and card-loss lines usually carry the tightest factor in the building, because a slow answer there costs far more than an agent’s idle hour — and regulators notice.

Airlines take a different route. When disruption stacks the queue, callback offers and messaging deflection protect the factor better than adding agents ever could.

The pattern repeats across industries: the tighter the promise, the more idle capacity you buy. That’s the trade every buyer is really signing when they pick a pair.

Related terms

ASF sits inside a small family of queue metrics, and most reporting disputes come from mixing them up. These are the terms you’ll see beside it on a weekly scorecard, and how each one differs from the factor itself.

• Service Level: the mainstream name for the same paired answer target, used interchangeably with ASF.
• Service Level Agreement (SLA): the contract document that turns the target into a penalty-bearing commitment.
• Average Speed of Answer (ASA): the mean wait across all contacts, which hides the long tail that ASF exposes.
• Abandon Rate Percentage: the share of callers who hang up before an agent answers, the failure side of the same queue.
• Rostered Staff Factor: the shrinkage multiplier that converts required agents into agents you must actually roster.
• Occupancy Rate: the share of logged-in time agents spend handling contacts, which rises as answer targets loosen.

FAQ

What does 80/20 mean in a call centre?

It means 80 percent of incoming contacts are answered within 20 seconds. The first number is the percentage, the second is the threshold in seconds.

Is accepted service factor the same as service level?

In practice, yes. Both describe the percentage of contacts answered inside a stated time, and telephone service factor is a third name for the same measure.

How do you calculate accepted service factor?

Divide the contacts answered within the threshold by the total contacts offered, then multiply by 100. Decide up front whether short abandons count against you.

What is a good accepted service factor target?

There’s no universal answer — 80/20 is the common default, while urgent or clinical lines run tighter and cost-led queues run looser.

Why do contact centres miss their service factor?

Usually because forecast volume, handling time or staff availability moved after the roster was already built.

If you’re comparing providers on their answer targets, the Outsource Accelerator library is a practical place to start.