Summarize with AI:ChatGPTPerplexityGoogle AIClaude

Quick Answer

Match the fix to the problem. Add AI for repeat questions your knowledge base already answers, hire for conversations that need judgment and product depth, and outsource nights, overflow and seasonal peaks.

Most teams end up using all three. No AI assistant is right every time, so keep a handoff to a person on every channel. Then compare cost per conversation handled, not salary against subscription.

Did this answer your question?
Three things people believe. Myth or fact?
Call each one, then see how other readers called it.
1 Outsourcing your support means handing your escalations to the partner as well.
2 Customers will accept AI-only support as long as the answers come quickly.
3 A new outsourced rep usually ramps up best on email before taking live chat.

Most support teams that fall behind do not have a staffing problem. They have a sorting problem. Repeat questions, after-hours chats and judgment calls all land in one queue, and every option looks wrong because each one is asked to carry all three kinds of work at once.

Think of a busy restaurant. When the phone rings unanswered during the dinner rush, nobody hires another chef. Someone answers the phone, and the kitchen keeps cooking.

Support works the same way. Menlo Ventures reported in December 2025 that 76 percent of enterprise AI use cases were bought, not built, so a team without engineers can now put an AI assistant in front of its repeat questions. The risk sits elsewhere. The Air Canada tribunal ruling of February 2024, over a refund policy a chatbot invented, is the reason I tell owners to judge any AI by what it does when it does not know the answer.

I will not claim that any assistant is right every time, or that it can run support without people. No honest vendor can. What follows is a way to sort your queue by contact type, a cost formula for the same monthly workload under each option, and a mix that keeps a person within reach of every customer.

Start with the conversations your team already struggles to answer. As one contact centre consultant put it, "Finance needs to understand what breaks, because your team hears it first."

Start by asking which conversations went unanswered last month, at what hour, and why each one stalled. Long waits on simple questions point to AI. Night and weekend gaps point to an outsourced partner. Complex, account-sensitive conversations point to a hire.

I hold that view because each option fails in a predictable place. A 2017 industry review of multilingual support counted seven operating models, from borrowing a colleague in another department to full BPO outsourcing, and found that every one of them traded cost against control. Adding AI has not removed that trade. It has added a third column to the ledger.

Two constraints shape every choice below.

  • Customers: a large majority still expect a route to a person whenever AI answers them, so any plan without a clear handoff starts with a gap it will have to close later.
  • Rollout: consultant Pier Ragone advises phased pilots and waves instead of "trying to flip a switch overnight," and that advice applies to a new hire or a new partner as much as to new software.

What follows is a decision guide built around the problems owners actually describe: long waits, night gaps, repeat questions and burnout. Each one has a fix, a cost formula and a point where that fix stops working. Burnout sits last on that list only because it is the hardest to see on a dashboard.

Questions this article answers

Should you hire in-house agents or outsource customer support?

Hire when a conversation needs judgment, product depth or authority over an account. Outsource when the gap is hours, overflow, seasonal peaks or languages your current team cannot cover.

Before you post a job or sign a contract, I recommend sorting each contact type with four plain questions:

  1. Does the answer depend on judgment? Refund exceptions, billing disputes and account changes belong with people you employ and coach directly.
  2. Does it require deep product knowledge? If an agent must reproduce a fault or explain a configuration, keep that contact in-house.
  3. Is the clock the problem, not the question? Nights, weekends and launch spikes are coverage problems. A trained partner solves coverage.
  4. Is language the problem? Written channels and voice need different answers, so treat them separately.

The pattern is visible at small companies first. One startup's operations manager described an IT assistant answering tickets until the executive team decided the load had become too heavy and hired its first outsourced representative through an agency. The advice that followed was practical: write escalation paths before onboarding anyone, start the new representative on email, and add chat once answers come confidently. At Gamma, the head of support manages a "really small" offshore BPO team through a weekly standup and constant Slack contact. Neither company handed over its judgment calls. Both handed over volume.

The common assumption is that outsourcing fails because partner agents care less. The evidence points to the contract instead. A former outsourced Verizon representative wrote that sales-weighted metrics meant agents could not issue a credit 9 out of 10 times, and that supervisor requests went to an escalation team that "would resent" agents who sent cases its way. Those are design failures. A buyer can write them out of an agreement.

Languages deserve their own line in the plan. Call Centre Helper reported in 2017 that, by its poll, over a third of contact centres could handle calls in only one language, and it described recruiting and keeping multilingual speakers as "difficult and expensive." In 2017, the same guide named the benchmark of 80% of calls answered in 20 seconds as a challenge under BPO outsourcing, and warned that handing work to a third party makes quality assurance targets "difficult to achieve."

A comparison of 5 sources shows one consistent rule. If partner agents will open customer records, ask how they sign in; LiveHelpNow offers two-factor authentication for agents, a code by email or SMS with a trusted device for 30 days. Ask, too, whether partner agents can sign in through your own identity provider; LiveHelpNow supports SAML 2.0 single sign-on with Microsoft Entra ID, Google Workspace and Okta. Quality depends on shared rules, not on who signs the paycheck.

Shared rules need a shared source of answers. At LiveHelpNow, one knowledge base serves three audiences: customers asking about their own accounts, agents who receive suggested replies and next steps, and managers asking about the business in plain English. When in-house and partner agents read from the same knowledge base software for customer support, a weekend agent gives the answer your Tuesday agent would give. Before signing with a partner, ask how long conversation data is kept; in LiveHelpNow, each account sets automatic data purge from immediately after an interaction to 30 days.

Can AI handle customer support instead of human agents?

AI should take the repeat questions your knowledge base already answers well. People should keep complex, emotional and account-sensitive cases. Test it first on your own top questions.

Gartner's research points the same way from both sides of the counter. In a March 2025 poll of 163 service leaders, 95% planned to retain human agents to define AI's role, and Gartner predicted that by 2027, 50% of organizations expecting to cut their service workforce significantly will abandon those plans. Customers agree. In a 2026 survey of 3,566 B2B and B2C customers, 87% said companies using generative AI in service must offer a way to reach a human agent.

Klarna shows both halves of the story. Business Analytics Review reports that the company launched an AI assistant in February 2024, handled 2.3 million conversations in the first month and automated two-thirds of customer interactions. Average resolution time fell from 11 minutes to under 2 minutes. Cost per transaction dropped from $0.32 to $0.19 over two years. Then complex cases degraded, institutional knowledge left with the agents, and in 2025 Klarna made a costly partial reversal that involved rehiring and rebuilding the capacity it had removed. The newsletter's conclusion is worth repeating: "AI scales tier-one volume, humans move up the value chain."

I do not read Klarna as a warning against AI. I read it as a reason to decide, before launch, which contact types stay with a person however well the AI performs.

Clay offers the more useful model for a growing team. Its head of support, George Dilthey, told Know Your Growth that AI deflection rose from around 10% to 45-50%, while refund requests and account deletions stay out of the AI flow entirely. His explanation is blunt: "Every AI support tool is using the same underlying models. Nobody's got a huge advantage when it comes to the actual AI. Most of it depends on how good your content is."

That shifts the decision. You are not choosing an AI. You are deciding which questions you trust it with, and for a healthcare practice, whether the vendor signs a business associate agreement; LiveHelpNow is HIPAA-ready with a business associate agreement, with PII encrypted at rest using AES-256, scheduled data purge and one-time codes for attachments.

Three conditions should be true before AI faces your customers:

  • Content: the top questions have current, approved answers in a knowledge base or help center.
  • Boundaries: refunds, cancellations, account deletion and disputes route straight to a person.
  • Exit: every customer can reach a human at any point, with the history attached.

Where those conditions hold, the AI assistant should sit inside the same omnichannel customer service workspace your agents use, so a customer who moves from chat to email or SMS does not start over. LiveHelpNow offers per-product free trials, which lets you test an AI assistant on your own questions before any budget changes. What that budget looks like for a team handling 1,000 conversations a month is a matter of arithmetic, and the formula is simpler than most vendors make it appear.

What makes AI or an outsourcing partner work for a support team that is behind?

In its first month, Klarna's AI assistant did work the company equated to 700 full-time agents. By 2025, a case study reports, Klarna was rehiring. Much of what we learned sits between those two facts.

Klarna's own announcement, dated February 27, 2024, reported 2.3 million conversations, two-thirds of its customer service chats, with errands resolved in under 2 minutes instead of 11. A June 2026 case study in the Business Analytics Review newsletter added later figures: $60 million in documented savings by Q3 2025, and cost per transaction down from $0.32 to $0.19 over two years.

The same case study describes what moving too fast cost. Klarna's early push to replace human agents, it says, led to "quality degradation on complex cases" and lost institutional knowledge, then to "a costly partial reversal in 2025 that involved rehiring and rebuilding the very capacity it had eliminated."

Few service leaders are planning the opposite. In a Gartner poll of 163 service leaders in March 2025, 95% said they plan to retain human agents. Gartner predicts that by 2027, 50% of organizations that expected to significantly reduce their customer service workforce will abandon those plans.

So why does AI carry one team and stall at another? George Dilthey, who leads a 16-person support team at the data platform Clay, answered bluntly in a January 2026 interview.

"Every AI support tool is using the same underlying models. Nobody's got a huge advantage when it comes to the actual AI. Most of it depends on how good your content is."

George Dilthey, head of support at Clay, 2026

Clay's AI deflection rose from around 10% to 45 to 50%, Dilthey said, and his team now treats the knowledge base as "the measure of intelligence for your custom AI." Account deletions go to Clay's privacy team, and refund requests stay out of the AI flow: "That's just a bad experience." As a maker of AI support software, we have a stake in his point. A practitioner on Reddit in 2024 described the other side: many companies still "have long-standing documentation gaps that AI requires to be successful."

Outsourcing tends to break in the same place. In summer 2024, the AI-first app company Mirage started getting one-star App Store reviews saying nobody ever replied. Eli Winderbaum, its head of customer experience, traced them to a contracted agent who "had quietly deleted hundreds of tickets per week from her queue to reduce her workload."

Gamma, the presentation platform, shows the other outcome. Hilary Dudek, who leads support there, inherited an offshore BPO team she had "zero say" in choosing. She holds a weekly standup with its team lead, says the two are "constantly communicating" on Slack, and notes that the BPO wrote much of its own early process documentation. She calls the fit "a stroke of luck." Winderbaum, who later deployed an AI agent at Mirage, reached a similar view: "your docs are now the source of truth for both human and AI consumption." He has invested in the AI vendor Mirage chose.

A partner's incentives also reach your customers. A former outsourced rep for Verizon wrote on Reddit in 2025 that issuing credits hurt the team's metrics, so 9 out of 10 times agents could not give one. The reps customers praised most, the rep wrote, "rarely stay very long because it's not worth it." One account proves no pattern. Still, it shows what a price quote leaves out: how the people answering your customers are measured and paid.

TeamFixWhat held it up or broke itSource
KlarnaAI assistantLarge early gains. Complex cases suffered, and the case study reports rehiring in 2025Klarna, February 2024; Business Analytics Review, June 2026
ClayAI first for 90% of customers who contact supportA maintained knowledge base. Refunds and account deletions go to peopleInterview, January 2026
MirageContracted agentsHundreds of tickets a week deleted, unnoticed until one-star reviewsHead of customer experience, September 2025
GammaOffshore BPO teamWeekly standup, constant Slack contact, process documentation written by the BPOPodcast interview, August 2024

Look at the four teams together and the price and the AI model matter less than you might expect. Each fix that worked rested on two things: written answers to the common questions, and a person inside the company who checked the work and took the hard cases. Where either was missing, the cost arrived later as deleted tickets, weaker handling of complex cases or rehiring. None of these companies stopped relying on its own people. Those people moved to writing the answers, reviewing the work and handling the cases that need judgment.

Before you add AI or a partner

  1. Write down your most common ticket types and how you answer each one. An agency founder who sells staff placements claims, without data, that even a rough version cuts ramp-up time in half.
  2. List the topics that always go to a person, the way Clay routes refunds and account deletions, and write the escalation path before anyone starts.
  3. Have someone you employ check the partner's or the AI's work every week, including how many tickets were closed and how.
  4. Ask every partner for its attrition rate, who covers when your rep is out, what happens if the fit is wrong, and which metrics its agents are paid on.
  5. If AI is meant to shrink your team, ask who will handle the complex cases and keep the knowledge base current afterward.

How we checked this

We used Klarna's own press release, a newsletter case study of Klarna, two Gartner press releases, interviews with the support leads at Clay and Gamma, an essay by Mirage's head of customer experience, and Reddit threads written by practitioners and a former outsourced rep. None of the figures here are ours. Klarna's 2024 numbers are its own claims. The rehiring account comes only from the newsletter, and none of our sources gives its size. Clay's deflection figures are Clay's own report. Mirage's author has invested in the AI vendor he describes. The ramp-up claim comes from an agency founder pitching his own firm, and the Verizon account is one person's experience. We sell support software with an AI assistant, so we have a stake in how this question is answered. Still unknown: how much of Clay's gain came from content work rather than other changes, and how Gamma's arrangement held up as its team grew.

  1. Klarna, AI assistant first-month announcement, February 27, 2024.
  2. Business Analytics Review, Klarna customer support case study, June 12, 2026.
  3. Gartner, prediction on customer service workforce plans, June 10, 2025.
  4. Yash Tekriwal, interview with Clay's head of support, January 12, 2026.
  5. Eli Winderbaum, essay on rebuilding support at Mirage, September 4, 2025.
  6. The Career Strategist, podcast interview with Gamma's support lead, August 13, 2024.
  7. Reddit r/customerexperience, discussion on replacing agents with AI, July 2024.
  8. Reddit r/SaaS, thread on outsourcing a first support rep, January 2026.
  9. Reddit r/verizon, post by a former outsourced customer service rep, March 2025.

What does it cost to handle 1,000 conversations a month?

Divide each option's full monthly cost by the conversations it actually handles. Compare cost per conversation, not salary against subscription, and the right starting point usually becomes obvious.

I would build the comparison on one number: cost per conversation handled. Business Analytics Review makes the same argument, calling cost per transaction the right metric for judging customer service AI. Klarna's own result shows why that metric needs context, because $60 million in documented savings by Q3 2025 sat beside the costly partial reversal described earlier. Savings that later have to be rebuilt are not savings.

Here is the formula for each option at the same workload.

OptionMonthly cost to countDivide by
Hire in-houseSalary + benefits + recruiting + training + tools + turnover replacement, spread across the months an agent staysConversations that agent handles in a month
OutsourcePartner fee (per agent, per interaction or per hour) + your own time on oversight and quality reviewConversations the partner handles
Add AIMonthly plan + time to set up and maintain the knowledge base + the cost of conversations handed to a personConversations the AI resolves without a handoff

Hire: The salary line is the smallest trap. Recruiting, training and replacing a leaver all land in the same months the queue is already behind, which is why I count them inside the cost of the hire rather than beside it. Use the wage your local market pays customer service representatives, then add the other five lines in full.

Outsource: One offshore outsourcing provider, in its own pricing guide, says the comparison "goes beyond an hourly wage comparison" because the partner absorbs hiring, training, infrastructure and workforce management. That is a vendor's pitch, yet the structure of the formula holds. Ask any partner for its fee model in writing, along with how quickly trained agents can go live on your channels. Speed is part of the cost here. Every week the queue stays behind carries a price of its own.

Add AI: The denominator matters most. Count only the conversations the assistant resolves, then add back the cost of every handoff to a person. LiveHelpNow lists Conversational AI from $499 a month with 1,000 or 3,000 AI conversations included, and each product has a free trial, so you can run this formula on your own volume before committing. The plan details sit on the AI customer support software page.

When owners tell us AI sounds expensive, our answer is to compare it with one more hire, using the price on the page. Setup is the other objection we hear, and we set it up with you; the person needed is a process owner, not a developer. That moves the setup line in the AI formula away from engineering hours and toward the people who already know your answers.

Which fix should you test first?

Start with the problem costing you the most this month, then test one fix on real volume. A demo shows how AI, your team and a handoff to a person fit together.

Small business owners in Goldman Sachs 10,000 Small Businesses research from 2026 named privacy and security (50%), lack of expertise (49%) and difficulty choosing tools (48%) as their main barriers to AI. Those are setup questions. They are answerable on your own content, with customers still able to reach a person.

No survey settles which mix fits your queue. Back in 2017, Lionbridge's Tom Tseki told Call Centre Helper that every common approach carried "significant pitfalls," and that remains true of staffing. Technology should add to human work, not stand in for it.

What should a support team that is falling behind do first?

List last month's conversations by type, then assign each type to AI, your own agents or a partner. Fix the largest gap first and measure cost per conversation.

I expect the next two years to reward teams that blend all three options rather than bet on one. With 87% of customers in Gartner's 2026 survey insisting on a route to a person, the teams that keep that route open while AI takes the repeat questions will carry less risk than teams that cut first and rebuild later.

Waiting is also a choice. A January 2026 r/SaaS thread shows a startup moving support to an outsourced rep because the load "has gotten too heavy," and one commenter put the cost of delay bluntly: "Your IT person doing support is a recipe for burnout and bad ticket quality."

In summary, the order of work matters more than the option you pick: count the conversations, assign each type, then test one change on real volume. I would appreciate it if you started with one queue this week. Please let me know which problem you sort first.

Frequently Asked Questions

What else do people ask about hiring, outsourcing or adding AI to support?

Is it cheaper to outsource customer service or to hire in-house?

Neither option is cheaper by default. Divide the full monthly cost of each option by the conversations it actually handles, and include recruiting, training and turnover on the hiring side. Outsourcing usually earns its place on hours and peaks you cannot staff; hiring earns its place on conversations that need judgment.

How do you keep quality up with outsourced or contract agents?

Make queue visibility part of the contract. Eli Winderbaum, head of customer experience at Mirage, wrote in 2025 of discovering that a remote, contracted agent had quietly deleted hundreds of tickets per week to reduce her workload; she was let go. One-star reviews had flagged the problem before any report did. I would ask every partner for open, closed and deleted ticket counts by agent.

How quickly can AI start resolving support questions?

It depends on the knowledge behind it. Mirage reported in 2025 that its AI agent resolved close to 50% of inbound volume on day one, 65% within weeks and later 75%, though Winderbaum disclosed an investment in the vendor. Resolution rate means the share of conversations closed without a person stepping in. Your own rate will track the quality of your help center content.

How can you try LiveHelpNow before committing?

Each LiveHelpNow product has a free trial, and you can book a demo on the LiveHelpNow website to see the AI assistant and your team in one workspace. Your data is used to answer your questions and is not used to train AI unless you choose to allow it.

Written by

Michael Kansky

Founder

Michael Kansky is a serial entrepreneur, software founder, and AI-driven business operator with more than two decades of experience building companies at the intersection of customer engagement, automation, software, digital services, and data-driven growth.

Connect on LinkedIn