Cathay's strategic asset is breadth — a customer can hold Cathay life policies, bank accounts, cards and funds — but its service reality is entity silos, where each subsidiary's desk starts from zero; an agentic frontline with governed cross-entity context, serving customers in Traditional Chinese and Taiwanese Hokkien, turns the holding-company structure from a service liability into the cross-sell machine the fee-income strategy needs.
Cathay Financial Holdings is Taiwan's largest financial holding company, anchored by Cathay Life — one of Taiwan's biggest insurers with a large exclusive agent force — and Cathay United Bank, a top retail bank.
Public factTaiwanese FHCs' publicly-stated strategies emphasize fee-income growth (wealth management, bancassurance) and cross-subsidiary synergies — both dependent on service experience across entities.
Public factTaiwan's aging society and phone-first older customers make Traditional Chinese voice quality — and Taiwanese Hokkien for older southern customers — a hard service bar automation has not met.
Reasoned inferenceTaiwan's Personal Data Protection Act (PDPA) governs cross-entity data use within FHCs, making governed, consent-aware context sharing a compliance design problem.
Public factCathay has publicly invested in digital transformation and data infrastructure across the group, including cloud adoption and a large technology organization.
Public factPolicy-servicing and claims-status volume at Cathay Life likely dominates group service contacts, with bancassurance questions spanning entities.
Seller hypothesis — validateValidate with the account team before outreach: Actual servicing volumes by subsidiary and language preference (Mandarin vs Hokkien) · Group digital-transformation program priorities and internal AI initiatives · PDPA and FSC posture on cross-entity data use and cloud AI processing · Incumbent contact-center stacks per subsidiary
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: Cathay runs one of Taiwan's largest financial technology organizations and a public digital-transformation program, so it will engage as a technical partner — but its build focus is data infrastructure and digital channels, not agentic voice in Traditional Chinese and Hokkien; the motion is partner-led with Cathay owning integration and consent architecture.
Why they won't build the full stack: Hokkien-capable, insurance-compliant voice automation is a specialization no single FHC can economically build and maintain against frontier model velocity; Cathay's engineering creates more value on the consent and integration architecture only it can own, over a bought conversational layer benchmarked for quality.
Cathay Financial's results emphasize recovery in life-insurance fundamentals alongside growth in banking fee income from wealth-management products.
GTM implication: Attach the service layer to the fee-income story: cross-entity experience is the operational bottleneck of the bancassurance and wealth strategy.
Taiwan's listed FHCs collectively posted record profits in the first half of 2026, giving the largest groups budget headroom for strategic technology investment.
GTM implication: Time the Transform proposal to a strong-earnings budget cycle — capacity to invest is publicly evident.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Cathay Life policy servicing desk Routine servicing resolved in Traditional Chinese or Taiwanese Hokkien with documents guided in-flow; agents and desks refocus on advice and claims. | Taiwan's largest in-force book generates the group's largest servicing volume — premiums, policy loans, beneficiary changes, claims status. Friction today: Older policyholders navigate IVR in a service register that matters; routine changes need agent visits or callbacks; Hokkien-preferring customers get Mandarin-only automation. | VoiceLINEApp chat | |||
Cathay United Bank service line Routine bank servicing resolved in-conversation with PDPA-governed awareness of the group relationship; licensed matters route to humans with context. | The bank's retail base overlaps the life book; card, account and wealth-servicing volume carries the same demographics. Friction today: Card and account servicing queues at peaks; wealth-product questions need licensed callbacks; context from the life relationship is invisible. | VoiceApp chatLINE | |||
Bancassurance and cross-entity journey desk Cross-entity journeys handled in one conversation under consent governance; the group finally feels like one Cathay. | Fee-income strategy runs through bancassurance; journeys that cross entities are where customers fall between desks. Friction today: A policy bought at the bank generates servicing questions neither entity's desk fully owns; transfers restart context. | VoiceLINEApp 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 Cathay Financial Holdings's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Cathay Financial Holdings: The group's ambition — consistent service across life, bank and securities entities — is inherently multi-BU: Transform scope, phased from Cathay Life servicing into bank and cross-entity journeys.
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.
“The holding-company thesis is breadth; service that carries context across life, bank and securities under proper governance is that thesis made real for the customer — and the fee-income engine depends on it.”
“One governed agent layer above subsidiary systems, with PDPA consent architecture built in, gives the group a shared conversational asset — deployed entity by entity on the integration rails your digital program already built.”
“Each subsidiary staffs its own peaks and its own language coverage; a shared elastic frontline pools that capacity and adds Hokkien voice quality no entity can justify staffing alone.”
“Your servicing desks and agent force carry Taiwan's largest in-force book; automating routine servicing in the customer's own language — including Hokkien — is the biggest single relief valve available.”
“Cross-entity context runs only through governed consent flows with 100% logging — a PDPA posture stronger than today's manual transfers, with licensed-matter routing enforced by policy, not agent memory.”
“The pilot measures cost per servicing contact at Cathay Life against your baseline; consolidation economics compound as each subsidiary joins the shared layer.”
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.
Taiwan's largest financial holding company spans Cathay Life's massive agent-driven insurance book, Cathay United Bank's retail franchise and asset-management arms — the deepest cross-sell surface in Taiwanese finance, and with it the deepest cross-entity service complexity.
Group-level briefing with digital and Cathay Life operations leadership: agree the PDPA consent architecture for cross-entity context, then pilot the policy-servicing desk with Hokkien voice acceptance testing.
Entry: Cathay Life policy servicing desk (premium, policy-loan, claims-status inquiries) · Transform package · 14–20 weeks phased across units. 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.