Author: gert.schonewille@gmail.com
-
When Being Technically Right Damages Trust
In customer support, being correct is often treated as the primary goal. Accurate information, clear explanations, and policy-aligned answers are all essential parts of the work. And yet, many support interactions break down even when the information provided is correct. The issue is not accuracy. It’s how correctness interacts with expectation, timing, and consequence. From…
-
Why Efficiency Often Hides Risk
Efficiency is a powerful organizing principle in customer support. Faster responses, shorter handle times, and higher throughput are easy to measure and easy to justify. They promise scalability, cost control, and predictability. In many ways, efficiency works. It removes waste, clarifies flow, and helps teams manage increasing demand. Without some focus on efficiency, support systems…
-
Why Support Work Is Hard to See From the Outside
From the outside, customer support often appears straightforward. Questions arrive. Answers are given. Problems are resolved. When everything works, the work itself remains largely invisible. When something goes wrong, the failure becomes visible immediately. This creates a distorted picture. Much of support work happens in the space between what is said and what is avoided.…
-
When Consistency Conflicts With Understanding
Consistency is often treated as a hallmark of good support. Customers expect predictable outcomes. Organizations rely on uniform processes to ensure fairness and reduce risk. From that perspective, consistency feels not just helpful, but necessary. And yet, many support interactions fail not because of inconsistency, but because consistency overrides understanding. This tension appears when the…
-
Why Fixing the Immediate Issue Often Makes Things Worse
When a support issue surfaces, the pressure to act quickly is strong. A customer is frustrated. A ticket is escalated. A failure is visible. The most natural response is to fix what’s directly in front of you. Often, that works. The immediate problem goes away. The customer moves on. The situation de-escalates. And yet, many…
-
How Process Decisions Create Support Debt
Processes in customer support are usually created to solve immediate problems. A queue is introduced to manage volume.A form is added to collect missing information.An approval step appears to prevent mistakes. Each decision makes sense in isolation. Over time, however, these decisions accumulate. The result is not just complexity, but debt. Support debt forms when…
-
Why Support Quality Degrades Gradually
Support quality rarely fails in obvious ways. There is usually no single moment where everything breaks, no clear decision that suddenly lowers standards, no announcement that the experience will now be worse. Instead, quality erodes slowly. Small compromises accumulate. Temporary measures become permanent. Edge cases multiply. Over time, the work feels heavier, even though no…
-
Why Adding More Tools Doesn’t Reduce Complexity
When support work starts to feel heavy, adding a new tool often looks like the most reasonable response. A tool promises visibility.It promises automation.It promises relief from manual effort and cognitive load. In isolation, these promises are often true. Over time, however, many teams discover that complexity continues to grow — even as tooling expands.…
-
What Scaling Support Actually Changes
Scaling support is often framed as a question of volume. More customers means more tickets. More tickets require more agents, more tooling, and more structure. On the surface, growth looks like a problem of capacity. In practice, scaling support changes much more than workload. As support grows, relationships become thinner. Early on, customers may interact…
-
What Escalations Say About Internal Systems
Escalations are often treated as isolated events. A difficult customer, a mishandled response, or a breakdown in communication. Seen this way, escalation appears as an exception — something to prevent, minimize, or resolve as quickly as possible. Looked at more closely, escalations are rarely isolated. They tend to cluster around the same issues, the same…