IndiaNBFC — commercial vehicle & retail lendingScale · $100K
Shriram Finance

Reach every truck-owner before the EMI slips — in Tamil, Telugu, or Hindi, timed to freight cycles, before a field visit is ever needed

Give Shriram's field-led collections model a digital first line that handles routine EMI reminders and PTP follow-ups conversationally, so costly field officers focus only on accounts a conversation cannot fix.

Entry use case
CV EMI reminders & PTP follow-up
Expected outcome
Fewer field visits per resolved account and improved early-bucket roll rates on the CV book.
Recommended next step
Pilot in two Tamil Nadu and Andhra territories: agent-first contact on buckets 0–1 for 60 days, field-visit-per-resolution delta reported.
What we understand

Shriram Finance's operating reality

India's largest commercial-vehicle financier, formed by the 2022 merger of Shriram Transport Finance and Shriram City Union Finance into Shriram Finance.

Public fact

Core franchise is used-CV and small-fleet finance to driver-owners in semi-urban and rural India, historically underwritten and collected through a relationship-based field force.

Public fact

Customer cash flows track freight cycles and are often cash-based; EMI timing conversations are as important as reminders themselves.

Reasoned inference

Field-visit collections cost per account is likely multiples of a phone resolution; routing only conversation-resistant accounts to the field is a large efficiency lever.

Reasoned inference

Voice in regional languages likely outperforms text for this base, where literacy and smartphone sophistication vary widely.

Reasoned inference

Validate with the account team before outreach: Actual split of phone vs field collection today and cost per field visit · LMS/field-app API maturity for real-time PTP write-back · Reachability data: when do CV borrowers actually answer calls

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: A relationship- and field-force-led lender whose merger integration and Shriram One app were delivered with vendor support; there is no publicly visible in-house AI platform team or build-first posture.

Why they won't build the full stack: Shriram's edge is field knowledge of its borrowers, not software; a packaged vernacular-voice platform integrated to the LMS and field app is the only realistic route to conversational coverage at its scale.

What management is signalling

Collection efficiency and rural cash-flow timing recur as operational themes in results discussions

Inferencerecent investor communications (validate) · late 2025

GTM implication: A collections-first pilot framed on field-visit substitution matches the operational lever management already narrates

What already exists (don't pitch this)
  • Shriram One super-app for payments and servicing
  • Central dialer-led collections plus a large field force
  • SMS dunning with payment links
  • Branch network as the service fallback
What customers still can't do end-to-end (pitch this)
  • →No vernacular voice automation tuned to freight-cycle timing
  • →PTPs live in field-app notes and are not auto-followed
  • →Dialers reach few working drivers in daytime windows
  • →Insurance-renewal cross-sell unworked at scale
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
EMI reminders timed to freight cycles
Policy-timed voice reminders in the borrower's language with in-channel payment or PTP capture; field queue shrinks to genuine cases.
Driver-owners' ability to pay follows trip settlements; a reminder timed and toned to that reality collects better than a fixed dialer cadence.
Friction today: Central dialers reach few working drivers during the day; field officers burn visits on accounts that just needed a nudge.
VoiceWhatsAppSMS
PTP follow-through & field-visit triage
Every PTP followed up automatically on its date; the field app receives a ranked queue of only unresolved accounts with transcripts.
Broken promises currently surface only when the next cycle runs; automatic follow-up protects field-force time.
Friction today: PTPs live in field-app notes; follow-up depends on officer load; no ranked field queue exists.
VoiceWhatsApp
Insurance & renewal cross-sell to the borrower base
Automated renewal-date conversations with compliant handoff to licensed staff for closure.
The captive borrower relationship supports vehicle-insurance renewal and deposit cross-sell that field officers rarely have time to work.
Friction today: Renewal dates pass unworked; cross-sell depends on branch initiative.
VoiceWhatsApp
Watch the change

CV EMI reminders & PTP follow-up: today vs the agentic model

Scenario: A used-truck owner on the Salem–Vijayawada route is 9 days past due, waiting on a freight settlement, and unreachable during driving hours
Today
same interaction, two worlds
Agentic layer
Day-1 contact coverage
capacity-limited
100% attempted, multi-channel
Platform capability
Roll-rate improvement
—
measured in pilot
Benchmark
Cost per contact
$13.50 median assisted
$1.84 median self-service
Benchmark
QA coverage
1–2% sampled
100% scored
Platform capability
Sources & assumptions
  • · Day-1 contact coverage: Coverage is a platform capability; contact success measured in pilot
  • · Roll-rate improvement: McKinsey: 20–25% NPL reduction among digital-first collections leaders
  • · 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
VoiceWhatsAppSMS

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 · Shriram Finance
LMSCollections platformPayment gatewayField-force appPolicy/renewal registryCRM

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

Trust & languages
HindiTamilTeluguKannadaMarathiRajasthani-accented HindiEnglish

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 interactions2.0M
Seller assumption — replace in discovery
Current cost per interaction ($)$0.9
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$1.8M
Current operating cost / mo
$7.3M
Modelled gross benefit / yr
0.2 mo
Payback on Scale
155%
3-yr ROI (modelled)
Automated/assisted interactions per month1.1M
Modelled AI run-cost per month (usage + cloud, system estimate)$385K
New monthly operating cost$1.2M

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 Shriram Finance'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 Shriram Finance: Voice-first workflows in multiple regional languages with LMS and field-app integration — two to three workflows in the scale scope, expandable to gold and MSME books after proof on CV.

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: LMS, Collections platform, Payment gateway
  • · A named business owner for cv emi reminders & ptp follow-up
  • · Security review counterpart and policy sign-off (LMS scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“The merger built India's biggest CV lender; a conversational first line lets the famed Shriram field force cover a bigger book without proportional hiring.”

CIO / CTO

“The agent plugs into the LMS and field app you already run — it feeds the field force better queues rather than replacing your systems.”

COO

“Field visits per resolved account is your costliest ratio; triaging with night-capable voice conversations bends it within a quarter.”

Head of Collections (CV)

“Reminders that respect freight-cycle timing, PTPs that chase themselves, and a ranked field queue every morning — built around how your borrowers actually earn.”

Chief Risk / Compliance Officer

“RBI recovery-conduct expectations extend to field behavior; moving routine contact to logged, bounded conversations reduces your conduct surface area.”

CFO / Procurement

“Substituting even a fifth of field visits with sub-dollar conversations pays for the deployment; the roll-rate upside is additive.”

Outreach

Pre-built offer emails for Shriram Finance

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 commercial-vehicle financier post the 2022 group merger, serving driver-owners in semi-urban and rural India — enormous field-collections intensity in regional languages, though a field-force culture may adopt gradually.

Recommended next step

Pilot in two Tamil Nadu and Andhra territories: agent-first contact on buckets 0–1 for 60 days, field-visit-per-resolution delta reported.

Entry: CV EMI reminders & PTP follow-up · 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.