Customer Support Is a Product Function, Not a Cost Centre

Support is typically measured on cost per ticket and time to resolution. Both metrics push in the same direction: handle contacts as cheaply and quickly as possible. This framing misses what support is actually generating.

Support is the highest-resolution product feedback available

Every ticket describes a point where the product failed to be self-explanatory. Aggregated, these constitute the most detailed usability data a company possesses — more specific than surveys and more honest than user interviews. Companies that route support themes into product planning fix causes; those that do not keep answering the same question indefinitely.

Deflection metrics measure the wrong thing

Reducing contact volume through obstruction — buried contact options, mandatory chatbots, forced self-service — lowers ticket counts without resolving anything. The problem persists, the customer is now also frustrated, and the company has destroyed its own feedback channel. Volume should fall because the product improved, not because contacting became difficult.

Resolution rate matters more than response time

Customers tolerate waiting considerably better than they tolerate being passed between agents and repeating themselves. First-contact resolution predicts satisfaction far more strongly than speed, and it requires agents with the authority and information to actually resolve things.

Recovery creates loyalty that flawless service does not

A well-handled failure produces stronger customer relationships than an experience with no problems at all. This is consistently demonstrated and consistently under-used, because it requires empowering front-line staff to make decisions involving money.

Scripts limit the ceiling

Rigid scripting prevents disasters and prevents excellence simultaneously. Agents who understand the reasoning behind policies handle situations the script never anticipated. Those who only know the script are helpless the moment a case is unusual.

Founders should read tickets

Not summaries — actual tickets, weekly. It is the fastest route to understanding what customers experience, and almost no dashboard conveys it.