Deploy agentic failed-delivery recovery, consignee communication, and shipper support across Ninja Van's six markets — on the Google Cloud platform it already runs — turning delivery exceptions into resolved conversations before they become RTOs.
Ninja Van is a Singapore-headquartered last-mile logistics network covering Singapore, Malaysia, Indonesia, Thailand, Vietnam and the Philippines, publicly cited as handling on the order of two million parcels a day at peak.
Public factNinja Van's engineering platform publicly runs on Google Cloud — its use of GKE and Google Cloud infrastructure is documented in public engineering material.
Public factFailed first attempts and COD rejections are the core margin leaks of SEA last-mile economics; every percentage point of first-attempt success moves network profitability.
Reasoned inferenceShipper support (pickup scheduling, claims, COD remittance queries) is a second contact universe that gates volume retention from e-commerce clients.
Reasoned inferenceE-commerce clients would pay for branded proactive delivery communication as a premium service — an agentic layer could become a Ninja Van revenue product, not just a cost tool.
Seller hypothesis — validateNinja Van's platform publicly runs on Google Cloud (GKE and related infrastructure, documented in public engineering content) — the agentic layer lands on infrastructure and billing relationships that already exist.
Publicly reported Google Cloud relevanceValidate with the account team before outreach: Real-time failed-attempt event availability from the ops platform · RTO cost model and avoidable-failure share by market · Shipper appetite for branded proactive-delivery communication as a paid product
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: Ninja Van's engineering is strong but concentrated on routing, sortation, and network-ops systems on Google Cloud — not conversational AI. With a publicly reported push toward profitability, it buys outcome-priced layers that move first-attempt success rather than staffing a platform team.
Why they won't build the full stack: Six languages of consignee voice and chat is a bought capability; every engineering hour spent building it is an hour not spent on the network-economics systems that are the company's actual moat. RTO recovery priced per avoided failure needs no build case at all.
Reported cost restructuring and a profitability push across the network as e-commerce logistics pricing normalizes regionally.
GTM implication: Price against the fully loaded cost of a failed delivery times avoidable RTOs per month — a margin story that fits the profitability narrative exactly.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Failed-delivery resolution Consignee engaged within minutes of a failed attempt in their language, address/slot/COD issue fixed conversationally, avoidance attributed. | The economics of the entire network concentrate at the failed doorstep; minutes-fast recovery converts RTOs into completed deliveries. Friction today: Driver notes are cryptic; consignees learn of failures hours later; second attempts repeat the same failure. | WhatsAppSMSVoice | |||
Consignee tracking & delivery preferences Conversational tracking with proactive exception notices; structured preference capture that feeds routing. | Where-is-my-parcel contacts scale with volume; preference capture (gate codes, safe-drop) prevents failures upstream. Friction today: Tracking pages answer poorly; preferences live in driver memory. | WhatsAppWeb chat | |||
Shipper support & claims Shipper-recognized support with claim intake validated in-flow and remittance status grounded in finance systems. | E-commerce clients churn networks over claim friction and COD remittance opacity. Friction today: Shipper tickets queue behind consumer volume; claims bounce on documentation. | Web chatEmailVoice |
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 Ninja Van's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Ninja Van: Consignee recovery, shipper support, and COD workflows across six markets and as many languages constitute a multi-workflow, multi-market Scale deployment on an already-friendly cloud estate.
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.
“Ninja Van's next margin story is operational: every recovered RTO is pure network profit, and a branded proactive-delivery experience becomes a product your e-commerce clients pay for.”
“You already run on Google Cloud — Gemini Enterprise agents grounded in your ops platform extend the same estate, and Tilicho Labs delivers the omnichannel communications layer.”
“Recovery conversations start within minutes of a failed scan, in six markets' languages, and structured preference capture stops repeat failures at the same doorsteps.”
“Second attempts stop being blind: the conversation fixes the address, slot, or COD readiness first, and your first-attempt-success dashboards show it within weeks.”
“Consignee outreach honors each market's data-protection regime — PDPA variants, PDP, Decree 13 — with consent management and complete logs built into the platform.”
“Price it against your own number for a failed delivery's fully loaded cost times avoidable RTOs per month — on cloud commercials you already have in place.”
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.
SEA-wide parcel network handling roughly two million parcels daily across six markets, publicly running on Google Cloud — failed-delivery resolution and shipper support are its economics in miniature, and the cloud fit is already proven.
Scope a two-market failed-delivery recovery pilot (Malaysia, Philippines) with first-attempt-success lift as the primary metric.
Entry: Failed-delivery resolution & consignee self-service · 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.