← ccPlanning Academy

Blended & multi-channel forecasting

Free visual lesson · about 5 minutes · short quiz at the end

ccPlanning academy · forecasting

Blended & multi-channel forecasting

Calls, chat, email, async — four channels, not one bigger queue.

The big idea

You can’t just add the channels together.

It’s tempting to total all contacts and forecast one number. But each channel arrives differently, is handled differently, and is staffed differently. Add them up and you blur every distinction that matters.

Difference 1

Different arrival shapes.

Calls peak mid-morning. Email piles up overnight and lands first thing. Chat tracks web traffic and runs later into the evening. Four channels can have four completely different intraday profiles.

Difference 2

Concurrency changes the maths.

One agent handles one call at a time — but two or three chats at once. So chat volume doesn’t convert to headcount the way call volume does. Ignore concurrency and you’ll massively over-staff chat.

A 1 call A 3 chats at once

Difference 3

Real-time vs deferrable.

A call must be answered now — you staff to a service level. Email and async can wait hours — you staff to a backlog and a deadline. They’re different planning problems with different maths (Erlang for one, throughput for the other).

The right approach

Forecast each channel on its own.

Separate volume, AHT and profile per channel. Convert to a workload or requirement per channel using the right model. Only then combine — at the requirement level, accounting for which staff can flex across channels.

The blending question

Can the same person do both?

Universal agents who switch between channels pool capacity and need fewer people overall. Dedicated teams don’t. Your blended requirement depends entirely on how flexible your workforce really is — not how flexible the org chart says it is.

The trap to avoid

The “easy” blended average

Pooling all channels into one volume and one AHT feels efficient, but it averages away the very things that drive staffing — a 6-minute call and a 20-minute email become a meaningless “13 minutes” that fits neither.

You end up under-staffing voice at the morning peak and over-staffing chat all day — wrong in both directions at once.

The takeaway

Forecast separately, combine carefully.

Each channel has its own shape, concurrency and urgency. Model them apart, convert to requirement with the right tool, and only blend where staff genuinely flex. Adding raw contacts together is the fast road to a wrong plan.

Now test yourself ↓

1 / 8

Slides done? Here’s the same idea in a bit more depth — the part worth keeping.

In depth: four channels, four planning problems

The instinct when contacts arrive across calls, chat, email and messaging is to total them up and forecast one big number. It feels tidier, and it’s wrong, because a “contact” means something completely different on each channel. They arrive in different shapes, they’re handled with different concurrency, and some must be answered now while others can wait. Blend them and you don’t simplify the problem — you erase the distinctions that decide how many people you need and when.

The three things that don’t transfer

First, arrival shape: calls peak mid-morning, email piles up overnight and lands first thing, chat tracks web traffic and runs late into the evening. Four channels, potentially four different intraday profiles. Second, concurrency: an agent handles one call at a time but two or three chats at once, so chat volume simply doesn’t convert into headcount the way calls do — ignore it and you’ll massively over-staff chat. Third, urgency: a call is a real-time problem you staff to a service level with queueing maths; email and async are deferrable, so you staff them to a backlog and a deadline using throughput logic. Same operation, genuinely different mathematics.

Forecast apart, then blend only where staff really flex

The right sequence is to forecast volume, AHT and profile per channel, convert each into a workload or requirement using the model that suits it, and only then combine — at the requirement level. And the size of the blended number depends entirely on one honest question: can the same person actually switch between channels? Universal agents pool capacity and need fewer people overall; dedicated teams don’t. The answer is about how flexible your workforce genuinely is on the day, not how flexible the org chart claims it is.

The principle to remember: forecast each channel on its own terms, convert with the right tool, and blend only where staff truly flex. Adding raw contacts together is the fast road to a plan that’s wrong in both directions at once.

Quick quiz

Five questions. Pick an answer to each, then check your score.

1. Why can’t you just total all channels and forecast one number?

Different shapes, concurrency and urgency — adding them blurs every distinction that matters.

2. What does concurrency mean for chat?

Concurrency means chat doesn’t map to headcount like calls — ignore it and you over-staff chat badly.

3. How do real-time and deferrable channels differ in staffing?

Different planning problems — Erlang/service-level for live channels, throughput against a deadline for deferrable ones.

4. What’s the right order of operations?

Model each channel apart, convert with the right tool, and only blend at the requirement level.

5. What does the blended requirement depend on most?

Universal agents pool capacity; dedicated teams don’t. Real flexibility — not the org chart — drives the blend.