AWS Financial Services Canada

Sun Life

Enterprise Knowledge Search

After launching more than 40 generative AI experiments, Sun Life needed to move from experimentation to production value with a secure way for employees to retrieve internal information quickly inside the company’s own technology environment.

It easily saved me several hours of manual work
over 10,000 queries a week
over 40 experiments
over 600,000 internal queries in its first 11 months

Reported impact

Business outcome

Sun Life Asks is handling more than 10,000 employee queries each week, resolved more than 600,000 internal queries in its first 11 months, and saves team members hours of manual work so they can reinvest time in higher-value tasks while Sun Life prepares additional client-facing AI use cases.

  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

Sun Life turned its early generative AI experiments into a production knowledge assistant by building Sun Life Asks on AWS. The chatbot runs inside the company’s secure technology environment and uses Amazon Bedrock to access Anthropic Claude models without Sun Life having to manage model infrastructure. Employee questions are grounded in internal company information, processed by Bedrock, and returned through the Sun Life Asks interface to staff across global operations. This architecture let Sun Life move from experimentation to value delivery quickly while keeping governance inside its own environment, and it created a reusable pattern for future client-facing use cases as the company scales broader generative AI adoption and workforce upskilling.

Data flow

Employee questions and internal company information flow into Sun Life Asks, which uses Amazon Bedrock and Anthropic Claude to generate secure responses for employees across Sun Life’s global operations.

Solution architecture

1 components · 1 layer
  1. Compute
    • Amazon Bedrock Provides the foundation-model service Sun Life uses to run its internal Sun Life Asks chatbot.

Architecture clues

  • Deployed globally to all employees.
  • Runs within Sun Life’s safe and secure technology ecosystem.
  • Uses Anthropic's Claude through Amazon Bedrock.

Evidence from the source

It easily saved me several hours of manual work.
Sun Life Asks resolved over 600,000 internal queries in its first 11 months.
Sun Life Asks uses Anthropic’s Claude through Amazon Bedrock.
Sun Life launched over 40 experiments, obtaining numerous lessons across its global operations.
employees are submitting over 10,000 queries a week.
Transparency Evidence & methodology 90/100 reference value · 87% 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 confidence87%
  • 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 provenance8/10
    The publication date comes from publisher-controlled metadata.
  • 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. AWS

    Sun Life customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/sun-life-case-study/
    Source type
    Vendor-published customer story
    Published
    Nov 21, 2024
    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.

Related

Similar use cases

See all like this