The challenge
What was deployed
The results
Last Updated: October 6, 2026
Commerzbank, one of Germany's leading financial institutions, spent roughly 17 months taking a generative-AI banking avatar from announced project to production. The agent, called Ava, now handles more than 30,000 customer conversations a month and resolves about 75% of them without a human, according to a Microsoft customer story featuring named Commerzbank executives. The interesting part is not the chatbot. It is that a regulated European bank put an LLM agent in front of retail customers with the authority to block a credit card — and built the compliance scaffolding first.
The problem: a service channel that could not keep up with the app
Commerzbank serves around 11 million private and small-business customers in Germany and transacts roughly 30% of the country's foreign trade financing. Its retail service model runs across branches, a remote advisory centre, and a mobile app. When the bank first announced the avatar project in November 2023, it framed the mobile channel as the beachhead: the assistant would be developed for mobile devices as a first step, for the target group of 2.2 million active banking app users.
The underlying problem is familiar to anyone who has run a retail bank's contact centre. The high-volume requests — what is my credit card limit, I have lost my card, can you raise my limit for a holiday — are simultaneously trivial in content and non-trivial in consequence. They are identity-sensitive, they are regulated, and they arrive at 11pm. Routing them to human agents is expensive; routing them to a 2018-era intent-classification bot produces the deflection theatre customers have learned to bypass by shouting “agent” at the phone.
Commerzbank's own framing in the Microsoft write-up is blunter than most vendor case studies allow. Gerald Ertl, who runs the bank's Strategic AI Program, describes a gap between expectation and capability:
We were seeing a necessity to build a bridge between what our customers expected and what our systems could deliver. We needed a new way to serve—not just faster, but smarter and more human.
— Gerald Ertl, Managing Director, Head of Strategic AI Program, Commerzbank AG, Microsoft Customer Stories
What was actually built
Ava is a conversational agent that lives inside the Commerzbank banking app. It is rendered as a photorealistic avatar — the bank says Ava is modeled after the likeness of an actress — and it is available 24/7 in natural language. That is the consumer-facing surface. The engineering underneath is a fairly standard enterprise agent stack, assembled from Microsoft components.
From the Microsoft customer story and the parallel Foundry Labs entry, the published architecture is:
How Ava is put together
Azure OpenAI models in Foundry interpret the customer's request and produce the reply. The agent is orchestrated on Foundry Agent Service and Microsoft Agent Framework.
Azure AI Content Safety filters sensitive data before it reaches the model and is used to detect potential fraud patterns. Commerzbank layers customised filters on top of the stock service.
Azure AI Search retrieves from trusted sources so answers about products and policies are not generated from model priors alone.
Azure Cosmos DB synchronises the shared context so a dialogue stays consistent across turns and systems.
Ava executes real transactions in-dialogue: ordering a card, blocking or unblocking one, changing limits, surfacing account and product data.
Complex enquiries are referred to experts in the bank's customer centre. Agents run on Azure Container Apps; Azure Kubernetes Service absorbs load spikes.
Two design decisions are worth isolating. First, Ava was given write authority over the credit card lifecycle from the start. Commerzbank's launch release lists ordering a new credit card, blocking or unblocking a current credit card, and changing limits as in-dialogue actions. Most banks that shipped an LLM assistant in 2024–25 restricted it to read-only Q&A precisely to avoid this. Second, the safety layer is treated as an employee-equivalent control, not a content filter bolted on at the end. Denise Reffelmann, the business product owner, puts the standard explicitly:
Security and trust are foundational. Ava doesn’t just talk to customers—she acts on their behalf. That means she must be as secure and compliant as any human employee, which is why we rely on Content Safety plus customized filters to monitor and help protect every interaction.
— Denise Reffelmann, Business Product Owner, Commerzbank AG, Microsoft Customer Stories
The measured outcome
The 2× development figure deserves a note, because it is the metric integration teams most often ignore. Microsoft attributes it to the combination of GitHub Copilot, Foundry tooling, and agentic frameworks, together with streamlined build-and-release processes and automated testing incorporated into the DevOps pipeline. In other words, part of the reported gain is AI-assisted coding and part is ordinary platform engineering hygiene. The case study does not separate the two.
Commerzbank announces the Banking Avatar project on Microsoft Azure OpenAI Service, positioning itself as one of the first banks to combine generative AI with avatar technology in a customer-facing application.
Ava goes live in the banking app, released gradually to customer devices, German-language only, with English promised for a later version.
The bank creates a Chief Data & AI Officer role reporting to the Board of Managing Directors, consolidating AI under its “Momentum” strategic upgrade, and cites Ava as a flagship use case.
Microsoft publishes the customer story with the 30,000-conversations and 75%-autonomous-resolution figures, and describes a move toward a network of specialised agents.
The governance move most teams skip
The May 2025 appointment is easy to read past, but it is structurally the most transferable part of this deployment. Commerzbank did not leave Ava as a product owned by a digital channels team. It put bank-wide AI responsibility and data management under one executive reporting into the board. Christiane Vorspel, the COO with responsibility for IT, framed it as integration rather than innovation:
By appointing Oliver Dörler as Chief Data & AI Officer, we are ensuring that our central themes of data and AI are strategically integrated. This will enable us to offer our customers improved products and services while optimising our internal processes more quickly and effectively.
— Christiane Vorspel, Member of the Board of Managing Directors and COO, Commerzbank AG, Commerzbank newsroom
Technical product owner Christoph Jakfeld describes the same discipline at the architecture level — modular, transparent and highly secure, so the team can build fast without creating risk. That phrasing, speed through auditability rather than in spite of it, is the pattern worth copying. Teams that treat compliance as a release gate ship late; teams that treat it as an architectural property ship repeatedly. If you are scoping something similar, our notes on production automation and model selection cover the same trade-off.
Autonomous resolution is not deflection
Resolved autonomously means the agent completed the customer's intent end to end. Deflected usually means the customer stopped asking. The two numbers can differ by tens of points on the same traffic. Commerzbank and Microsoft use the resolution framing, which is the harder claim — but neither publishes the measurement method behind it.
What the public record does not tell us
This is a well-documented deployment by the standards of European banking, and it is still thin in the places that matter most to a buyer.
No customer satisfaction data. Microsoft notes that Microsoft Fabric is being implemented to persist and analyse conversation flows so the bank can measure outcome quality and continuously improve customer satisfaction. That phrasing implies the satisfaction measurement loop was not yet fully in place when the story was published. No CSAT, NPS, or complaint-rate figure has been published for Ava.
No cost figure. Neither Commerzbank nor Microsoft has published a cost-per-conversation, a headcount effect, or a return-on-investment number for Ava specifically. The Microsoft story says the automation brings considerable relief to call center agents — a qualitative claim, not a measured one.
No accuracy or incident data. There is no published hallucination rate, no wrong-action rate on card blocking or limit changes, and no record of how often escalation happens because the agent failed rather than because the query was genuinely complex.
The metrics are vendor-published. The 30,000 and 75% figures appear in a Microsoft customer story and a Microsoft Foundry Labs entry, with Commerzbank executives quoted by name. We did not find those figures in Commerzbank's own press releases or investor materials. Named-executive attribution raises confidence; it is not the same as a bank-audited disclosure.
Scale context is missing. Commerzbank identified 2.2 million active app users in 2023. 30,000 conversations a month works out to roughly 1.4% of that base per month — our arithmetic, not the bank's. That is a real production system, but it is not yet the primary service channel, and no source states what share of total retail service contacts Ava now carries.
Reading a vendor case study as a benchmark
A 75% autonomous resolution rate gets screenshotted into board decks as a target. But the denominator is Ava's own routed traffic on a deliberately scoped set of intents — credit card lifecycle, savings and balance inquiries, account management — not the bank's full contact mix. Narrow the scope enough and 75% is achievable; widen it and the same architecture will read far lower.
How this compares to the common alternatives
| Approach | What it gets you | Where it breaks |
|---|---|---|
| Intent-classification chatbot (pre-LLM) | Predictable, cheap, fully auditable responses | Falls over on paraphrase; customers learn to bypass it |
| Read-only LLM assistant over a knowledge base | Fast to ship, low blast radius | Answers questions but resolves nothing; escalation rate stays high |
| Transacting agent with a safety gate (Commerzbank's Ava) | Completes real work in-dialogue; measurable resolution | Needs content safety, grounding, memory and audit built before launch; ~17 months announce-to-production |
| Full multi-agent network across the bank | Orchestrates multistep workflows across domains | Stated as Commerzbank's next step, not yet an evidenced outcome |
What an integration team should take away
Scope by consequence, not by difficulty. Commerzbank picked the credit card lifecycle — high volume, emotionally urgent, and crucially a domain with clean, well-defined, reversible operations. Blocking a card is a high-stakes action with a low-ambiguity trigger. That is a much better first agent target than open-ended financial advice.
Build the audit path before the conversation path. Content safety, grounded retrieval, persistent context and escalation all appear in the published architecture as first-class components. In a regulated environment these are not optimisations; they are the reason the thing is allowed to transact at all.
Expect a long runway and say so. November 2023 announcement to April 2025 launch is about seventeen months, and the bank released Ava gradually to devices rather than flipping a switch. Anyone promising a transacting banking agent in a quarter is describing a demo.
Treat the first agent as a platform decision. Microsoft reports that Commerzbank now sees Ava's framework as a blueprint for the bank's next wave of AI initiatives, from internal agents that support employees to advisory agents. Ertl's own summary of the shift:
Foundry Agent Service gives us the building blocks for the future and has changed how we think about service. Ava offers expert knowledge 24/7 without waiting time and empowers our teams, because they can now focus on what they do best: building customer relationships, solving complex problems, and driving innovation.
— Gerald Ertl, Managing Director, Head of Strategic AI Program, Commerzbank AG, Microsoft Customer Stories
Note what that quote does and does not claim. It claims availability and focus. It does not claim cost reduction. Executives who have the savings number usually publish the savings number. For more deployments read the same way, see our case study library, or talk to us about scoping your own.
Frequently Asked Questions
What is Commerzbank's Ava?
Ava is a generative-AI banking assistant inside the Commerzbank mobile banking app, presented as an avatar modeled after the likeness of an actress. It answers product and account questions in natural language and executes transactions in dialogue, including ordering a credit card, blocking or unblocking one, and changing limits. It launched in April 2025, is available 24/7, and refers complex enquiries to human experts in the bank's customer centre.
How many conversations does Ava handle, and how many does it resolve?
A Microsoft customer story published in November 2025 reports that Ava manages more than 30,000 customer conversations per month and resolves roughly 75% of them autonomously, with round-the-clock availability. Those figures come from Microsoft's write-up, which quotes Commerzbank executives by name. Commerzbank has not published equivalent figures in the newsroom releases we were able to locate.
What technology stack does Ava run on?
Microsoft Foundry Agent Service and Microsoft Agent Framework for orchestration, Azure OpenAI in Foundry Models for language understanding and generation, Azure AI Search for grounded retrieval, Azure AI Content Safety for filtering and fraud pattern detection, Azure Cosmos DB for shared conversation context, Azure Kubernetes Service and Azure Container Apps for scale, Microsoft Fabric for conversation analytics, and Azure Speech text-to-speech avatar technology for the voice and visual persona.
How long did it take to build?
Commerzbank announced the Banking Avatar project in November 2023 and launched Ava in the banking app in April 2025 — about seventeen months, followed by a gradual release to customer devices rather than a single switch-on. Microsoft separately reports that the associated frameworks made development twice as fast compared with previous approaches, crediting GitHub Copilot, Foundry tooling, and automated testing in the DevOps pipeline.
Has Commerzbank published cost savings or customer satisfaction results?
No. Neither Commerzbank nor Microsoft has published a cost-per-conversation, headcount effect, ROI figure, CSAT score, or accuracy and incident data for Ava. The Microsoft story notes that Microsoft Fabric is being implemented to analyse conversation flows and measure outcome quality, which suggests satisfaction measurement was still being stood up at the time of publication.
What is Commerzbank doing next with agents?
Microsoft reports that Commerzbank is evolving Ava so that a network of specialised agents will manage distinct tasks across the bank's operations, with upcoming iterations intended to orchestrate multistep workflows across lending, business banking and operations inside the same transparent, auditable framework. The bank also treats Ava's architecture as a blueprint for internal employee agents and advisory agents. These are stated plans, not evidenced outcomes.
Twarx analysis
Original interpretationCommerzbank's result did not come from a better model — it came from scoping the agent to a narrow, high-volume, low-ambiguity domain (the credit card lifecycle) and building content safety, grounded retrieval, persistent memory and auditable escalation as first-class architecture before letting the agent transact. In regulated environments, the compliance scaffolding is not a release gate; it is the thing that makes autonomous resolution permissible at all.
Read the numbers honestly
Analysis by
Rushil Shah · AI Systems Builder & Founder, Twarx


