How to Reduce Cost per Resolution: 10 Levers, With the Maths
Cost per resolution is total support cost divided by issues genuinely solved. Here is a worked example and 10 levers ranked by effort, impact and time to value.
On this page 8 sections
To reduce cost per resolution, lower total support cost or raise the number of issues genuinely resolved. The biggest levers are removing the causes of your top contact drivers, fixing knowledge base gaps, letting AI resolve repetitive questions at a low unit price, cutting reopens and repeat contacts, and choosing a pricing model that does not bill for failures.
Key takeaways
- Cost per resolution is fully loaded support cost divided by issues genuinely resolved, not tickets closed.
- Labour is usually the largest line, so levers that remove contacts beat levers that speed agents up.
- AI resolution at $0.45 to $0.69 against a human marginal cost near $10 moves the average quickly, but only on repetitive intents.
- A vendor that bills conversations or deflections inflates your real cost per resolution.
- Reducing reopens and repeat contacts improves the metric without spending anything.
To reduce cost per resolution, you either lower your total fully loaded support cost or increase the number of issues genuinely resolved, and the best levers do both. In practice the biggest gains come from removing the root causes of your top contact drivers, fixing gaps in your knowledge base, letting AI resolve repetitive questions at a low unit price, cutting reopens and repeat contacts, and choosing vendor pricing that does not bill you for failures.
This guide gives the formula, a fully worked example, ten levers ranked by effort and impact, and an explanation of how per-resolution vendor pricing interacts with your own internal number. For the definition on its own, see our cost per resolution glossary entry.
The formula
Cost per resolution = total fully loaded support cost ÷ issues genuinely resolved
Both halves need care, and we cover the full method in building a cost per resolution model.
The numerator includes:
- Agent salaries plus benefits and employer taxes.
- The share of management and team lead time spent on support.
- Engineering time spent on support escalations.
- Helpdesk, knowledge base, chat, analytics and QA tooling.
- AI and automation spend.
- Training and quality assurance time.
The denominator is issues resolved, not tickets closed:
- Remove tickets auto-closed for inactivity.
- Merge repeat contacts about the same problem into one issue.
- Include issues resolved by AI or self-service where you can verify the resolution.
On the loading factor, US Bureau of Labor Statistics data for June 2026 shows benefits make up 30.0% of private industry employer compensation costs, with wages at 70.0%. That means benefits add roughly 43% on top of wages on average. Your figure will differ by country and company, so use your own payroll data where you can.
A fully worked example
An illustrative B2B SaaS support team. Substitute your own figures.
| Line | Calculation | Monthly cost |
|---|---|---|
| Agents | 6 x $50,000 salary x 1.43 loading ÷ 12 | $35,750 |
| Management | 30% of a $90,000 manager x 1.43 ÷ 12 | $3,218 |
| Helpdesk seats | 6 x $115 | $690 |
| Knowledge base, analytics, QA tools | Flat | $400 |
| Total cost | $40,058 |
Volume for the month:
- 5,000 tickets closed.
- 300 were auto-closed with no reply from the customer.
- 700 were repeat contacts about issues already open or recently closed.
- Issues genuinely resolved: 4,000.
Cost per resolution: $40,058 ÷ 4,000 = $10.01.
For comparison, cost per ticket is $40,058 ÷ 5,000 = $8.01. The gap between the two numbers is the cost of repeat contacts and auto-closures, which cost per ticket hides. Our support cost calculator page walks through the same method with a second example.
Note that labour is 97% of this total. That fact decides which levers matter.
The 10 levers
1. Remove the causes of your top contact drivers
The cheapest resolution is the contact that never happens. Tag a month of tickets by reason, rank reasons by volume, and take the top three to product or engineering. A confusing billing page, a missing export button or an unclear error message can each generate hundreds of tickets a month. Our anatomy of a support queue method shows how to do the ranking.
This removes cost from the numerator and, because resolved issues fall too, the ratio moves less than the total. Measure total cost as well as the ratio.
2. Fix knowledge base gaps
In a 2024 Gartner survey of 5,728 customers, only 14% of customer service issues were fully resolved in self-service, and the most common failure was customers being unable to find content relevant to their issue, cited in more than 43% of cases. Missing, outdated or contradictory articles push contacts to your most expensive channel. Audit articles on refunds, pricing, cancellation and your top ten contact reasons first. See how to audit a knowledge base before adding AI.
3. Let AI resolve repetitive intents
Password resets, invoice requests, plan questions and “how do I” questions answerable from your docs are the cheapest place to apply AI. The gap between channels is large: Gartner’s 2019 poll of service leaders put live channels at an average of $8.01 per contact against about $0.10 for self-service. That figure is old and predates modern AI agents, so treat it as directional, but the shape of the gap has not changed.
In the worked example, the human marginal cost is roughly $39,000 of labour ÷ 4,000 issues, just under $10 each. An AI resolution at $0.69, or $0.45 above 1,000 a month, is a very different unit cost, provided the answer is genuinely correct.
4. Route to the right person first time
Every transfer adds handling time and often a repeat explanation from the customer. Route by topic and customer tier, send billing to someone who can issue refunds, and send technical bugs directly to the people who can reproduce them. Measure transfers per resolved issue.
5. Build macros for the top twenty replies
Well-written macros cut handling time on common replies and improve consistency. The gain is real but smaller than removing contacts, because it speeds up work that still happens.
6. Reduce reopens and repeat contacts
In the example, 700 repeat contacts cost agent time and added nothing to the denominator. Common causes: closing before the customer confirms, answering the literal question rather than the underlying problem, and missing follow-up when an engineering fix ships. Track reopen rate by agent and topic. This lever costs almost nothing.
7. Invest in proactive and in-product help
Status pages during incidents, in-app guidance at the moments that generate tickets, and emails before a known change all prevent contacts. An incident without a status page can generate a large spike in avoidable tickets.
8. Right-size seats and tooling
Audit licences quarterly. Seats bought for last year’s peak, duplicate tools, and add-ons nobody uses all sit in the numerator. If your helpdesk bills per seat and AI per usage, check for seat plus usage double billing.
9. Choose a pricing model that does not bill for failures
The unit your AI vendor bills on changes your real cost per resolution. Per-conversation and per-interaction pricing bills whether or not the customer was helped. Per-resolution pricing bills only for successes, but only if the definition excludes abandonment, timeouts and handoffs. We compare units in per-resolution vs per-seat pricing.
10. Set spend caps and review monthly
Usage-priced tools can run away during spikes or bot traffic. A hard monthly cap keeps the numerator predictable. Review cost per resolution by topic every month, not once a year.
The levers compared
| Lever | Effort | Impact on cost per resolution | Time to value |
|---|---|---|---|
| 1. Remove top contact drivers | Medium to high, needs product time | High on total cost | 1 to 3 months |
| 2. Fix knowledge base gaps | Medium | Medium to high | 2 to 6 weeks |
| 3. AI resolution on repetitive intents | Low to medium | High, if content is good | Days to weeks |
| 4. Better routing | Low to medium | Medium | 2 to 4 weeks |
| 5. Macros | Low | Low to medium | 1 to 2 weeks |
| 6. Reduce reopens and repeats | Low | Medium | 2 to 6 weeks |
| 7. Proactive and in-product help | Medium | Medium | 1 to 3 months |
| 8. Right-size seats and tools | Low | Low to medium | Next billing cycle |
| 9. Pricing model choice | Low, at renewal | Medium to high | Next contract |
| 10. Spend caps and monthly review | Low | Protects gains | Immediate |
Effort and impact ratings are our judgement for a typical SaaS team, not measured benchmarks. Your ranking depends on where your costs sit.
How per-resolution vendor pricing interacts with your internal number
This is where many teams get confused, so it is worth separating two figures.
The vendor’s price per resolution is one input to your numerator. At Fidiora it is $0.69 per genuine resolution, dropping to $0.45 above 1,000 a month.
Your internal cost per resolution is the blended number across humans, AI and tools.
Continuing the worked example, suppose AI resolves 40% of the 4,000 issues. That rate is an assumption for illustration, so test on your own questions.
| Scenario | Total monthly cost | Issues resolved | Cost per resolution |
|---|---|---|---|
| Today, no AI | $40,058 | 4,000 | $10.01 |
| Volume grows 40%, same team, AI resolves 2,240 (1,000 at $0.69, 1,240 at $0.45) | $40,058 + $1,248 = $41,306 | 5,600 | $7.38 |
| Same volume, AI resolves 1,600, two roles not backfilled after attrition | $27,911 + $960 = $28,871 | 4,000 | $7.22 |
In the growth scenario, humans handle 3,360 issues, fewer than today, so the same team absorbs 40% more demand. In the attrition scenario, the saving comes from not replacing leavers. Neither assumes layoffs.
Three things to notice.
Human cost per ticket goes up. AI takes the easy questions, so each remaining human ticket is harder on average. That is expected, and it is why blended cost per resolution is the number to track.
The vendor’s definition changes your real unit cost. If a vendor charges $1.00 per conversation across 3,000 conversations and genuinely resolves 1,500, your effective AI cost is $2.00 per resolution, not $1.00. If a vendor counts deflections or abandoned chats as resolutions, the invoice rises while your denominator does not. Read the definition; ours is published in full on the resolution page.
AI does not help every topic. Complex integration issues, account-specific disputes and anything that needs judgement still belong with people. AI resolution is a lever for the repetitive share of your queue, which is why lever 1 and lever 2 matter as much as lever 3.
When Fidiora is not the right lever
If your queue is dominated by complex, account-specific technical work with little repetition, AI resolution will move your cost per resolution only slightly and your time is better spent on routing, engineering escalation paths and root-cause fixes. If your knowledge base is thin or contradictory, fix that first, because any AI will answer from what it is given.
If a large share of your volume is repetitive and answerable from your docs, Fidiora resolves those questions, hands the rest to your team in your existing helpdesk at no charge, and bills only for genuine resolutions, with a hard spend cap and no seat fees.
Where to start this week
- Calculate cost per resolution for last month using the formula above.
- Tag a sample of 200 tickets by reason and rank them.
- Split the top reasons into “fix the cause”, “fix the article” and “repetitive, answerable from docs”.
- Price the third group at your AI vendor’s genuine resolution rate and compare against your human marginal cost.
That analysis takes an afternoon, and it tells you which of the ten levers to pull first.