Give Ashok Leyland an agentic uptime and network layer: breakdown-assist intake, service scheduling, parts-availability answers, and dealer support in the languages its driver and operator base actually speaks — turning uptime promises into instrumented conversations.
Flagship Hinduja-group CV maker; India's #2 in medium/heavy trucks with ~31% MHCV share and a leading bus franchise, plus Switch Mobility for electric buses and e-LCVs.
Public factFY26 was a record year — all-time-high CV volumes (~220,000 units), record revenue, and profitable EV subsidiary performance — publicly celebrated by management.
Public factRuns uptime-oriented service propositions (24×7 assistance, service networks along freight corridors) because operator economics punish downtime directly.
Public factBreakdown and service-status conversations likely run through call centers and dealer phones in Hindi/English while drivers on corridor routes speak Tamil, Telugu, Punjabi, or Bengali.
Reasoned inferenceFleet customers likely judge OEMs on how service events are handled — status opacity during a repair generates repeated calls up the relationship chain.
Reasoned inferenceValidate with the account team before outreach: Current assist-desk volumes, language mix, and repeat-call rates · Telematics and DMS API readiness for status grounding · How uptime commitments are contracted with fleet customers today
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: Engineering strength is vehicles and powertrains; digital initiatives (telematics, dealer systems) are vendor-delivered, and there is no internal conversational-AI capability — a packaged platform integrated to existing systems is the natural form.
Why they won't build the full stack: A CV OEM will not build speech, telephony, and evaluation infrastructure; it buys proven capability that makes its existing uptime investments conversational.
FY26 delivered record CV volumes (~220,000 units), record revenue, and strong bus and EV momentum
GTM implication: A record parc entering warranty and service years makes after-sales capacity the next operational constraint — automation scales it without headcount
Management continues to emphasize margin discipline and non-cyclical revenue (spares, services) growth
GTM implication: Instrumented uptime conversations directly support the aftermarket revenue line management wants to grow
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Breakdown-assist intake & proactive repair status Vernacular breakdown intake with location capture, nearest-workshop dispatch coordination, and stage-by-stage status pushed to driver and fleet owner alike. | A stranded truck bleeds the operator's revenue hourly; intake speed and status transparency are the service brand. Friction today: Driver calls a hotline, explains location and symptoms in his language to an agent working a script in another; the operator then calls repeatedly for status nobody pushes. | VoiceWhatsApp | |||
Dealer & parts network support Instant grounded parts-availability, order-status, and warranty-procedure answers in the dealer's language; claims guided in-flow. | Workshop turnaround depends on parts availability answers and warranty clarity that today wait on regional-office callbacks. Friction today: Dealer staff chase parts status by phone; warranty claims bounce on documentation; scheme details propagate unevenly. | WhatsAppVoice | |||
Preventive-service scheduling for fleets Proactive service-due conversations at fleet level with slot coordination across workshops; compliance and retention measured per account. | Scheduled maintenance protects uptime and parts revenue; fleet-level coordination beats vehicle-by-vehicle phone tag. Friction today: Service-due tracking is spreadsheet-and-phone work between fleet managers and workshops. | 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 Ashok Leyland's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Ashok Leyland: Two-three workflows (breakdown assist, service status, dealer/parts support) with telematics, DMS, and parts-system integration — scale scope aligned to a network-wide rollout after one-region proof.
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.
“Record volumes mean a record parc to support; uptime delivered conversationally, in the driver's language, is the after-sales moat that defends share through the next CV cycle.”
“This grounds on telematics, DMS, and parts systems you already run — one conversational layer replacing phone-tag across the assist and dealer estate.”
“Breakdown-to-resolution time drops when intake is structured and status is pushed; repeat status calls stop consuming assist-desk capacity.”
“Uptime becomes a measured, per-fleet metric with every service event instrumented — the strongest possible renewal and AMC sales argument.”
“Every assist and warranty conversation logged and scored — consistent process across the network instead of dealer-by-dealer variance.”
“Pilot on one corridor: measure breakdown cycle time, repeat-call suppression, and AMC attach — hard operational numbers before network-wide commitment.”
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.
Hinduja-group CV major (India's #2 in trucks and buses, record FY26 volumes) whose customers are fleet operators for whom vehicle downtime is direct income loss — uptime support, dealer/service coordination, and driver-facing conversations are the operational product.
Corridor pilot: vernacular breakdown intake and proactive repair status on one freight corridor for 90 days, measured on cycle time and repeat-call volume.
Entry: Breakdown assistance & service-status conversations · 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.