A customer tells your agent she needs the shipment before the 14th, because the office is moving that weekend and after that there’s nobody at the dock.
That conversation happened in your channel. It contains a date, a reason, and a fairly clear consequence, and none of it will reach anyone who plans supply. Historically, that was a reasonable outcome, since there was no practical way to get it there.
Voice of the customer work has always had a credibility problem with operations, largely due to it’s historical framing. You can bring scores, verbatims, and a well-run survey program, and you’ll get a respectful hearing and not much else. The reason isn’t politics. Themes arrive too late and too vague to move a decision that’s already been made on a spreadsheet, and sampling four hundred calls a quarter was built to tell you how customers feel about you, which is a different question from how much of anything to build.
What’s changing is the volume and the structure. Agents are handling conversations at the edge of the enterprise, spoken and written, all day, and material that used to sit in recordings nobody had time to listen to is becoming something you can actually query. This is where the hidden value resides, ready to be extracted. An agent picks up why a customer wants something, when they really need it, what they’d take instead, and how much patience is left in the account, because customers surface that kind of insight in natural conversation rather than in the data-entry fields of your legacy ERP system.
The systems that run supply were never going to get there. Order management picks up the decision after it’s made, forecasting works from the pattern those decisions form, and distribution tracks where things went. They describe outcomes, which is what they were built to do. The reasoning behind the outcome wasn’t recorded anywhere, because until recently there was nothing capable of recording it.
This changes what a CX organization is for, and I don’t think many CX leaders have recognized this strategic shift yet. The function has spent twenty years downstream, reporting on the results of decisions made somewhere else. The conversation layer sits upstream of the order, which puts the earliest usable read on demand in the company inside your systems.
The raw material has been captured by the enterprise for years. Contact centers have recorded calls and stored chat transcripts for coaching, dispute resolution, and whatever the regulators ask for, and that archive has mostly sat there, because reading it in bulk was never realistic. Agents can work through it continuously now, and what surfaces looks different from a QA report. A cluster of accounts pushing on the same delivery window. A region where nobody will accept a substitution anymore. A product line where the complaints have shifted from price to availability.
Those are supply signals that happen to arrive through a customer conversation. When they come out of CX with evidence attached, the character of the conversation with the rest of the company changes. Satisfaction reporting after the fact is a modest thing to bring to an operating review next to the earliest available view of what demand is about to do. Planning teams have never thought of service as a source of that, which was a fair assumption for most of the last twenty years. The evidence is what changes it, and it moves CX into the strategic conversation the C-suite is already having about supply.
The bigger shift is what CX becomes as agents move to the edge of the enterprise. Service has spent its whole history as the last function to learn about a problem. The conversation layer makes it the first to watch intent take shape, weeks before that intent turns into an order, an allocation, or a shortage somebody has to explain to the board. None of that is really a tooling question. It’s a question about what the function is for, and it’s worth answering before the rest of the company works out what you’ve been sitting on.