Shinhan has publicly piloted AI bankers in branches while consolidating its physical network; the phone channel is where its older, loyal customer base actually lands, and an honorific-fluent Korean voice agent lets Shinhan shrink branch costs without abandoning the customers digital apps leave behind.
Shinhan Bank is a flagship of Shinhan Financial Group, one of Korea's largest banking groups, and has publicly showcased AI-banker deployments and digital-branch formats.
Public factKorean banks, Shinhan included, have been steadily consolidating branch networks, drawing regulatory and political attention to service access for elderly customers.
Public factThe customers displaced by branch closures skew older and phone-first — exactly the demographic least served by app-only digital shift.
Reasoned inferenceKorean honorific speech levels are a genuine quality bar for voice AI in banking; a wrong register with a 70-year-old depositor is a brand incident.
Reasoned inferenceContact volume likely spikes around rate changes, government loan programs and deposit-product maturities.
Seller hypothesis — validateFSC cloud and outsourcing rules for financial institutions will shape the deployment architecture and must lead the conversation.
Reasoned inferenceValidate with the account team before outreach: Incumbent AICC vendor relationships (Korean telcos sell competing AI contact-center stacks) · FSC/cloud compliance route for LLM processing of banking conversations · Actual phone-channel demographics and volume trend post branch consolidation
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: Shinhan has real digital capability — AI-banker branch pilots, a large IT organization and group digital programs — but it buys platforms for regulated production systems and works through vendors and Korean AICC providers; it needs a partner for honorific-quality voice AI, FSC-compliant cloud architecture and contact-center-scale delivery.
Why they won't build the full stack: A bank's engineering priority is core banking, channels and regulatory programs, not building and evaluating LLM voice infrastructure; FSC cloud/outsourcing rules reward a governed, auditable platform with human gates over an internal science project, and honorific-register Korean speech quality is a specialist capability no bank team will staff.
Korean banks including Shinhan continue consolidating branch networks while regulators press on service access for elderly customers — a publicly visible tension in the digital-shift program.
GTM implication: Position the honorific-fluent AI phone line as the service-access answer that lets branch consolidation continue without political cost.
Group profitability targets likely keep cost-income ratio improvement central, with contact-center growth partially recapturing branch savings.
GTM implication: Quantify the leak: measured cost-per-call reduction on the everyday banking line, presented against the branch-savings narrative the group already reports.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Everyday banking service line Routine phone banking resolved in natural honorific Korean; human time reserved for advice and exceptions. | Routine balance, transfer, certificate-issuance and branch-guidance calls dominate volume and queue behind complex cases. Friction today: IVR trees frustrate older callers; simple requests wait for scarce human capacity. | VoiceApp chatKakaoTalk | |||
Loan and mortgage servicing desk Grounded servicing answers at scale during rate events; regulated decisions stay human. | Rate resets and government housing-program changes drive urgent, complex inquiry waves. Friction today: Rate and repayment questions exceed IVR capability and swamp specialists during policy shifts. | VoiceApp chat | |||
Deposit-maturity and retention outreach Every maturing customer gets a conversation with policy-bounded rollover offers; retention measured. | Maturing time deposits are Korea's most contested retention moment as customers rate-shop across banks. Friction today: Outbound maturity calls are capacity-limited; most customers get only an SMS. | VoiceKakaoTalkSMS |
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 Shinhan Bank's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Shinhan Bank: A major bank's contact center justifies multi-workflow scope — everyday service plus loan servicing plus proactive maturity outreach — with the integration depth Scale is built for.
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.
“Branch consolidation only works politically and commercially if service access visibly improves; an honorific-fluent AI phone line is the proof point regulators and older customers will both feel.”
“You've already crossed the AI-banker Rubicon in branches; extending the same posture to the phone estate on a governed platform is the logical next system, architected to FSC cloud rules.”
“Every closed branch reroutes its customers to your phones; agentic capacity absorbs that structural volume shift without rebuilding the cost you just removed.”
“Your queues are rate-event-driven and demographically phone-first; an agent that handles the routine 70% in flawless honorifics changes both your wait times and your staffing model.”
“Deployment is designed to Korea's financial cloud and outsourcing rules: human gates on all regulated decisions, complete logging, and an evaluation framework your audit team can inspect.”
“Branch savings are being partially recaptured by contact-center growth; this closes that leak with a measured cost-per-call number, usage billed on consumption.”
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.
One of Korea's big-four banks, publicly committed to AI-staffed branches and digital shift while consolidating physical branches — a large contact-center estate plus an aging customer base that still calls.
Present a Korea-compliant reference architecture to IT risk, then scope a Scale deployment starting with the everyday banking line ahead of the next rate-change cycle.
Entry: Everyday banking service line (balances, transfers, certificates, branch guidance) · 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.