3. Omnichannel Enablement: Building the Right Team, Stack, and Routing Logic

Great support across channels doesn't happen by accident0:09

Great support across channels doesn't happen by accident. It takes intentional team design, a smart tech stack, and routing logic that connects the right customer to the right person at the right time. In this session, we're diving in to how to build the back end structure that enables excellent omni-channel experiences without creating chaos for your agents or leadership.

Let's start with team design0:36

Let's start with team design. The first thing you need to understand is that not all channels are created equal, especially when it comes to staffing models. Let's compare, voice and live chat to real time channels. They require constant availability, demand, fast reflexes, and emotional intelligence. They often have high concurrency pressure and they're ideal for dedicated roles or specialized live teams. Take email and social, asynchronous channels.

They can be batch handled, offer more time for detailed answers, and they're easier to distribute across time zones. Many orgs separate real time and async queues and staff accordingly. Trying to have one agent juggle chat, email, and calls could lead to burnout and slow resolution.

As you scale, routing logic becomes essential1:28

As you scale, routing logic becomes essential. Every minute your agents spend triaging instead of solving is wasted. Here's how smart teams design routing. Skill-based routing assigns tickets based on agent skills, product knowledge, tier level, language, or even tone fit. Channel-based queues, each channel get its own workflow, KPIs, and SLAs. You can still have blended agents, but you avoid cross-channel chaos.

Intent routing, often AI powered, tools like Zendesk, Intercom, or customer can analyze ticket intent and auto route it to the right team. Priority routing, high value customers, escalations, or VIP segments get prioritized and routed to top tier agents. When routing is clean, resolution time drops. FCR goes up and agents feel less overwhelmed.

Now, let's talk tools2:27

Now, let's talk tools. A common mistake, buying too much tech that doesn't play well together. The best Army Channel CX stacks have a unified CRM or help desk. It centralizes all channels into one view. Key players include Zendesk, Gorgeous, Intercom, Salesforce, and Customer. Then you have a collaboration leader, Slack, Teams, or internal note systems that let support tag other departments, escalate, or bring in ops or product.

Then you have routing and automation tools, tools like assembled for workforce management, customer for intent-based routing, or ADA for chat box. Next, you need an analytics layer to track performance across all channels in real time. The key isn't how many tools you have. It's how well they integrate and how usable they are for your team.

At Wistia, one of the first things on my list of priorities3:24

At Wistia, one of the first things on my list of priorities when I started was launching live chat for paid customers. The support team had tested chat as a support channel a few years before I'd started, but it hadn't worked out. So the goal this time around was to launch it thoughtfully as a permanent support channel for all paid users. The first challenge was to decide on what chat platform made sense for our team and our use case.

At the time, Zendesk had not yet integrated chat into the unified agent workspace, so chats loaded in a small iframe window. Because of this, as well as reporting being separate, I researched standalone chat software. But in my evaluations, I came across a newer help desk software called Dixa.

Since the team at Wistia was small and we wouldn't have a dedicated chat team, the fact that the agent experience for handling a chat was identical to the email experience and the way that Dixa offered chats and email tickets to agents seemed like it would reduce a lot of the cognitive load for the team. It enabled us to launch live chat in a way that wasn't overwhelming for the team. So we managed to migrate from Zendesk to Dixa in under six months.

We rolled out chat to our advanced and premium plan customers first to pressure test our scheduling and staffing and to ensure we could meet our customers' expectations. The initial launch was a success and we were able to expand live chat to all paid Wistia customers a year later and maintain an average c-set of 95% and immediate wait time of 48 seconds without increasing team headcount or burning out the team.

No matter how many channels you offer, it should feel like one conversation for your customer. That means investing in unified customer profiles. Every agent, no matter what channel they're working on, should be able to see. Customer history, including purchases, issues, previous contexts. Channel touch points and context, notes from other agents and internal tags or VIP flags. Why? Because 89% of customers get frustrated when they have to repeat themselves to multiple agents.

If your tools aren't surfacing contexts automatically, you're setting your team up for failure and killing trust.

On the channel isn't just about talking to agents, it's5:51

On the channel isn't just about talking to agents, it's about reducing contact in the first place. That's where smart deflection and self-service come in. Here's what modern teams are using, help centers with smart search articles that update dynamically based on ticket themes or seasonal volume. AA chatbots with escalation paths, bots that actually help, not frustrate. The best ones resolve FAQs, but escalate when needed. Embedded support in app or product.

Live help embedded into the product experience, especially in SAS or mobile. Feedback loops, deflection analytics to tell you which articles or bot flows reduce volume. Done right? Deflection isn't about avoidance, it's about empowerment. Customers want to solve problems fast. If you can help them do that without a human, they're often happier and your team is less stressed.

Let's look at a real example6:49

Let's look at a real example. An e-commerce brand Horatio worked with scaled from 10 to 100 agents in a year. Initially, they had one shared inbox for email and chat. Chaos, no routing, no ownership. Horatio implemented skill-based queues for product categories, chat bot triage for common issues, CRM sync with order management system, shift based schedules for peak hours and self service flows for shipping updates. What was the result?

32% drop in ticket volume, CSAT up 15 points, average handled time down 40 seconds and agent retention improved due to less stress. The tech wasn't fancy, the workflows were simple, but it worked because it was designed for scale. So to recap, design your team based on channel type. Don't ask agents to juggle chaos. Use smart routing to reduce triage time and match the right agent to the right issue. Choose tools that integrate, not just impress in a demo.

Create unified profiles that surface context and invest in self service as a core part of your omni-channel design. Consider AI chat bots if the budget allows it. True omni-channel isn't just a customer experience, it's a system and systems need structure. In the final video, we'll talk about how to measure omni-channel performance and what metrics actually matter when your customers are everywhere.