MongoDB Telecommunications Switzerland

Swisscom

Enterprise Knowledge Search

Swisscom needed to help banking users search and summarize a fast-growing library of more than 3,500 industry documents with better speed, relevance, and trust than general-purpose online AI tools could provide.

Swisscom reached out to MongoDB on February 6, 2024 and had a prototype built by February 15.
The service is used by 30 of Switzerland's leading banks.
Total development effort for the first solution was around six days.
e.foresight has over 3,500 documents in its library, with more being added each day.

Reported impact

Business outcome

Swisscom stood up the first solution with about six days of development effort, moved from concept to prototype in days, improved the speed and relevance of banking-content searches and summaries, and created a reusable pattern for additional Swiss AI Platform services.

  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

Swisscom built a retrieval-augmented generation service for e.foresight, its banking-industry think tank, by putting the entire document library on MongoDB Atlas and using MongoDB Vector Search to ground LLM responses. Reports, live-event recordings, graphics, and external studies are stored in Atlas as the single secure repository, then vectorized so the application can retrieve relevant segments and feed domain-specific context into large language models. The team went from first contact with MongoDB on February 6 to a working subset prototype by February 15, then production in early May after joint testing with ZHAW and internal operations handoff. Because the data stays in Switzerland and every answer can point back to cited source material, Swisscom can serve banks with faster, more accurate summaries while meeting the trust and sensitivity requirements of the financial sector.

Data flow

Reports, event recordings, graphics, and external studies are stored in MongoDB Atlas, converted into embeddings, searched with MongoDB Vector Search, and the retrieved context is passed to LLMs so e.foresight users receive condensed, source-linked answers instead of manual document lists.

Solution architecture

2 components · 2 layers
  1. Storage
    • MongoDB Atlas Stores e.foresight's banking research corpus and operational data in one secure repository.
  2. Serving
    • MongoDB Vector Search Retrieves the most relevant document segments to ground AI-generated responses for banking users.

Architecture clues

  • All generated answers include links back to source material.
  • Swisscom emphasizes that sensitive banking data is held only in Switzerland.
  • The application stores all content in MongoDB Atlas and retrieves relevant segments for RAG workflows.
  • Users can uptick answers to improve future retrieval quality.

Evidence from the source

"Swisscom can then convert the unstructured data into vector embeddings and use MongoDB Vector Search on Atlas to find segments of relevant context to feed the LLMs."
"Total development effort for the first solution was around six days."
"With this project we’ve proved we can create something powerful using data held only in Switzerland."
"e.foresight has over 3,500 documents about trends in the banking industry in its library, with more being added each day."
Transparency Evidence & methodology 90/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 value90/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 specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric 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
    4 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. MongoDB

    Swisscom customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/swisscom
    Source type
    Vendor-published customer story
    Published
    Aug 11, 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 Aug 11, 2026 · MongoDB · 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.