The promise of a dynamic customer journey is the continuity that allows a customer to start researching a product on mobile during a commute, continue browsing on a laptop later that evening, open a chat the next day, call the contact center, and update details in an app over the weekend, and expect the business to understand that all of those moments belong to the same person.
But the reality behind every “seamless” journey is an increasingly complex identity problem: is this the same customer, acting in the same context, with the same permissions, preferences and consent status as before?
In a static journey map, that question can be glossed over. In a dynamic journey, it determines what the customer sees, which data the system retrieves, the authentication required, which offers are suppressed and what actions can be taken.
CRM platforms, CDPs, orchestration engines and AI-powered journey tools should connect interactions into a seamless narrative. But in practice, identity is rarely a single, stable record. It is a probabilistic, constantly shifting calculation influenced by device changes, channel switches, cookie loss, phone number updates, shared email addresses, contact center verification, consent state and system latency.
The issue is whether the business can recognize a customer with enough confidence to act.
Shared household devices, changing email addresses, multiple phone numbers, anonymous browsing, privacy restrictions, cookie deprecation and disconnected support systems all contribute to an “identity gap.” And if the identity context is wrong, the customer journey can fail in ways that are frustrating, risky or non-compliant.
Alex Salazar, Co-founder and CEO of Arcade.dev, told CX Today that many enterprises are underestimating how tightly identity and AI governance are becoming linked.
“Right now, in 2026, the biggest blocker to production deployment of agents is identity and governance.”
A customer who is recognized in-app may be treated as unknown when they call. A chatbot may authenticate a customer, only for the live agent to ask the same questions again. A CDP may merge two profiles with high enough confidence for marketing, but not enough confidence for account recovery. A CRM may hold the latest service case, while IAM holds the strongest authentication signal, and the orchestration layer has to decide which one matters.
The consequences are increasingly visible to customers in the form of duplicate outreach, incorrect offers, broken suppression rules, repeated authentication requests, support interactions routed to the wrong history and AI systems making decisions based on incomplete or mismatched customer records.
Forrester’s Identity Resolution Survey found that 70 percent of marketing leaders struggle to identify and reach audiences across multiple touchpoints, “making well-informed marketing strategies and connected customer experiences increasingly difficult to achieve.”
That challenge is forcing enterprises to rethink the assumption embedded in many journey orchestration programs that customer identity is stable.
Why Agentic AI Makes the Identity Problem Harder
Traditional customer journey mapping was built around relatively fixed identifiers. A customer logged in using one email address, interacted through a known device and maintained a relatively stable relationship with the brand over time.
Today’s journeys are far more fragmented. Modern CDPs attempt to solve this through identity resolution, the process of matching identifiers across systems into a unified customer profile. Most platforms combine deterministic matching, which relies on exact identifiers such as email addresses or phone numbers, with probabilistic matching, which uses behavioral patterns, device signals, IP addresses and statistical likelihoods to infer connections between records.
But a customer may be one record in CRM, another profile in the CDP, a separate login in IAM, and a partially matched contact in the contact center. Their consent may be stored in one place, their service history in another and their behavioral data somewhere else. A dynamic journey engine then has to decide, often in real time, what to trust.
The consequences go beyond the customer interaction, potentially creating security exposure.
If the system over-trusts a weak match, it may expose account information to the wrong person, and if consent status is not linked to identity in real time, the business may personalize or activate data it should not use.
In a CX Today roundtable panel, Mary Ann Miller, Fraud & Cybercrime Executive Advisor and VP of Client Experience at Prove, described the fragility of this kind of AI-enabled architecture through what she calls “data fuses,” the data feeds that power AI environments and customer-facing decisioning.
“If those data sources are dependent on your AI environment to work flawlessly, but you're not looking to see if one of those data sources failed, then suddenly the information going into the system is incorrect or not the right data.”
Miller’s point applies directly to identity orchestration. A journey may look dynamic, but if the data feed carrying the latest phone number, consent state, login status, service history, fraud signal or loyalty profile fails, the system may act on degraded context.
That carries more significant consequences as AI agents enter the journey with the ability to retrieve information, infer intent, trigger workflows and increasingly take action across downstream systems.
Orchestration platforms are increasingly functioning as security systems because they now determine who can access data, what actions can be taken, and how trust is evaluated across channels and workflows. Identity, authentication, fraud prevention, and consent enforcement are becoming embedded directly into orchestration logic.
