Hana built its franchise on FX and cross-border money movement, which hands it Korea's most multilingual service base — foreign workers, students and businesses banking in a dozen languages — and an agentic frontline that resolves remittance, FX and account servicing in the customer's own language extends Hana's signature strength to the channel where it is weakest today.
Hana Bank anchors Hana Financial Group and holds a leading position in Korean FX and cross-border remittances, historically rooted in the Korea Exchange Bank merger.
Public factHana runs dedicated services for foreign residents — multilingual banking support and remittance products for Korea's growing foreign-worker and student population.
Public factHana One Q is the group's flagship app with broad self-service, but remittance exceptions, documentation questions and FX timing inquiries still generate heavy assisted volume.
Reasoned inferenceKorea's foreign-resident population has passed two million and keeps growing, expanding a service base that Korean-only automation cannot reach.
Public factPIPA plus FX-transaction reporting rules make cross-border servicing conversations compliance-sensitive — an auditability argument for governed automation.
Reasoned inferenceRemittance-status and documentation calls likely spike around holidays in origin-country calendars, straining fixed multilingual staffing.
Seller hypothesis — validateValidate with the account team before outreach: Actual remittance-servicing volumes and language distribution · Hana Financial Group AI initiatives and preferred-vendor positions · FSS/cloud outsourcing route for cross-border conversation processing · Peak-pattern data around origin-country holiday calendars
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: Hana Financial Group invests seriously in digital (Hana One Q, group data initiatives) but has no public program for multilingual conversational-AI infrastructure; its integration capacity is real, so the motion is partner-led — Hana owns systems and journeys, the platform supplies language breadth and governed voice automation.
Why they won't build the full stack: A dozen-language voice frontline at banking-compliance grade is precisely the capability global platforms amortize across customers and a single bank cannot economically build; Hana's engineering is better spent on the payments and FX rails that actually differentiate it.
Hana Financial Group's investor narrative emphasizes fee-income growth, FX/cross-border strength and cost discipline under the Korean Value-up program.
GTM implication: Tie multilingual servicing automation to fee-business growth: better remittance experience compounds the franchise the market already values Hana for.
Korea's foreign-resident population growth keeps expanding the cross-border customer segment Korean banks compete for.
GTM implication: Position language-complete service as the land-grab move in the fastest-growing retail segment in Korean banking.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Remittance and FX servicing line Status, rates and documentation resolved in the customer's language with proactive updates as transfers progress; specialists handle exceptions only. | Cross-border money movement is Hana's franchise; every stuck remittance is a trust moment in the customer's most stressful financial task. Friction today: Status and documentation questions arrive in a dozen languages; multilingual staffing is thin and expensive; repeat calls pile up while transfers clear. | VoiceApp chatKakaoTalk | |||
Foreign-resident onboarding and account servicing Guided onboarding and servicing in the customer's language with documents validated in-flow; completion rises, branch load falls. | The foreign-customer franchise is a growth engine competitors cannot easily copy; onboarding friction in unfamiliar Korean processes is its biggest leak. Friction today: Document requirements confuse non-Korean speakers; visa-status and eligibility questions need staff who speak the customer's language. | App chatVoiceWeb | |||
SME banking service desk SME servicing answered around the clock with live status from trade and payments systems; relationship managers reclaim advisory time. | Hana's SME base generates payments, limit and trade-finance-status inquiries that queue behind retail volume. Friction today: Business owners call outside business hours; trade-document status requires specialist callbacks. | VoiceApp chat |
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 Hana Bank's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Hana Bank: Multilingual remittance servicing plus SME account servicing are two bounded workflows over core and payments integrations — Scale scope with a distinctive language-depth requirement that stresses exactly what the platform does best.
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.
“Hana's identity is cross-border banking; serving every remittance customer in their own language at any hour is that identity made operational — a franchise moat competitors with Korean-only service cannot cross.”
“One governed agent layer above payments, FX and core systems delivers a dozen languages from a single deployment — no multilingual staffing model can match that architecture, and it benchmarks cleanly against any internal build.”
“Multilingual agents are the scarcest, most expensive staff in your centers; elastic language capacity removes your hardest hiring problem while holiday remittance spikes stop melting queues.”
“The foreign-resident franchise grows with Korea's demographics; onboarding and servicing in the customer's language is the single biggest conversion and retention lever you control.”
“FX and remittance conversations carry reporting obligations; 100% logged, script-governed interactions in every language provide compliance evidence sampled QA cannot — PIPA-aligned throughout.”
“Multilingual service today costs a premium per contact; the pilot measures per-contact cost and repeat-call reduction on the remittance line against your own baseline, 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.
Korea's leading FX and cross-border bank inside Hana Financial Group, with the Hana One Q app estate, a large SME franchise and the country's strongest foreign-customer banking business — a distinctive multilingual service problem no Korean rival shares at the same scale.
Remittance-line workshop with global-business and operations leadership: baseline language mix and repeat-contact rates, then pilot the remittance-status workflow in the top three foreign-customer languages.
Entry: Remittance and FX servicing line (rates, tracking, documentation) · 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.