IBM Financial Services Japan

Tokio Marine & Nichido Anshin Life Insurance

Anshin Life wanted to use customer feedback to improve operations and service quality, but manually reading and classifying up to 18,000 unstructured feedback entries each year was slow, inconsistent, and difficult to scale with traditional machine-learning approaches.

500 hours of work per year reduced
approximately 75% reduction in processing time, from 7-8 minutes to 2-3 minutes
up to 18,000 customer feedback entries annually

Reported impact

Business outcome

Anshin Life significantly reduced the time needed to review and classify feedback, standardized judgments across reviewers, and uncovered previously hidden customer trends that it can now use to improve operations and future service decisions.

  • Customer Experience
  • Productivity Improvement

Solution

Anshin Life co-created a feedback-classification and analysis workflow with IBM Client Engineering using IBM watsonx.ai as the core reasoning layer. Customer comments from calls, online channels, and surveys are ingested into a generative AI process that first classifies them against roughly 40 insurance-industry codes and then extracts company-defined keywords and clusters so teams can analyze patterns hidden inside unstructured text. The design combines watsonx.ai natural-language processing with retrieval-augmented generation so the insurer can update information and launch new products without repeated fine-tuning, which reduces maintenance effort while preserving classification quality. Business and IT teams worked together in weekly agile cycles, using an “application owner system” to move from proof of concept to production quickly. This makes the solution more than a tagging tool: it is now part of Anshin Life’s voice-of-customer operating model, helping the insurer surface trends, improve hypotheses, and expand generative AI into other departments.

Data flow

Customer feedback from phone, online, and survey channels is fed into watsonx.ai, classified into industry codes, enriched with extracted keywords and clusters, and then returned to business teams as structured insight for operations, service quality, and policy planning.

Solution architecture

2 components · 2 layers
  1. Compute
    • IBM watsonx.ai Runs the generative classification, keyword extraction, and clustering workflows for customer feedback analysis.
  2. Orchestration
    • IBM Client Engineering Co-created the solution with Anshin Life and helped move it from proof of concept to production through agile iterations.

Architecture clues

  • System prompts and RAG avoided the need for fine-tuning when new products or information were introduced.
  • The first phase classified feedback into approximately 40 industry-wide codes.
  • The second phase extracted keywords as hashtags and applied cluster analysis.

Evidence from the source

“Processing time for reading and categorizing each customer feedback entry was reduced by approximately 75%, from 7-8 minutes to 2-3 minutes.”
“System prompts and RAG eliminated the need for fine tuning when launching new products and updating information.”
“The company receives up to 18,000 customer feedback entries annually”
“customer feedback from phone calls and other sources was captured by generative AI and classified into approximately 40 industry-wide codes.”
“the combination of watsonx.ai’s natural language processing technology and Retrieval Augmented Generation (RAG) technology achieved both high accuracy and flexibility.”
Transparency Evidence & methodology 100/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 value100/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 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. IBM

    Tokio Marine & Nichido Anshin Life Insurance customer story

    First-party
    https://www.ibm.com/case-studies/tmr-anshin-watsonx-ai
    Source type
    Vendor-published customer story
    Published
    Dec 9, 2025
    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

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.