Call drivers
Definition
Call drivers
Call drivers are the reasons a customer contacts support: by phone, chat, email, or social. Each contact is tagged to a fixed list at wrap. The tagged mix turns raw volume into a map of what to fix, not just a queue to staff.
Most contact centres keep those reasons in a taxonomy: a 15-to-40-line list covering “billing dispute” or “password reset.” Agents pick one at call-close.
The taxonomy feeds every workforce plan, self-service business case, and product feedback loop a contact center runs. Without it, more headcount treats symptoms and never causes.
The discipline started at telco and utility centres tracking Interactive Voice Response (IVR) selections in the 1990s.
It’s now standard at every business process outsourcing (BPO) provider of scale, and at in-house support teams where the taxonomy feeds the product roadmap directly.
Key takeaways
- A call driver is the specific reason a customer contacts support, tagged from a 15–40 line taxonomy on every interaction.
- Drivers split into external triggers (seasonality, marketing, outages) and internal ones (launches, policy changes, defects).
- The top five drivers usually account for 60–80% of total contact volume.
- Managed drivers feed the product roadmap; unmanaged ones inflate headcount indefinitely.
- Deloitte’s 2024 Global Contact Center Survey found driver-level tracking cut cost per contact 15–25% within 12 months.
How it works
Call drivers work as a diagnostic layer on top of raw contact volume. Every interaction — voice, chat, email, social — is tagged against a fixed taxonomy at wrap, and the weekly aggregate shows which upstream problems generate the most inbound cost.
A working taxonomy has three columns: the driver, its parent category, and the root cause ops suspects. Agents pick one driver from a dropdown at call-close. QA reviews a 5–10% sample weekly to catch tag drift.
The list splits into two families, external and internal, because each needs a different fix owner:
| Family | Example drivers | Fix owner |
|---|---|---|
| External (market, event) | Seasonal spike, marketing campaign, economic shift, weather event | Marketing, forecasting, workforce management |
| Internal (product, ops) | Product launch, service outage, policy change, defect | Product, ops, comms, engineering |
Deloitte’s 2024 Global Contact Center Survey found operations tracking driver-level data see cost per contact fall 15–25% within 12 months of a taxonomy refresh — driven almost entirely by moving the top three drivers to self-serve.
Salesforce’s State of Service report tracks the same self-service shift across service teams, with automation absorbing the highest-volume, lowest-complexity reasons first.
Tag hygiene matters as much as the list itself — a disciplined 30-line taxonomy beats a 200-line one nobody uses. ICMI’s resource library is where most centres pull their sampling and calibration routines.
Most operations cap tagging at 30 drivers so an agent can scan the list mid-call. Average handle time (AHT) then shows which of those drivers burn the most agent minutes.
Reporting cadence does the rest of the work. A weekly driver-mix report goes to ops, a monthly one to the client or the executive team, and each carries a movement column so nobody argues about whether a driver is growing.
Examples
Real call-driver programmes vary by industry, but the top five categories usually carry 60–80% of volume, a Pareto pattern that repeats across retail, telco, fintech, and airlines. Four named cases show the shape.
Amazon (US, retail). Return-related drivers account for 35–40% of contact volume in Q4. Amazon shifted “where is my return?” to self-serve in 2019, cutting agent-handled return contacts double digits year-on-year, per its investor day disclosures.
Southwest Airlines (December 2022). A weather-triggered scheduling meltdown drove more than 16,000 cancellations over ten days. Call volume peaked at roughly 11,000% of a normal weekday, according to Department of Transportation enforcement filings.
Klarna (2024). The buy-now-pay-later firm said its AI assistant handles work equivalent to 700 agents, covering the top five self-service-eligible drivers: payment status, refund query, dispute intake, plan change, and credit availability.
CEO Sebastian Siemiatkowski put the annual saving at US$40 million. That’s the clearest public example of a driver taxonomy doubling as an automation roadmap.
BT (UK, telco). Network-outage drivers spike when infrastructure fails. The January 2022 emergency-call outage pushed sustained overflow into commercial call centres, and BT reports quarterly driver-mix data through Ofcom’s complaints publications.
On the provider side, the driver mix decides staffing shape. A book dominated by password resets and status checks can run leaner and lean on chat; a book heavy on disputes and cancellations needs tenured agents and longer handle time.
The pattern across all four is the same: the driver-mix report doesn’t only size next month’s roster, it names which upstream team owns the fix. That’s why first-call resolution tracks driver hygiene so closely.
Related terms
Call drivers sit inside a wider contact-centre measurement set: the taxonomy names the reason, and the metrics next to it tell you what that reason costs. These are the closest neighbours and how each one differs.
- Call Center: the voice-only forerunner where driver-taxonomy discipline first emerged.
- First-Call Resolution (FCR): the metric most sensitive to driver mix, so unmanaged drivers drag it down fast.
- Average Handle Time (AHT): the minutes each driver consumes, which flags what to script or automate.
- Customer Satisfaction: the outcome variable driver management is trying to move.
- Business Process Outsourcing (BPO): the delivery model that made a driver taxonomy a contractual requirement.
- Key Performance Indicator (KPI): the reporting frame where driver mix sits beside AHT, FCR, and customer satisfaction.
FAQ
Here are the questions operations leads ask most about call drivers: how they differ from call types, how many belong in a taxonomy, who owns it, how BPOs price against it, and what AI automation changes.
What’s the difference between a call driver and a call type?
A call type is a coarse channel label like “inbound support” or “outbound sales.” A call driver is the specific reason inside that channel: “password reset,” “billing dispute,” “refund query.” Call types number three to five; drivers run 15 to 40.
How many call drivers should a taxonomy have?
Most well-run operations cap it between 15 and 30. Below 15 the tags are too coarse to act on; above 40, agents pick “other” or the nearest match instead of reading the list. Gartner’s 2024 contact-centre guidance suggests 20 to 25.
Who owns the call-driver taxonomy?
The ops manager owns day-to-day tagging and QA sampling. Product and engineering own the fixes for internal drivers. In a BPO relationship the client usually owns the taxonomy structure, while the vendor executes it and reports the mix.
How do BPOs use call drivers to price contracts?
Most outcome-based contracts price on cost per contact by driver family, with voice-heavy drivers at one rate and chat-eligible drivers lower. The provider reports driver mix monthly, and shared-savings clauses fire when the top three drivers move to self-serve.
How often should the taxonomy be reviewed?
Quarterly at minimum. Launches, policy changes, and new channels introduce fresh drivers within weeks. A stale taxonomy is worse than none, because agents force-fit inquiries into obsolete tags and the dashboard starts lying to leadership.
Do AI chatbots change call-driver management?
Yes: AI now absorbs the simplest status checks and reversals, leaving a smaller, higher-complexity mix that lifts average handle time and raises the skill floor.
Ready to scope an outsourced contact-centre programme with driver-taxonomy discipline built in? Explore vetted providers on the Outsource Accelerator hubs.
Independent
