Nubank's five support agents: card-delivery agent gains 37 points of transactional NPS in A/B tests
Nubank's KDD '26 paper describes five customer support agents in production and the evaluation pipeline behind them. One A/B test showed a 37-point NPS gain and a 29-point self-service gain.
- Organization
- Nubank
- Industry
- Fintech
- When
- Jun 2026
- Evidence
- Research paper
- Agents and tools
- LLM judgesGEPA prompt optimization
Reported outcome
In A/B tests on the card-delivery agent, AI transactional NPS rose 37 points and self-service rate rose 29 points over prior agent variants.
- +37 points (paper)AI transactional NPS gain
- +29 points (paper)Self-service rate gain
- 5 (paper)Agents in production
Caveats
Described in a paper with a stated method. Peer review status varies.
- The headline gains are for the card-delivery agent only, compared with Nubank's earlier agent variants, not with human agents.
- The paper is by Nubank's own staff. We read the abstract page, not the full paper, so we have not checked the method or the authors' stated limits.
- The abstract says AI satisfaction on most use cases is within a few points of human experts, but gives no exact figure.
What the agents do
Nubank runs five support agents: card delivery, debt management, credit-limit support, card management, and product explanation. The paper is mostly about how the team builds and tests them.
Why this works
The authors' central claim is that the quality of the evaluation pipeline sets how fast a team can improve its agents. Their framework has four parts: structured context engineering, human-in-the-loop prompt iteration, LLM-judge evaluation with measured agreement between raters, and a path from idea to production validation.
What to copy
- Test an LLM judge against human raters before you trust it.
- Run live A/B tests against your previous agent version, not only offline tests.
- Track a customer-reported score (like NPS) and a task score (like self-service rate) together.
Starter prompt
Written by us, not by Nubank.
You are grading a customer support conversation.
Conversation: {transcript}
Goal of the customer: {goal}
Score 1-5 on each: resolved the goal, accurate, clear, appropriate tone.
Give one sentence of evidence per score, quoting the conversation.
If a score is below 3, name the exact turn where it went wrong.
Sources
- Building Customer Support AI Agents at 100M-User Scale: An Evaluation-Driven Framework — arXiv (KDD '26), Jun 2026
Added Oct 19, 2026. Spotted an error? Send a correction.
Get new use cases weekly
One short email. Sources included.
Related use cases
Octopus Energy's AI email assistant Arlo scored higher satisfaction than human replies
76% customer satisfaction for AI replies vs 72% for comparable human replies, on ~8,000 emails a week (4% of UK customer emails).
Salesforce runs its own support on Agentforce and cut support headcount from ~9,000 to ~5,000
About 1.5M customer conversations handled by agents, with CSAT about the same as humans; support headcount went from ~9,000 to ~5,000.
Lyft cut average support resolution time by 87% with a Claude-based assistant
Average resolution time fell by more than 87%, with thousands of requests resolved per day (company claim).