Case Volume
Definition
Case Volume
Case volume is the total number of cases opened, handled, or closed by a support function inside a defined period, usually a week or a month. It is the workload denominator every support capacity plan starts from, and it sets the staffing baseline.
A case is not a contact. One customer problem can generate five emails, two calls, and a chat, yet still count as a single case — which is exactly why volume is measured at case level.
Case volume matters most when it is broken down. Opened, closed, and still-open counts describe three different operational realities, and only reading all three together shows whether the team is keeping up.
Key takeaways
- Case volume counts cases, not individual contacts, so it is immune to channel-hopping.
- Opened minus closed gives net backlog movement, the single most useful derived figure.
- Volume must be segmented by type and priority before it can drive staffing.
- Regulators and agencies publish annual case volume — which makes external benchmarking possible.
How it works
Case volume is counted by summing cases created in a period, then reported alongside cases closed and cases still open. The three counts together show whether the queue is shrinking, holding steady, or quietly building a backlog.
The core derived figure is: cases opened − cases closed = net backlog change.
Raw volume alone is close to useless for planning. A team that handles 4,000 password resets and a team that handles 4,000 billing disputes need very different headcounts.
| Segment | What it drives | Typical planning use |
|---|---|---|
| Case type | Handling effort per case | Skill mix and training |
| Priority tier | Response and resolution targets | Service-level design |
| Channel of origin | Tooling and routing | Deflection strategy |
| Reopen flag | Quality of prior closure | Root-cause review |
Segmented volume becomes a forecast. Historical case counts by week and type feed the same maths as call center forecasting, just with a longer handling cycle.
Discipline in case management is what keeps the count trustworthy. Duplicate cases, cases opened for internal admin, and cases left open after resolution all distort the number.
Public bodies publish case volume in a form private teams can borrow. The U.S. Equal Employment Opportunity Commission maintains enforcement and litigation statistics with charge receipt tables running from FY 1997 through FY 2025.
Tax administration shows the same seasonal shape at far larger scale. The IRS Data Book records 50.4 million taxpayers assisted by calling or visiting an IRS office in FY 2025.
Volume should be reported as a trend with a backlog line beside it. A flat opened count paired with a rising open count means the team is falling behind at a steady rate, which is easy to miss on a single-number dashboard.
Reopen rate is the quality check on the volume figure. A case reopened after closure inflates both the opened and the closed counts while representing a single unresolved problem.
Aged case buckets turn volume into a risk view. Splitting open cases into under seven days, seven to 30 days, and over 30 days shows where service commitments are about to be missed.
Deflection changes the number without changing demand. A good self-service journey reduces case volume while leaving total customer effort untouched, so the metric should never be read alone as a success measure.
Case volume also has to survive a tooling change. Migrating ticket systems almost always breaks the historical series, so planners keep a parallel count for a quarter either side of the cutover.
Examples
Case volume patterns follow the product and the calendar, not the support team’s preference. Three cases show how software, insurance, and healthcare providers read and plan against the same metric.
Software companies see release-driven spikes. A major version launch reliably lifts case volume for two to three weeks, so vendors staff a launch surge rather than a permanent uplift.
Insurers see event-driven spikes measured in days. A single regional storm can multiply claims case volume tenfold inside a week — which is why most carriers hold standing surge agreements with outsourced partners.
Healthcare revenue teams see steady, high-complexity volume. Denials and prior-authorisation cases arrive at a predictable rate but take days rather than minutes, so backlog rather than arrival rate is the binding constraint.
Retail banks split case volume by regulatory clock. Complaint cases carry statutory deadlines, so they are counted, aged, and staffed separately from servicing cases even when one team handles both.
Logistics operators see volume follow the shipment curve with a lag. Claims and tracing cases peak two to three weeks after a delivery peak — which is why post-peak headcount cuts so reliably create a backlog.
Related terms
Case volume connects the intake side of support to the tooling and timing that resolve each case. The terms below cover the smaller unit of work, the systems that hold it, and the clock that governs it.
- Case Management: the process of tracking a customer issue from intake to confirmed closure.
- Support Ticket: the individual record of a single reported issue.
- Ticketing System: the platform that stores, routes, and reports on cases.
- Open Ticket: a case still awaiting resolution, and the basis of backlog counts.
- Resolution Time: the elapsed time from case creation to confirmed closure.
- Workforce Management (WFM): the discipline that turns forecast case volume into schedules.
FAQ
Is case volume the same as ticket volume?
Not quite. A case can contain several tickets or contacts, so case volume is usually the smaller and more stable of the two counts.
What period should case volume be measured over?
Weekly for operational staffing and monthly for capacity planning. Daily counts are too noisy for anything but live queue management.
How does case volume drive headcount?
Multiply segmented volume by average handling effort per segment, then divide by productive hours available per agent.
What causes case volume to rise without demand rising?
Duplicate case creation, poor deflection, and reopened cases are the three most common causes.
Should closed cases be counted in volume?
Report both, since opened and closed counts together are what reveal backlog movement.
How does case volume differ from case backlog?
Volume counts the cases arriving or closing inside a period, while backlog counts the cases still open at the end of it.
Source partners scaling case-handling capacity can compare delivery models across Outsource Accelerator hubs.
Independent
