Editorial
On-Demand Webinar
Do More with Less: Modernizing the Cloud Contact Center
The Gist
- Flows carry the real operational logic. What looks like a simple process often encodes policies, exceptions and institutional knowledge that determine whether work actually gets resolved.
- Context-rich data is the missing link. Disconnected logs and reports don’t move work forward — continuous, outcome-linked data is what preserves meaning across handoffs.
- AI’s value is portability, not automation alone. Agentic AI doesn’t eliminate workflows; it allows work and context to move together across systems without breaking the customer story.
I still remember an early helpdesk incident that was supposed to be simple — but wasn't. The issue touched five backend systems, two IT teams and a trail of emails no one fully understood. By the time it was resolved, the original problem barely resembled what the user experienced.
Recently, I observed a same pattern. A customer service agent opened a ticket, requested more information and escalated the issue. They did everything right, but they still lost context every time they handed it off. And by the time the issue reached the right specialist, you could barely recognize the original story.
The problem? No one had the full picture in one place. The work moved forward, but the context didn't.
This is how experience breaks inside complex organizations. Not because people don't care, and not because there's a lack of data (although a dearth of high-quality data is often an issue). Typically, the customer experience breaks down because work and context are fragmented across tools, teams and interfaces.
Table of Contents
- The Hidden Structure Behind Broken Experiences
- What AI Actually Changes (and What It Doesn't)
- Why Flow and Data Are the Key to CX
- Don't Skip the Customer Trust Layer
- The Portfolio Reframe: Evaluate Moats, Not Apps
The Hidden Structure Behind Broken Experiences
When you strip the tooling away, most operational work comes down to two things:
- Flow: the sequence of steps that turns intent into outcomes
- Data: the context that makes flows smart, safe and correct
Until now, flow and data have usually been tied to individual systems and screens. The work only moved forward when someone clicked the right buttons, in the right order, using the right tools. And any context was typically stuck in the past, rather than staying tied to the work.
The result is a failure pattern that's all too familiar:
- Customers repeat themselves
- Employees bounce between systems
- Resolution slows as agents have to reconstruct context manually
- Trust and brand reputation take a hit even when the "fix" eventually lands
Most organizations have tried to solve this with better processes, more integrations or more dashboards — but these elements don't change the underlying shape of the work.
Once you see the flow vs. data split clearly, you can start evaluating your stack in a new way: determining which tools have real moats, and which ones are about to feel a lot more replaceable.
Related Article: What's Behind the Best and Worst Customer Service Strategies?
What AI Actually Changes (and What It Doesn't)
There's a lot of hype around AI "agents" running everything end-to-end. That's not the real shift, especially since a lot of it is AI washing that just makes a platform easier to use.
The meaningful change is simpler: Agentic AI does not make flow disappear. It makes flow portable. In other words, it makes it practical for work to move without requiring people to click between systems — and for context to follow that work in real time.
Instead of a person stitching together information from multiple, siloed tools, AI systems can:
- Gather relevant customer and order context across systems
- Propose next actions
- Execute approved steps
- Verify whether the outcome actually worked for your organization and the customer
This doesn't remove humans from the process. It removes unnecessary choreography. And when work no longer depends on specific screens or institutional knowledge, organizations gain something critical: portability. The work can keep going forward without a costly reset at every handoff.
Why Flow and Data Are the Key to CX
Some tools matter because of flow — the way they encode policies, edge cases and operational nuance that would be risky to recreate elsewhere. Others matter because of data—high-quality contextual signals that explain not just what happened but why.
However, many tools have survived simply because they sit at the heart of the CX process.
Instead of seeing your stack as a collection of apps, try to break it down into flows and data sources. Then choose your most painful workflows and ask:
- Is the flow uniquely valuable, or just a series of steps? Unique flows embed governance, handle real-world anomalies and make outcomes auditable and verifiable over time.
- Is the data uniquely valuable, or can it be sourced elsewhere? Unique data is continuous, contextual, trustworthy, governed and tied to outcomes — not just raw logs or delayed reports.
When a tool offers neither, it's likely contributing to experience friction rather than resolving it.
With AI agents, you don't just need more data — you need the right data with the right context. That's when data becomes a shared resource that can power multiple flows, giving you an even deeper moat.
Don't Skip the Customer Trust Layer
Your customers don't only care how fast something runs. They care whether it works — and whether it solves their problem for good.
AI systems that can act across environments introduce real risk if they're wrong at speed. Successful organizations know the importance of solid guardrails, including scoped execution, human approval at key points, clear audit trails and verification that the fixes actually work.
If you're evaluating tools, ask vendors to show you those controls — not as slides, but as mechanisms. (You should also ask if their platform can operate headless, in other words, what do you lose if you remove their UI from the story?)
Webinar
Mar
24
Operational Efficiency in Government: Delivering Modern Service on Real-World Budgets
See how state and local agencies use AI to cut costs, boost efficiency and deliver modern service to citizens.
Register
Webinar
Mar
24
Beyond Modernization: Engineering a Secure, Mission-Critical Contact Center
A straight conversation for leaders who need to build an operation that's actually ready for AI.
Register
Webinar
Mar
25
Content Leaders Collective: Navigating Content Decisions at Scale
Discover how content leaders are modernizing content operations, avoiding costly missteps and preparing for scale and AI.
Register
Webinar
Mar
26
New Research on AI for CX: What Consumers Want, What Enterprises Prioritize and Where the Gap is Growing
Based on Ada's 2026 survey, this session explores evolving expectations for AI-powered CX.
Register
Webinar
Mar
26
Do Learning Programs Really Work? How to Turn Education Into Engagement In Healthcare
See how leaders are using learning programs to build trust with healthcare professionals and create measurable engagement.
Register
Webinar
Mar
31
The Repeat Contact Problem: The Back-Office Answer
NiCE and Aberdeen reveal the real CX issue and how top teams fix it.
Register
Evaluating CX Tools Through Flow and Data Moats
Editor's note: Not all tools in your stack are created equal. This framework helps identify which systems provide defensible value — and which are simply along for the ride.
| Evaluation Dimension | High-Value (Moat) | Low-Value (Replaceable) | Key Question to Ask | AI Impact |
|---|---|---|---|---|
| Flow (Operational Logic) | Encodes policies, edge cases and governance; handles real-world complexity and exceptions | Linear, generic steps that could be recreated in another tool with minimal effort | Does this workflow capture unique institutional knowledge or just process steps? | AI can execute and orchestrate flows — but only valuable flows are worth preserving |
| Data (Context Quality) | Continuous, contextual, governed and tied to outcomes; reflects customer reality in real time | Static logs, siloed reports or delayed metrics with limited context | Is this data uniquely valuable, or can it be sourced elsewhere? | AI depends on high-quality context; poor data leads to fast but flawed decisions |
| System Role in CX | Actively improves resolution quality and speed by preserving context across touchpoints | Acts as a pass-through or handoff point where context is lost or fragmented | Does this tool reduce friction, or does it introduce more handoffs? | AI reduces the need for system hopping, exposing weak links in the stack |
| Dependency Risk | Difficult to replace without operational disruption due to embedded knowledge or unique data | Easily swapped with minimal impact on outcomes | What breaks if this tool is removed tomorrow? | AI increases portability, making non-differentiated tools easier to replace |
| Trust and Governance | Includes audit trails, validation loops and controlled execution of actions | Lacks transparency, validation or safeguards for automated actions | Can this system prove outcomes are correct and compliant? | AI amplifies risk — governance becomes a core differentiator |
The Portfolio Reframe: Evaluate Moats, Not Apps
The shift comes when you start thinking about your software portfolio as a set of unique flows and data lakes, rather than a stack of software apps. A "moat audit" can uncover which tools have a special flow, which tools have special data and which tools have neither and have survived largely because they were "where the work happened."
As flows become more flexible and data more shareable, this approach lets you reduce friction and resolve issues faster by rethinking where real value lives. If you can name where your true moats are — unique flow and unique data — about your AI platforms, and build customer service models that can actually keep up with the rate of change.
Learn how you can join our contributor community.