Stop Calling It Orchestration If the Customer Has to Start Over
If context dies at the handoff and ownership is fuzzy, you didn’t design a journey—you designed a workflow that shifts the real work to your customer.
A lot of companies think they’re orchestrating journeys when they’re really just sequencing messages.
The email is timed well. The offer is personalized. The next step is triggered.
But the customer is still repeating the problem. Still switching channels. Still trying to figure out who owns the issue. Still holding the experience together when the company doesn’t.
That’s the gap.
The business sees orchestration.
The customer feels the hassle.
The promise sounds good
Journey orchestration is easy to like on paper.
Better timing. Better coordination. Better follow-up. Less customer effort.
All of that sounds right.
And to be fair, some progress has been real. Companies have invested heavily in journey platforms and orchestration tools, and customers clearly expect a more connected experience than most brands actually deliver.
But better tools do not automatically create a better experience.
You cannot fix fragmentation just by layering orchestration on top of it.
A lot of what gets called journey orchestration is really just better message sequencing.
The company got better at deciding what to send next.
The customer still ends up doing the work.
That’s the part most dashboards never show.
NEW: The DCX AI Today - AI Tool Directory - An expanding directory of tools featured in DCX AI Today, sorted by category, with links and descriptions. If you lead a CX team and want a curated shortlist of tools worth evaluating, this is your starting point.
Where it actually breaks
This is usually not a strategy problem.
It is a continuity problem.
Most orchestration efforts are built around company actions instead of customer continuity.
The company asks:
What should we send next?
What offer should we trigger?
What channel should we use?
What audience is this person in?
Those questions matter.
But they miss the ones that actually determine whether the journey feels connected.
The customer is wondering:
What’s actually happening right now?
What have I already told you?
What did you say would happen next?
If this goes wrong, who owns it?
Will the next person I talk to know any of this?
That is where journeys break.
It happens in the handoff. In the exception. In the moment when the customer has to stop and think, Wait, do I really have to start over?
That is the experience they remember.
The company is split up. The customer is not.
Orchestration often sits on top of a company that still works in pieces.
Different teams. Different systems. Different goals. Different measures of success.
Marketing wants response.
Digital wants completion.
Service wants containment.
Operations wants efficiency.
The customer just wants the company to make sense.
When it doesn’t, they feel it immediately. The workflow may be connected behind the scenes. The experience still feels broken from the outside.
How to fix it, one journey at a time
Start smaller than most companies want to.
Skip the big enterprise vision for end-to-end orchestration. That is usually where the language gets polished and the reality gets fuzzy.
Start with one journey that is already causing pain.
Pick the place where customers are most likely to bounce between channels, repeat themselves, get stuck in a handoff, or hear different answers from different parts of the business. Billing issue. Service problem. Onboarding. Claims. Save flow.
The point is to start where the breakdown is real and visible.
Map the promises, not just the process
This is where a lot of teams lose the plot.
They document steps, systems, and touchpoints.
Fine.
What you really need to map are the promises.
What does the customer think you told them?
What are they expecting you to remember?
Where do they believe ownership sits?
At what point are they quietly being asked to hold the whole thing together on your behalf?
That is where the truth usually is.
A lot of broken journeys are not broken because the workflow is impossible.
They break because the company made a promise it did not realize it was making. Or it made several small promises that quietly conflict.
Decide what context must survive the handoff
Do not settle for vague language like “we need better data.”
That does not help.
Get specific about what has to carry forward every time.
The reason for contact
What already happened
The last action taken
Any constraint that matters
What the customer was told
Who owns the issue now
If that context does not move with the customer, the orchestration is failing.
It may still look impressive from the inside.
It is still failing.
Put one person on the hook for the journey
Someone has to own what happens across the seams.
Not just the campaign. Not just the channel. Not just the platform.
The journey.
Otherwise, every team will do its part, and the customer will still get a broken experience.
That is one of the quiet reasons orchestration disappoints. Plenty of people are accountable for pieces. Almost nobody is accountable for the moments in between.
And that is exactly where customers get stuck.
Build for recovery, not just progression
Real journeys do not stay clean for long.
A payment fails. An appointment moves. A case gets misrouted. A message fires at the wrong time. A customer ignores one step and shows up somewhere else. An employee steps in without enough context.
That is normal.
So the question is not only whether the system can move the customer forward.
You also need to know what happens when the journey goes sideways.
Can the next channel see the problem?
Can the employee pick up the thread?
Can the company recover without making the customer repeat the whole story?
That matters more than most trigger logic.
Watch for effort transfer
This is one of the easiest mistakes to miss.
A company automates a step and calls it progress.
But did the work actually go away?
Or did it move to the customer?
If the customer has to repeat information, chase updates, translate between departments, or figure out who owns the issue, then the company did not remove effort.
It pushed it outward.
That is not orchestration.
That is cost shifting with nicer language.
Test in the messy middle, not the happy path
Do not test orchestration only in workshops or polished demos.
Use the late payment.
The missed technician visit.
The angry callback.
The exception case.
The channel switch.
The half-complete application.
The customer who did everything right and still got stuck.
That is where you find out whether the journey holds together.
The messy middle tells the truth.
The standard is simple
Journey orchestration works when the customer no longer has to carry the experience for the company.
They shouldn’t have to keep reintroducing the problem.
They shouldn’t have to bridge the gap between channels.
They shouldn’t have to guess who owns the issue.
They shouldn’t have to repair the disconnects between your teams.
If they still do, the orchestration isn’t working.
No matter how good the dashboard looks
www.marklevy.co
Follow me on Linkedin
What Successful CX Leaders Do on Sundays
DCX Links: Six must-read picks to fuel your leadership journey delivered every Sunday morning. Dive into the latest edition now!
Thanks for being here. I’ll see you next Tuesday at 8:15 am ET.
👉 If you enjoyed this newsletter and value this work, please consider forwarding it to your friends and colleagues or sharing it on social media. New to DCX? Sign Up.
✉️ Join 1,500+ CX leaders who stay ahead of the next customer curve.
Human-centered insights. Plug-and-play frameworks. Smart tools that actually work. All designed for CX pros who want to build with purpose—and deliver with impact.
👉 Subscribe today and get the tools to elevate your strategy (and your sanity).