How Klarna turned customer service triage into a durable AI workflow

August 28, 2026 · 5 min · Free, with full transcript

Klarna rebuilt one of its highest-volume, most repetitive operations around an AI agent rather than bolting AI onto an existing process. The decisions they made, and the ones they got wrong initially, offer a practical template for any team facing a similar problem.

Listen to the podcast

4 min

Read the full transcript

Welcome to the Leaders Insights podcast.

Today's episode, how Klarna turned customer service triage into a durable AI workflow.

Everyone keeps telling me Klarna fired 700 people because of an AI agent.

That's the story.

Is it true?

It's the story people want to be true, which is exactly why you should distrust it.

The layoffs made the headlines in early 2024.

The durable part came later, and it wasn't about headcount at all.

The interesting decision Klarna made was refusing to bolt AI onto their existing customer service

process.

What does bolt-on actually mean, though?

That sounds like a slogan.

Fair.

Bolting on means you keep your old workflow, not one, the ticket comes in, gets categorized,

routed to a queue, then a human answers, and you just drop a chatbot in front of it.

Klarna's first instinct was that, and it failed.

The bot became a very expensive speed bump before you reached a real person.

So what did they change?

They rebuilt the triage.

Triage being the sorting step, deciding what a request even is before anyone touches it.

Around the AI agent, instead of around the human org chart.

The old categories existed because humans needed them.

Refund, dispute, where's my stuff?

The model didn't need those buckets, so they threw them out and let it reason from the

raw message.

That sounds like a fancy way of saying they remove structure.

Isn't structure the thing that keeps these systems from hallucinating?

Inventing answers that sound right and aren't?

That's the contrarian bit, and it's where most teams get it backwards.

They think guardrails mean more rules, more decision trees, more if the customer

says X do Y.

Klarna found the opposite.

The more rigid the script, the more the model would twist a genuine request to fit a box.

Give it fewer categories and one clear escalation path to a human.

And the hallucination rate dropped.

Structure in the wrong place is what breaks these things.

Give me a number or I don't believe you.

Klarna's own figures, and this is the vendor talking about itself, so hold it loosely,

claim the agent handled roughly two-thirds of chats and cut average resolution time from

11 minutes to under two.

The number I actually trust more is the repeat contact rate.

How often the same customer comes back because the first answer was garbage.

That fell, and that one's hard to fake because it costs you real money when it's high.

What did they get wrong first?

You keep hinting.

The big early mistake was measuring the agent on deflection, the share of tickets that

never reach a human.

Deflection is the worst metric in this entire field.

You can hit 90% deflection by making it impossible to reach a person, and your customers will

quietly hate you and leave.

Klarna optimized for it.

Watch satisfaction sag and switch to measuring resolved and didn't come back.

Different incentive, completely different behavior.

So the prompt engineering, the way you write instructions for the model, that's the secret

sauce?

No, and I'll die on this hill.

Prompt engineering is the plumbing, not the architecture.

Klarna's win came from redesigning what the job was, then writing prompts to serve that.

Teams obsess over clever prompt tricks, the way people rearrange furniture in a house with

no foundation.

A beautifully worded prompt pointed at a broken process gives you a very polite failure.

That's a little cocky.

What's the evidence a normal team can copy any of this?

Because the transferable part is boring and free.

One, kill your legacy categories and let the model read the raw request.

Two, pick a metric that punishes bad answers, not one that rewards dodging humans.

Three, make the escalation path to a person one click, not a maze.

None of that requires Klarna's budget.

The expensive part was learning it.

You get it for the price of this podcast.

And the funny thing nobody admits?

Half these AI agents work brilliantly in the demo and fall apart in production for the

same reason as Souffle does, the moment you open the door and let reality in.

So the one thing I do Monday morning?

Find the metric your support team is judged on.

If it rewards avoiding customers rather than resolving them, fix that before you write

a single prompt.

Everything else is downstream of that number.

That's your five.

Full AI track, structured, no fluff, is at MBA-training.com.

Read and go deeper