MalaysiaFintech / e-walletScale · $100K
Touch 'n Go Digital

Every Malaysian highway and half its wallets: resolving TNG's reload and toll disputes before the next toll plaza

Deploy an agentic layer for TNG Digital's reload, RFID toll-dispute, and eKYC conversations — resolving money-and-mobility anxiety in Bahasa, English, Mandarin, or Tamil at wallet-scale unit costs.

Entry use case
Reload failure & toll-dispute resolution
Expected outcome
In-channel resolution of the two dominant contact classes with grounded ledger and toll-transaction context, cutting repeat contacts and app-store escalations
Recommended next step
Size the reload-failure and toll-dispute contact classes with the CX team and scope an in-app + WhatsApp resolution pilot.
What we understand

Touch 'n Go Digital's operating reality

TNG Digital operates the TNG eWallet — Malaysia's most widely used e-wallet with tens of millions of registered users — within the Touch 'n Go group (CIMB orbit) and with Ant Group as a publicly known strategic partner.

Public fact

Touch 'n Go is the backbone of Malaysian toll payments (cards and RFID), so wallet support inherits mobility-critical urgency: a failed reload can strand a driver at a plaza.

Public fact

Reload failures, stuck transfers, RFID misreads and double-charges are the dominant contact drivers; volumes spike with holidays and balik kampung travel waves.

Reasoned inference

GO+ (investment) and lending features add regulated conversations under BNM e-money and related frameworks that scripts handle poorly.

Reasoned inference

Proactive RFID-dispute resolution (detecting double-charges and notifying users first) could convert the angriest contact class into a loyalty moment.

Seller hypothesis — validate

Validate with the account team before outreach: Ledger and toll-system API readiness for real-time grounding · Actual contact volume by driver and current SLA baselines · Ant-stack dependencies that constrain platform choices

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: TNG Digital's product engineering is real (strengthened by the Ant partnership), but it is pointed at payments features and compliance — service still runs on ticket queues with day-scale SLAs. The Ant stack supplies payments infrastructure, not Malay/Tamil conversational service automation; that layer gets bought.

Why they won't build the full stack: Wallet-thin margins cannot fund a conversational platform build, and the engineering roadmap is contested by regulated feature work (GO+, lending). Buying outcome-priced resolution is the only service model that scales with transaction growth.

What management is signalling

Reported progress toward wallet profitability within the CIMB group orbit, with monetization of GO+ and lending features.

Inferencerecent investor communications (validate) · 2025

GTM implication: A profitability-focused wallet buys against unit economics — price the pitch on cost per resolved dispute versus current ticket-handling cost.

What already exists (don't pitch this)
  • TNG eWallet app with in-app support ticketing
  • Ant-derived platform capabilities
  • RFID and toll-system integration
  • eKYC pipeline for account upgrades
What customers still can't do end-to-end (pitch this)
  • →Real-time ledger-grounded dispute resolution instead of day-scale tickets
  • →Voice and chat quality across Bahasa Malaysia, English, Mandarin, and Tamil
  • →Proactive double-charge detection and outreach
  • →Cross-system context between wallet ledger and toll transactions
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Reload & transaction dispute resolution
Ledger-grounded status in seconds, reversal initiation within policy, proactive updates until closure.
Failed reloads and stuck transfers are money-anxiety moments that define wallet trust.
Friction today: In-app tickets with day-scale SLAs; users flood social channels when balances look wrong.
In-app chatVoiceWhatsApp
RFID & toll-charge disputes
Toll-transaction lookup in-conversation, double-charge detection and refund within policy, RFID troubleshooting guided step-by-step.
Toll disputes mix wallet data with plaza transaction data — slow resolution poisons both product experiences.
Friction today: Users cannot see why a charge occurred; support reconciles across systems manually.
In-app chatWhatsAppVoice
eKYC upgrade & feature activation
Guided recapture in the user's language, proactive completion nudges, funnel instrumented.
Verified users unlock higher limits and GO+ — each stalled eKYC caps lifetime value.
Friction today: Document rejections are silent; users abandon at the camera step.
In-app chatWhatsApp
Watch the change

Reload failure & toll-dispute resolution: today vs the agentic model

Scenario: A driver's reload fails at a plaza entrance during Raya travel; the agent confirms the bank-side failure, pushes a retry link, and the RFID lane accepts the car before the queue behind honks twice.
Today
same interaction, two worlds
Agentic layer
Languages served
2–3 staffed
10+ in one deployment
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
  • · Languages served: Platform capability: Gemini + Chirp speech
  • · 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
In-app chatVoiceWhatsApp

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 · Touch 'n Go Digital
Wallet ledgerPayment gatewayDispute managementToll transaction systemseKYC pipelineCRM

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

Trust & languages
Bahasa MalaysiaEnglishMandarinTamil

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.7
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$1.4M
Current operating cost / mo
$4.6M
Modelled gross benefit / yr
0.3 mo
Payback on Scale
99%
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.0M

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 Touch 'n Go Digital'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 Touch 'n Go Digital: Reload, toll-dispute, and eKYC workflows across in-app chat, voice, and WhatsApp with ledger and toll-system integrations constitute a natural multi-workflow deployment.

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: Wallet ledger, Payment gateway, Dispute management
  • · A named business owner for reload failure & toll-dispute resolution
  • · Security review counterpart and policy sign-off (Wallet ledger scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“TNG eWallet won ubiquity; the next fight is trust per transaction. Resolving reload and toll anxiety in seconds — in the user's language — is what keeps ubiquity from eroding at the margins.”

CIO / CTO

“Agents grounded in the wallet ledger and toll transaction systems replace ticket queues with in-conversation resolution — with every action policy-bounded and logged.”

COO

“Holiday travel waves stop overwhelming support: capacity is elastic, and proactive double-charge detection removes your angriest queue before it forms.”

Head of Customer Experience

“Your team stops apologizing for day-scale SLAs on money questions. Repeat-contact rate and app-store rating become the metrics that move first.”

Chief Risk / Compliance Officer

“BNM e-money rules and PDPA consent enforced in configuration, refunds bounded by policy matrices, and a complete audit trail on every ringgit-touching conversation.”

CFO / Procurement

“Wallet economics cannot fund human handling of routine disputes. Automated resolution at a fraction of assisted cost is the only service model that scales with transaction growth.”

Outreach

Pre-built offer emails for Touch 'n Go Digital

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

Malaysia's dominant e-wallet (TNG eWallet) plus the toll-payment backbone — reload failures, RFID toll disputes, and GO+ questions generate relentless volume at wallet-thin margins; Ant-partnership heritage means high automation receptivity.

Recommended next step

Size the reload-failure and toll-dispute contact classes with the CX team and scope an in-app + WhatsApp resolution pilot.

Entry: Reload failure & toll-dispute resolution · 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.