For an operator whose survival math depends on slowing churn while cutting cost, an agentic retention and service layer is one of the few investments that attacks both sides of the equation simultaneously.
The government converted dues into equity and holds roughly 49% of Vodafone Idea; a 2025-26 relief package froze large AGR dues with payments capped at low annual amounts from March 2026.
Public factVi has lost subscribers continuously to Jio and Airtel for years; after its 2025 fundraise it expanded 4G coverage, added ~17,000 towers, and launched 5G in 17 circles, slowing but not stopping losses.
Public factVi's strongest circles remain Maharashtra, Gujarat, Kerala, and Mumbai — retention economics concentrate in a handful of geographies and languages.
Public factWith capex committed to network catch-up, opex lines like contact-center spend face permanent pressure — automation is a survival lever, not an innovation project.
Reasoned inferencePort-out requests generate a UPC-code signal window during which a conversational save attempt is possible; Vi's outbound capacity likely covers only a fraction of these windows today.
Seller hypothesis — validateValidate with the account team before outreach: Current save-desk coverage rate of port-out signal windows · Procurement reality: appetite and budget cycle under the cost-transformation program · Existing cloud/AI vendor commitments (Vi has historically worked with multiple network vendors)
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: Survival economics leave no room for an internal AI build: engineering bandwidth is consumed by 4G/5G network catch-up, opex must shrink structurally, and Vi has no AI platform organization of scale. Every technology decision is a procurement decision under capital discipline.
Why they won't build the full stack: Building would require hiring an AI team while cutting costs everywhere else — strategically incoherent for a company whose investor story is cost transformation. A usage-priced bought solution that scales down as well as up matches Vi's capital reality exactly.
Cash-flow and AGR stress dominate the investor narrative: government dues converted to ~49% equity, relief packages capping near-term payments, and continued subscriber losses.
GTM implication: Frame the deal as one of the few line items that cuts opex and defends revenue simultaneously — cost-per-saved-subscriber against blended ARPU.
Management flags cost optimization as a survival priority alongside committed network capex.
GTM implication: Keep entry scope small and usage-priced; procurement will reject anything resembling a platform program.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Port-out prevention & retention 100% of save windows attempted conversationally; save rate measured and attributed. | Every retained subscriber directly extends Vi's survival runway; churn is the existential metric. Friction today: Outbound save-desk capacity reaches a fraction of port-out signals within the decision window. | VoiceWhatsAppSMS | |||
Recharge & plan service deflection In-channel recharge and plan resolution at self-service economics. | Every deflected human contact is direct opex removed from a P&L that must shrink. Friction today: Limited-language IVR; contact-center spend competes with network capex. | VoiceWhatsApp | |||
5G/4G upgrade migration outreach DND-compliant conversational migration with device/coverage checks in-flow. | The new network only pays back if subscribers move onto it before deciding to port. Friction today: Campaign SMS ignored; no conversational channel to handle 'is 5G available for me' questions. | 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 Vodafone Idea's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Vodafone Idea: Vi needs multi-workflow impact (retention + service deflection) fast, but capital discipline rules out a Transform-scale program; Scale hits retention and cost lines in one deployment.
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.
“Vi's equity story is 'losses slowing, network catching up'. A measurable churn-reduction engine is one of the cheapest proof points you can put in front of investors and the government board seats.”
“No rip-and-replace: the agent layer sits on existing BSS/CRM APIs, starts in your four strongest circles, and its usage-based cost scales down as well as up — matching Vi's capital reality.”
“You cannot staff your way to covering every port-out window. An agent attempts 100% of them within hours, and hands hardship or high-value cases to your save specialists with full context.”
“Vi's service perception drives churn as much as network does. Consistent, instant, vernacular answers are achievable now, without growing headcount you cannot afford.”
“With ~49% government ownership, auditability matters doubly: every retention offer comes from an approved matrix, every conversation is logged, TRAI DND and DPDP compliance are enforced by policy.”
“This is one of the few line items that cuts opex and defends revenue at once. Model it as cost-per-saved-subscriber against your blended ARPU and current save-desk cost.”
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.
Third operator (~190M subscribers) in existential cost-cutting mode: AGR relief and government ~49% ownership bought time, but survival now depends on stemming subscriber losses at minimum cost — extreme fit for automation economics, constrained budgets.
Propose a 90-day retention pilot in two strong circles (Maharashtra, Gujarat) with a save-rate baseline and an offer matrix signed off by Vi's revenue team.
Entry: Port-out prevention & at-risk subscriber retention · 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.