Salesforce Financial Services Japan

Aflac Japan

Customer Service Automation

Aflac Japan's manually intensive insurance contracting, claims, and customer-support work is difficult to scale as the working population shrinks, while customer data is distributed across multiple environments.

In the past, what required 100 people might now be done by 10.

Reported impact

Business outcome

Agentforce reduces manual touchpoints and operating costs, helps representatives prepare customer-specific proposals, and gives employees more time for customer conversations. Aflac says work that previously required 100 people might now be done by 10, and describes the goal of improving customer experience and operational resilience.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Aflac Japan uses Salesforce Agentforce as an agentic co-worker for repetitive insurance work, including policy management, claims, after-sales service, and customer-meeting preparation. Agentforce gathers and analyzes information from multiple systems, bringing customer history, policy options, and prior support interactions together so representatives can prepare proposals and focus on customer conversations. Data 360 connects the distributed information through a zero-copy architecture, allowing Agentforce to access and analyze data without copying or moving it. Salesforce's built-in trust layer is described as protecting sensitive health and financial information. The story does not name the underlying systems, connectors, model versions, storage services, or detailed runtime orchestration.

Data flow

Data 360 provides zero-copy access to information distributed across Aflac's systems. Agentforce gathers and analyzes customer history, policy options, and prior support interactions, then surfaces the context to insurance representatives preparing customer meetings and handling policy or claims work.

Solution architecture

2 components · 2 layers
  1. Storage
    • Data 360 Unifies access to data scattered across Aflac's systems through a zero-copy architecture without copying or moving the data.
  2. Uncategorized
    • Agentforce Automates repetitive insurance tasks and gathers and analyzes information to assist employees and agency representatives with policy, claims, and customer work.

Architecture clues

  • Aflac says it was the first company in Japan to introduce Agentforce.
  • Data 360 uses a zero-copy architecture to provide access without copying or moving data.
  • The interview describes a built-in trust layer for sensitive health and financial data.

Evidence from the source

Agentforce helps us address both. It acts as an agentic co-worker, automating repetitive tasks and assisting employees and sales associates in complex processes like policy management, claims, and after-sales service.
Data 360 allows us to bring together data scattered across our systems — without copying or moving it — through its zero-copy architecture.
In the past, what required 100 people might now be done by 10.
The platform's built-in trust layer gives us the confidence to innovate with agentic AI while keeping information safe and compliant.
Transparency Evidence & methodology 75/100 reference value · 91% confidence · 2 sources

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 value75/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 impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence91%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 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 transparency10/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/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. Salesforce

    From, “Try and learn” to first mover: Why Aflac Japan has confidence and trust in Agentforce

    First-party
    https://www.salesforce.com/customer-stories/aflac-tohru-futami-interview/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Industry
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
  2. アフラック生命保険株式会社

    コーポレートデータ | 会社情報 | 企業情報

    First-party
    https://www.aflac.co.jp/corp/profile/data.html

    The corporate-data page identifies アフラック生命保険株式会社 and lists 社員数 4,832人; the page states figures are as of 2025年度末.

    Source type
    official company website
    Supports
    • Company size

Date evidence

  • Published on source page Nov 5, 2026 · Salesforce · First-party
    Open date source
Not separately sourced Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.