AI cuts customer support costs in proportion to the share of tickets it finishes without a human. Gartner projects that agentic AI will autonomously resolve 80% of common customer service issues by 2029 and cut operational costs by 30%, while a field study of 5,179 support agents published by the NBER found that an AI assist tool lifted issues resolved per hour by 14%. That spread, 14% to 30%, is the difference between helping a person work faster and removing the person from the ticket. Below are seven levers that move the bill, the evidence for each, and where the savings never show up.
Key takeaways
Full resolution beats assist by roughly two to one: Gartner's 30% cost projection assumes 80% of common issues resolved autonomously; the NBER agent-assist study measured 14%, rising to 34% for novice agents.
Price your human baseline from payroll. The US median customer service wage was $21.53 an hour in May 2025 (BLS), so a 10-minute contact costs about $3.60 in base wage before benefits, software, supervision and QA.
Decision rule: automate a ticket type only when you can name the systems it touches, the policy it applies, and the trigger that hands it to a person. If you cannot write those three things down, the saving does not exist yet.
Pay per outcome, not per seat or per conversation, and get escalation billing in writing. Under per-conversation pricing you pay for the vendor's failures.
Plan for the human queue to get harder before it gets smaller. Gartner found only 20% of service leaders had actually reduced agent staffing because of AI as of October 2025.
How much does AI actually cut customer support costs?
The published range runs from a 14% productivity gain when AI assists a human to a projected 30% cut in operating costs when AI resolves the ticket itself, and the variable that decides where you land is how much of each ticket the AI completes.
The most rigorous measurement is the NBER working paper Generative AI at Work, which tracked the rollout of a conversational assist tool across 5,179 support agents. Issues resolved per hour rose 14% on average, 34% for novice agents, and barely moved for experienced ones. That is an assist result: headcount stays, handle time falls, and the gain concentrates in new hires.
The autonomous-resolution figure is a forecast. In March 2025 Gartner predicted that by 2029 agentic AI will autonomously resolve 80% of common customer service issues, leading to a 30% reduction in operational costs. Treat it as a ceiling, not a budget line.
The best-known company-reported result sits between the two. In its February 2024 press release, Klarna said its AI assistant handled 2.3 million conversations in its first month, two-thirds of its customer service chats, did the equivalent work of 700 full-time agents, cut repeat inquiries by 25%, and was estimated to drive a $40 million profit improvement in 2024. Those are first-month, self-reported numbers. The repeat-inquiry drop is the one to copy into your model, because a repeat contact is a second ticket at full price.
The pattern is the same in all three: savings scale with completed work, not conversations touched. That makes resolution versus deflection a finance question.
Where does the money go in a support budget?
Labor: handle time multiplied by loaded wage, plus the cost of replacing the people who leave.
The US Bureau of Labor Statistics counted 2,666,000 customer service representative jobs in 2025 at a median wage of $21.53 an hour, or $44,770 a year. It also projects about 289,500 openings a year through 2035, all replacement hires for people who leave or retire. Each opening carries recruiting, training and ramp cost, so turnover belongs in your baseline alongside wages.
From the wage you can build a cost per contact. At the median, a 10-minute chat costs about $3.60 in base wage and a 20-minute phone call about $7.20, before benefits, software seats, supervision and QA. Ask finance for your loaded hourly rate and use that instead. Then split your queue by handle time, not ticket count. A minority of ticket types, the ones that touch several systems, need a policy decision or pass through two tiers, usually consume most agent hours. That is where an AI program pays or does not. Our guide to customer service cost per ticket walks through the split.
Seven levers that reduce support costs with AI, ranked by impact
Ranked by how much human cost each one removes, from most to least.
1. Resolve the ticket end to end
The AI verifies the customer, reads the account, applies the policy, takes the action and confirms the outcome. This removes the whole handle time rather than a slice, which is why it dominates every other lever. It also has the highest bar: backend integrations, a written policy per action, and deterministic steps for anything a regulator will audit. Answering without taking the action leaves the expensive part of the ticket on your queue.
2. Take voice calls off the human queue
Phone is usually the costliest channel per contact because one agent handles one call at a time, while chat agents run several conversations at once. A voice agent that answers in under a second and completes the same account actions as chat moves the longest handle times off payroll first. If it cannot take actions, it is an IVR with better manners and the saving is small. Check what a voice agent can do before you count it.
3. Prevent the repeat contact
Klarna's reported 25% drop in repeat inquiries is the most transferable number in its release. Every repeat contact is a full-price ticket caused by an incomplete first answer. Measure reopen and second-contact rates on AI-handled tickets from week one. An AI that closes fast but leaves customers coming back moves cost rather than removing it.
4. Replace QA sampling with full coverage
Manual QA reviews a small sample because reviewer time is scarce, so most conversations are never checked. Automated QA scores every conversation, human and AI, for cents per ticket, turning QA from a headcount decision into a line item, and it catches the drift that creates repeat contacts. Our quality assurance page lists what full coverage should report.
5. Assist the humans who remain
The NBER result is the evidence: 14% on average, 34% for novices, and the study also found the assist tool improved employee retention. Assist does not shrink the team, but it shortens ramp time and lowers the replacement cost the BLS turnover figure implies. Treat it as a complement to lever one, not a substitute.
6. Absorb peaks without temporary hiring
Seasonal spikes force a choice between idle capacity in quiet months and missed targets in busy ones. AI capacity scales both ways, so a tax deadline or billing run stops triggering a hiring cycle. The saving is the temp staff and overtime you no longer buy. We cover the mechanics in scaling support without hiring.
7. Pay per outcome
Per-seat pricing charges for capacity whether or not work gets done. Per-conversation pricing charges for every interaction, including the ones the AI abandoned. Per-resolution pricing charges when the problem is solved, and it only works if you define the resolution and escalations are not billed. Get both terms in the contract. Published per-resolution pricing is what makes the payback arithmetic below possible.
Which tickets should you automate first?
The ones that are high volume, fully specified and low consequence when wrong, then move up the difficulty curve as your own evidence accumulates.
Sort one month of tickets into three buckets: answerable from documentation, requiring an account lookup or action, and requiring judgment or an exception. Bucket one is cheap to automate and was cheap to begin with, so it saves little. Bucket two is where the money is, and it is only safe when the action is deterministic and the hand-off trigger is written down. Bucket three stays human. Gartner's September 2025 guidance: AI excels at routine and well-defined problems but often struggles with exceptions and high-risk scenarios.
Apply the decision rule from the takeaways to each bucket-two ticket type. A payment date change passes. A hardship request passes only if the workflow routes it to a person the moment the customer signals distress. In financial services, anything with a regulatory clock, such as a dispute intake, needs the deadline computed by the workflow, not generated by the model.
How do you calculate payback before you sign?
Multiply the tickets the AI will finish each month by the loaded human cost you avoid, subtract what you will pay per resolution and for QA, and divide your implementation cost by that monthly figure.
Four corrections keep the model honest. Count only tickets confirmed resolved, using reopen and second-contact rates, not tickets the AI touched. Subtract double handling: an escalated ticket costs the AI interaction plus the full human handle time. Include the internal time spent writing policies and reviewing QA flags, real cost even when setup is free. And treat every vendor benchmark as a ceiling until you have run the candidate on your own historical tickets. Simulations that replay real scenarios against configured workflows give you a resolved share on your ticket mix before any customer is exposed, which is the number the payback formula actually needs.
Where do the savings not show up?
On the human queue in the first months, in customer trust when the exit to a person is hidden, and in every ticket the AI touches but does not finish.
Start with headcount. In a Gartner survey of 321 service leaders in October 2025, only 20% had reduced agent staffing because of AI, and Gartner expects half of the companies that attributed cuts to AI to rehire for similar functions by 2027. An earlier Gartner poll found 95% of service leaders plan to retain human agents and predicted that 50% of organizations expecting to significantly reduce their service workforce will abandon those plans. The realistic first-year outcome is flat headcount absorbing more volume, with savings arriving as avoided hires.
Next, customer trust. A Gartner survey of 5,728 consumers found 64% would prefer companies did not use AI in customer service and 53% would consider switching to a competitor over it, with difficulty reaching a person as the top concern. An AI that blocks the path to a human saves a ticket and risks the account. Make the hand-off easy.
Then the metrics that look worse. Average human handle time rises after launch because the easy tickets left the queue; do not read that as failure. Deflection that leaves the customer unhelped produces a second contact through a costlier channel, often the phone. And per-conversation billing on escalated tickets means paying twice for the AI's misses. These are the lines a finance review will find if you leave them out.
What this looks like in practice: a worked example
Take a consumer lender handling 20,000 contacts a month across chat, email and phone: payment dates, balance questions, identity checks and card issues, with disputes and hardship cases mixed in. Finance sets the loaded human cost at $6.00 per contact, roughly 15 minutes at the BLS median wage plus overhead. Substitute your own figure.
Running the levers on Lorikeet, the lender sorts its historical tickets into the three buckets and replays bucket-two scenarios in pre-launch simulations and red-team runs, which yields a resolved share on its own data rather than a vendor average. For the model, assume 50% of contacts finish end to end, in line with what Carmoola, an FCA-regulated UK car finance lender, publishes at 60% of inbound resolved end to end. Regulated steps such as identity verification and payment date changes run as deterministic structured workflows, the conversational parts run as natural-language workflows, and both sit in one interaction. Hardship signals route to a person immediately.
The arithmetic: 10,000 finished contacts at $6.00 avoided is $60,000 a month. Lorikeet's published pricing is about $0.80 per chat, email or SMS resolution and about $1.20 per voice resolution, so a blended 10,000 resolutions cost roughly $9,000. Coach, the automated QA layer, reviews 100% of the 20,000 conversations at about $0.25 each, or $5,000, replacing manual sampling. Net saving is about $46,000 a month before internal implementation time. Unresolved or unsatisfactory tickets cost nothing. Security review covers SOC 2, PII redaction, RBAC and US, UK or Australian data residency, documented on the trust page.
The limitation to write into the business case: Lorikeet does not publish a platform-wide resolution rate, so the 50% in this model is the lender's simulation estimate to confirm, not a guarantee, and an escalation-heavy queue saves less on any platform. Disputes are intake and deadline tracking only. The agent collects the details and computes the Reg E clock, and it never forms an opinion on whether the claim is covered. To run this model on your own tickets, book a demo.
What still needs a human
Judgment, exceptions and accountability, and in a Lorikeet deployment these are routed to people by design. Gartner predicts that none of the Fortune 500 will have fully eliminated human customer service by 2028, and the cost model above assumes the same.
Adjudication. Whether a dispute is valid, whether a claim is covered, whether a fee is waived outside policy. The AI gathers and computes; a person decides.
Vulnerable and distressed customers. Hardship, bereavement, complaints that mention a regulator. Route on the first signal, not after a failed attempt.
Exceptions with no written policy. If the rule does not exist, the AI cannot apply it. Write the rule first or keep the ticket human.
Supervising the AI. Reviewing QA flags from Coach, tuning guardrails, approving workflows and owning the audit trail. This is new work, and some freed hours go here.
Relationship conversations. Retention, upgrades, anything that depends on trust built over time.
Reducing support costs with AI comes down to one measurement: the share of expensive tickets the AI finishes, confirmed by reopen and second-contact rates, priced against a loaded human cost from your own payroll. Get that number on your own tickets before you sign, pay per outcome with escalations excluded, and budget for a human team that gets more senior rather than smaller.
