Wrap LIC's policy-servicing and renewal machinery in a conversational layer: two-way vernacular renewal reminders, grounded servicing answers, and an agent-support desk — moving persistency and cost-to-serve at the largest scale in world life insurance.
The largest life insurer in India and among the largest globally by policies in force, with a million-plus tied-agent force and a nationwide branch and satellite-office network.
Public factListed in 2022; persistency ratios (13th/61st month) are reported quarterly and compared unfavorably with private insurers by analysts, and management has publicly discussed revival campaigns and ticket-size changes in response.
Public factHas publicly launched the DIVE (Digital Innovation and Value Enhancement) transformation program, and the ANANDA agent-assisted digital app processes millions of policy completions — digital works at LIC when it supports the agency force rather than bypassing it.
Public factRenewal reminders today are largely one-way SMS and mail; a meaningful share of lapses on lower-ticket policies are likely recoverable with timely, two-way vernacular conversations.
Reasoned inferencePolicy servicing (address and NEFT changes, loans against policy, maturity and survival-benefit status) likely drives enormous branch footfall and call volume answerable verbatim from the policy system.
Reasoned inferenceAgent-support queries — proposal status, commission, product rules — likely consume significant back-office and branch capacity that a grounded agent desk could absorb.
Seller hypothesis — validateValidate with the account team before outreach: Procurement route: tender, empanelment, or DIVE-program vendor onboarding · Policy-admin API readiness on the legacy estate for real-time dues and revival computation · Which office owns persistency improvement and renewal outreach today
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: Technology at LIC is delivered through large SI and vendor programs — DIVE itself is consultant- and vendor-executed — and there is no internal conversational-AI engineering capability; procurement is tender-led with a strong preference for accountable vendors.
Why they won't build the full stack: A state-linked insurer running a legacy policy-admin estate will not build speech models, telephony orchestration, or evaluation tooling; the entire conversational stack must arrive packaged, integrated, and auditable.
Persistency ratios trail private-sector peers and management has publicly acknowledged the gap, citing revival campaigns and product ticket-size changes
GTM implication: A renewal-reminder and revival pilot attacks the most publicly scrutinized metric LIC reports each quarter
The DIVE digital transformation program has been publicly launched to modernize customer, agent, and partner journeys
GTM implication: Budget and mandate for digital modernization exist — position the conversational layer inside the DIVE agenda, not as a standalone bet
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Renewal-premium reminders & lapse revival Every due policy gets a two-way, language-matched conversation with in-channel payment; lapsed policies get structured revival dialogues with dues computed. | Persistency is the most publicly scrutinized metric LIC reports; every saved renewal on a policy base this size compounds embedded value at national scale. Friction today: Reminders are one-way SMS/mail blasts; revival campaigns are periodic and generic; agent follow-up covers only active agency relationships. | VoiceWhatsAppSMS | |||
Policy-servicing line & branch deflection Grounded self-service for the top servicing intents in the policyholder's language; branch visits reserved for genuine exceptions. | Servicing requests that end in branch queues today are the single largest addressable service-cost pool in Indian insurance. Friction today: Address, nomination, NEFT, loan-against-policy, and maturity-status requests route to branches and overloaded lines; answers exist verbatim in the policy system. | VoiceWhatsAppApp chat | |||
Agent-support desk A grounded, always-on agent desk for proposal status, product rules, and commission queries — consistent answers, escalations documented. | A million-plus agents are LIC's distribution moat; every hour they spend chasing proposal status or product rules is selling time lost. Friction today: Agent queries queue through branch staff and helplines; answers vary by branch and experience. | WhatsAppVoiceApp 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 LIC of India's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for LIC of India: Tender-led PSU procurement favors a bounded, provable scope — renewal reminders, servicing deflection, and agent support on policy-admin integrations — with the enterprise-wide expansion case documented for the next procurement cycle.
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.
“Persistency is the number the street compares with private insurers every quarter; a conversational renewal layer moves it at a scale no calling operation can — while visibly modernizing policyholder service.”
“This rides the DIVE modernization agenda: one policy-admin integration powers renewal, servicing, and agent-desk workflows with complete logging — no rip-and-replace of the legacy estate.”
“Branch counters absorb servicing volume that a grounded conversational line can answer verbatim; deflection frees branch capacity without a single process redesign.”
“Every due policy gets a two-way reminder in the policyholder's own language — coverage your SMS blasts and agency follow-up structurally cannot reach.”
“IRDAI-compliant scripts, consent-governed outreach, and complete transcripts make policyholder communication evidencable — a stronger conduct posture than today's untracked branch phone calls.”
“Priced against the embedded-value impact of even fractional persistency improvement on the largest policy base in the world, a bounded scale deployment is among the cheapest value levers available.”
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.
India's largest life insurer by an order of magnitude — hundreds of millions of in-force policies, a million-plus tied-agent force, and renewal-premium, policy-servicing, and agent-support volumes without peer; legacy systems and tender-led procurement set the pace.
Propose a persistency pilot in one zone: two-way vernacular renewal reminders on a defined policy cohort for 90 days, persistency and revival lift measured against SMS-only control.
Entry: Renewal-premium reminders & lapse revival · 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.