Give MoMo an agentic service layer that resolves transaction disputes, merchant queries, and eKYC drop-offs in Vietnamese at wallet-scale unit costs — on the cloud where its AI already runs.
MoMo is Vietnam's largest e-wallet and financial super-app with 30M+ registered users spanning payments, savings, credit distribution, insurance, donations, and ticketing.
Public factMoMo publicly runs AI workloads — chatbots, eKYC, recommendations — on NVIDIA GPUs in Google Cloud, reported via NVIDIA's own case coverage.
Public factFailed top-ups, pending transfers, and merchant settlement questions are the dominant contact drivers for any wallet at this scale; peaks follow salary days and mega-promo events.
Reasoned inferenceMoMo distributes credit and investment products with licensed partners, creating a compliance-sensitive support surface (eligibility, repayment, disclosure) it cannot fully script today.
Reasoned inferenceeKYC drop-off rescue is likely a measurable growth lever: users who stall at document capture rarely return without proactive outreach.
Seller hypothesis — validateSBV oversight of payment intermediaries plus Vietnam's PDPD (Decree 13/2023) make in-country data handling and consent-governed outreach non-negotiable design constraints.
Public factPublicly reported (via NVIDIA) to run chatbot, eKYC, and recommendation inference on NVIDIA GPUs in Google Cloud — an existing consumption relationship to build on.
Publicly reported Google Cloud relevanceValidate with the account team before outreach: Actual monthly contact volume by driver (disputes vs merchant vs onboarding) · Where dispute-case state lives and API readiness of the ledger and dispute systems · Zalo Official Account usage and consent posture for proactive outreach
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: MoMo has genuine in-house AI engineering — it runs its own chatbot, eKYC, and recommendation models on Google Cloud GPUs — but that capability is pointed at product features and risk models, not contact-center orchestration. Its operational tooling has historically been bought, and wallet economics reward outcome-priced platforms over platform ownership.
Why they won't build the full stack: Building an SBV-auditable omnichannel service stack (Vietnamese voice, Zalo, policy engines, 100% interaction logging) is a multi-year infrastructure program outside MoMo's product roadmap. A newly profitability-focused MoMo cannot justify diverting growth engineers to rebuild what a governed platform delivers in weeks.
Widely reported to have reached profitability in 2024 after a decade of growth investment, with investor interest reportedly valuing the company around $3B.
GTM implication: A profitability-era MoMo buys against unit economics — lead with cost per resolved contact and eKYC completion lift, not innovation branding.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Transaction dispute & wallet service In-conversation status from the transaction ledger, automated reversal initiation within policy, full audit log. | Pending transfers and failed top-ups are the highest-volume, highest-anxiety contact class for a 30M-user wallet. Friction today: App chat bot deflects to FAQs; unresolved cases become app-store complaints and SBV-reportable grievances. | In-app chatVoiceZalo | |||
Merchant activation & settlement support Merchant recognized by ID, settlement status grounded in the payout system, re-activation nudges automated. | Hundreds of thousands of small merchants accept MoMo; settlement and QR issues directly gate payment volume. Friction today: Small merchants call or message ad hoc; support staffed for consumers, not B2B settlement questions. | ZaloVoiceIn-app chat | |||
eKYC and onboarding rescue Consent-based outreach that walks users through document recapture; completion lift measured per cohort. | Every abandoned eKYC is a lost lifetime value across payments, credit, and investment products. Friction today: Drop-offs are invisible until monthly funnel reviews; no proactive, guided re-engagement. | In-app chatZaloSMS |
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 MoMo's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for MoMo: Multiple high-volume workflows (disputes, merchant support, onboarding rescue) across app chat, voice, and Zalo justify a multi-channel deployment rather than a single pilot.
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.
“Your super-app strategy monetizes trust. An agentic layer that resolves money-movement anxiety in one thread is a trust asset that compounds across every product you cross-sell.”
“You already run inference on Google Cloud GPUs. Gemini Enterprise extends that same estate with grounded agents on your ledger and dispute systems — no new cloud posture to defend.”
“Salary-day and promo spikes force you to staff for peaks. Elastic conversational capacity absorbs the spike while your team keeps only the judgment cases.”
“eKYC drop-off rescue is a growth feature disguised as support: every completed onboarding is recovered LTV across payments, credit, and investments.”
“Every interaction is logged, scored, and policy-bounded — SBV grievance handling and Decree 13 consent rules become enforceable configuration, not training slides.”
“Wallet margins cannot fund human-assisted contacts at scale. Moving the dominant contact classes to ~sub-dollar automated resolution changes the service cost curve permanently.”
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.
30M+ user wallet with merchant, lending-partner, and eKYC support volumes; already runs AI on Google Cloud GPUs, so the platform conversation starts warm — but wallet economics demand sub-dollar interaction costs.
Workshop with the CX and platform teams to size the dispute-contact class and scope a Zalo + in-app pilot on the transaction ledger.
Entry: Transaction dispute & wallet service resolution · 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.