Hong KongLife & health insuranceScale · $100K
AIA Group

The agency giant's second frontline — agentic policy servicing and claims care for AIA's Hong Kong engine

AIA's Hong Kong business writes enormous volumes for both local customers and Mainland Chinese Visitors, all serviced through a premier agency force built for selling and advising — not for the structural tide of policy servicing, claims status and renewal questions that follows every sale; an agentic frontline in native Cantonese and Mandarin handles that tide around the clock, keeps MCV customers served across the boundary, and hands agents back their selling hours.

Entry use case
Policy servicing and claims-status desk
Expected outcome
Resolve routine servicing and claims-status contacts in-conversation in the policyholder's language, cutting agent-inbox load and claims status calls.
Recommended next step
Workshop with AIA Hong Kong operations and distribution leadership: baseline servicing contact volume including agent-handled servicing, then scope a Scale pilot on the servicing and claims-status desk.
What we understand

AIA Group's operating reality

AIA Group is one of the world's largest life insurers, headquartered and listed in Hong Kong, operating across 18 Asian markets with its signature Premier Agency distribution model.

Public fact

AIA Hong Kong's new business has been substantially boosted by Mainland Chinese Visitor demand since the border reopening, making cross-boundary customers a structural part of the book.

Public fact

AIA runs a group-wide Technology, Digital and Analytics transformation program and has publicly invested in digital and analytics capability.

Public fact

MCV policyholders service their Hong Kong policies remotely — status checks, premium payments and claims from the mainland — making Mandarin-native remote service a retention issue, not a nicety.

Reasoned inference

Agents field a large share of servicing questions informally; every hour an agent spends on servicing is an hour not spent selling — the agency economics quietly subsidize the service model.

Reasoned inference

Medical-claims volume and status inquiries likely grow faster than premiums as the health book expands and medical inflation drives utilization.

Seller hypothesis — validate

Validate with the account team before outreach: How much servicing volume flows through agents versus hotlines today · Group TDA program scope and any incumbent conversational-AI deployments · PDPO and cross-boundary data constraints for MCV customer conversations · Which market (HK first vs regional) the group would pilot in

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: AIA has genuine group technology capability and a funded TDA transformation, but its build focus is analytics, digital journeys and agency tools; trilingual conversational AI with claims-grade governance is adjacent specialist ground where AIA needs a partner for voice quality, orchestration and delivery at contact-center scale.

Why they won't build the full stack: AIA's engineering priority is the agency platform and digital journeys across 18 markets, not LLM voice infrastructure; a governed platform with human gates delivers measurable servicing economics in one market this year and a regional expansion path the TDA program can own.

What management is signalling

AIA has reported strong new-business growth with Hong Kong a standout segment, substantially driven by Mainland Chinese Visitor demand since the border reopening.

Reported factrecent annual and interim results · 2025

GTM implication: The MCV book creates a structurally Mandarin, remote-service customer base — sell cross-boundary servicing capacity as protection for the growth segment management highlights every half.

Sustained buybacks and capital-return programs keep operating efficiency and margin quality under investor focus alongside growth.

Inferencerecent investor communications (validate) · 2025-2026

GTM implication: Frame servicing automation as operating leverage on the in-force book — cost-to-serve falling while the book compounds.

What already exists (don't pitch this)
  • AIA+ / AIA Connect apps with policy self-service
  • Premier Agency force as the primary service channel
  • Claims e-submission for simple cases
  • Group TDA digital and analytics transformation program
What customers still can't do end-to-end (pitch this)
  • →Transactional servicing depth — changes and payments still route to agents or hotlines
  • →Proactive claims-status communication that suppresses repeat contacts
  • →Native Mandarin remote servicing matched to the MCV book
  • →Cross-channel context between agents, hotline and app
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Policy servicing and claims-status desk
Routine servicing resolved in-conversation with proactive claims status; agents freed for advice and sales.
Premium, beneficiary, policy-value and claims-status questions are the structural volume of a huge in-force book — routine, high-stakes and trilingual.
Friction today: Policyholders route questions to their agent or queue on hotlines; claims status generates repeat calls for weeks.
VoiceApp chatWhatsApp
Medical claims intake and document care
Structured intake with documents validated in-flow, proactive status at every stage, human adjusters on every assessment.
Health-claims moments define trust for the fastest-growing product line.
Friction today: Document chases and format rejections stretch cycle times; claimants call agents for updates.
App chatWhatsAppVoice
Premium-due and lapse-prevention outreach
Every premium-due policyholder gets a conversation in their language with payment completed in-channel; lapse rates measured.
Lapses on an in-force book this size are silent revenue leakage; MCV customers are hardest to reach by mail.
Friction today: Reminder letters and SMS go unanswered; agent follow-up is uneven across the force.
WhatsAppVoiceSMS
Watch the change

Policy servicing and claims-status desk: today vs the agentic model

Scenario: A Shenzhen-based policyholder messages about her hospitalization claim at 9pm; the agent, in Mandarin, verifies identity, confirms the outstanding document, validates her re-upload in-flow, explains the assessment timeline and pushes proactive status at every stage — she never has to call her selling agent once.
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 chatWhatsAppSMS

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 · AIA Group
Policy administrationClaims platformCRMDocument managementPayments

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

Trust & languages
CantoneseEnglishMandarin

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 interactions900K
Seller assumption — replace in discovery
Current cost per interaction ($)$6.0
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$5.4M
Current operating cost / mo
$33.6M
Modelled gross benefit / yr
0.0 mo
Payback on Scale
1587%
3-yr ROI (modelled)
Automated/assisted interactions per month495K
Modelled AI run-cost per month (usage + cloud, system estimate)$173K
New monthly operating cost$2.6M

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 AIA Group'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 AIA Group: Policy servicing plus claims-status care plus renewal outreach are natural multi-workflow Scale scope for a major insurer, with policy-admin and claims integration depth Scale is built for.

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: Policy administration, Claims platform, CRM
  • · A named business owner for policy servicing and claims-status desk
  • · Security review counterpart and policy sign-off (Policy administration scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“AIA's compounding machine is agency productivity; an agentic servicing frontline gives every agent back their selling hours while giving MCV customers the cross-boundary service the growth story depends on.”

CIO / CTO

“This extends the TDA program to the conversation layer — a governed agent over policy-admin and claims APIs, with the evaluation and audit framework a listed insurer needs, not another chatbot bolted to the hotline.”

COO

“Servicing and claims volume scales with the in-force book mechanically; elastic trilingual capacity is the only service model that tracks that curve without linear hiring.”

Chief Customer / Distribution Officer

“Your agents are doing unpaid servicing work between sales; moving the routine tide to an agent frontline is the productivity lever hiding inside your own channel.”

Chief Risk / Compliance Officer

“Human gates on every claims assessment and advice moment, PDPO-aligned processing across boundary contexts, and 100% conversation logging — audit evidence sampled QA never gave you.”

CFO / Procurement

“Cost per servicing contact and claims cycle time are measurable in one quarter; the pilot prices against your own baseline with usage billed on consumption.”

Outreach

Pre-built offer emails for AIA Group

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

The pan-Asian life insurer headquartered in Hong Kong — a massive agency force, a Hong Kong business supercharged by mainland-visitor demand, and claims-and-servicing volume across the region that no agency channel can absorb alone.

30 / 60 / 90-day plan
  • Day 0–30: Workshop with AIA Hong Kong operations and distribution leadership: baseline servicing contact volume including agent-handled servicing, then scope a Scale pilot on the servicing and claims-status desk.; confirm sponsor and baseline data access; validate: How much servicing volume flows through agents versus hotlines today
  • 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; policy servicing and claims-status desk pilot in build; success thresholds locked with the Chief Customer / Distribution Officer
Recommended next step

Workshop with AIA Hong Kong operations and distribution leadership: baseline servicing contact volume including agent-handled servicing, then scope a Scale pilot on the servicing and claims-status desk.

Entry: Policy servicing and claims-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.