IndiaPrivate bank — universalTransform · $200K
ICICI Bank

iMobile-grade experience on the phone line: every ICICI service call resolved with the context the app already has

Extend ICICI Bank's acknowledged digital leadership from the app to voice and WhatsApp, so the millions of customers who still call get the same instant, contextual resolution iMobile users get.

Entry use case
Retail inbound service line (accounts, cards, loans)
Expected outcome
Raise first-contact resolution on the retail line; cut repeat-contact volume driven by ticket-deferred answers.
Recommended next step
Propose a two-week discovery with the phone-banking head to quantify repeat-contact rate on the top 10 retail intents and size an FCR pilot.
What we understand

ICICI Bank's operating reality

Second-largest private bank in India with an publicly stated 'One Bank, One Team' customer-centric operating philosophy and sector-leading profitability.

Public fact

iMobile Pay was opened to customers of any bank — a widely reported digital land-grab strategy that expanded its serviceable base beyond its own accounts.

Public fact

Widely reported early and broad adoption of AI/ML in underwriting and service within Indian banking.

Public fact

A bank this digitally mature likely sees residual call volume concentrated in exceptions — disputes, trace requests, deceased-claim and locker workflows — where context handoff from app to human is weakest.

Reasoned inference

Service consistency between branch, phone, and app answers is likely a measured internal KPI, making a 100%-scored conversation layer attractive.

Seller hypothesis — validate

Validate with the account team before outreach: Actual repeat-contact and FCR baselines on the retail line · Incumbent conversational-AI vendors and internal build appetite · Data-residency and outsourcing-policy constraints for voice AI

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: iMobile, the iPal assistant, and widely reported early AI/ML adoption reflect one of Indian banking's strongest internal technology franchises — but the bank's pattern is to partner for specialized platforms while owning architecture and orchestration.

Why they won't build the full stack: Even for ICICI's engineering depth, building speech, telephony, multilingual voice, and conversation-evaluation infrastructure is off-thesis; the opening is a governed conversational layer grounded on the same APIs iMobile already calls.

What management is signalling

Management consistently frames the story around risk-calibrated growth and operating-leverage discipline, with cost-to-income a watched metric

Reported factrecent earnings calls · late 2025

GTM implication: A cost-to-serve pilot with measured FCR economics fits the operating-leverage narrative management already tells the street

What already exists (don't pitch this)
  • iPal chatbot on web and app
  • iMobile Pay opened to any bank's customers
  • WhatsApp banking
  • Established IVR and phone-banking estate
What customers still can't do end-to-end (pitch this)
  • →Chatbot handles FAQs better than regulated transactions
  • →Voice line lacks the context the app already has
  • →Repeat contacts driven by ticket-deferred resolution
  • →Vernacular voice coverage thin versus the branch-language footprint
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Retail service line with in-conversation actions
Grounded resolution of statements, disputes-status, limit and nomination changes in one conversation; warm human handoff for complaints.
Residual call volume at a digital-first bank is exception-heavy; deferring these to tickets drives the repeat contacts ICICI's NPS program tracks.
Friction today: Callers who failed in the app re-authenticate and re-explain; agents raise service requests instead of resolving live.
VoiceWhatsAppApp chat
Personal-loan and card cross-sell follow-through
Minutes-fast, consent-governed follow-up on pre-approved offers with structured qualification and bookable RM slots.
Pre-approved offers surface in iMobile but conversion depends on timely human follow-up that telecalling capacity limits.
Friction today: Offer leads decay in dialer queues; pitch quality varies; DND and consent handling are manual.
WhatsAppVoice
NRI service desk across time zones
24/7 grounded NRI servicing with specialist escalation windows matched to the customer's time zone.
ICICI has one of India's largest NRI franchises; time-zone coverage makes human-only service structurally expensive.
Friction today: NRI callers hit India business-hours queues; remittance and FATCA/KYC questions need specialist callbacks.
VoiceWhatsAppEmail
Watch the change

Retail inbound service line (accounts, cards, loans): today vs the agentic model

Scenario: An iMobile user whose UPI dispute stalled in-app calls the ICICI care line and expects the agent to already know
Today
same interaction, two worlds
Agentic layer
First-contact resolution
deferred via tickets
in-conversation actions
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
  • · First-contact resolution: Process design: agent acts in systems of record
  • · 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
VoiceWhatsAppApp chatEmail

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 · ICICI Bank
Core bankingCard systemService-request workflowOffer engineCRMLoan originationRemittance platformKYC workflow

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

Trust & languages
HindiEnglishMarathiGujaratiTamilTeluguKannadaBengali

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 interactions6.0M
Seller assumption — replace in discovery
Current cost per interaction ($)$1.4
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$8.4M
Current operating cost / mo
$41.6M
Modelled gross benefit / yr
0.1 mo
Payback on Transform
298%
3-yr ROI (modelled)
Automated/assisted interactions per month3.3M
Modelled AI run-cost per month (usage + cloud, system estimate)$1.2M
New monthly operating cost$4.9M

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 ICICI Bank's measured baseline. Package price covers implementation only; recurring usage billed separately.

Recommended package

Transform — $200K implementation

Transform · $200K · A broader enterprise deployment14–20 weeks phased across units

Why this package for ICICI Bank: Scale and integration depth match the transform scope: multiple retail products, mature APIs, and an organization capable of absorbing a multi-workflow deployment quickly.

Included
  • 7–10 channels
  • Multiple inbound + outbound workflows
  • Complex enterprise integrations
  • Multiple business units or geographies
  • Advanced agent orchestration
  • Enterprise grounding
  • Governance & evaluation framework
  • Role-based human supervision
  • Custom analytics & optimization
  • Production hardening + managed rollout plan
Not included
  • ✕Usage & consumption (billed separately)
  • ✕Ongoing managed operations (contracted separately)
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: Core banking, Card system, Service-request workflow
  • · A named business owner for retail inbound service line (accounts, cards, loans)
  • · Security review counterpart and policy sign-off (Core banking scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“Return of capital discipline made ICICI the profitability benchmark; an agentic service layer applies the same discipline to the cost-to-serve line while protecting the NPS gains.”

CIO / CTO

“Your API maturity is the asset here — the agent grounds on the same services iMobile calls, so voice finally inherits the context the app already has.”

COO

“Repeat contacts from ticket-deferred answers are your hidden volume; in-conversation actions collapse three calls into one and are measurable within a quarter.”

Head of Customer Service & Phone Banking

“Every call scored, every answer grounded on the system of record — the consistency you currently sample for at 1–2% becomes the default at 100%.”

Chief Risk / Compliance Officer

“Policy-bounded scripts, full transcripts, and DND-aware outreach give you evidentiary-grade conduct records across every retail conversation.”

CFO / Procurement

“Usage-priced automation against a six-million-contact month gives a business case you can validate in a single-circle pilot before any enterprise commitment.”

Outreach

Pre-built offer emails for ICICI Bank

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

India's second-largest private bank, publicly regarded as a digital and profitability leader — high volume, high sophistication, and a management team that measures service economics closely.

30 / 60 / 90-day plan
  • Day 0–30: Propose a two-week discovery with the phone-banking head to quantify repeat-contact rate on the top 10 retail intents and size an FCR pilot.; confirm sponsor and baseline data access; validate: Actual repeat-contact and FCR baselines on the retail line
  • Day 31–60: architecture & security review with the platform team; Tilicho Labs scoping on Voice + WhatsApp; pilot scope signed
  • Day 61–90: Transform package kickoff; retail inbound service line (accounts, cards, loans) pilot in build; success thresholds locked with the Head of Customer Service & Phone Banking
Recommended next step

Propose a two-week discovery with the phone-banking head to quantify repeat-contact rate on the top 10 retail intents and size an FCR pilot.

Entry: Retail inbound service line (accounts, cards, loans) · Transform package · 14–20 weeks phased across units. 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.