Customer Support: Conflicting Instructions and Corrective Loops

A customer contacts support because they have an objective they cannot complete alone. The department's philosophy determines whether the system treats that person as someone to help, a ticket to close, a risk to contain, or a burden on the queue.

The Same Department Can Have Different Purposes

One support organization may believe, “Our purpose is to solve people's problems.” Another may behave as though its purpose is to answer calls, reduce handle time, prevent refunds, protect the company, or move work out of the visible queue.

Those purposes produce recognizable tells: direct answers or intentional ambiguity, listening or interruption, ownership or reflexive transfer, explanation or scripted deflection, and curiosity or contempt.

From “Help the Person” to “Manage the Queue”

UXR calls the gradual movement away from the department's human purpose institutional drift.

Employees may not personally intend harm. They may be adapting rationally to what the institution measures and rewards. If ownership increases handle time, transfer becomes safer. If a direct answer creates liability, ambiguity becomes safer. If a refund hurts a metric, exhaustion becomes useful to the system even when nobody says so openly.

Customer as External Coordinator

In a transfer loop, the institution's departments fail to coordinate internally. The customer must remember the history, repeat the evidence, compare contradictory explanations, identify the responsible office, and carry information between teams.

This is burden transfer. The company saves internal coordination while the customer performs it without authority, training, compensation, or reliable access to the record.

Intent Must Still Be Proven

A loop can produce abandonment and benefit the institution without proof that it was deliberately designed for that purpose. UXR distinguishes accidental friction, neglected friction, exploited friction, and strategic friction.

What Better Support Measures

A humane support system should measure more than call speed. It should examine whether the person reached the legitimate objective, understood the result, retained records, avoided unnecessary repetition, could reach someone with authority, and had a usable remedy when the first path failed.

Institutions become what they measure. A department that measures only the queue may learn to manage people out of the queue rather than help them out of the problem.

When Costs Don't Disappear · How UXR Creates Accountability · UXR Taxonomy