Skip to content
SupportLayer

Support costs

The real cost of a ticket: What does one support contact actually cost?

Most teams can say what a ticket costs. Fewer can say what the same ticket costs when it comes back, gets escalated, or convinces a customer to stop buying. The number on the dashboard is usually the smallest part of the bill.

By the team · · 3 min read

Cost per contact usually counts the agent's time. The rest of the bill arrives somewhere else: in repeat contacts, escalations, and customers who quietly leave.

What the usual number counts

Cost per contact is normally built from agent time, tooling, and overhead, divided by volume. It is a useful number for planning a budget. It is a poor number for understanding what a problem actually costs the business, because it stops counting the moment the ticket closes.

The costs that land somewhere else

A contact that should have been unnecessary has already cost the customer time before anyone in support hears about it. A contact that comes back costs the queue twice. A contact that ends in an escalation pulls in senior people whose time never appears in the per-ticket figure. And a customer who gives up after a bad experience costs revenue that no support report will ever show.

None of these are exotic cases. They are the normal way a cheap-looking ticket becomes an expensive problem.

Averages hide the expensive contacts

A single average treats a password reset and a billing dispute as the same event. In most queues, a small share of contact types accounts for a large share of repeats, escalations, and churn risk. The average looks calm while a few journeys burn money in the background. Finding those journeys matters more than shaving seconds off the ones that already work.

What to read alongside the cost number

Repeat contact rate, escalation rate, and what customers do after the interaction: refunds, cancellations, quiet churn. Read together, these turn cost per contact from an accounting figure into a picture of where the money actually goes. Read alone, it mostly tells you how busy the team was.

Where to start looking

Pick one journey that generates contacts and follow it from the customer's side: what they tried first, where the instructions sent them, and what happened after the ticket closed. The expensive patterns usually show up quickly once someone looks at a single journey end to end.

Our free customer friction assessment does exactly that for one journey you choose. We review the screens and materials customers actually use and send you a short summary of what we noticed and what we think may be going on. It is a starting point, not a full audit.

These questions are only the beginning. The answers depend on your team, your systems, and your customers, and they are exactly what we help you work through.

Request a free customer friction assessment

Request a conversation

If this describes your situation, start there.

Tell us what is happening on your side of it and we will tell you whether an assessment is the right first step.