Mistral Software / SaaS global

SAP

Customer Service Automation · Enterprise Knowledge Search · IT Operations Automation

SAP needed to reduce repetitive support demand, break down knowledge silos, and automate business processes for regulated, multilingual customers without sacrificing European data localization or trust in AI-generated answers.

100% European, locally hosted AI, maintained in SAP-operated infrastructure.
80% reduction in repetitive support queries.
From 1,000 pilot users expanding to 30,000 employees
Multilingual: several languages supported natively including German, French, and Italian.

Reported impact

Business outcome

SAP's Mistral-powered framework cut repetitive support demand at SBB, scaled from a 1,000-user pilot to 30,000 employees, continuously expanded its knowledge base through expert feedback, and established a reusable path toward autonomous finance and procurement workflows for regulated industries.

  • Compliance
  • Productivity Improvement
  • Scalability

Solution

SAP built a reusable enterprise AI framework on top of Mistral Large to support multilingual knowledge work and agentic business processes while keeping data hosted on SAP operated infrastructure in Europe. In the first deployment at Swiss Federal Railways, the team implemented a chatbot that uses retrieval-augmented generation to pull answers from FAQs, training materials, recordings, and screenshots, then applies glossary-based query rewriting so abbreviations such as "SO" are expanded before retrieval. When the bot cannot answer, human-in-the-loop escalation captures expert responses and feeds them back into the knowledge base. The service is surfaced inside SAP Build Work Zone and Microsoft Teams, and the same hosted framework is being extended to autonomous agents such as SAP's Accounting Accruals agent that reads SAP system data and policy documents to prepare draft journal entries.

Data flow

FAQs, training materials, recordings, and screenshots feed a RAG knowledge base; employee questions arrive through SAP Build Work Zone or Microsoft Teams, glossary rewriting expands domain abbreviations before Mistral Large retrieves and answers, and unresolved cases are escalated to experts whose responses are written back into the knowledge base.

Solution architecture

4 components · 2 layers
  1. Compute
    • SAP operated infrastructure Hosts the models locally so SAP can keep data residency and sovereignty controls in place.
  2. Serving
    • Mistral Large Provides the multilingual language understanding and response generation layer for SAP's chatbot and agent workflows.
    • SAP Build Work Zone Embeds the support assistant into employees' existing portal workflows.
    • Microsoft Teams Provides a collaboration entry point for the multilingual support experience.

Architecture clues

  • Glossary-based query rewriting expands abbreviations such as SO to sales order before retrieval.
  • Human-in-the-loop escalation captures expert answers and adds them back to the knowledge base.
  • The Accounting Accruals agent reads SAP systems and accounting policy documents to prepare draft journal entries.

Evidence from the source

"80% reduction in repetitive support queries."
"The AI reads data from SAP systems and interprets accounting policy documents using Mistral's language understanding capabilities."
"The chatbot employs sophisticated retrieval-augmented generation (RAG) to draw from multiple knowledge sources including FAQs, training materials, and unstructured content like recordings and screenshots."
"The solution integrates directly into employees' existing workflows through SAP's Build Work Zone portal and Microsoft Teams"
"when the AI cannot resolve a query, expert responses are automatically captured and added to the knowledge base"
Transparency Evidence & methodology 96/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value96/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Mistral

    SAP customer story

    First-party
    https://mistral.ai/customers/sap/
    Source type
    Vendor-published customer story
    Published
    Apr 24, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Apr 24, 2026 · Mistral · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.