Give VietinBank an agentic layer for iPay service, retail and SME collections, and branch-deflecting servicing in Vietnamese — SBV-auditable, Decree 13-compliant, and consistent with MUFG-grade governance.
VietinBank is one of Vietnam's Big-4 state banks, with MUFG Bank holding a roughly 20% strategic stake since 2013 — the deepest foreign partnership among the state banks — and the VietinBank iPay app anchoring its retail digital channel.
Public factIts franchise skews corporate and SME, meaning collections and servicing workflows span business borrowers where documented conduct and relationship preservation both matter.
Reasoned inferenceSBV supervision, periodic loan-restructuring programs, and Decree 13 consent rules define the compliance envelope any outreach automation must inhabit.
Reasoned inferenceZalo-first customer behavior and a branch-heavy service model create the same large deflection pool as at peer state banks — with the added angle that MUFG's regional playbook includes technology partnerships across its investees.
Reasoned inferenceMUFG governance experience (it also holds stakes in Security Bank, Bank Danamon, Krungsri) means platform decisions with regional reference cases travel well into VietinBank's approval processes.
Seller hypothesis — validateValidate with the account team before outreach: Procurement route and MUFG governance requirements for AI vendors · Collections and core API accessibility · Zalo Official Account consent posture for outbound contact
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: Like its Big-4 peers, VietinBank procures platforms through formal tender and integrates internally; the MUFG relationship reinforces a proven-vendor, governance-first pattern rather than internal platform building.
Why they won't build the full stack: State-bank engineering is absorbed by core modernization and compliance programs; the collections and service economics are available now through procurement, while a build would still be in committee when the credit cycle turns.
Results commentary emphasizes credit-quality control, retail expansion, and digital transformation, in line with Big-4 peers under SBV supervision.
GTM implication: Pitch in the sector's shared vocabulary — credit cost and cost-to-income — with the MUFG governance angle as the differentiated door-opener.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Retail & SME early-delinquency collections Policy-timed Zalo/voice outreach in Vietnamese with relationship-aware scripts, offers from the approved matrix, automatic follow-up, hardship and key-relationship cases routed to officers. | Credit cost is the P&L line SBV supervision and the market both watch; early-bucket coverage is its most controllable driver. Friction today: Dialer capacity caps coverage; offers vary; PTP follow-up is manual; SME collections risk damaging relationships when handled bluntly. | ZaloVoiceSMS | |||
iPay service & dispute support Grounded in-conversation resolution and dispute intake with documented handling and warm handoff. | Retail digital growth generates app-adjacent service volume that should resolve in-channel, not in branches. Friction today: Transfer, payment, and card questions queue into hotline and branches with no session context. | In-app chatZaloVoice | |||
SME & corporate servicing desk Proactive status and grounded answers with eFAST integration; officers receive context-rich escalations only. | The corporate-SME franchise is the bank's identity; officer hours spent on status queries are origination capacity lost. Friction today: Disbursement status, guarantee, and trade queries flow through officers by phone and email. | ZaloEmailVoice |
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 VietinBank's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for VietinBank: Collections, iPay service, and SME servicing are adjacent high-volume workflows on one core integration — Big-4 volume makes a multi-workflow deployment the economically rational entry.
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.
“VietinBank's MUFG partnership was the boldest governance move among the state banks; partner-delivered service automation is its operational sequel — proven platforms, formal procurement, measured results.”
“One integration into core, payments, and origination systems powers collections, iPay service, and SME workflows — partner-led delivery that respects the modernization roadmap and MUFG-grade vendor governance.”
“Coverage stops being a dialer constraint and branch service migrates to Zalo and voice — elastically, in Vietnamese, with your teams on exceptions.”
“Early-bucket coverage hits 100% with relationship-aware conduct, and officers get their selling hours back — both measured against today's baselines.”
“SBV conduct expectations and Decree 13 consent enforced as configuration with complete interaction logs — an examination posture sampled QA cannot offer.”
“Priced on implementation plus usage through formal tender; the return is denominated in credit cost and cost-to-income, audited on control cohorts.”
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.
Big-4 state bank with MUFG as ~20% strategic investor, the iPay retail app, and a heavy corporate-SME franchise — the same state-scale service and collections economics as BIDV, with MUFG governance adding comfort with proven partner platforms.
Scope a control-group collections pilot on one retail portfolio through formal procurement, with MUFG-comparable governance references in the submission.
Entry: Retail early-delinquency collections · 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.