Translating Demand into Workload

Contact Center Field Guide · Foundation 03

Best for: Healthcare executives, contact-center leaders, workforce-management leaders, finance partners, and emerging leaders
Helps with: Capacity planning, workforce assumptions, channel comparisons, budget discussions, and demand scenarios
Reading time: Approximately 10 minutes
Last reviewed: October 7, 2026

Executive summary

Contact volume tells leaders how many interactions arrived. Workload estimates how much handling effort those interactions required.

For a simple voice calculation:

Raw workload = handled contacts × average handle time

If 10,000 calls require an average of six minutes each, they represent 60,000 minutes, or 1,000 hours, of raw handling work.

That arithmetic is important, but it is only the beginning. Contact centers must place capacity where work arrives, not merely accumulate enough hours across a month. Queueing, service objectives, shrinkage, occupancy, skill requirements, channel behavior, and schedule fit affect how raw workload becomes a staffing requirement.

The main executive distinction is this:

Workload describes work. It does not, by itself, equal required employees, scheduled employees, paid hours, expense, or savings.

Leaders who preserve those distinctions can evaluate capacity and investment choices more accurately.

The concept in plain English

Demand counts interactions or work items.

Handle time estimates the employee effort associated with each handled interaction.

Workload combines the two.

The International Customer Management Institute describes a contact as a basic unit of contact-center work and average handle time as an estimate of the labor required for one unit.¹ For voice interactions, handle time commonly includes talk, hold, and after-contact work. Nonvoice channels require definitions suited to how the work occurs.

The basic relationship is multiplicative:

More contacts create more workload when handling effort remains constant.

More handling effort creates more workload when contact volume remains constant.

This is why leaders should not evaluate volume and handle time separately when making capacity decisions.

A basic workload calculation

Illustrative example: These assumptions demonstrate the calculation and are not industry benchmarks. Results estimate raw workload under the stated conditions and do not represent required staffing or financial impact.

Assume a healthcare scheduling operation handles:

• 10,000 voice contacts during one week; and
• an average handle time of six minutes.

The calculation is:

10,000 contacts × 6 minutes = 60,000 workload minutes

60,000 minutes ÷ 60 = 1,000 raw workload hours

This result means employees collectively spent or would need to spend approximately 1,000 hours handling those contacts under the stated average.

It does not mean the center can schedule exactly 1,000 paid hours and meet its service objective. It also does not mean that 25 people working 40 hours each would provide the right coverage.

The timing of the work matters.

Why monthly averages are insufficient

Suppose the same 10,000 contacts arrive evenly across every open hour. The operation faces one capacity problem.

Now suppose a large share arrives on Monday morning, after a holiday, or following an outbound patient communication. The total workload may remain 1,000 hours, but the queue can become much more difficult to manage.

Live contact centers must respond to work that arrives by interval. When incoming workload temporarily exceeds available capacity, contacts wait or abandon.

This creates three planning layers:

Total workload

How much handling effort the period contains.

Workload distribution

When that effort arrives by day, interval, channel, contact reason, and skill requirement.

Service requirement

How quickly the organization intends to respond and how much waiting or backlog it accepts.

Annual or monthly workload can support budget planning. Interval workload supports operational staffing and scheduling. Leaders need both views.

Five inputs that shape workload

1. Contact volume

Volume should match the unit being planned. A forecast may count offered contacts, handled contacts, completed work items, messages, cases, or another defined unit.

Using offered volume with a handle-time average based only on answered contacts can create confusion. The planner must document which contacts enter each calculation.

2. Average handle time

For voice, a common formula includes talk time, hold time, and after-contact work divided by handled contacts.² Organizations should document local definitions because platform treatment of conferences, consults, transfers, and wrap time can vary.

An average can also hide a wide distribution. A six-minute average might include many brief interactions and a smaller number of complex requests requiring much longer.

3. Contact mix

Different reasons and channels require different effort. A portal-password reset, a referral-status question, a complex billing issue, and a multiappointment scheduling request should not be assumed to consume the same workload.

Changes in mix can increase workload even when total volume remains stable.

4. Timing

Workload must be placed into the intervals when work arrives or must be completed. Live voice and chat often require rapid response. Email, messaging, callbacks, and administrative work may permit delay, but they still need a response-time objective and backlog plan.

ICMI guidance on nonphone channels notes that workload and response-time expectations both influence required resources.³

5. Concurrency and active work

An employee may handle one voice interaction at a time but several chats concurrently. A messaging conversation may remain open while neither party is actively working.

Elapsed time is therefore not always handling effort. Digital workload calculations should distinguish active employee time from the total duration between the first and final message.

Workload is not staffing

Raw workload is one input to staffing. Several additional factors intervene.

Queueing and service objectives

Live contacts arrive randomly and require different amounts of time. Staffing only to the average workload would leave no protection against ordinary variation.

Queueing models estimate how many people must be available to achieve a selected responsiveness objective under defined assumptions.

Occupancy

Employees handling live contacts are not continuously busy at exactly the average rate. Some available time occurs between interactions. Occupancy describes the relationship between handling time and available contact-handling time.

Extremely high occupancy can create long waits, reduce resilience, and increase employee strain.

Shrinkage

Employees are paid for time that cannot be scheduled as available contact-handling capacity. Training, coaching, meetings, breaks, time off, system issues, and other activities affect the conversion from required available staff to scheduled or budgeted staff.

Schedule fit

The organization needs capacity in particular intervals. A schedule can provide enough total hours while placing them at the wrong times.

Skills and routing

Not every employee can handle every interaction. Dividing work into small skill groups can reduce the effective pooling of capacity and create simultaneous overstaffing and understaffing in different queues.

The full relationship is therefore:

Demand × handling effort = raw workload

Raw workload + timing + service objective + queueing behavior = required available capacity

Required available capacity + shrinkage + schedule design = scheduled workforce requirement

This is a conceptual sequence, not a single universal formula.

A multichannel example

Illustrative example: The figures below demonstrate method and should not be interpreted as benchmarks.

Assume an operation expects during one day:

• 1,000 voice contacts at six minutes of AHT;
• 600 chat conversations requiring four active employee minutes each; and
• 300 secure messages requiring five active employee minutes each.

Raw workload is:

The 165-hour total does not mean the channels should share one staffing assumption.

• Voice workload must often be covered by short intervals.
• Chat requirements depend on concurrency and how active time is measured.
• Secure messages may permit a longer response window but can create a backlog.
• Skills may overlap partially rather than completely.

Aggregating the hours supports a broad capacity view. Channel-specific planning still matters.

What workload does not tell us

Workload alone does not reveal:

• how quickly the organization should respond;
• how much capacity must be available by interval;
• the staffing model required to manage variation;
• whether work can be blended across channels;
• the amount of shrinkage;
• schedule efficiency;
• employee proficiency differences;
• whether the interactions resolved the underlying need;
• whether some demand was preventable; or
• the realized financial impact of a workload change.

A workload reduction can create potential capacity. The organization realizes a financial benefit only if it changes overtime, outsourcing, hiring, attrition replacement, staffing levels, or another cost decision. Otherwise, the organization may use that capacity to improve responsiveness, absorb growth, complete other work, or reduce strain.

Common mistakes

Converting monthly hours directly into employees

Dividing raw workload by paid hours ignores service objectives, interval coverage, shrinkage, schedule fit, and other constraints.

Treating every channel minute the same

Voice elapsed time, active chat work, asynchronous messaging, and deferred cases behave differently.

Applying one average across unlike work

A single AHT can obscure meaningful changes in contact mix and complexity.

Ignoring repeat demand

Several contacts may represent one unresolved need. The operation still must handle them, but leaders should not interpret all of the workload as independent new demand.

Calling potential capacity “savings”

Reduced workload can create options. Savings require a corresponding financial action and should not be claimed automatically.

Why executives should care

Workload connects patient behavior with workforce and financial choices.

It helps leaders answer:

• How much operating work did a change create?
• What capacity might a process improvement release?
• Why did staffing pressure increase despite stable contact volume?
• How could channel migration change employee effort?
• What portion of a business case represents theoretical workload versus realized expense?
• Which assumptions have the greatest influence on required capacity?

The arithmetic creates transparency. The discipline comes from preserving what each calculation does and does not establish.

Questions leaders should ask

1. What exactly counts as a contact or work item in this model?
2. Does the handling-time definition include all active employee work?
3. Are averages masking changes in complexity or contact mix?
4. How is workload distributed by interval, channel, and skill?
5. Which channels use concurrency, and how is active work measured?
6. What service objectives and queueing assumptions convert workload into capacity?
7. Which shrinkage assumptions convert available capacity into schedules?
8. Does the analysis describe workload, required staff, paid hours, expense, or realized savings?
9. How much workload reflects repeat or preventable demand?

Decisions this concept should inform

Workload analysis should inform:

• forecasts and staffing plans;
• channel and routing strategy;
• workforce budgets;
• process-improvement cases;
• digital-service investments;
• automation scenarios;
• overtime and outsourcing decisions;
• schedule design; and
• the evaluation of workload released by better resolution.

Illustrative-model policy: Calculations in this entry demonstrate operating relationships and are not industry benchmarks. Results estimate workload under stated assumptions. Leaders should substitute local demand, channel, handling, workforce, service, and cost data before making decisions.