Why the Customer Journey Keeps Breaking – Context is the New Competitive Advantage
9 April 2026
Organisations are pouring millions into service modernisation. So why do customers still feel like they’re going in circles? The answer isn’t a lack of technology – it’s a lack of context.
The hidden problem:
Siloed fixes in a modernised world
Picture this: An organisation spends 18 months modernising its service operation. New ticketing system. New self-service portal. New AI chatbot. And yet customers are still calling them on the phone. Agents are still re-entering data. Complaints are still escalating. Nothing has fundamentally changed.
The problem isn’t that teams aren’t trying. It’s that they’re fixing symptoms, not causes. A broken journey looks like a broken channel, so organisations fix the channel. The real breakdown happens between the channels – in the invisible seams where data fails to follow the customer journey.
“Quite often that fix breaks because it’s a siloed fix — fixing what is thought to be one problem that turns out to be the symptom, not the root cause.”
The result? Fragmented journeys that drive multiple contacts, frustrated customers, exhausted agents and ever-rising cost to serve. Taking a shortcut, as someone recently observed, often turns out to be the longest journey.
What the analysts are saying:
Journey orchestration, integrated data and the cost-to-serve crisis
Forrester’s latest customer experience predictions land with a clear warning: Teams focused on speed, efficiency and volume handled are measuring activity rather than outcomes. The faster you handle broken interactions, the more you generate – a death spiral driven by the wrong KPIs.
1/5 to 1/3
reduction in cost-to-serve when organisations get connected data and orchestration right
McKinsey points to the remedy: Unify data scattered across marketing, sales, product development and back-office functions, then use that single view to design end-to-end journeys with intelligent automation. Gartner goes further with ‘enterprise data planes’ – making the right data available at the right place and time to orchestrate every decision. Their BOAT (Business Orchestration and Automation Technologies) market is growing at 33.9% annually, with 70% of enterprises expected to consolidate onto unified automation platforms by 2030.
Forrester’s most urgent warning: At least two significant AI scandals are predicted in the near term, from organisations acting on AI-generated insights without proper context or human oversight. Enthusiasm for AI-led service is running ahead of the data foundations required to make it safe.
The vital ingredient:
Context: The one thing that changes everything
“What connects intake, triage, assessment and resolution is context. Without it, it’s very difficult to get any of them right.”
Consider a customer calling their broadband provider because they think they’re paying too much. Simple – except it isn’t. You need to know who they are, what package they’re on, what negotiating parameters agents can apply and whether any previous changes are still in progress. Get any of those wrong and they call back next month about a billing error. Now it’s a complaint.
Or a patient asking a hospital where to park. Trivial – until the agent can see this patient is elderly, attending for a significant procedure, with mobility flags on their record. Now the question becomes: Has transport been arranged? Are access arrangements in place? Context doesn’t just improve the answer – it can change the outcome for that patient.
Every service journey runs through four stages: Intake, triage, assessment, resolution. Context is the connective tissue between all four. Without it, mistakes cascade – wrong routes, duplicated effort, errors that need rework, loops that don’t close. Get it right and cost to serve drops by between a fifth and a third.
The AI risks nobody’s talking about:
Why agentic AI can accelerate failure
Agentic AI is genuinely exciting – efficiency gains of 30–50% are real. But an AI agent will relentlessly pursue its objective using whatever information it has. If that information is incomplete, the AI doesn’t hesitate. It just executes.
“If we’ve not presented the right information – if we’ve left it blind – agentic AI could be accelerating the mess.”
Organisations deploying AI on top of fragmented data risk delivering confidently wrong answers at scale. A major UK bank demonstrated this recently, exposing customers’ account details and National Insurance numbers through a modernised app built over an unchanged legacy core. The new experience looked modern. The architecture underneath it hadn’t changed. The risk with agentic AI isn’t intelligence – it’s ignorance. And ignorance, in this context, is a data problem.
The platform built for this:
Liberty: Where front-of-house and back-office finally connect
Most organisations have invested heavily in their customer-facing layer – CCaaS platforms, digital experience platforms (DXPs), conversational AI. The problem is that these front-of-house systems are only as good as what’s behind them. Without a back-office orchestration layer that can enable, integrate and operationalise the processes, AI agents and data they rely on, the front of house is performing without a script.
This is the architecture Netcall has built with Liberty. DXP and Converse CCaaS handle front-of-house delivery and orchestration of customer experience. The Liberty platform then goes beyond BOAT – consolidating RPA, iPaaS, low-code, intelligent document processing and process discovery, design and analytics into a single composable engine – does the back-office heavy lifting: Orchestrating workflows, exposing APIs, grounding AI agents with the right data and making sure context flows to wherever it’s needed next.
“Find. Engage. Resolve. Fulfil. All with shared context. That’s what Liberty was built for.”
When these layers work together, the results are tangible: Coordinated end-to-end automation, more personalised omnichannel journeys and lower operating costs from consolidating what was previously an unmanageable spread of point solutions. Process maps define the sequence and data required at each touchpoint – so the system knows not just what to do, but what information it needs to do it well.
One architecture, three interlocking roles
Liberty’s approach is best understood as three roles working in concert. The platform acts as the central orchestrator: Consolidating automation technologies, exposing orchestration APIs and providing the process intelligence that everything else depends on. Liberty Converse handles channel routing and the agent workspace – the multimodal layer through which customers and advisors interact. And Liberty AI provides the dialogue logic and RAG grounding that makes interactions feel intelligent rather than scripted.
Context – conversation summaries, customer history, RAG-grounded knowledge – moves across all three as the journey progresses. A question that starts in self-service carries its full context when it escalates to a voice call. An agent picking up a complex case sees everything: What was asked, what was tried, what the system already knows. No rework. No cold starts. No customer having to repeat themselves.
One architecture, three interlocking roles
One of Liberty’s most immediate commercial arguments is the reduction in automation sprawl. Most organisations have accumulated a fragmented estate of RPA bots, integration middleware, workflow tools and document processing systems – each with its own licensing cost, maintenance burden and skills requirement. Liberty consolidates these into a single platform, simplifying governance, reducing total cost of ownership and enabling AI-driven automations to run across CCaaS workflows without requiring a separate integration project for each one.
In the public sector, Citizen Hub and Tenant Hub layer casework capability over multiple legacy systems without touching them. In healthcare, Liberty’s Patient Relationship Management (PRM) surfaces clinical context – mobility flags, transport arrangements, appointment types – to agents who would otherwise be answering questions blind. University Hospital Sussex is a recent example: Light-touch to implement, but significant in the value it unlocks.
Days → Hours
processing time improvement at UK Power Networks after automating manual workflows with Liberty Create
£265,000
saved by the London Borough of Croydon replacing Microsoft Dynamics with Liberty Create
Human + AI: Better together
CCaaS and DXP platforms are evolving fast – GenAI and agentic capabilities are arriving quickly and the pressure to deploy them is real. But deployment without orchestration is precisely the risk the analysts are warning about. BOAT-type platforms are the natural place to operationalise AI-enabled services: Governing how agents behave, grounding them in clean and connected data and defining the handoff points where human judgment should take over. Liberty doesn’t position AI and human agents as alternatives – it orchestrates them as complementary layers. When a patient’s parking question is straightforward, automation handles it instantly. When the same question carries mobility flags and unconfirmed transport arrangements, Converse CX transfers the conversation to a human agent who already has the full picture – no repetition for the customer, no cold start for the agent.
Liberty AI also surfaces knowledge and context to advisors in real-time. A new agent with the right information at the right moment can perform at a level that previously took years to develop. That’s not just better service – it’s a more resilient operation that doesn’t depend on institutional knowledge walking out the door when experienced staff leave.
Measuring what actually matters
Liberty is built to surface the metrics that reveal whether journeys are working: First contact resolution, repeat contact rate, mean time to resolution, contact deflection — and failure demand. That last one is perhaps the most powerful: When you can see that a contact spike was caused by a billing communication sent last week, you fix the root cause rather than adding capacity to handle the symptom. The organisations that will lead in service transformation are the ones that build the data and orchestration foundations that make AI trustworthy – and that make every step of the journey work, not just the channel it travels through.
“The journey doesn’t fail because the channel is weak. It fails because context isn’t flowing.”
About the author
Richard Higginbotham
Product Marketing – Intelligent Automation
Richard and his team bring the Liberty platform to life – showing how people and AI can work better together. With a background in transformation, data and enterprise tech, he’s helped organisations across sectors modernise operations and reimagine service delivery, delivering human-centric solutions that make work smarter, safer and more effective.