Hanwha Life's competitive weapon is distribution — a massive exclusive-agent salesforce selling into a saturated market — which means two frontlines to feed: policyholders who call about policies, and agents who call about products, underwriting and commissions; an agentic layer that serves both in proper honorific Korean lets the distribution machine scale without the back-office scaling with it.
Hanwha Life is one of Korea's largest life insurers, part of Hanwha Group, and spun its exclusive salesforce into Hanwha Life Financial Services — one of Korea's biggest insurance distribution organizations.
Public factKorea's life market is saturated and aging: new-business growth is hard-won, shifting economics toward in-force servicing efficiency and health/protection products.
Public factKorean insurers face IFRS 17/K-ICS capital regimes that put public focus on CSM quality and cost discipline.
Public factA distribution-heavy model generates large internal support volume — product, underwriting-status and commission questions from thousands of agents daily.
Reasoned inferencePolicyholder demographics skew older and phone-first; honorific-register voice quality is a hard adoption bar for servicing conversations.
Reasoned inferencePolicy-loan and surrender inquiry volume likely spikes with rate moves and economic stress, straining fixed servicing capacity.
Seller hypothesis — validateValidate with the account team before outreach: Actual servicing and agent-desk contact volumes and current wait times · FSS/cloud compliance route for LLM processing of insurance conversations · Hanwha Group AI initiatives and any mandated internal platforms · Incumbent AICC vendors (Korean telcos sell competing stacks into insurers)
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: Hanwha Life is a distribution-led insurer, not a technology organization: group-level AI activity exists at Hanwha, but the insurer's own change capacity is vendor-led and committed to IFRS 17-era systems work — honorific-quality conversational AI with FSS-grade governance is a buy, sold with sensitivity to any group-platform preferences.
Why they won't build the full stack: An insurer competing on distribution cannot divert engineering into voice-AI infrastructure; regulatory expectations (FSS outsourcing, consumer-protection scripts) favor a proven, auditable platform with human gates, and the agent-productivity clock rewards capacity this year over a multi-year internal program.
Korean life insurers operate under the IFRS 17/K-ICS regime, with public reporting focused on CSM growth, capital ratios and cost discipline in a saturated domestic market.
GTM implication: Tie servicing automation directly to reported cost-discipline and CSM-quality narratives — efficiency the market already rewards.
Hanwha Life continues investing in distribution scale (Hanwha Life Financial Services) and overseas expansion as domestic growth saturates.
GTM implication: Pitch the agent help desk as a distribution-productivity investment — the same strategic lane the company is already funding.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Policy servicing desk Routine servicing resolved in honorific conversation with documents guided in-flow; wait times drop for the oldest callers. | Premium, policy-loan, surrender and beneficiary questions are the structural volume of a large in-force book in an aging market. Friction today: Older policyholders navigate IVR trees; routine changes need documents, callbacks or an agent visit. | VoiceKakaoTalkApp chat | |||
Agent-channel product and underwriting help desk Instant grounded answers for the agent channel around the clock; internal desk capacity refocuses on complex cases. | Agent productivity is the business model; every minute an agent waits on a product or underwriting-status answer is selling time lost. Friction today: Agents queue on internal lines for product rules, underwriting status and commission questions answered from multiple systems. | VoiceApp chat | |||
Claims intake and status care Structured compassionate intake any hour with proactive status at every stage; assessments stay human. | Claims moments define insurer trust; status inquiries recur for weeks when updates aren't proactive. Friction today: FNOL queues behind routine calls; document chases run by mail and callbacks. | VoiceKakaoTalkApp chat |
Voice & channel orchestration, telephony, conversational execution, session/state, routing, integration build. Capability coverage validated during implementation.
API access to these systems is the critical-path dependency.
Identity-bound sessions, policy-bounded actions, 100% audit logging, human approvals at defined points, in-tenant intelligence.
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 Hanwha Life's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Hanwha Life: Policyholder servicing plus the agent-channel help desk are two distinct, well-bounded workflows over shared policy-admin integrations — natural Scale scope for a major insurer.
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.
“In a saturated market the winners are decided by distribution productivity and servicing cost; an agentic layer that feeds both frontlines is a structural advantage competitors staffing call centers cannot match.”
“A governed agent platform over policy admin, underwriting and commission systems gives one conversational layer for policyholders and the salesforce — architected to FSS cloud and outsourcing expectations from day one.”
“Servicing demand rises with the age of the book while Korean service labor grows scarcer and costlier; elastic honorific-quality capacity is the only model that tracks both curves.”
“Your agents lose selling hours to internal queues; instant product and underwriting-status answers at any hour is the cheapest productivity lever available to a 20,000-agent force.”
“Underwriting and claims decisions stay human; consumer-protection scripts are enforced verbatim, every conversation logged and scored — stronger conduct evidence than sampled QA under FSS scrutiny.”
“Under IFRS 17, servicing cost discipline flows straight to CSM quality; the pilot measures cost per servicing contact and agent-desk wait times against your own baseline, usage billed on consumption.”
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.
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.
Korea's second-tier life major runs one of the country's largest agent-distribution networks (via Hanwha Life Financial Services) and a big in-force book in a saturated, aging market — heavy policy-servicing and agent-support volume with structural cost pressure.
Dual-track scoping with policy operations and Hanwha Life Financial Services: baseline both servicing and agent-desk volumes, then pilot the policy-servicing line first.
Entry: Policy servicing desk (premium, loan, surrender and beneficiary inquiries) · Scale package · 10–14 weeks to production across priority workflows. Human fallback throughout; success thresholds agreed before build.
Start the pursuitResearch-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.