Resolution matters more than speed
A fast response that does not solve the problem produces a second contact and a worse impression than a slower answer that ends it.
Omni Core · Object
Customer Support
What happens when something goes wrong or someone needs help: how they reach you, whether it gets resolved, what they could have solved themselves, and where it goes when it cannot be.
The term
What it is
Support is where the promise is tested. A customer contacting support has already had something not work, and what happens next determines whether the failure is remembered as a failure or as competence.
The measures that dominate support management — response time, ticket volume, handling time — describe the function’s efficiency rather than whether the customer’s problem went away. Resolution is the measure that matters and is harder to define.
The largest available improvement in most support operations is upstream: the contacts that should never have been necessary, caused by something confusing, broken or unexplained elsewhere.
Why it earns a place
What goes wrong without it
Most contacts are avoidable
Support volume is a measure of how well everything else works. Reducing it by fixing causes is cheaper than handling it efficiently.
Self-service works only when it is genuinely faster
Customers use the route that gets them an answer soonest. Self-service that is slower than asking a person is not used, whatever it costs to build.
One level in
The modules within customer support
Four working areas: how customers reach help, whether the problem is actually solved, what they could solve alone, and what happens when nobody can solve it.
Getting help
How customers reach support, how easily, and whether the route matches the urgency of what they need. The part that determines who contacts you and who simply leaves.
LearnResolution
Whether the problem actually went away, measured properly rather than through response times and closure rates that can be met without solving anything.
LearnSelf-service and knowledge
What customers can resolve without contact, and whether the material is good enough that they would choose to. Cheap when it works and expensive when it does not.
LearnEscalation
What happens when the first line cannot resolve it — where most of the memorable failures occur, because the customer repeats themselves and waits.
Learn
Across the framework
What it touches
- Customer FeedbackSupport contacts are feedback with a problem attached and are the largest untapped source of it.
- Business CoreMost support volume originates in a process or product problem that belongs to another function.
- Brand CoreSupport is where the promise is tested, and a recovery handled well is remembered better than nothing going wrong.
- Data CoreContact reasons are among the most useful data an organisation holds and among the least analysed.
Beyond the framework
Models worth knowing here
The Omnigoal says where this belongs and what it touches. It does not tell you how to think about it — other people have done that, and done it well. These are theirs.
SERVQUAL and the gaps model
Parasuraman, Zeithaml & Berry · 1985Also known as Service quality gaps model
Poor service is the gap between what customers expected and what they perceived, and that gap has four causes behind it.
Not knowing what customers expect; specifying a standard that does not match it; not delivering to the standard; and promising something different in communication. Locating which of the four is open changes what you do — three of them are internal problems and one of them is a marketing problem, and they are routinely confused.
- Reach for it when
- When service scores are poor and the response is more training for the people at the counter.
- Where it stops
- The associated questionnaire and its five dimensions have been criticised for decades, particularly the expectations half. The gap structure has aged better than the instrument.
A. Parasuraman, Valarie A. Zeithaml & Leonard L. Berry, “A Conceptual Model of Service Quality”, Journal of Marketing, 1985.
Service recovery
Studied by McCollough, Bharadwaj and others · 1992A failure handled well can leave a customer more committed than if nothing had gone wrong — but only sometimes.
The paradox is real and conditional: it holds for first failures, when recovery is fast and generous, and it does not survive repetition. What is robust in the literature underneath it is less dramatic and more useful — speed matters more than compensation, and being told what happened matters more than either.
- Reach for it when
- When designing what happens after something goes wrong, and when deciding how much authority the first person to hear about it should have.
- Where it stops
- It is not a licence to fail deliberately. The effect is unreliable, the second failure removes it entirely, and prevention is cheaper than any recovery.
Michael A. McCollough & Sundar G. Bharadwaj, “The Recovery Paradox”, AMA Educators’ Conference, 1992; extensive literature since.
These are other people’s models, named here so you can go to the source and use them properly. The Omnigoal is not affiliated with their authors and is not endorsed by them; nothing of theirs is reproduced here — no canvas, no diagram, no wording. Each is described in our own words, with the originator credited, because the framework is a place to put thinking, not a replacement for the people who did it. Model names and trademarks belong to their respective owners and are used here only to refer to the work itself.
Every model in the framework, and where each one belongsSupport volume measures how well everything else works. Fixing causes is cheaper than handling contacts efficiently.
The other objects in the Omni Core
Customer Journey Mapping
Visualises the entire customer journey from initial awareness to post-purchase, providing a comprehensive understanding of the customer’s interactions and experiences. This process identifies key stages, critical moments, and pain points that influence customer satisfaction and loyalty. By mapping out these journeys, businesses can design targeted interventions to enhance each phase of the customer lifecycle, ensuring a cohesive and satisfying experience.
LearnCustomer Feedback
Collects and analyses customer feedback to gain valuable insights into their experiences and areas for improvement, driving continuous enhancements in service and product offerings.
LearnUI and UX Optimization
Ensures that digital interactions are intuitive, engaging, and user-friendly, contributing to a seamless and enjoyable customer experience across all digital platforms.
LearnPersonalization
Tailors interactions and experiences based on individual customer preferences and behaviour, enhancing engagement and satisfaction through customised content and recommendations.
LearnLoyalty Programs
Develops and manages programmes that reward and incentivise repeat customers, fostering long-term loyalty and positive experiences through attractive rewards and benefits.
LearnOmnichannel Integration
Ensures a consistent and seamless experience across all channels, integrating personalised interactions and synchronised customer data to provide a unified and cohesive customer journey.
Learn