IndiaHealth insurance — retailScale · $100K
Star Health Insurance

Every Star Health claim narrated from pre-auth to settlement — and every policyholder call answered without a hospital-corridor wait

Deploy an agentic claims-communication and service layer for Star Health: proactive cashless pre-auth updates, document chasing, and renewal conversations — rebuilding policyholder trust interaction by logged interaction.

Entry use case
Cashless pre-auth & claim-status communication
Expected outcome
Suppressed claim-status call volume and faster document completion; measurable TAT improvement on retail claims.
Recommended next step
Pilot proactive cashless-claim narration in two southern states for 90 days, measuring status-call suppression and pre-auth TAT with the claims team.
What we understand

Star Health Insurance's operating reality

India's largest standalone retail health insurer, distributing predominantly through an agency force of over half a million agents.

Public fact

Suffered a widely reported customer-data breach in 2024, making data-handling credibility a live board topic.

Public fact

IRDAI's cashless-everywhere push and TAT norms raise the communication load per claim — pre-auth status, deficiency notices, and settlement updates.

Public fact

Claim-status inquiries from anxious families at hospital counters likely dominate call volume, with agents also calling on their customers' behalf — double traffic per claim.

Reasoned inference

Renewal persistency on retail health likely hinges on premium-hike explanation conversations that blast SMS cannot deliver.

Seller hypothesis — validate

Validate with the account team before outreach: Share of call volume that is claim-status inquiry (policyholder vs agent) · Claims-platform API readiness and TPA interface constraints · Post-breach security-review requirements for new vendors

Build vs buy

Why we have a right to win here

Buy-led target

Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution

Evidence: An agency-led distribution franchise whose technology estate (customer app, claims platform) is vendor-built; after the 2024 breach, the internal bar is vendor accountability and security review, not in-house AI construction.

Why they won't build the full stack: Claims-communication automation needs speech, document-flow, and evaluation infrastructure no retail health insurer builds internally; a DPDP-conscious packaged platform with clean audit trails is the sellable shape.

What management is signalling

Loss-ratio and expense pressure in retail health has featured in recent results discussions

Inferencerecent investor communications (validate) · late 2025

GTM implication: Claims-line deflection plus renewal-persistency lift attacks both sides of the combined ratio in one deployment

What already exists (don't pitch this)
  • Star Health customer app with claim tracking
  • Agent-facing digital tools for a 600K+ agent force
  • Hospital/TPA network interfaces
  • SMS/email claim and renewal notifications
What customers still can't do end-to-end (pitch this)
  • →Claim-status narration is reactive — families and agents both call
  • →Deficiency handling remains letter-grade
  • →Premium-hike explanations do not scale beyond active agents
  • →No vernacular voice line
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Cashless pre-auth & claim-status narration
Every pre-auth and claim stage pushed proactively to policyholder and agent; status calls collapse.
The hospital-admission moment is the product's truth test; silence during pre-auth is where trust and renewals are lost.
Friction today: Families and their agents both call for status; pre-auth and deficiency updates travel by letter-grade processes.
WhatsAppVoiceSMS
Claim-document chase & deficiency resolution
Checklist-tracked, in-chat document guidance with validation; deficiency cycle time measurably cut.
Deficiency cycles stretch TATs that IRDAI norms and NPS both punish.
Friction today: Deficiency letters confuse claimants; re-submissions bounce on format; each cycle adds days.
WhatsAppVoice
Renewal & premium-explanation conversations
Two-way renewal conversations that explain premium changes and options, with in-channel payment and agent escalation.
Retail health renewals fund the franchise; age-band and medical-inflation premium hikes need explanation, not just notification.
Friction today: Renewal notices with higher premiums go unexplained; agents cover only their active books.
VoiceWhatsApp
Watch the change

Cashless pre-auth & claim-status communication: today vs the agentic model

Scenario: A policyholder's son at a Chennai hospital counter waits on cashless pre-auth for his father's surgery while the family calls three numbers for status
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
WhatsAppVoiceSMS

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 · Star Health Insurance
Health claims platformHospital/TPA interfacesPolicy adminClaims platformDocument managementPayment gatewayAgent CRM

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

Trust & languages
HindiEnglishTamilTeluguMalayalamKannadaMarathiBengali

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 ($)$1.6
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$1.1M
Current operating cost / mo
$5.8M
Modelled gross benefit / yr
0.2 mo
Payback on Scale
348%
3-yr ROI (modelled)
Automated/assisted interactions per month385K
Modelled AI run-cost per month (usage + cloud, system estimate)$135K
New monthly operating cost$639K

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 Star Health Insurance'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 Star Health Insurance: Claims communication, renewal retention, and agent-force support are two-three workflows over claims and policy-admin systems — scale scope with clear regulatory-reporting side benefits.

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: Health claims platform, Hospital/TPA interfaces, Policy admin
  • · A named business owner for cashless pre-auth & claim-status communication
  • · Security review counterpart and policy sign-off (Health claims platform scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“Retail health is bought on trust and renewed on claims experience; narrating every claim proactively is the most visible trust investment available this year.”

CIO / CTO

“Post-breach, every customer-data touchpoint must be defensible; this layer is DPDP-conscious by design — consented channels, minimal disclosure, complete logs.”

COO

“Status calls from both policyholders and agents are double traffic per claim; proactive push removes the cause across your entire claims line.”

Head of Claims

“Pre-auth updates, deficiency guidance, and settlement notices delivered automatically in eight languages — TAT improvement your IRDAI reporting will show.”

Chief Risk / Compliance Officer

“Consistent, logged, policy-wording-aligned claim communication reduces ombudsman exposure and evidences the conduct IRDAI's norms expect.”

CFO / Procurement

“Claims-line deflection plus renewal-persistency lift attack expense and growth in one deployment; the pilot isolates each effect for the business case.”

Outreach

Pre-built offer emails for Star Health Insurance

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 2 — high-potential incubation

Why this tier

India's largest retail health insurer with a 600K+ agent force and claims servicing as its daily brand test; post its 2024 data-breach episode, trust-rebuilding via visibly better, safer customer communication is strategically urgent.

Recommended next step

Pilot proactive cashless-claim narration in two southern states for 90 days, measuring status-call suppression and pre-auth TAT with the claims team.

Entry: Cashless pre-auth & claim-status communication · 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.