Give Manipal a single agentic patient-access layer across its rapidly acquired network — one conversational front door for appointments, insurance guidance, and follow-ups that standardizes patient experience faster than system integrations ever could.
Among India's largest hospital networks — 37+ hospitals and 10,500+ beds after acquiring AMRI Hospitals (2023) and Medica Synergie, with Temasek holding a majority stake.
Public factGrowth has been acquisition-led, meaning multiple HIS, scheduling, and telephony estates coexist across the network — patient experience varies by legacy system.
Reasoned inferenceStrong southern and eastern footprints (Bengaluru heartland; Kolkata via AMRI/Medica) put Kannada and Bengali alongside Hindi and English as core service languages.
Public factAppointment access and insurance-desk guidance likely dominate non-clinical contact volume, with sharp variance between flagship and acquired units.
Reasoned inferenceA Temasek-backed board pursuing scale likely values a standardization layer that improves experience metrics without waiting on multi-year HIS consolidation.
Seller hypothesis — validateValidate with the account team before outreach: HIS landscape per unit and realistic grounding depth at acquired hospitals · Where network-standardization budget sits (integration program vs operations) · Language mix of actual call volume in eastern units
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: An acquisition-led operator whose management bandwidth is consumed by clinical and system integration; technology is bought, and a packaged conversational layer is precisely the kind of standardization purchase the board model favors.
Why they won't build the full stack: Building conversational AI while integrating three hospital systems is implausible; the value is a bought layer that works across heterogeneous HIS estates from day one.
Network scale roughly doubled through the AMRI and Medica acquisitions, with integration and occupancy ramp the stated operational focus
GTM implication: A conversational standardization layer is the fastest visible integration win — one experience across the enlarged network
Continued expansion appetite and possible capital-market event speculation in press coverage
GTM implication: Standardized, measurable experience metrics across units strengthen any equity story — a board-level framing for the platform
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
One conversational front door for appointments Uniform any-hour booking in five languages across all units, with reminders and one-tap reschedule; no-show and abandonment metrics standardized network-wide. | Acquired hospitals each answer the phone differently; a single conversational layer delivers brand-consistent access instantly. Friction today: Booking experiences differ by legacy system; peak-hour queues; no-shows unmanaged in acquired units. | VoiceWhatsAppWeb chat | |||
Insurance & cashless-admission guidance Standardized guided insurance conversations with proactive pre-auth status across every unit, in the patient's language. | Payor confusion at admission is the highest-anxiety, highest-variance experience across the network. Friction today: Empanelment, TPA, and document answers vary by unit; pre-auth status is opaque; desks queue. | WhatsAppVoice | |||
Post-discharge follow-up & care-plan adherence Automated vernacular follow-up conversations with medication and appointment adherence nudges; clinical flags routed to nurses. | Readmission prevention and follow-up compliance drive outcomes and reputation — and are chronically under-resourced phone work. Friction today: Follow-up calls happen when staff have time; instructions are re-explained; adherence is unmeasured. | WhatsAppVoice |
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 Manipal Hospitals's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Manipal Hospitals: A network of 37+ hospitals across multiple HIS estates, several languages, and three-plus workflows is genuinely transform-scope — phased by cluster, it also becomes the experience-standardization program for the acquisitions.
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.
“The acquisition thesis needs one Manipal experience; a conversational front door delivers that standardization in months, not the years HIS consolidation will take.”
“The agent grounds on each legacy HIS as-is — experience unifies at the conversation layer while system integration proceeds underneath at its own pace.”
“No-show, abandonment, and desk-load metrics become comparable across all 37+ units for the first time — operational variance made visible and fixable.”
“Every patient gets the flagship experience regardless of which unit answers — in Bengali in Kolkata, Kannada in Bengaluru, at any hour.”
“DPDP-conformant consent, full logging, and enforced clinical-escalation boundaries — one governed standard replacing per-unit telephone practice.”
“Utilization lift and standardized access economics across an acquired estate — the integration dividend, bought as a platform instead of built over years.”
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 or second-largest hospital network (37+ hospitals after the AMRI and Medica acquisitions, Temasek-backed) integrating multiple acquired systems — appointment, insurance, and multi-city coordination volume at national scale with an explicit integration mandate.
Two-cluster pilot: one Bengaluru flagship plus one acquired Kolkata unit on the same conversational booking layer, measured on no-shows, abandonment, and experience-score convergence.
Entry: Network-wide appointment booking & reminders · Transform package · 14–20 weeks phased across units. 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.