What Does Your Support Actually Cost?
Most teams divide salaries by tickets and call it a day. That misses 40-60% of real spend. Slide the numbers below and watch the gap widen.
You think it costs
$10.83
per conversation (salary only)
It actually costs
$16.72
per conversation (fully loaded)
Team basics
Hidden costs
The stuff most teams forget to count.
Monthly cost breakdown
The gap you're not seeing
Naive cost
Salary / conversations
$10.83
True cost
Everything included
$16.72
You're underestimating by $5.89 per conversation
What that gap means annually
Why most teams get this number wrong
The standard formula is simple: total support cost divided by total conversations. Clean, easy to report, and consistently wrong.
It's wrong because "total support cost" usually means salaries. Maybe software licenses if the finance team is thorough. But it almost never includes the 15-35% benefits load, the management hours spent on scheduling and QA reviews, the training time for new hires, or the quiet drain of replacing agents who leave every year.
Agent attrition alone is the silent budget killer. Support teams average 25-40% annual turnover. Each departure costs 3+ months of salary in recruiting, onboarding, and ramping. For a 10-person team losing 3 agents a year, that's an invisible $40,000+ line item that never shows up in the "cost per conversation" calculation.
This isn't about making your numbers look bad. It's about making decisions with real data. Whether you're evaluating AI automation, building a business case for better tooling, or just trying to understand your unit economics, you need the actual number.
Frequently asked questions
Support that keeps your costs boring.
Try SupportWire Free