Customer experience often breaks after the first conversation, not during it.
A customer may receive a quick response, speak to a capable agent, and share the right information. The experience still fails if the work needed to solve the issue gets trapped between service, operations, fulfillment, IT, finance, or field teams.
For Daniel Wilks, Vice President of ServiceNow CRM EMEA, that gap exposes a practical limit in many CRM and service strategies. The customer-facing layer may look modern, but the resolution process still depends on employees moving information between disconnected systems. Wilks framed the issue as a handoff problem:
“The breakdown often happens at the handoff between the initial interaction and whatever needs to happen next.”
In a recent CX Today interview, Wilks explored the wider CRM shift from customer record to customer resolution, arguing that enterprises need to connect sales, service, operations, fulfillment, and finance around shared workflows rather than leaving employees to carry context between systems.
That handoff is now where many CX programs need closer attention. A better channel can help a customer ask for support, but connected operations decide whether the business can complete the work behind the request.
Where Resolution Breaks After the First Contact
Service journeys often begin in a contact center, chatbot, portal, or self-service flow. Resolution may then require a billing update, inventory check, field visit, IT incident, finance approval, or fulfillment process.
Customer experience starts to deteriorate when those steps sit in separate systems with unclear ownership.
Wilks argued that employees often become the connective layer when applications and teams do not share context. Agents may need to copy information from one system to another, chase internal teams, or ask customers to repeat information already provided. Wilks outlined the operational burden:
“That can leave employees bridging the gaps themselves, moving between applications and manually carrying customer context from one step to the next.”
ServiceNow’s CX Shift research found that resolving a single customer problem can require employees to work across three to five applications. The impact reaches customers as slower updates, repeated explanations, inconsistent responses, and cases that appear active without moving toward closure.
Connected operations bring that same issue into the work behind the interaction. A customer cannot feel understood if the organization loses the context as soon as the request leaves the front office.
Better Channels Still Need Connected Work
Investment in channels, self-service, and customer data can improve access. Those investments do not guarantee resolution when the operational path behind the journey remains fragmented.
Wilks pointed to the difference between improving the front door and completing the work that follows. A customer may use a digital channel to report a fault, change an order, or ask for help, but the outcome still depends on whether the next team has the information, authority, and workflow needed to act. Wilks described the limit of front-end improvement:
“Better front-end experiences cannot compensate for disconnected processes behind them.”
That observation changes the CRM discussion. CRM cannot only store the interaction or display the customer record. A more useful model connects the customer context to the next action.
A service issue might need field operations to assign an engineer, finance to approve a credit, inventory to confirm availability, or IT to fix an underlying system problem.