WFM guideChannel management

Omnichannel contact centre

Q: What is the difference between omnichannel and multichannel contact centre?

A multichannel contact centre handles contacts on multiple channels (phone, chat, email, social media) but each channel operates independently. An agent answering a phone call has no visibility of the customer's previous chat conversation, and the customer must repeat their context when switching channels. An omnichannel contact centre joins the channels together through a unified customer record: when a customer calls after chatting, the agent sees the chat transcript, and the routing system can use the chat context to inform how the call is routed. Omnichannel requires a unified CRM or customer data platform that all channels write to and read from, and an omnichannel routing engine that can pass context across channels. Most operations claiming to be omnichannel are in practice multichannel — true omnichannel requires the technology investment and the agent training to use cross-channel context effectively.

Q: How does omnichannel affect contact centre WFM?

Omnichannel creates volume interdependence between channels that does not exist in a pure multichannel model. When a customer starts an issue on chat and then escalates to voice, the voice contact is not independent — it is the continuation of the chat contact. This means: (1) the voice volume forecast must account for deflection failures from chat (contacts that started on chat but were not resolved and moved to voice); (2) AHT on escalated voice contacts is typically shorter (the customer does not need to re-explain context, and the agent has the chat history), but agent effort is higher (they must read and synthesise the chat before and during the call); (3) scheduling must account for cross-channel skill requirements, since agents who handle escalated contacts must be trained and skilled across both channels. Omnichannel WFM requires the WFM platform to treat cross-channel journeys as a single demand stream, not as independent channel queues.

Omnichannel is not multichannel with a better name. Multichannel means handling contacts on multiple channels. Omnichannel means those channels share context: the customer does not restart their story when they switch from chat to voice. That distinction has profound implications for routing design, agent requirements, WFM planning, and technology infrastructure.

Multichannel vs. omnichannel

Multichannel

○Multiple channels exist and are staffed independently

○Each channel has its own queue, its own agents, its own AHT

○A customer switching from chat to voice is treated as a new contact

○Agent has no visibility of the customer's prior channel activity

○Volume on each channel is forecast independently

○WFM plans each channel queue as a separate demand stream

Most contact centres claiming omnichannel operate in this model.

Omnichannel

●All channels write to and read from a unified customer record

●Channel context is passed when a customer switches: agent sees prior interactions

●Routing engine knows the customer's channel history and routes accordingly

●A customer escalating from chat to voice is treated as a continuation, not a new contact

●Volume is modelled as cross-channel journeys, not independent queues

●AHT for escalated contacts accounts for context read-time (shorter re-explanation, longer agent cognition)

Requires unified CRM, omnichannel routing engine, and agent training to use cross-channel context.

The technology prerequisite

True omnichannel requires a unified customer data platform (CDP) or CRM that all channels write to in real time, an omnichannel routing engine with cross-channel context passing (Salesforce Omni-Channel, NICE CXone, Genesys Cloud CX, or equivalent), and agent desktops that surface the full cross-channel history in a single view. Without all three, you have multichannel with a policy that agents should check prior interactions. That relies on agent compliance rather than system design, and fails under volume pressure.

Omnichannel routing models

Channel-of-choice routing

How it works

Customer chooses their preferred channel. Routing respects the choice. If the customer moves to a second channel, routing connects them to the same agent where possible (agent continuity), or to a new agent with full context passed from the unified record.

When to use

Best for service operations where relationship continuity matters: financial services, healthcare case management, complex B2B service. Agent continuity reduces context loss and improves CSAT.

WFM implication

Agent continuity creates scheduling constraints: if the same agent must be available for a returning customer, they cannot be in break or off shift. WFM must model agent reservation windows for open cases.

Intelligent / predictive routing

How it works

Routing engine uses the customer's contact history, CRM segment, predicted intent (from prior chat or IVR input), and real-time agent attributes (skills, capacity, prior case familiarity) to route to the optimal agent. A customer who previously had a complaint handled by Agent A may be routed back to Agent A if available and appropriately skilled.

When to use

Best for operations with high contact complexity, high CSAT sensitivity, or where relationship banking (one agent per account) adds value. Also used to route vulnerable customers to trained specialist agents.

WFM implication

Predictive routing reduces the usefulness of simple skill-based headcount modelling. WFM must model agent availability across predicted routing preferences, not just raw skill groups. More complex; typically requires the WFM platform to integrate with the routing engine data.

Universal queue

How it works

All channels (voice, chat, email, social) enter a single queue. The routing engine assigns the next available appropriately-skilled agent to the next contact regardless of channel. An agent might handle a voice call, then a chat, then an email in sequence.

When to use

Best for operations with blended agents who are trained across all channels, and where volume fluctuates significantly between channels (the universal queue absorbs channel imbalances automatically).

WFM implication

Universal queue requires agents skilled across all channels, so the staffing model cannot separate channel-specific headcount. AHT planning must account for channel mix (voice AHT ≠ chat AHT ≠ email AHT). The Erlang C model cannot be applied directly: concurrency (for chat), backlog flow (for email), and Poisson queuing (for voice) are all in the same pool.

Agent requirements for omnichannel

Requirement	Why omnichannel raises the bar	Training implication
Written communication skills	Chat and email require the agent to write accurately, concisely, and in the right tone. Voice agents who are reskilled for chat without writing assessment produce low-quality written interactions.	Writing skills assessment before chat onboarding. Separate training track for written channel agents (grammar, tone, response templates, typing speed minimum).
Cross-channel context synthesis	In omnichannel, the agent must quickly read prior channel interactions and synthesise them into a coherent understanding of the customer's issue before the current interaction begins. This is a distinct skill from simply handling a single-channel contact.	Specific training on reading and using cross-channel history from the unified record. Simulated practice with pre-built case histories across channels before going live on escalated contacts.
Multi-tasking ability (for concurrent channels)	Agents in a universal queue may simultaneously handle 2 chats and an email while a voice call is waiting. The cognitive load is significantly higher than single-channel handling. Not all agents can do this at quality.	Concurrent channel handling is a capability that requires assessed readiness: not all agents can handle multiple chat sessions simultaneously at acceptable AHT and quality. Piloting concurrent handling before full deployment is best practice.
CRM / unified desktop proficiency	The value of omnichannel context is only realised if agents can find and use the cross-channel history quickly under the pressure of a live contact.	System proficiency assessment on the omnichannel desktop as part of training sign-off. Agents who cannot navigate the unified record efficiently will revert to treating contacts as new, destroying the omnichannel value.

WFM implications of omnichannel

Volume forecasting

Challenge

In a multichannel model, voice, chat, and email volumes are forecast independently. In omnichannel, channels are interdependent: a high chat-deflection day reduces voice volume; a chat self-service failure creates voice spikes. The forecast must model cross-channel demand, not independent queues.

Approach

Use a channel-flow model for omnichannel forecasting. Model the customer journey (intent → channel 1 → deflection? → channel 2) rather than starting with channel volume. Track cross-channel transitions daily to calibrate the flow model.

AHT modelling

Challenge

Omnichannel AHT is not simply a weighted average of channel AHTs. Escalated contacts (chat → voice) have a different AHT profile: shorter re-explanation time (context passed) but higher agent reading/synthesis time. First-contact AHT and escalation AHT must be modelled separately.

Approach

Tag contacts with their channel journey in the ACD. Calculate AHT separately for first-touch contacts and escalated contacts on each channel. Blend these by the expected escalation rate in the Erlang C and staffing calculations.

Skill group design

Challenge

Pure skill-based routing cannot express omnichannel readiness. An agent skilled for voice and chat does not automatically have the cross-channel synthesis skill, the writing proficiency, and the unified-desktop proficiency that omnichannel handling requires.

Approach

Define an 'omnichannel-ready' skill tier above individual channel skills. Only agents who have passed the full cross-channel training and assessment are placed in omnichannel skill groups. Maintain channel-only skill groups for agents still in single-channel mode.

Scheduling

Challenge

Agent continuity routing (same agent for returning customers) creates scheduling constraints: the preferred agent must be available within the customer's expected retry window. Standard shift scheduling does not account for case-level agent reservations.

Approach

For high-value segments where agent continuity is used, schedule agents in overlapping shifts that maximise availability windows. For standard omnichannel (context-passing without agent continuity), standard scheduling applies: the routing engine routes to the best available agent, not the same agent.

Omnichannel questions

What is the difference between omnichannel and multichannel contact centre?

Multichannel: multiple channels operate independently. Customer must repeat context when switching channels. Agent has no cross-channel visibility. Omnichannel: channels share a unified customer record. Agent sees prior channel interactions. Routing passes context when customers switch channels. Most contact centres claiming omnichannel are in practice multichannel; true omnichannel requires a unified CRM/CDP, omnichannel routing engine, and agent training to use the cross-channel context effectively.

How does omnichannel affect contact centre WFM?

Channels become interdependent: a chat-deflection failure creates voice spikes. Volume cannot be forecast as independent queues, so use a cross-channel flow model. AHT on escalated contacts (chat → voice) is different from first-touch AHT. Agent skill groups must distinguish omnichannel-ready agents from single-channel agents. Agent continuity routing creates scheduling constraints for high-value segments.