Taishin built Richart into the digital bank young Taiwan actually uses, then took on a transformative merger integration — a combination that multiplies service volume while its digital-native base tolerates queues least; an agentic frontline that resolves servicing instantly in-channel is the only service model that matches both the Richart brand promise and the integration workload.
Taishin Financial's Richart is Taiwan's leading digital-banking brand by users, built on a young, app-native customer base and playful brand identity.
Public factTaishin completed a landmark merger with Shin Kong Financial, materially enlarging its insurance and banking franchise and creating a multi-year integration workload.
Public factDigital-native customers contact support less often but expect instant, in-app resolution when they do — queues and callbacks break the brand contract.
Reasoned inferenceMerger integrations generate confused-customer volume — account migrations, product mappings, branding changes — layered on baseline service.
Reasoned inferencePDPA governs cross-entity data use during integration, making governed context handling a compliance requirement, not just a CX feature.
Public factThe absorbed Shin Kong life-insurance base skews older and phone-first — the demographic opposite of Richart — forcing Taishin to serve both extremes at once.
Reasoned inferenceValidate with the account team before outreach: Integration-milestone calendar and projected inquiry waves · Richart platform architecture and in-app support integration points · PDPA/FSC constraints on cross-entity context during integration · Absorbed Shin Kong book's service volumes and channel mix
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: Taishin's Richart proves real digital product capability, but the organization's engineering is consumed by the Shin Kong integration — the largest systems consolidation in its history; the motion is partner-led: Taishin owns digital product and integration, the platform supplies conversational capacity through the merger window.
Why they won't build the full stack: No FHC mid-merger builds conversational-AI infrastructure; every engineering hour is committed to estate consolidation under regulatory timelines, while the integration itself generates the service surge that needs capacity now — a bought layer rides above both estates and scales down as integration completes.
Taishin's merger with Shin Kong Financial created one of Taiwan's larger FHCs, with integration synergies and execution now the central investor question.
GTM implication: Sell service consolidation as a measurable synergy line — the integration story investors are scoring management on.
Richart's digital-banking leadership remains Taishin's public differentiation in a market of larger balance sheets.
GTM implication: Position instant agentic service as the Richart brand promise operationalized — retention infrastructure for the franchise's crown jewel.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Richart and retail servicing line Servicing resolved in-conversation at Richart speed with transactions executed; human chat reserved for exceptions. | The digital-native base is the franchise; instant in-channel resolution is the brand promise service must keep. Friction today: App-support and payment questions queue to human chat; peaks follow campaign and salary-day cycles; instant expectation meets callback reality. | App chatLINEVoice | |||
Merger-integration inquiry desk Integration questions answered consistently at unlimited capacity, updated centrally as each milestone lands; complex cases escalate with context. | The Shin Kong integration generates migration questions from millions of customers over a multi-year calendar. Friction today: Account-mapping and product-change questions spike with each integration milestone; answers must be policy-exact and consistent. | VoiceLINEApp chat | |||
Insurance policy servicing desk (absorbed book) Policy servicing resolved by voice at honorific-equivalent Taiwanese courtesy, without building out a legacy call-center estate. | The Shin Kong life book brings older, phone-first policyholders needing voice servicing in Traditional Chinese and Hokkien. Friction today: An older demographic meets a digital-first bank's thinner phone estate; servicing needs conflict with Taishin's channel strategy. | VoiceLINE |
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 Taishin Financial's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Taishin Financial: Digital-banking servicing plus merger-integration support are two urgent workflows; Scale fits an FHC whose service volume is being multiplied by integration while its brand demands instant resolution.
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 merger doubles the franchise while the Richart brand promises instant service; only elastic agentic capacity delivers both — integration absorbed, brand promise kept, no surge workforce to unwind later.”
“You are consolidating two estates anyway; a governed agent layer above both gives customers one consistent conversational front while systems merge underneath on their own timeline.”
“Integration inquiry waves stack on baseline volume for years; usage-priced capacity matches that curve exactly — no permanent cost from temporary volume.”
“Your base churns on friction, not price; instant in-channel resolution is the retention feature that matches how they chose you in the first place.”
“Integration conversations are compliance-sensitive; policy-exact scripted answers with 100% logging give conduct evidence through the FSC-watched merger, PDPA-governed across entities.”
“Merger synergies are the promise your investors priced; service consolidation onto one agentic layer is a synergy line item you can measure by quarter.”
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.
The FHC behind Richart — Taiwan's most successful digital-banking brand with millions of young users — is scaling beyond its mid-size weight after absorbing Shin Kong's franchise, leaving it with a digital-native customer base whose service expectations outrun a mid-size bank's staffing economics.
Integration-calendar session with operations and Richart leadership: map inquiry waves to migration milestones, then pilot the integration inquiry desk before the next major milestone.
Entry: Richart and retail servicing line (account, card, payment and app-support inquiries) · 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.