JapanBanking (megabank)Transform · $200K
MUFG Bank

The branch that never closed — agentic retail servicing for MUFG's post-branch-reduction base

MUFG spent a decade cutting branches on the logic that digital would absorb the load — but the older half of its base still phones, and rate normalization suddenly makes deposit retention and product conversations valuable again; an agentic frontline that resolves account servicing in keigo-grade voice, guides procedures that once required branch visits, and conducts compliant outreach at scale is the missing layer between the branch network MUFG dismantled and the app it built.

Entry use case
Everyday banking service and procedure desk
Expected outcome
Resolve routine account, card and procedure inquiries in-conversation, cutting call wait times and branch-referral volume for the phone-first base.
Recommended next step
Workshop with retail-channels leadership: baseline call volumes, branch-referral rates and inheritance-procedure cycle times, then scope a Transform phase one on the servicing desk with FSA-conscious gates.
What we understand

MUFG Bank's operating reality

MUFG has reduced its domestic branch network by a large share over the past decade, shifting routine servicing toward app, ATM and phone channels.

Public fact

MUFG has reported record net profits in the rate-normalization era, with domestic deposit economics newly valuable after decades of zero rates.

Public fact

BOJ policy normalization has revived deposit competition among banks and against securities platforms — retention and product conversations at scale matter for the first time in a generation.

Public fact

An older customer segment remains phone- and branch-first for procedures like inheritance, address changes and account matters; remaining branches queue accordingly.

Reasoned inference

Procedure abandonment — customers giving up on inheritance or change filings until forced — likely creates downstream cost and compliance exposure the bank does not fully see.

Seller hypothesis — validate

Japanese megabank contact centers lean heavily on domestic BPO staffing whose wage costs and attrition are rising with the labor market.

Reasoned inference

Validate with the account team before outreach: Contact volumes, BPO structure and cost per call across retail servicing · Compliance posture on conversational execution of procedures and outreach · Inheritance-procedure volumes, cycle times and abandonment · Internal AI programs and incumbent vendor commitments across channels

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: MUFG has serious internal technology capability and group AI initiatives, but megabank delivery reality is partner-led: regulated conversational workflows will be built with platform vendors and integrators under bank governance, not from scratch — the sale is industry workflows, governance tooling and speed.

Why they won't build the full stack: Internal engineering is committed to core modernization and group digital programs; assembling keigo-grade conversational servicing with FSA-grade conduct governance is multi-year undifferentiated work, while a partner-delivered platform lands measurable servicing capacity inside a fiscal year.

What management is signalling

MUFG has reported record net profits in the rate-normalization era while having reduced its domestic branch network substantially over the past decade.

Reported factFY2025 annual results and disclosed channel strategy · May 2025

GTM implication: Record profits fund modernization and branch reduction created the service gap — pitch the servicing desk as the completion of the published channel strategy.

Management commentary emphasizes deposit-franchise value and wealth-product cross-sell as rates normalize.

Inferencerecent investor communications (validate) · 2025-2026

GTM implication: Position proactive outreach capacity as monetizing the deposit base the branch network can no longer converse with.

What already exists (don't pitch this)
  • Mitsubishi UFJ direct app and web banking at national scale
  • IVR and large outsourced call-center estate
  • Reduced but significant branch network for complex matters
  • Group digital and AI initiatives
What customers still can't do end-to-end (pitch this)
  • →Conversational execution of procedures the app cannot handle
  • →Keigo-quality voice automation for the older phone-first base
  • →Proactive compliant outreach at deposit-base scale
  • →Cross-channel context between branch, phone and app journeys
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Everyday banking service and procedure desk
Routine servicing resolved in keigo-grade conversation with system writes; procedures guided end-to-end with documents prepared before any branch step.
Branch reduction moved the routine servicing burden onto channels never built to execute procedures conversationally.
Friction today: Account, card and procedure questions queue by phone in business hours; complex procedures still end in branch referrals and repeat visits.
VoiceApp chatWeb
Inheritance and life-event procedure support
Guided, patient intake with document checklists in-flow and human specialists for judgment steps; cycle times and family burden drop.
Japan's demographic reality makes inheritance processing a structurally growing workload, painful for families and expensive for the bank.
Friction today: Bereaved families navigate document-heavy processes across calls and visits; handle times are the longest in retail banking.
VoiceWebMail-triggered callback
Deposit retention and product-information outreach
Consent-governed, compliant outreach converses about rates and products within approved scripts, booking human advisors for regulated advice.
Normalized rates make deposit conversations economically meaningful; outbound capacity is nowhere near the base's size.
Friction today: Rate and product campaigns run by mail and app banners; conversations happen only when customers initiate.
VoiceApp chatSMS
Watch the change

Everyday banking service and procedure desk: today vs the agentic model

Scenario: A 68-year-old customer whose local branch closed last year calls about transferring her late husband's account; the agent explains the inheritance procedure step by step in patient keigo, generates her personalized document checklist, books the single required branch appointment and schedules a follow-up call — what took three visits now takes one.
Today
same interaction, two worlds
Agentic layer
First-contact resolution
deferred via tickets
in-conversation actions
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
  • · First-contact resolution: Process design: agent acts in systems of record
  • · 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
VoiceApp chatWebMail-triggered callbackSMS

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 · MUFG Bank
Core banking interfacesCard systemsWorkflow/CRMInheritance workflowDocument managementCRMProduct catalogCampaign systems

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

Trust & languages
JapaneseEnglish

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 interactions3.0M
Seller assumption — replace in discovery
Current cost per interaction ($)$5.0
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$15.0M
Current operating cost / mo
$92.1M
Modelled gross benefit / yr
0.0 mo
Payback on Transform
1315%
3-yr ROI (modelled)
Automated/assisted interactions per month1.7M
Modelled AI run-cost per month (usage + cloud, system estimate)$578K
New monthly operating cost$7.3M

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 MUFG Bank's measured baseline. Package price covers implementation only; recurring usage billed separately.

Recommended package

Transform — $200K implementation

Transform · $200K · A broader enterprise deployment14–20 weeks phased across units

Why this package for MUFG Bank: Retail servicing, procedure guidance and proactive deposit/product outreach span regulated workflows at megabank scale — a phased Transform program with strict human gates matches both scale and FSA posture.

Included
  • 7–10 channels
  • Multiple inbound + outbound workflows
  • Complex enterprise integrations
  • Multiple business units or geographies
  • Advanced agent orchestration
  • Enterprise grounding
  • Governance & evaluation framework
  • Role-based human supervision
  • Custom analytics & optimization
  • Production hardening + managed rollout plan
Not included
  • ✕Usage & consumption (billed separately)
  • ✕Ongoing managed operations (contracted separately)
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: Core banking interfaces, Card systems, Workflow/CRM
  • · A named business owner for everyday banking service and procedure desk
  • · Security review counterpart and policy sign-off (Core banking interfaces scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO (Retail Banking)

“Branch reduction was the right cost call and left a service debt to the customers who fund the deposit franchise; agentic servicing pays that debt at software economics exactly as deposits become worth competing for again.”

CIO / CTO

“A governed agent layer over core-banking interfaces with strict human gates — bounded integration, evidence-grade logging, alignment with existing channel architecture rather than another parallel stack.”

COO

“Call-center wage inflation and BPO attrition are structural; conversational capacity absorbs routine volume elastically while your people handle the judgment work regulation requires of them.”

Head of Retail Channels / Customer Service

“Your longest queues are procedures the app cannot do and branches no longer exist to do; a conversational desk that executes procedures is the channel your network plan always assumed would arrive.”

Chief Risk / Compliance Officer

“FSA-conscious design: human gates on regulated advice and transactions, approved-script enforcement, 100% conversation logging — a stronger conduct record than sampled QA across an outsourced estate.”

CFO / Procurement

“Cost per servicing contact at megabank volume is a structural line; conversation-priced automation bends it measurably in the pilot, benchmarked on your own queues and reported quarterly.”

Outreach

Pre-built offer emails for MUFG Bank

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 1 — immediate strategic pursuit

Why this tier

Japan's largest bank has cut a large share of its branch network while rates normalize and deposit competition returns — tens of millions of retail customers now depend on app and phone servicing the branch model used to absorb, making conversational capacity the megabank's new front door.

30 / 60 / 90-day plan
  • Day 0–30: Workshop with retail-channels leadership: baseline call volumes, branch-referral rates and inheritance-procedure cycle times, then scope a Transform phase one on the servicing desk with FSA-conscious gates.; confirm sponsor and baseline data access; validate: Contact volumes, BPO structure and cost per call across retail servicing
  • Day 31–60: architecture & security review with the platform team; Tilicho Labs scoping on Voice + App chat; pilot scope signed
  • Day 61–90: Transform package kickoff; everyday banking service and procedure desk pilot in build; success thresholds locked with the Head of Retail Channels / Customer Service
Recommended next step

Workshop with retail-channels leadership: baseline call volumes, branch-referral rates and inheritance-procedure cycle times, then scope a Transform phase one on the servicing desk with FSA-conscious gates.

Entry: Everyday banking service and procedure desk · Transform package · 14–20 weeks phased across units. 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.