AI Showreel consulting-grade analysis, for everyone FR
← The index
Proof B Live confirmed

bunq

genAI financial assistant (search + support)

IndustryBanking, insurance & fintechLeverRetentionFamilyConversationImplementationHybridStagepost-purchase
Pattern proven in 10 industries still untouched in Retail & e-commerce, CPG & D2C, Tech & SaaS +3 See the pattern map
environ 97%
Support activity handled by Finn
"97% of all user support activity" S2

Finn, the GenAI assistant of the Dutch bank bunq launched in December 2023, handles about 97% of support activity with 90% satisfaction and a 47-second response time, on a base of more than 20 million European users at the end of 2025.

Key points

  • Finn GenAI financial assistant that replaces the app's search and absorbs support.
  • Third-party LLM connected to transactions via an in-house RAG layer, in the bunq app.
  • About 97% of support handled, 90% satisfaction, 47-second response.
  • Evidence level B, confirmed active status.

Objective

Replace the app's search function with a conversational assistant that answers directly on finances, budget, and transactions, and absorb support to serve a fast-growing European base without growing the teams.

The deployment

bunq launched Finn in December 2023, presenting itself as Europe's first bank with a GenAI assistant. Finn replaces the app's search function: the user asks questions in natural language about their finances, budget, transactions, and spending. The bank then made Finn fully conversational (memory of previous exchanges, chained questions). According to bunq, Finn independently resolves up to 40% of requests and assists 35% more; on its first anniversary, the bank announced that Finn handles about 97% of support activity with 90% satisfaction and a 47-second response time. bunq had 11 million users in the EU at launch, more than 20 million at the end of 2025.

Results Proof B

environ 97%
Support activity handled by Finn
"97% of all user support activity" S2
90%
User satisfaction
"90% user satisfaction rating" S2
47 secondes
Response time
"47 seconds" S2
40% resolues seul
Requests resolved independently, 35% more assisted
"independently resolves up to 40% of user inquiries" S3

Figures published by bunq in its official releases (T1) and picked up by the fintech press (T3/T4), consistent. Operational metrics provided by the brand, not audited as financial results, hence B.

How it works

Inferred typical approach

The internal detail is not public. Here is a proven approach that leads to the same result, to adapt to your stack.

escalade Utilisateur dans l'appbunq Finn (LLM + RAG) Transactions et donneesde compte Support humain

The stack in detail

  • llm LLM tiers (fournisseur non nomme) bunq does not publicly disclose the provider or the model version behind Finn; the record stays at the documented level: a third-party generative LLM.
  • outil Plateforme GenAI maison bunq (RAG) Internal pipelines that connect the LLM to the client's transactions and account data, with memory of previous exchanges.
  • plateforme App bunq Finn's single channel, which replaces the in-app search function and absorbs support.

How it runs, concretely

For ops teams
CadenceReal time in the app, on every question and every support request
Operated bybunq's product and data team, on an in-house GenAI layer (RAG on bunq's data pipelines)
  1. 1
    Question in the app client

    The user asks their question in natural language instead of a search (budget, transaction, spending, support).

  2. 2
    Contextualized answer AI

    Finn combines the LLM and the client's account data (RAG) to answer precisely, keeping track of previous exchanges.

  3. 3
    Support escalation AI / support

    Requests that Finn does not resolve are assisted or passed to a human.

  4. 4
    Monitoring data team

    The team tracks resolution rate, satisfaction, and response time to adjust Finn's scope.

The signal that drives it

The share of requests resolved without a human and satisfaction. Since Finn relies on the client's transaction data via RAG, answer quality depends directly on the freshness and structure of that data.

How your customers perceive this type of use

Sourced studies

Les consommateurs n'acceptent pas les chatbots par defaut : 64% prefereraient que les entreprises n'utilisent pas d'IA dans leur service client (Gartner, 2024) et pres d'un utilisateur sur cinq du service client par IA n'en retire aucun benefice (Qualtrics, 2025). L'acceptation se construit sur trois conditions mesurees par Salesforce : savoir qu'on parle a une IA, pouvoir escalader vers un humain, comprendre la logique de l'agent.

64%
Consommateurs qui prefereraient que les entreprises n'utilisent pas d'IA dans leur service client (2024)
53%
Consommateurs qui envisageraient de passer a un concurrent s'ils apprenaient que l'entreprise prevoit d'utiliser l'IA pour le service client (2024)
pres de 75%
Consommateurs qui veulent savoir s'ils communiquent avec un agent IA (2024)

Acceptance conditions

  • Etre informe qu'on parle a une IA et non a un humain (pres de 75% le demandent, Salesforce 2024)
  • Un chemin d'escalade clair vers un agent humain (45% plus enclins a utiliser l'agent IA, Salesforce 2024)
  • Une logique de l'agent clairement expliquee (44% plus enclins, Salesforce 2024)

Red lines

  • Rendre l'humain injoignable : c'est la premiere inquietude des consommateurs sur l'IA dans le service client (Gartner 2024) et 50% craignent que l'IA les coupe du contact humain (Qualtrics 2025)
  • Remplacer le service client par l'IA sans alternative : 53% envisageraient de partir chez un concurrent (Gartner 2024)

Sources: Salesforce 2024 · Gartner 2024 · Qualtrics 2025

See full acceptance: by country, by use, by generation

How to replicate

Inference, not sourced

Data prerequisites

  • Structured and fresh transaction and account data
  • Support knowledge base
  • Conversation history for refinement

Org prerequisites

  • In-house or tooled RAG layer connecting LLM and client data
  • Escalation rule to support
  • Owned AI transparency on the product side

Possible stack

  • Generative LLM (third-party or open)
  • RAG pipeline on the banking data
  • Integration with the mobile app
Team to operate2-3 developers / ML engineers + 1 PM + customer support to define the escalation rules.

The plan, step by step

  1. Step 1
    Scope a set of frequent questions (balance, budget, transactions) and the data access rules: read-only, confidentiality, AI transparency.Deliverable: Functional scope and compliance framework validated.
  2. Step 2
    Build the RAG layer between the LLM and the structured account data, and test it on the set of questions in a test environment.Deliverable: Assistant answering the scoped set of questions correctly.
  3. Step 3
    Replace the app's search with the assistant for a beta segment, with the AI nature displayed to the client.Deliverable: Beta in production with satisfaction tracking.
  4. Step 4
    Open first-level support with a clear escalation rule to a human.Deliverable: Assistant handling simple support requests, working escalation.
  5. Step 5
    Measure the without-human resolution rate, satisfaction, and response time, then broaden the covered scope.Deliverable: Resolution dashboard and expansion roadmap.

First step: Replace the app's search with an assistant connected via RAG to the client's transactions, on a scoped set of questions, before opening support.

Sources

  1. S1 bunq becomes the first AI-powered bank in Europe as it unveils its own GenAI platform Primary press.bunq.com · 2023-12-19 · accessed 2026-07-11 archive pending
  2. S2 bunq launches smarter, more powerful upgrade to GenAI financial assistant Primary press.bunq.com · 2025-12-16 · accessed 2026-07-11 archive pending
  3. S3 bunq's GenAI assistant Finn is now fully conversational Secondary fintech.global · 2024-05-14 · accessed 2026-07-11 archive pending