← ccPlanning Academy · Channel planning track
The blended multi-channel operation
ccPlanning academy · channel planning · deep dive
The blended multi-channel operation
Bringing the channels back together — without pretending they’re the same.
Slides done? Here’s the same idea in a bit more depth — the part worth keeping.
In depth: bringing the channels back together
Each channel needs its own method — that’s the rest of this track. The final job is recombining them into one workforce plan: deciding who handles what, when they flex, and how to see the whole operation at once. The mistake is jumping straight to “everyone does everything,” because the recombination has to be deliberate, not a shrug at universal agents.
Universal vs dedicated, honestly
The core trade-off is universal agents (handle any channel — flexible, and pooling efficiency lets fewer people cover the same demand) versus dedicated agents (one channel done well — higher quality, simpler to manage, but fragmented pools and a pooling tax). Most operations land in between, and the reason matters: full universal sounds maximally efficient, but real agents aren’t equally good or fast across channels, can’t truly do live voice and live chat at once, and lose proficiency when spread thin — so the theoretical pooling gain is real but the practical version is smaller. Plan on what people genuinely can do. And mind the live-channel pull: when an agent can do both, the ringing phone beats the ageing email every time, so without explicit priority and ring-fencing — reserved email hours, say — the patient channels quietly breach whenever live demand is up.
Common units, routing, and real-time
The trick to a single view is translating every channel into the same currency — required agent hours by interval — whether it’s live (Erlang), concurrent (chat factor), deferrable (throughput) or outbound (funnel). Only then can you see total demand, choose the universal/dedicated split, and staff coherently. Two things make the plan actually hold: routing, which is the control surface where your channel mix, priorities and concurrency limits live (a beautiful plan with routing that lets agents cherry-pick will fail), and real-time control across channels, because now intraday decisions move people between channels — pulling universals to voice in a call spike, pushing them to email when it’s quiet.
The principle to remember: separate to plan, common units to combine. Plan each channel on its own terms, recombine by converting all to required agent hours, choose the universal/dedicated balance honestly, protect deferrable work with priority rules, and remember routing and real-time control are how the plan holds.
Quick quiz
Five questions. Pick an answer to each, then check your score.
1. What’s the right sequence for a multi-channel plan?
The mistake is jumping straight to ‘everyone does everything’.
2. What’s the core trade-off in agent design?
Most operations land between the two — the pooling tax pushes toward universal, quality toward dedicated.
3. Why doesn’t ‘everyone does everything’ deliver the full theoretical gain?
The pooling gain is real but the practical version is smaller — plan on what people genuinely can do.
4. What happens to deferrable work when agents can also do live work?
The ringing phone beats the ageing email every time — reserve time or the patient channels breach.
5. How do you get all channels into one comparable plan?
Live (Erlang), chat (concurrency factor), deferrable (throughput), outbound (funnel) → common units.
Related: Skills-based routing & pooling and Reading the day’s signals.
You’ve finished the channel planning track. Ready for your certificate? Take the final exam →