Taiwan Mobile's strategy stitches mobile service to the broader ecosystem around it — e-commerce, content, payments — which multiplies the reasons customers contact it while merger-absorbed Taiwan Star subscribers still generate integration questions; an agentic frontline that resolves billing, migration and bundle servicing in-conversation converts the #2 operator's ecosystem ambition from service burden into retention machine.
Taiwan Mobile is Taiwan's #2 mobile operator, closely associated with the Fubon group, and completed its merger with Taiwan Star as the market consolidated from five operators to three.
Public factThe company's strategy publicly links telecom with e-commerce (momo), content and financial-service partnerships — a 'telco-plus' ecosystem model.
Public factMerger-absorbed Taiwan Star subscribers required plan migrations and network transitions, generating a multi-year tail of integration service volume.
Reasoned inferenceThree-operator consolidation intensified retention stakes: every port-out in a saturated market is a zero-sum loss to exactly two rivals.
Reasoned inferenceTaiwan Mobile has public AI ambitions including partnerships for AI infrastructure and consumer AI services.
Public factEcosystem bundles (telecom + momo benefits + payments) likely generate cross-service billing questions no single support desk fully owns.
Seller hypothesis — validateValidate with the account team before outreach: Expiring-cohort sizes and current save-desk coverage · Taiwan Star migration-inquiry volumes and remaining integration calendar · Group AI-infrastructure initiatives and their consumer-service ambitions · PDPA boundaries for ecosystem-data use in retention offers
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: Taiwan Mobile has public AI ambitions and group-level technology investments, but its consumer-AI work targets products and infrastructure, not frontline voice automation in Traditional Chinese and Hokkien; the motion is partner-led — Taiwan Mobile owns ecosystem integration, the platform supplies conversational depth, benchmarked against group initiatives.
Why they won't build the full stack: A #2 operator consolidating a merger while funding ecosystem expansion cannot also fund frontier-grade conversational infrastructure; the retention clock in a three-operator market rewards coverage this year, and a bought platform delivers it quarters before any internal program.
Taiwan Mobile's results emphasize merger-synergy capture from the Taiwan Star integration and growth in its telco-plus ecosystem businesses.
GTM implication: Frame service automation as synergy capture plus ecosystem enablement — both lanes management already reports progress on.
Saturated-market competition among Taiwan's three consolidated operators keeps ARPU defense and retention economics central to the investment story.
GTM implication: Lead with retention coverage: in a three-player market, saved subscribers are the cleanest revenue math available.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Billing and plan service line Billing and plan servicing resolved in-conversation with migrations explained policy-exactly; peaks absorbed elastically. | Routine billing is the structural volume; merger-migrated subscribers add mapping and benefit-transition questions on top. Friction today: Billing peaks queue; migrated Taiwan Star customers hit plan-mapping confusion; bundle benefits span systems. | VoiceApp chatLINE | |||
Retention and contract-renewal desk Full expiring-cohort coverage with policy-bounded offers that bundle ecosystem benefits; port-out economics measurably bent. | In a three-operator market, expiring cohorts decide share; coverage beats offer generosity. Friction today: Save teams reach a fraction of expiring contracts; ecosystem benefits that could anchor retention go unmentioned in rushed calls. | LINEVoiceSMS | |||
Ecosystem bundle service desk Bundle questions resolved in one conversation with governed access to ecosystem benefit rules; the telco-plus promise feels seamless. | Telco-plus bundles are the differentiation; their cross-service questions are the friction tax. Friction today: momo-benefit, payment and content questions bounce between telecom support and ecosystem partners. | App chatLINEVoice |
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 Taiwan Mobile's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Taiwan Mobile: Billing servicing plus retention are two urgent workflows for a consolidating #2 operator; Scale fits, with ecosystem-service expansion once core telecom automation proves out.
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 telco-plus strategy multiplies customer touchpoints; an agentic frontline that serves them all in one conversation is the operating model that makes the ecosystem thesis profitable rather than expensive.”
“A governed agent layer above BSS and ecosystem benefit systems delivers converged service without waiting for converged IT — and benchmarks cleanly against any group AI initiative.”
“Merger-migration volume and billing peaks stack on baseline; usage-priced elastic capacity matches the integration curve and scales down as it completes.”
“Retention coverage is the #2 operator's share defense; reaching every expiring contract with ecosystem-bundled offers is the growth lever staffing has never allowed.”
“PDPA-governed use of ecosystem data in offers, approved-matrix boundaries and 100% logging — retention automation with conduct evidence built in.”
“The pilot measures save-rate lift and cost per contact against your own baselines within a quarter; for a #2 operator's margins, per-contact economics compound fastest.”
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 #2 mobile operator — part of the Fubon group orbit — absorbed Taiwan Star in the market's three-way consolidation and runs a telecom-plus-ecosystem strategy (momo e-commerce ties, content, fintech links) whose cross-service customer base multiplies service surfaces faster than staffing can follow.
Retention-economics workshop with consumer-business leadership: baseline expiring-cohort coverage and migration-inquiry volumes, then pilot the renewal desk on the next expiring cohort.
Entry: Billing and plan service line (mobile and bundle servicing) · 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.