The map

Is AI going to replace customer support?

No. What the Klarna walk-back, Gartner's 2027 prediction, and 86% of AI conversations needing a human tell us about where AI actually fits in customer support.


Justin Thompson6 min read

No. At least not in the way the 2024 pitch decks promised.

AI is already changing customer support. It can answer basic questions, draft replies, classify tickets, summarize conversations, and pull context from systems faster than a person can. That part is real.

But replacing the support function is a different claim. The brands that treated AI as a replacement for the human relationship are already walking that back. Customers still strongly prefer humans for anything that is not a basic lookup, AI hits hard ceilings on the categories of ticket that matter most, and some of the companies that cut support staff to deploy AI are now hiring them back.

The useful question is not whether AI will replace customer support. It is where AI fits underneath humans to make the team faster and the customer happier.

What “replace” would even mean

“Replace” is the word that breaks the conversation. It bundles three different propositions together.

Will AI do some of the work humans used to do? Yes, and already does. Order status lookups, FAQ answers, internal note drafting, ticket classification, draft replies. All of that is real and useful.

Will AI handle some categories of ticket end-to-end without a human? Yes, in the categories where it can. Stable answers, structured data, low emotional load. Order status. Password reset. Return eligibility lookups.

Will AI replace the customer support function as a role inside the company? No. Not in 2026, and not in the trajectory the data points to.

When a CEO asks “will AI replace customer support,” they almost always mean the third one. The answer matters because the wrong framing leads to the wrong decision: cut headcount based on AI handling the work it does well, hit a quality crater on the work it does not, then hire the staff back twelve months later.

What the data says

The Klarna case is the canonical version. In February 2024 Sebastian Siemiatkowski announced Klarna’s AI assistant was handling work equivalent to 700 FTEs in its first month. Fourteen months later he told Fortune that cost had been “a too predominant evaluation factor” and Klarna was rehiring humans.

Gartner now predicts that 50% of companies that cut customer service staff because of AI will rehire by 2027. That isn’t a contrarian analyst’s take. It’s the firm enterprise CX leaders cite when defending budget conversations.

If 86% of AI conversations eventually involve a human, the AI is not replacing the human. It is sharing the conversation with them. The replacement framing assumes a tool that completes the work end to end. The reality is a tool that hands most of the work over.

And the consumer side is harder still. 79% of Americans strongly prefer talking to a human over an AI in customer service, and half of US consumers say they prefer brands that don’t use generative AI in customer-facing messages, advertising, and content. The pattern shows up downstream as Trustpilot deterioration, repeat-contact spikes, and visible brand damage three to six months after deflection metrics climb.

What AI does replace

AI replaces work, not roles. The work it replaces, in the categories where it works, is real:

  • Pulling order status from Shopify (or wherever your data lives)
  • Looking up return eligibility against policy
  • Drafting first-pass replies for high-volume question types
  • Classifying tickets by intent, urgency, and category
  • Writing internal notes summarising what the customer said and what’s been done

Done well, this lifts a support team’s throughput several times over without growing headcount or eroding answer quality. The team is the same size. The work it gets through is different.

That is what every functional AI deployment in customer support actually looks like in 2026. The companies that confused it with replacement are the ones now rehiring.

What it doesn’t replace, and why

The ceiling on AI-resolved tickets is not just a model-quality problem. It is a shape-of-the-work problem.

Empathy load matters before the customer has typed enough for the bot to recognise the situation. A reply that is accurate but tone-deaf can hurt more than a slower reply that lands.

Judgment matters when policy and good business outcome diverge. The bot can apply the rule. It can’t decide when bending the rule keeps a customer for ten years.

Brand voice matters most when the customer can tell. AI can imitate voice. It cannot sustain the character of a brand under pressure.

Escalation matters precisely because some tickets need to escalate. A bot that closes a ticket the customer wanted escalated is worse than a bot that does nothing.

The per-category ceilings put refunds, complaints, and damage tickets under 10% AI-alone resolution for these reasons. The categories that need a human will keep needing one.

The question worth asking instead

Not “will AI replace customer support.”

The better question is: where do humans become higher-leverage when AI handles the work underneath them?

That is what the brands getting AI in customer support right are answering. Their teams are not necessarily smaller. Their throughput is higher. Their reps spend less time on tab-switching and lookup. Their customer experience tracks resolution rate, not deflection rate.

Teams plus AI beats teams alone, and beats AI alone. The framing that gets the answer right starts with team-side AI, not replacement.

Sources

Part of the AI in customer service: the map series

The AI-in-CX category is still being drawn. Deflection, assist, automation, copilot, agent. These words mean different things to different vendors, and the map of the category is contested. This pillar publishes our reading of the map, and where Handsom sits on it.

See the full series

What is Handsom?

Team-side AI that briefs your support team on every ticket before they open it. Lookup work happens once, by the AI; your reps reply with context.

See how it works

More in The map