Give DTDC a network-wide agentic layer for tracking, pickup booking, COD/remittance, and franchisee support — delivering the consistent customer experience its franchise model cannot enforce by training alone, in the languages its customers actually speak.
Among India's largest express-parcel companies, built on a franchise model with 10,000+ channel partners spanning metros to small towns; carries retail, SME, and e-commerce shipments domestically and internationally.
Public factThe franchise structure means the customer-facing frontline is thousands of independently run counters — experience and answer quality vary by franchisee.
Reasoned inferenceWISMO (where-is-my-order) queries dominate contact volume in Indian express logistics, spiking during e-commerce events and weather disruptions.
Reasoned inferenceCOD collections and franchisee remittance reconciliation generate a second, internal conversation load between network and partners.
Reasoned inferenceSME shippers — the profitable core — choose carriers partly on service responsiveness; a consistently answering network is a sales weapon against Delhivery and Blue Dart.
Seller hypothesis — validateValidate with the account team before outreach: Tracking-backbone API readiness and event granularity for proactive exceptions · How customer-service volume actually splits between central lines and franchise counters · Franchisee-economics sensitivity — who pays for and who benefits from deflection
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: A network-operations company whose technology is bought and integrated around its tracking backbone; no internal AI-platform engineering, and franchise economics demand packaged capability that works uniformly across thousands of small partners.
Why they won't build the full stack: Building conversational infrastructure across vernacular voice and telephony is far outside a franchise logistics operator's model; the value is a bought layer that standardizes what franchising cannot.
Indian express-parcel volumes continue structural growth with e-commerce, while pricing competition from integrated players pressures margins
GTM implication: Cost-per-interaction discipline and RTO reduction are the two levers a franchise network can pull without touching linehaul economics
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Tracking & delivery-exception conversations Instant vernacular tracking answers on any channel plus proactive exception outreach that fixes addresses before RTO; WISMO deflection measured network-wide. | WISMO is the dominant volume; every call handled by a franchisee counter or central line is cost and inconsistency. Friction today: Customers call franchise counters or a central line for status the tracking system already knows; exceptions (address issues, failed attempts) surface only after repeated failures. | WhatsAppVoiceWeb chat | |||
Pickup booking & SME shipper servicing Conversational pickup booking with serviceability and rate answers grounded in network systems; SME shippers get a reliable, instant front door. | Retail and SME pickup requests currently route through franchisees and phone lines; friction here is lost bookings to competitors. Friction today: Pickup scheduling depends on franchisee responsiveness; rate and serviceability questions get inconsistent answers. | WhatsAppVoiceWeb chat | |||
Franchisee support & COD-remittance line Instant grounded answers on remittance status, claims, and procedures in the franchisee's language; disputes structured and tracked. | 10,000+ partners generate constant operational queries — COD reconciliation, claim procedures, scheme updates — answered today by regional offices. Friction today: Franchisees phone regional managers; answers vary; remittance disputes drag on email threads. | 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 DTDC Express's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for DTDC Express: Two-three workflows (tracking/exceptions, pickup booking, franchisee support) integrated to the tracking backbone across voice and WhatsApp — scale scope with clear SME-seller expansion.
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 franchise model built DTDC's reach; a conversational layer gives it the one thing franchising cannot enforce — a single, excellent standard of answer at every touchpoint.”
“One integration to the tracking backbone serves customers, SME shippers, and 10,000+ franchisees — the highest-leverage system in the estate.”
“Proactive exception handling attacks RTO — the costliest failure in the network — while WISMO deflection frees central and franchise capacity simultaneously.”
“Partners get instant operational answers instead of waiting on regional offices, and their counters stop drowning in status queries — franchisee economics improve.”
“COD and remittance conversations become logged, structured, and auditable — replacing phone-and-email reconciliation disputes with evidence.”
“At sub-dollar interaction costs and parcel-scale volume, WISMO deflection plus RTO reduction is a fast, countable case — pilot it on one zone's traffic.”
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.
One of India's largest express-parcel players built on a distinctive franchise model (10,000+ franchise touchpoints) — where tracking, pickup, and COD conversations are fielded inconsistently by thousands of small franchisees, making a standardized conversational layer unusually valuable.
Zone pilot: WhatsApp/voice tracking and proactive exception outreach on one zone's parcel traffic for 90 days, measured on WISMO deflection and RTO rate vs control.
Entry: Shipment tracking & delivery-exception 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.