Omnichannel (customer service)
Customer service that routes every channel through one engine and one agent workspace, so history and capacity carry across voice, chat, email and messaging.
Omnichannel customer service handles every contact channel, such as voice, chat, email, SMS and messaging apps, through one routing system and one agent workspace, with a shared history of each customer’s conversations.
How it works. Microsoft’s unified routing for Dynamics 365 works in two stages. Classification tags each incoming work item using rules or machine learning. Assignment then prioritizes it and matches it to a queue and a representative by skills, workload and availability, taking into account what that person is already handling on other channels. Salesforce describes Omni-Channel Unified Routing the same way: one routing engine, consistent decisions across channels, and representatives who can blend voice and messaging work. Each representative has a single capacity aggregated across all service channels, so a busy phone agent is not also handed three chats. AWS describes Amazon Connect Customer’s voice, chat, SMS, email and task channels as managed and analyzed in a single omnichannel solution.
Omnichannel and multichannel. Offering many channels does not make a service omnichannel. The test is whether the channels share routing, capacity and history. If a chat moves to a phone call and the person on the call cannot see the chat, the channels are running side by side as separate systems.
Agents as a channel. From a contact center’s point of view, structured requests from AI agents, arriving over a protocol such as A2A, are one more channel. Handled the omnichannel way, they get the same routing rules, the same customer history and the same path to a person as a chat or a call.
Neighbouring terms. Most CCaaS platforms provide omnichannel routing. Ticketing is how requests that need follow-up are tracked once routed. Live agent handoff is the move from an automated channel to a person.