JapanNon-life insurance / nursing careScale · $100K
Sompo Holdings

Trust, rebuilt one logged conversation at a time — agentic claims and care coordination for Sompo

The Bigmotor affair made conduct governance Sompo's board-level priority: an agentic frontline where every claims conversation follows approved scripts, logs 100% and gates every payout decision to humans is not just cheaper service — it is the compliance architecture the FSA order demanded, delivered as customer experience; and the same platform coordinates family and shift communications for Sompo Care, where Japan's caregiver shortage bites hardest.

Entry use case
Auto claims FNOL and proactive status desk
Expected outcome
Structured, script-governed claims intake and proactive status with 100% conversation logging — measurable service recovery that doubles as compliance evidence.
Recommended next step
Workshop with claims and compliance leadership jointly: map the improvement-order requirements to conversation-governance capabilities, then scope a Scale pilot on auto FNOL and status.
What we understand

Sompo Holdings's operating reality

Sompo Japan received an FSA business-improvement order over its handling of the Bigmotor insurance-fraud affair, with senior leadership changes and a public governance overhaul following.

Public fact

Sompo Care is among Japan's largest nursing-care operators, giving the group direct exposure to caregiver labor scarcity and family-communication load.

Public fact

The 2023 non-life price-adjustment scandal additionally hardened compliance expectations across the sector, including at Sompo.

Public fact

Post-scandal, agency-channel oversight and communications consistency are under intense internal scrutiny — manual QA sampling cannot evidence conduct at scale.

Reasoned inference

Typhoon and hail surges strain claims intake exactly as at peers, but Sompo's reputational recovery makes slow cat response costlier than for rivals.

Reasoned inference

Sompo Care facilities likely field heavy family phone inquiries (condition updates, billing, scheduling) that consume caregiver and admin hours.

Seller hypothesis — validate

Validate with the account team before outreach: Improvement-order remediation program status and owners · Status-call ratios and cat-surge staffing arrangements · Sompo Care facility communication volumes and system landscape · Palantir and internal data-platform commitments that shape the stack

Build vs buy

Why we have a right to win here

Partner-led target

Technically capable but needs industry workflows, integration, acceleration, or managed operations

Evidence: Sompo has real digital assets — a publicized data-platform strategy and technology investments — so it expects to shape its stack, but conversational-frontline engineering with conduct governance is not its capability; partner-led delivery that plugs into its data-platform commitments is the credible fit.

Why they won't build the full stack: Internal change capacity is consumed by governance remediation and the data-platform agenda; building compliant voice AI internally would put an unproven system at the center of a trust rebuild — a partner-delivered, evidence-grade platform de-risks exactly what the board cannot afford to get wrong.

What management is signalling

Sompo Japan operated under an FSA business-improvement order following the Bigmotor affair, with leadership changes and a governance overhaul publicly committed.

Reported factpublic FSA action and company statements · 2023-2024

GTM implication: Sell conversation governance as remediation infrastructure — the rare compliance spend that also cuts cost per contact.

Group results emphasize recovery in domestic P&C profitability alongside international growth, with conduct and efficiency both on the management agenda.

Inferencerecent investor communications (validate) · 2025-2026

GTM implication: Position the pilot to report to both the compliance program and the P&L — two sponsors, one deployment.

What already exists (don't pitch this)
  • Digital claims filing on web and app
  • Agency network and portal tooling
  • Publicized group data-platform strategy and technology investments
  • Sompo Care facility operations at national scale
What customers still can't do end-to-end (pitch this)
  • →Script-governed conversational FNOL with complete logging
  • →Proactive status suppressing repeat calls
  • →Elastic cat-surge intake
  • →Family-communication automation for care facilities
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Auto claims FNOL and proactive status desk
Any-hour structured FNOL, proactive updates, approved-script enforcement and complete logs; status calls fall while conduct evidence rises.
Claims conduct is where trust was lost; script-governed, fully-logged claims conversations are where it is visibly rebuilt.
Friction today: Phone-hour FNOL queues, document chases, weekly status calls interrupting adjusters — all under a compliance microscope.
VoiceApp chatWebLINE
Catastrophe-surge communication protocol
Elastic intake with vulnerable-case triage; first response in minutes for every claimant.
A rebuilt brand cannot afford week-long cat silences; surge response is reputation in real time.
Friction today: Cat events multiply intake beyond fixed capacity while field adjusters deploy.
VoiceSMSLINEWeb
Sompo Care family-communication and scheduling desk
Routine family inquiries and scheduling resolved conversationally with facility-system lookups; caregivers stay with residents.
Caregiver hours spent on phone administration are bedside hours lost — the group's most human-facing labor-scarcity problem.
Friction today: Families call facilities for updates, billing and visit scheduling; staff answer between care tasks.
VoiceLINEWeb
Watch the change

Auto claims FNOL and proactive status desk: today vs the agentic model

Scenario: A claimant whose repair-shop estimate raised questions calls at 8pm; the agent takes the details against the approved script, attaches photos in-chat, schedules the adjuster review and sends a written summary — the entire exchange logged and scored, the payout decision untouched by automation, the compliance file complete by itself.
Today
same interaction, two worlds
Agentic layer
Status-call volume
dominant inbound driver
suppressed by proactive updates
Platform capability
Cost per contact
$13.50 median assisted
$1.84 median self-service
Benchmark
QA coverage
1–2% sampled
100% scored
Platform capability
Sources & assumptions
  • · Status-call volume: Process design; measured in pilot
  • · Cost per contact: Gartner customer service cost benchmarks, 2024
  • · QA coverage: Platform capability: every interaction logged and evaluated
  • · Gartner, customer service cost benchmarks (2024): $13.50 median assisted vs $1.84 self-service per contact
  • · McKinsey, digital-first collections research: 20–25% NPL reduction among leaders; up to 40% opex reduction with gen AI
  • · Baymard Institute: ~70% average cart abandonment (meta-analysis)
  • · IAMAI–Kantar via IBEF (2025): 900M+ Indian internet users; 98% consume Indic-language content
  • · LeadSquared and vendor funnel studies: 78% of students choose the first institution to respond (directional, vendor data)
  • · HDI / ITSM operator benchmarks: $15–25 per L1 ticket; 40–60% of L1 volume is resets/status (validate per customer)
  • · Conventional-flow wait times and volumes are typical operator patterns — assumptions to replace with the customer's own baseline
  • · Agentic-flow behaviors (context retention, 100% logging, in-line policy checks) are platform capabilities, not projections
Recommended solution

One integrated stack, opinionated for this account

Channels · Tilicho Labs
VoiceApp chatWebLINESMS

Voice & channel orchestration, telephony, conversational execution, session/state, routing, integration build. Capability coverage validated during implementation.

Intelligence · Google Cloud
Gemini reasoningEnterprise groundingWorkflow agentsMulti-agent orchestrationGoverned actionsEvaluation & analytics
Systems · Sompo Holdings
Claims workflowPolicy administrationDocument managementCat-event managementCRMCare-facility systemsBillingScheduling

API access to these systems is the critical-path dependency.

Trust & languages
JapaneseEnglish

Identity-bound sessions, policy-bounded actions, 100% audit logging, human approvals at defined points, in-tenant intelligence.

Business case

The economics, with your numbers

Addressable monthly interactions700K
Seller assumption — replace in discovery
Current cost per interaction ($)$6.0
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$4.2M
Current operating cost / mo
$26.1M
Modelled gross benefit / yr
0.0 mo
Payback on Scale
1580%
3-yr ROI (modelled)
Automated/assisted interactions per month385K
Modelled AI run-cost per month (usage + cloud, system estimate)$135K
New monthly operating cost$2.0M

All figures are modelling estimates from the labeled inputs above — nothing here is customer-provided yet. The pilot's first job is replacing these assumptions with Sompo Holdings's measured baseline. Package price covers implementation only; recurring usage billed separately.

Recommended package

Scale — $100K implementation

Scale · $100K · A multi-channel production deployment10–14 weeks to production across priority workflows

Why this package for Sompo Holdings: Claims FNOL/status plus cat-surge protocol are bounded Scale workflows; the nursing-care coordination line is a distinctive expansion that can follow as a second phase.

Included
  • 4–6 channels
  • 2–3 priority workflows
  • Multiple enterprise integrations
  • API credential & security setup
  • Advanced orchestration
  • Multilingual support
  • Agent Assist / human escalation
  • Production analytics
  • Expansion roadmap
Not included
  • ✕Usage & consumption (billed separately)
  • ✕Enterprise-wide governance build-out
  • ✕Multi-BU rollout
Recurring costs (separate from the package)

Packages cover implementation and integration only. Recurring costs are billed separately: Tilicho Labs platform usage (~$0.15/call-min indicative, usage only), Google Cloud consumption, telephony/carrier charges, managed operations, and support & optimization. No package includes unlimited usage.

Customer resources required
  • · API access + credentials for: Claims workflow, Policy administration, Document management
  • · A named business owner for auto claims fnol and proactive status desk
  • · Security review counterpart and policy sign-off (Claims workflow scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“The governance overhaul promised the market conduct you can prove; a frontline where every conversation is logged, scored and script-governed turns that promise into infrastructure — and better service is the visible byproduct.”

CIO / CTO

“A governed agent layer over claims and care systems with approved-script enforcement and complete audit trails — compliance architecture and modernization in one bounded integration program.”

COO

“Claims surge capacity and caregiver phone load are both labor problems Japan's market won't solve; elastic conversational capacity addresses both from one platform.”

Head of Claims Service

“Your adjusters carry casework plus status calls plus post-scandal documentation burden; structured intake and proactive updates return their hours to the judgment work only they can do.”

Chief Risk / Compliance Officer

“This is the control environment the improvement order pointed toward: 100% conversation coverage, script enforcement, human gates on every settlement — evidence-grade conduct governance replacing sampled QA.”

CFO / Procurement

“Compliance remediation usually only costs; this remediation line pays back in cost per contact and adjuster productivity, measured against your own baseline in the pilot.”

Outreach

Pre-built offer emails for Sompo Holdings

Written from this account's own research — the strategic signal, the capability gap, the entry workflow, and the modelled economics — not a mail-merge template. Pick the moment and the persona, edit anything, then copy or open in your mail client.

Moment in the deal
Cold outreach — no prior conversation
Who it's addressed to
Cares about: The workflow itself and its daily failure modes
Register
Length
Draft — edit freely before sending
Open in mail client

Customer-safe by construction: drafts are composed only from customer-facing fields. Account tier, build-vs-buy classification, priority score, internal routing, and partner-commercial detail are not inputs to the composer, so they cannot appear in a draft. Money figures are always framed as modelled from the customer's own volumes. Read before sending — you own what goes out.

The pursuit

Tier 1 — immediate strategic pursuit

Why this tier

Sompo is rebuilding trust after the Bigmotor fraud scandal forced a business-improvement order and leadership change — every customer conversation is now a governance artifact — while its nursing-care arm makes it the one insurer whose labor-scarcity problem is also a bedside-care problem.

30 / 60 / 90-day plan
  • Day 0–30: Workshop with claims and compliance leadership jointly: map the improvement-order requirements to conversation-governance capabilities, then scope a Scale pilot on auto FNOL and status.; confirm sponsor and baseline data access; validate: Improvement-order remediation program status and owners
  • Day 31–60: architecture & security review with the platform team; Tilicho Labs scoping on Voice + App chat; pilot scope signed
  • Day 61–90: Scale package kickoff; auto claims fnol and proactive status desk pilot in build; success thresholds locked with the Head of Claims Service
Recommended next step

Workshop with claims and compliance leadership jointly: map the improvement-order requirements to conversation-governance capabilities, then scope a Scale pilot on auto FNOL and status.

Entry: Auto claims FNOL and proactive status desk · Scale package · 10–14 weeks to production across priority workflows. Human fallback throughout; success thresholds agreed before build.

Start the pursuit

Research-based priority-account universe assembled from public information, market scale, communication volume, and solution fit. This is NOT an authoritative list of top Google Cloud customers; existing Google Cloud relationships are noted only where publicly reported. Validate every account with the account team before outreach.