KoreaBankingLaunch · $50K
Woori Bank

Trust rebuilt one logged conversation at a time — an agentic, audit-first frontline for Woori's catch-up fight

Woori competes from fourth place with thinner technology resources and a board consumed by internal-control remediation; an agentic frontline whose every conversation is logged, script-governed and auditable delivers the two things Woori needs simultaneously — a cost-income story that closes the gap to peers and compliance evidence that supports the internal-control narrative regulators are watching.

Entry use case
Retail servicing line (account, card-linkage, certificate and rate inquiries)
Expected outcome
Cut cost per routine servicing contact with fully-logged conversations, generating both efficiency gains and conduct-evidence quality no sampled QA matches.
Recommended next step
Governance-first briefing with compliance and operations: present the logging and script-control architecture, then baseline one servicing line for a Launch pilot.
What we understand

Woori Bank's operating reality

Woori Financial Group is Korea's fourth major banking group, fully privatized from government ownership only in recent years and operating with a thinner non-banking portfolio than KB, Shinhan or Hana.

Public fact

Woori has faced public internal-control failures — including improper-lending scandals connected to former leadership that drew FSS scrutiny and board changes.

Public fact

Woori's cost-income and profitability metrics trail the leading groups, making efficiency the persistent investor question.

Reasoned inference

The Woori WON Banking app modernized retail self-service, but residual phone volume remains heavy for servicing and certificate tasks.

Reasoned inference

FSS attention on Woori's controls makes any new customer-facing automation a governance conversation first and a technology conversation second.

Reasoned inference

Servicing volume likely skews to older customers and small merchants, phone-first segments the app has not absorbed.

Seller hypothesis — validate

Validate with the account team before outreach: Current servicing volumes and cost per contact by line · Internal-control remediation program priorities and how automation fits them · FSS posture toward Woori adopting cloud AI for customer conversations · Incumbent contact-center vendor contracts and renewal windows

Build vs buy

Why we have a right to win here

Buy-led target

Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution

Evidence: Woori has the thinnest technology bench of Korea's four major groups, no public LLM or AI-platform program of consequence, and leadership bandwidth consumed by control remediation — a governed, proven platform bought and deployed fast is the only credible route to frontline AI this cycle.

Why they won't build the full stack: A bank rebuilding regulator trust cannot spend years assembling voice-AI infrastructure while peers deploy; buying auditable capability now converts Woori's constraint — scrutiny — into an argument for the most governed platform available rather than an internal experiment.

What management is signalling

Woori Financial Group's improper-lending controversies drew FSS scrutiny, sanctions processes and public commitments to internal-control overhaul.

Reported factpublic disclosures and FSS announcements · 2024-2025

GTM implication: Lead with governance: sell the platform as conduct-evidence infrastructure that happens to cut costs, matching the board's actual priority ordering.

Woori's investor communications emphasize closing the profitability and cost-income gap to larger rivals and strengthening shareholder returns.

Inferencerecent investor communications (validate) · 2025-2026

GTM implication: Quantify the pilot in cost-income terms — the exact metric Woori's catch-up narrative is judged on.

What already exists (don't pitch this)
  • Woori WON Banking app with retail self-service
  • IVR and chatbot deflection
  • KakaoTalk notification channels
  • Branch network serving phone-first segments
What customers still can't do end-to-end (pitch this)
  • →Transactional voice automation at honorific quality
  • →Conversation-level conduct evidence beyond sampled QA
  • →Cross-channel context between app, phone and branch
  • →After-hours servicing for merchants and workers
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Retail servicing line
Routine servicing resolved in honorific conversation, 100% logged and scored; wait times and per-contact cost drop measurably.
Routine servicing is the highest-volume, lowest-risk automation target — the right first proof for a governance-sensitive bank.
Friction today: IVR trees and queues for tasks the app cannot finish; per-contact costs rise with Korean service wages.
VoiceKakaoTalkApp chat
Loan-servicing and repayment desk
Policy-exact repayment answers with hardship cues routed to specialists, every conversation documented for conduct review.
Household-debt stress raises repayment and restructuring inquiries; consistent policy answers matter under supervisory attention.
Friction today: Repayment-option explanations vary by agent; hardship cases need careful, documented handling.
VoiceKakaoTalk
Small-merchant banking desk
Merchant servicing answered around the clock with live status from core systems; branch and RM load falls.
Woori serves a large small-merchant base whose banking questions arrive outside branch hours.
Friction today: Merchants queue for settlement, limit and loan-status questions during their own business day.
VoiceApp chat
Watch the change

Retail servicing line (account, card-linkage, certificate and rate inquiries): today vs the agentic model

Scenario: A small-restaurant owner calls at 10pm about tomorrow's settlement timing and a loan-limit question; the agent verifies identity, reads live settlement status from core systems, explains his limit and books an RM callback for the increase request — resolved in honorific Korean, fully logged, no branch visit lost from his working day.
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
VoiceKakaoTalkApp chat

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 · Woori Bank
Core bankingCRMLoan systemsCollections platformSME loan systems

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

Trust & languages
KoreanEnglish

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 interactions1.3M
Seller assumption — replace in discovery
Current cost per interaction ($)$4.0
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$5.2M
Current operating cost / mo
$31.3M
Modelled gross benefit / yr
0.0 mo
Payback on Launch
1037%
3-yr ROI (modelled)
Automated/assisted interactions per month715K
Modelled AI run-cost per month (usage + cloud, system estimate)$250K
New monthly operating cost$2.6M

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

Recommended package

Launch — $50K implementation

Launch · $50K · A focused, fast production pilot8–10 weeks to a live, measured pilot

Why this package for Woori Bank: A focused, fast pilot on one high-volume servicing line fits a bank that needs a provable win quickly and will scale only after internal stakeholders see logged-conversation governance working.

Included
  • Up to 3 channels
  • One priority workflow
  • Limited enterprise integrations (1–2 systems)
  • API credential & security setup
  • Core conversational + workflow configuration
  • Basic analytics
  • Controlled production pilot with defined success criteria
Not included
  • ✕Usage & consumption (billed separately)
  • ✕Additional workflows
  • ✕Multi-geography rollout
  • ✕Managed operations
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, CRM, Loan systems
  • · A named business owner for retail servicing line (account, card-linkage, certificate and rate inquiries)
  • · Security review counterpart and policy sign-off (Core banking scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“Woori's turnaround story needs operational proof visible to customers and regulators alike; a frontline where every conversation is logged and governed is efficiency and internal-control evidence in a single investment.”

CIO / CTO

“With thinner engineering resources than your three larger rivals, a proven governed platform closes the AI gap in quarters, not years — no internal build program required.”

COO

“The cost-income gap to peers is largely a service-operations gap; elastic automation on routine servicing is the fastest lever that doesn't require branch-network surgery.”

Head of Retail Banking

“Your phone-first customers are your most loyal; resolving their servicing in one respectful call protects deposits while cutting the queue costs your P&L carries.”

Chief Risk / Compliance Officer

“After the internal-control headlines, 100% conversation logging with script governance and human gates is exactly the evidence posture the FSS wants to see — stronger than any sampled-QA regime.”

CFO / Procurement

“A Launch pilot prices the proof at a fraction of an internal program; cost per contact against your own baseline in one quarter, usage billed on consumption.”

Outreach

Pre-built offer emails for Woori 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 2 — high-potential incubation

Why this tier

Korea's fourth major banking group is rebuilding trust after internal-control failures and lending-scandal headlines while chasing the cost-income gap to its three larger rivals — a bank that needs visible service and compliance wins fast, without a large internal AI program to deliver them.

Recommended next step

Governance-first briefing with compliance and operations: present the logging and script-control architecture, then baseline one servicing line for a Launch pilot.

Entry: Retail servicing line (account, card-linkage, certificate and rate inquiries) · Launch package · 8–10 weeks to a live, measured pilot. 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.