Inspired by themes in the book Can I Speak to a Real Person?
Imagine yourself as the customer for a moment. Something has gone wrong. Not a catastrophe that derails your life, simply something irritating enough to take emotional budget you did not plan to spend. A delivery misses its promised date. A charge appears that you do not recognise. A commitment made earlier in the week dissolves quietly by the time you need it most. You reach out because that is what the system invites you to do. You explain your problem clearly. You wait with patience. You try to believe that the person helping you understands not only the technical issue, but the inconvenience wrapped inside it.
Yet at some point, something shifts in your body. It is not anger, not entitlement, but a quiet fear that your issue may disappear into a queue, lost in the rush of standard responses and automated acknowledgements. You begin to imagine your concern dissolving beneath the sentence “We are experiencing high volumes.” You worry that your experience might be treated as ordinary, when it feels anything but. That is when you ask for a manager. You do not do it because you want conflict. You do it because you want certainty. You want to be seen.
It is uncomfortable but true that customers learned this behaviour from the structure itself. Companies taught them, slowly and indirectly, that escalation is the only surefire path to visibility.
Escalation as a Learned Survival Strategy
Customers have not invented escalation out of nowhere. They have watched what happens when they remain quiet and cooperative. They have seen polite explanations go nowhere, while forceful ones spark action. They have witnessed time and again that managers appear when emotions rise, not when accuracy demands it. They have observed exceptions made only when volume increases, tone shifts, or a threat of cancellation enters the room. In this way escalation is not rebellion. It is adaptation. When a system rewards escalation with resolution, customers escalate to survive the experience.
It would be easy to dismiss this as entitlement, but customers are responding rationally to the patterns the organisation has created. If quiet customers wait indefinitely while loud ones receive attention, the behaviour becomes predictable. Escalation becomes the strategy that protects them from being lost in the noise.
When Leadership Accidentally Reinforces the Pattern
Leadership teams often intervene with the best of intentions. They step in to stabilise tension, to prevent a negative review, to stop a conversation from spiralling publicly, or to soothe a customer who has reached the end of their patience. The outcome, however, is that leadership unintentionally demonstrates exactly what customers suspected: the frontline is friendly but not equipped with real authority. The frontline watches as their decisions are reversed to restore calm. Customers watch as policy suddenly bends in response to frustration. Both sides receive the same message. Escalation works.
Once a pattern forms, it is difficult to unlearn. Escalation becomes part of the customer’s internal script: explain the issue, sense hesitation, ask for a manager. The moment the frontline says they need to check with someone else, the customer imagines their problem slipping into the backlog and uses escalation as a safeguard.
The Habit That Became a System
Over time this shifted escalation from an exception to an expected stage in the interaction. Customers escalate because they believe it is the only reliable route to certainty. Frontline staff escalate because they lack authority, access, or structural permission to act independently. Leaders intervene because the system has created patterns that collapse under pressure. What began as a behavioural instinct has quietly hardened into a system design.
This is not a story about poor behaviour. It is a story about cause and effect. Customers escalate because the design has conditioned them to. The frontline transfers because they have no other route to resolution. Leadership cleans up the outcome because the underlying processes were never built to sustain real ownership.
The Cost of Scattered Ownership
A large part of the escalation dynamic emerges from the fact that ownership is scattered across organisational layers. Insight sits in one place. Authority sits in another. Exceptions rest in a different corner entirely. Technical fixes belong to people the customer will never meet. Policy interpretation is centralised somewhere else again. By the time the customer reaches the frontline, they are speaking to the only human available yet the only human without the power to change the outcome. The customer feels the passing of responsibility even if they cannot articulate it. They sense the distance between the person hearing their problem and the person capable of resolving it.
Escalation, in this context, is not impatience. It is logic. When customers feel they are speaking to someone who cannot act, they reach for someone who can.
A Different Kind of Power
The solution to escalation culture is not sterner scripts or firmer boundaries. It is not demanding that customers moderate their emotions. Nor is it expecting frontline professionals to absorb repeated waves of frustration without structural support. The real solution is redesign. It requires equipping the frontline with genuine authority, meaningful problem-solving skills, and direct access to the tools that allow them to resolve issues rather than transfer them.
This is where the philosophy behind The Six Sigma Problem Solver becomes a practical intervention. Six Sigma, translated into the human language of frontline work, is not about statistical mastery. It is about clarity. It is about interpreting complexity. It is about seeing defects as information rather than personal failure. It is about giving people a way to diagnose, not react. A frontline agent who understands the system and is trusted to act within it becomes a stabilising force. Customers recognise that confidence immediately. Escalation becomes unnecessary because capability is visible.
Redesigning the System: What If Defects Did Not Wait for the Customer to Find Them?
Imagine a different world entirely. Instead of waiting for customers to point out what has gone wrong, the system itself notices. A delayed shipment triggers proactive correction. A payment anomaly triggers investigation. A mismatched label triggers immediate rerouting. A policy conflict triggers review before the customer ever encounters the contradiction. The customer receives a calm message explaining what was detected, what was corrected, and what to expect. The frontline receives the same information, with context, history, and suggested next steps. No scrambling. No guesswork. No emotional firefighting.
This is not fantasy. Companies are already experimenting with versions of this approach. Predictive issue resolution, anomaly detection, agent-assist tools, and AI-driven workflow triggers are quietly emerging in the background. The aim is not to replace humans but to reduce the number of problems that require human intervention in the first place. When done well, automation becomes the housekeeping staff of a complex system. It tidies the mess before the guests notice anything amiss.
How Automation and Empowerment Work Together
Automation and empowerment are not rivals. They are partners. Automation clears the noise so that empowered humans can perform the work machines cannot. At present frontline professionals spend much of their time resolving issues that should never have been allowed to reach them. They spend emotional and cognitive energy compensating for system weaknesses, repeating explanations, and absorbing customer frustration that originates from design flaws rather than service failures. No amount of training or emotional resilience can compensate for a system that repeatedly places humans in unwinnable positions.
When automation takes on the early detection of defects, the repetitive gathering of context, and the first layer of pattern recognition, the frontline is freed to do the work humans excel at. They can judge nuance, interpret ambiguous cases, communicate with empathy, and engage in redesign conversations with clarity rather than exhaustion. Automation reduces the volume of problems. Empowerment increases the quality of solutions. One prepares the ground. The other cultivates it. Neither can stand alone.
In this shared model GenAI becomes an early-warning system rather than a replacement. It identifies anomalies, flags contradictions, and offers suggestions based on historical patterns. The agent remains the decision-maker, the interpreter, the human presence shaping the outcome. Automation provides foresight. Humans provide wisdom. And that combination creates a service environment where escalation loses its fuel source because problems are either prevented or resolved with confidence at the point of contact.
The Aha Question
For all the effort organisations invest in understanding customer behaviour, here is one question that remains surprisingly unexplored: how many calls involve a request for a manager, and why? What patterns would emerge if we studied those moments with curiosity rather than blame? Would we discover that escalation has little to do with the temperament of the customer and everything to do with the architecture of the system? Would the data reveal gaps in authority, clarity, or communication? Would it show emotional triggers or structural inconsistencies we have never named?
After this PEAK season, I think I may do that deep dive myself. I suspect the findings will not only be informative but will reveal a story far more intricate and far more human than we have acknowledged.