234 incidents on record · 2026HeadlightsIncident reports by Ellie Harris · Melbourne
5 new this weekLibrary last updated 14 October 2026
← The incident library
HD-INC-019
Financial services · Sweden / global · 2024 · Scope drift

Klarna Said Its AI Assistant Did the Work of 700 Agents, Then Admitted Quality Had Fallen

By Ellie Harris · Filed 27 February 2024

Alleged: Klarna Bank AB, OpenAI developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

Klarna Said Its AI Assistant Did the Work of 700 Agents, Then Admitted Quality Had Fallen

What happened

It was reported that in February 2024, Swedish payments company Klarna announced that its new AI customer service assistant, developed with OpenAI, had handled 2.3 million conversations in its first month. The company claimed the technology was doing the equivalent work of 700 full-time employees, reducing response times and delivering customer satisfaction scores comparable to those achieved by human agents.

Klarna projected that the technology would contribute 40 million USD in additional profit that year, and the announcement quickly became an example of how AI could transform customer service. The comparison with 700 employees attracted particular attention, although the figure represented additional staff Klarna estimated it would otherwise have needed, rather than 700 people directly replaced by the chatbot.

As the company continued expanding its use of AI, however, the limitations of the approach became more apparent. While the assistant could deal with straightforward enquiries about payments and refunds, more complicated situations requiring judgement, reassurance or an understanding of individual circumstances were harder to manage through automation.

By May 2025, Klarna chief executive Sebastian Siemiatkowski was publicly acknowledging that the company’s focus on efficiency had come at a cost to customer service.

“We focused too much on cost,” he said. “The result was lower quality.”

Klarna subsequently announced plans to recruit more human customer service agents and make it easier for customers to speak to a person. The company was not abandoning AI, but recognising that automation alone could not provide the level of service it wanted to deliver.

What an auditable version would have shown

Klarna’s early performance figures told an impressive story about efficiency, but the number of conversations handled and the average time taken to resolve them could not fully explain whether customers were receiving the help they needed.

A chatbot might successfully answer thousands of routine payment questions while struggling with a smaller number of complicated disputes. When those experiences are combined into one overall satisfaction score, problems affecting particular groups of customers can be difficult to identify.

An auditable system would have measured performance separately across different types of enquiries, including payment disputes, fraud concerns and situations requiring more detailed assistance. A MetricRecord could have tracked whether problems were genuinely resolved, while a ConductRecord could have shown when customers needed further support or asked to speak with a person.

The public reporting does not establish exactly which internal measures Klarna used or when the company first identified declining service quality.

Where the gap was

The issue was not that Klarna introduced AI into customer service, because the technology appeared capable of handling a substantial volume of routine enquiries. The difficulty arose when the benefits demonstrated in straightforward interactions were used to support a much broader approach to customer service.

Headlights identifies scope drift, where a system that performs well within a particular set of tasks is given responsibilities that require capabilities it has not demonstrated consistently.

There is a human tendency behind this pattern. When a technology delivers impressive early results, organisations can become increasingly confident in its ability to do more, particularly when those results support financial targets. Measures such as response times, conversation volumes and operating costs are easy to communicate, while the experience of a customer struggling through a complicated financial problem is harder to capture in a single number.

This does not establish that Klarna deliberately overlooked those customers, but it shows why overall efficiency figures can provide an incomplete picture of service quality. A system can appear successful across thousands of interactions while still performing poorly in the situations where customers most need help.

This behavioural interpretation is Headlights’ analysis, not an official finding about Klarna’s internal decisions.

What governance should have looked like

Klarna needed clear boundaries around the types of enquiries its AI assistant could manage reliably, supported by regular reviews of customer outcomes rather than relying primarily on overall efficiency.

Routine questions could be handled automatically, while disputes, fraud concerns and sensitive financial situations should have a straightforward route to human assistance. Customers requesting a person should not have to repeatedly explain their problem before being transferred.

A MetricRecord could identify declining satisfaction or unresolved complaints within particular categories, while a ConductRecord could preserve the reasons for escalation and help reveal where the assistant was struggling. Together, these records would give the company a clearer understanding of which tasks were suitable for automation and which continued to require human judgement.

Klarna’s decision to expand human support demonstrated the importance of that distinction. The lesson is not that AI has no place in customer service, but that handling a large number of conversations is not the same as resolving every customer’s problem.

Failure Pattern: Klarna initially reported substantial efficiency gains from its AI customer service assistant, but its chief executive later acknowledged that prioritising cost reduction had affected service quality. The company subsequently moved to expand human support alongside automation.

Governance Principle: AI customer service should be assessed on the quality of outcomes across different types of enquiries, with clear limits on automation and accessible human assistance when customers need it.

The reference implementation of MetricRecord and ConductRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

Sent through Substack. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and Klarna Bank AB, OpenAI could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →