Hong KongBankingScale · $100K
Hang Seng Bank

The bank Hong Kong grew up with, now wholly inside HSBC — a trilingual agentic frontline for Hang Seng's integration era

Hang Seng serves a huge, loyal, older-skewing Hong Kong retail base that still banks by phone and branch in Cantonese; with the HSBC privatization complete and integration economics under the spotlight, an agentic frontline that resolves everyday banking in native Cantonese, English and Mandarin is the visible service upgrade that makes branch-era cost structures modernizable without abandoning the customers who built the bank.

Entry use case
Everyday banking service line (balances, cards, transfers, branch guidance)
Expected outcome
Resolve the routine majority of phone banking in-conversation in the caller's language, cutting queues for the older customers most affected by branch rationalization.
Recommended next step
Present an HKMA-aligned reference architecture to retail banking and risk leadership, then scope a Scale pilot on the everyday banking line ahead of the next deposit-rate cycle.
What we understand

Hang Seng Bank's operating reality

Hang Seng Bank is one of Hong Kong's largest locally headquartered banks, with a retail base in the millions, a dense branch network and the brand that compiles the Hang Seng Index.

Public fact

HSBC completed the privatization of Hang Seng Bank in January 2026, buying out minority shareholders and delisting the bank — making it a wholly-owned subsidiary inside the HSBC Group.

Public fact

Hang Seng's recent results were weighed down by elevated credit provisions tied to Hong Kong commercial real estate, keeping cost discipline and efficiency publicly in focus.

Public fact

The customer base skews older and Cantonese-first; phone and branch remain the binding channels for deposits, cards and wealth servicing even as apps improve.

Reasoned inference

Post-privatization integration will pressure the bank to show service continuity while unifying operations with HSBC standards — a politically visible balance in Hong Kong.

Reasoned inference

Time-deposit maturity waves and rate changes likely drive contact spikes that fixed phone-bank staffing absorbs badly.

Seller hypothesis — validate

Validate with the account team before outreach: How post-privatization integration affects vendor selection and whether HSBC group platforms are mandated · Actual phone-channel demographics and volumes by queue · HKMA posture on automated conversations for regulated banking workflows · Incumbent contact-center and IVR estate and its refresh timeline

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: Hang Seng inherits HSBC group technology standards and real digital capability, but its own engineering is channel- and integration-focused with no internal LLM platform; it needs a partner for trilingual voice quality, HKMA-compliant architecture and contact-center-scale delivery inside group governance.

Why they won't build the full stack: Integration with HSBC will consume internal change capacity for years, and Cantonese-register voice AI at banking-compliance grade is specialist ground; a governed platform with human gates delivers measurable service and cost results this year while the group decides its long-term stack.

What management is signalling

HSBC completed its privatization of Hang Seng Bank in January 2026 with strong shareholder approval, delisting the bank and absorbing it as a wholly-owned subsidiary.

Reported factpublic announcements and scheme documents · Jan 2026

GTM implication: Integration puts cost synergy and operating-model decisions on the table now — sell the agentic frontline as a bookable efficiency that visibly improves service during a sensitive transition.

Hang Seng's recent reporting has been marked by elevated expected-credit-loss provisions tied to Hong Kong commercial real estate exposure, keeping profitability and cost discipline under scrutiny.

Reported factrecent results announcements · 2025

GTM implication: Frame service automation as a controllable cost lever in a year when credit costs are not controllable.

Branch rationalization and an aging depositor base are shifting structural volume to phone channels.

Inferencerecent investor communications (validate) · 2025-2026

GTM implication: Quantify the phone-channel volume shift with the account team and anchor the pilot on the everyday banking line.

What already exists (don't pitch this)
  • Hang Seng Mobile App with broad self-service and investment functions
  • IVR phone banking in Cantonese, English and Mandarin
  • Chatbot deflection (HARO virtual assistant) on common FAQs
  • Dense branch network with staged rationalization underway
What customers still can't do end-to-end (pitch this)
  • →Transactional depth on voice — transfers, rollovers and card fixes still route to human queues
  • →Natural-language trilingual service for the older, phone-first base
  • →Proactive deposit-maturity outreach beyond SMS
  • →Cross-channel context between branch, app and phone
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Everyday banking service line
Routine phone banking resolved in natural Cantonese, English or Mandarin; human bankers reserved for advice and exceptions.
Balance, card, transfer and branch-guidance calls dominate volume and queue behind complex cases on the same trilingual lines.
Friction today: IVR trees frustrate older Cantonese-first callers; simple requests wait for scarce human capacity across three languages.
VoiceApp chatWeb
Time-deposit maturity and retention outreach
Every maturing depositor gets a conversation with policy-bounded rollover options; retention measured and attributed.
Hong Kong depositors rate-shop aggressively at maturity; every un-contacted customer is a balance at risk to a rival's promotional rate.
Friction today: Outbound maturity calls are capacity-limited; most customers get only an SMS or letter.
VoiceSMSApp chat
Card and payments dispute desk
Structured intake in-conversation with proactive status; human decisions on every chargeback judgment.
Card servicing and dispute intake are high-emotion, compliance-heavy contact classes that inflate handle times.
Friction today: Dispute intake requires forms and callbacks; status inquiries recur for weeks.
VoiceApp chat
Watch the change

Everyday banking service line (balances, cards, transfers, branch guidance): today vs the agentic model

Scenario: A 67-year-old depositor calls about a maturing time deposit after her local branch consolidated; the agent, in natural Cantonese, verifies identity, explains rollover options from the approved product set, executes her choice in core banking and books a branch appointment for the wealth question that deserves a human.
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 chatWebSMS

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 · Hang Seng Bank
Core bankingCard systemsCRMDeposit systemsOffer matrixDispute management

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

Trust & languages
CantoneseEnglishMandarin

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.2M
Seller assumption — replace in discovery
Current cost per interaction ($)$6.0
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$7.2M
Current operating cost / mo
$44.7M
Modelled gross benefit / yr
0.0 mo
Payback on Scale
1594%
3-yr ROI (modelled)
Automated/assisted interactions per month660K
Modelled AI run-cost per month (usage + cloud, system estimate)$231K
New monthly operating cost$3.5M

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

Recommended package

Scale — $100K implementation

Scale · $100K · A multi-channel production deployment10–14 weeks to production across priority workflows

Why this package for Hang Seng Bank: A major retail bank's phone estate justifies multi-workflow scope — everyday service, card servicing and time-deposit maturity outreach — with the core-banking integration depth Scale is built for.

Included
  • 4–6 channels
  • 2–3 priority workflows
  • Multiple enterprise integrations
  • API credential & security setup
  • Advanced orchestration
  • Multilingual support
  • Agent Assist / human escalation
  • Production analytics
  • Expansion roadmap
Not included
  • ✕Usage & consumption (billed separately)
  • ✕Enterprise-wide governance build-out
  • ✕Multi-BU rollout
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, Card systems, CRM
  • · A named business owner for everyday banking service line (balances, cards, transfers, branch guidance)
  • · 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

“Privatization put Hang Seng's cost base and service model on HSBC's agenda; a trilingual agentic frontline is the modernization story that improves service for your most loyal customers while integration reshapes everything behind them.”

CIO / CTO

“A governed agent layer over core banking and card APIs can be architected to HSBC group standards from day one — bounded integration, full audit trails, no dependency on the legacy IVR estate you're likely to retire.”

COO

“Branch rationalization reroutes older customers to your phones; elastic Cantonese-first capacity absorbs that structural shift without rebuilding the cost you're removing.”

Head of Retail Banking / Contact Center

“Your queues are rate-event-driven and demographically phone-first; an agent that resolves the routine 70% in flawless Cantonese changes wait times and staffing economics at once.”

Chief Risk / Compliance Officer

“HKMA-aligned deployment: human gates on regulated decisions, PDPO-compliant processing, 100% conversation logging — stronger evidence than sampled QA, designed for group audit.”

CFO / Procurement

“Integration economics will be scrutinized line by line; a measured cost-per-call reduction on the everyday banking line is a synergy you can book without touching frontline service quality.”

Outreach

Pre-built offer emails for Hang Seng 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

Hong Kong's flagship local retail bank — millions of customers, a dense branch-plus-phone service estate, and a just-completed HSBC privatization that puts cost synergy and service modernization explicitly on the agenda.

30 / 60 / 90-day plan
  • Day 0–30: Present an HKMA-aligned reference architecture to retail banking and risk leadership, then scope a Scale pilot on the everyday banking line ahead of the next deposit-rate cycle.; confirm sponsor and baseline data access; validate: How post-privatization integration affects vendor selection and whether HSBC group platforms are mandated
  • Day 31–60: architecture & security review with the platform team; Tilicho Labs scoping on Voice + App chat; pilot scope signed
  • Day 61–90: Scale package kickoff; everyday banking service line (balances, cards, transfers, branch guidance) pilot in build; success thresholds locked with the Head of Retail Banking / Contact Center
Recommended next step

Present an HKMA-aligned reference architecture to retail banking and risk leadership, then scope a Scale pilot on the everyday banking line ahead of the next deposit-rate cycle.

Entry: Everyday banking service line (balances, cards, transfers, branch guidance) · Scale package · 10–14 weeks to production across priority workflows. 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.