Thinking / Customer growth
Customer journeys are becoming decision systems
Why agentic customer experience depends on connected context, explicit objectives and governed decisions across the customer lifecycle.
The answer in brief
- What it is
- Why agentic customer experience depends on connected context, explicit objectives and governed decisions across the customer lifecycle.
- Best suited to
- Leaders who need to translate this issue into an investment, workflow, governance or capability decision.
- What useful progress looks like
- Journey maps remain useful for understanding needs, moments and organisational handoffs. Real customers arrive with changing context, move between channels and encounter operational conditions the map cannot predict. Agentic systems create the possibility of interpreting that context and selecting an appropriate action as the experience unfolds. This shifts design attention towards the decisions beneath the journey: what the organisation should do, which objective it serves and how the action connects to what happens next.
The question leaders ask
How will AI agents change customer journeys?
Agents can interpret live customer context and coordinate next actions across workflows. Leaders must define the objectives, trade-offs, permissions and human recovery paths that govern those decisions.
01
Static journeys describe an intended path
Journey maps remain useful for understanding needs, moments and organisational handoffs. Real customers arrive with changing context, move between channels and encounter operational conditions the map cannot predict. Agentic systems create the possibility of interpreting that context and selecting an appropriate action as the experience unfolds. This shifts design attention towards the decisions beneath the journey: what the organisation should do, which objective it serves and how the action connects to what happens next.
02
Start with a bounded customer workflow
A growing business should begin where the need is frequent, the outcome is measurable and the escalation path is clear.
Service resolution
Assemble context, classify need, recommend or complete permitted action and escalate complexity.
Onboarding
Detect missing steps, adapt guidance and coordinate timely intervention.
Opportunity nurturing
Use consented signals to determine whether, when and how to continue a useful conversation.
Retention
Identify service, usage or relationship signals and route a proportionate recovery action.
Case management
Carry context across handoffs so the customer does not repeatedly reconstruct the issue.
Source: McKinsey, Rewiring customer experience for the agentic era03
Make the objective and trade-offs explicit
An agent optimising handling time may shorten interactions while weakening trust. A system optimising conversion may create pressure or poor-fit demand. Define how customer value, commercial value, cost, fairness, risk and operational capacity are balanced. Specify when the customer can request a person, challenge an outcome or understand why an action occurred. The organisation should retain responsibility for the experience, even when several agents or suppliers participate.
04
Build towards connected orchestration carefully
Value can compound when context travels across adjacent workflows and actions remain aligned. Complexity also compounds. Shared identity, reliable memory, permissions, monitoring and cross-functional ownership become essential. Prove one workflow, learn how customers and employees respond, then connect the next decision only where the evidence supports it. This creates a route towards orchestration without hard-coding fragmented or unfair decisions into a faster system.
FAQ
Questions leaders ask.
Direct answers to the questions that commonly shape an initial conversation.
01Are customer journey maps becoming obsolete?+
No. They remain useful research and design tools. Agentic delivery adds a live decision layer that responds to context within governed boundaries.
02What should an AI customer agent optimise?+
Use a balanced objective reflecting customer outcome, trust, commercial value, cost and risk rather than a single efficiency measure.
03When must a human intervene?+
Provide intervention for ambiguity, distress, vulnerability, material consequence, repeated failure and any request that exceeds delegated authority.
04How should success be measured?+
Combine resolution, satisfaction, conversion or retention with quality, fairness, escalation, recontact, cost and employee outcomes.
Latest from the blog
Useful ideas for the decision in front of you.
Plate Spinner's PerspectiveFF＝01
Plate Spinner's Perspective · 8 minLearning to disagree with AI
Why a confident, persuasive answer should be the start of leadership judgement, not the end of it.
Read the articlePlate Spinner's PerspectiveFF＝02
Plate Spinner's Perspective · 7 minWhat does a Chief of Staff do in an AI business?
The operating role between technical possibility, commercial pressure and executive attention.
Read the articlePlate Spinner's PerspectiveFF＝03
Plate Spinner's Perspective · 7 minChief of Staff vs COO: where does the work split?
A practical distinction between enterprise operations and the executive agenda that cuts across them.
Read the articleApply the thinking
Design the customer decision before selecting the agent
Bring the live decision, workflow or commercial pressure. We will help translate the idea into a focused next step.
Discuss the implication