I sent a specific question to an organisation capable of answering it.
The question was simple, contained, answerable by anyone with access to the relevant information. It required no investigation, no consultation, no escalation to a specialist. It was the kind of question that exists precisely because organisations of this kind hold the information required to answer it, and people outside those organisations do not.
The reply arrived promptly. It did not answer the question.
It thanked me for my enquiry. It confirmed that my query had been received. It informed me that for questions of this nature, I would need to speak with an advisor, and for me to provide a phone number and a set of available hours during which that conversation could take place. The email was signed by a Consumer Services Officer.
The question remained unanswered.
The system did not fail to respond. It failed to resolve. These are different failures, and the difference between them is worth being precise about, because the first is easily mistaken for the second.
A response is a reply. It acknowledges that something was received and that the receiving organisation is aware of it. In this sense the system worked correctly—the email arrived, it was processed, a reply was generated and returned within a timeframe that would appear, in any service metric, as satisfactory. The response was prompt and appropriately toned: courteous and clear about what the next step should be.
The next step was mine.
This is the turn the response made without announcing it. The question arrived as my responsibility—I had a question, I needed an answer. The reply returned it as my responsibility, differently shaped—I had a question, I now needed to make a phone call. The responsibility had not been discharged. It had been redirected, back toward me, via a process I had not asked for and which required more of my time and effort than the original enquiry had.
The distance between my question and its answer had increased.
The phone call, as a mechanism for answering precise written questions, is a particular kind of inefficiency that deserves examination on its own terms.
A written question is specific. It is fixed at the moment of writing. It cannot be misheard, cannot be misremembered in the moment, does not require the person receiving it to be available at the same time as the person asking it. It can be answered with the same precision at which it was posed. The answer, when it arrives in writing, is a record—available for future reference, not subject to the distortions of memory or the ambiguities of a conversation conducted in real time.
A phone call is none of these things. It requires both parties to be available simultaneously, and the question to be restated verbally with the possibility of paraphrase and imprecision. It requires the answer to be retained in memory. As a mechanism for conveying specific information, it is inferior to writing.
The question arrived in writing because writing is the appropriate medium for specific enquiries. The instruction to call was not a recommendation about which channel would best serve the enquiry. It was a direction about which channel would best serve the organisation—moving the interaction from a medium that requires a specific, recorded, accountable answer to a medium that is fluid, unrecorded in any form available to me, and manageable by an advisor trained to contain enquiries rather than resolve them.
The shift was made smoothly, in the register of helpfulness. For questions of this nature, please call. The phrase implies that calling is the appropriate method—that the question’s nature is what determines the channel. It does not acknowledge that the channel change also changes what the organisation is required to provide. In writing, the question asks for a specific answer. On the phone, the question becomes a conversation. Conversations can be guided. Answers to specific questions cannot.
The title Consumer Services Officer is worth a moment’s attention.
It contains a claim. The word service, in its original meaning, describes the reduction of distance between a need and its satisfaction. To service something is to attend to it in a way that restores or maintains its function. A service organisation, by this logic, is one that takes a need and moves it toward resolution. The Consumer Services Officer is the person through whom this movement occurs.
In practice, the function described by the title is different from the function suggested by it. The Consumer Services Officer receives enquiries. Acknowledges them. Redirects them. Manages the workflow through which they pass. What the Consumer Services Officer does not typically do is answer specific questions with specific answers—because specific answers require specific information, and the provision of that information directly, in writing, at the level of precision the enquirer requires, is not what the system is designed to do.
The system is designed to receive, acknowledge, redirect, and contain. These are real functions. But they are not service in any sense that includes resolution.
The title suggests an outcome. The role delivers a process.
There is a distinction operating here between enquiry management and resolution, and the distinction has become so embedded in how organisations function that it is no longer visible as a choice. It presents as natural. Complex questions require a phone call, an advisor is needed and these things take time. The process is mistaken for the answer, and the mistake is so common that neither party in the exchange is likely to notice it.
I noticed it because the question was not complex. It was specific, contained, and answerable by any person with access to the relevant information. The organisation holds that information. The Consumer Services Officer has access to it, or to the person who does. The information exists, is known, could be conveyed in two sentences. The decision not to convey it in two sentences—to redirect me instead to a phone call with an advisor during specific available hours—was not a decision about my question’s complexity. It was a decision about the organisation’s preferred mode of interaction.
The preferred mode is one in which the answer is always one step further away than the current interaction. The email refers to the phone call. The phone call refers to the advisor. The advisor may refer to a specialist, or a callback, or a written confirmation that will arrive in due course. At each stage, a response is provided. At each stage, the resolution is deferred. The question moves through the system without arriving anywhere. The system remains, throughout, in motion.
Resolution, when it occurs, is the end of a process. It closes the loop. It returns the person with the question to a state in which the question no longer exists, because it has been answered. Resolution is, from the organisation’s perspective, a conclusion—the interaction is over, the resource it consumed can be reallocated.
Process management is not resolution. It is the continuation of the interaction in a form that appears to be moving toward resolution without arriving there. The interaction remains open. The resource continues to be consumed. The person with the question continues to participate in the system—making phone calls, waiting for callbacks, speaking with advisors—without the question having been answered.
This is the accumulated result of systems designed around the management of volume rather than the resolution of individual enquiries. A system that must process thousands of questions cannot treat each question as a specific problem requiring a specific answer. It must categorise, redirect, triage. The category determines the channel. The channel determines the process. The process produces a response. The response closes the immediate interaction and opens the next one.
The question itself—the specific, particular thing the specific, particular person wanted to know—is not the unit the system processes. The enquiry is. Enquiries can be managed. Questions require answers.
This sits alongside other patterns I have observed in how the relationship between individuals and organisations is currently managed.
A transaction is completed and then extended, unbidden, through a request that was not part of the original agreement. Consent is assumed rather than requested, because the person assuming it has substituted their own preferences for another person’s. Intent is offered as a substitute for consequence, and accepted as sufficient. A customer is treated as an interruption to the smooth running of a business that exists to serve them.
In each case, something is offered that resembles what was agreed to and is not what was agreed to. A review request resembles gratitude. Assumed consent resembles consideration. Stated intent resembles accountability. A response resembles an answer.
The resemblance is functional. It produces the appearance of the thing without the thing itself. The review request looks like a natural extension of the transaction. The response to my question looked like service. The Consumer Services Officer title looks like a function oriented toward resolution.
The appearance is consistent. The substance is elsewhere.
I sent a specific question. A reply arrived. The reply was courteous, prompt, and completely unrelated to the information I had asked for.
I have not arranged a time for the phone call. The question is still unanswered.
This is not a complaint about rudeness or negligence. No one was rude. No one was negligent. The system operated exactly as it was designed to operate. The design simply does not include the resolution of specific questions as a primary function. It includes the management of enquiries—their receipt, their acknowledgment, their routing through appropriate channels, their containment within processes that keep them moving without requiring them to arrive.
The question was specific. The system is general. The gap between them is the gap between what service promises and what it delivers.
The system responded. It did not answer.
