Hong KongTelecomScale · $100K
HKT

One operator, every Hong Kong household — a trilingual agentic frontline for HKT's converged service estate

HKT touches nearly every Hong Kong household across broadband, mobile, TV, home solutions and The Club — but each product line answers its own hotline, and an aging, Cantonese-first customer base still calls for everything from bill questions to router restarts; an agentic frontline that recognizes the household, resolves billing and technical issues in-conversation, and cross-serves the converged bundle turns HKT's product breadth from a service cost multiplier into its retention moat.

Entry use case
Converged billing and plan service line (csl / 1O1O / Netvigator)
Expected outcome
Resolve routine billing, plan and renewal contacts in-conversation across mobile and broadband, cutting cost per contact on the highest-volume lines.
Recommended next step
Workshop with consumer service leadership: baseline cross-product contact volumes and truck-roll rates, then scope a Scale pilot on the converged billing line.
What we understand

HKT's operating reality

HKT, majority-owned by PCCW, is Hong Kong's incumbent telecom operator with the leading fixed broadband base (Netvigator), major mobile brands (csl, 1O1O, Club Sim), Now TV and a broad home and payments ecosystem.

Public fact

The Club, HKT's loyalty and e-commerce platform, spans the group's customer base and gives HKT a household-level relationship beyond connectivity.

Public fact

Hong Kong's telecom market is saturated and fiercely price-competitive; growth comes from bundling, 5G upsell and enterprise, making retention economics central.

Public fact

An aging population skews a meaningful share of the base to Cantonese-first phone service; HKT has publicly leaned into 'silver' services for elderly customers.

Reasoned inference

Product-line hotlines (mobile, broadband, TV) likely operate as separate service stacks, so one household generates multiple uncoordinated service relationships.

Seller hypothesis — validate

Contract-renewal windows drive churn-decisive conversations that outbound capacity cannot fully cover.

Reasoned inference

Validate with the account team before outreach: How service operations are split across product lines today · Incumbent CCaaS and chatbot vendors and contract timelines · Truck-roll volumes and avoidable-visit share · Renewal-window coverage rates by outbound capacity

Build vs buy

Why we have a right to win here

Buy-led target

Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution

Evidence: HKT is an operator whose technology change runs through network vendors and systems integrators; it markets digital services but has no internal LLM platform program, and trilingual conversational AI across BSS and OSS estates is a capability it will buy and govern.

Why they won't build the full stack: Engineering capacity is committed to network evolution and the converged product estate; building Cantonese-register voice AI in-house has no sponsor in a margin-disciplined operator, while a bought platform with human gates delivers measured billing-line economics this year.

What management is signalling

HKT consistently reports a saturated, price-competitive Hong Kong market where bundling, 5G upsell and cost discipline drive results, alongside steady dividend commitments that reward operating efficiency.

Reported factrecent annual and interim results · 2025

GTM implication: Cost per contact and churn are the two levers management already reports on — anchor the business case directly on both.

Aging-population service demand and 'silver economy' positioning are growing themes in HKT's consumer strategy.

Inferencerecent investor communications (validate) · 2025-2026

GTM implication: Patient Cantonese voice automation is the scalable answer to an older base that will not migrate to apps — validate demographic contact mix with the account team.

What already exists (don't pitch this)
  • My HKT and csl apps with billing and plan self-service
  • The Club loyalty and e-commerce platform across the base
  • Product-line hotlines and IVRs in three languages
  • Netvigator self-help and service-status tools
What customers still can't do end-to-end (pitch this)
  • →Transactional depth — re-bundling, renewals and fixes still route to human queues
  • →Household-level context across mobile, broadband and TV service stacks
  • →Trilingual conversational voice matched to an aging base
  • →Proactive renewal outreach at full-base coverage
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Converged billing and plan service line
One conversation resolves billing and plan questions across the household's services; repeat contacts drop.
Billing questions and plan changes across mobile and broadband are the structural volume of the incumbent's base.
Friction today: Separate hotlines per product line; older customers wait in Cantonese queues for answers that span systems.
VoiceApp chatWhatsApp
Broadband technical triage and visit scheduling
Grounded, device-aware triage resolves routine faults; visits scheduled in-flow only when genuinely needed.
Router, Wi-Fi and set-top issues drive long-AHT technical calls and truck rolls for problems often fixable in-conversation.
Friction today: Technical scripts read by generalist agents; engineer visits booked for issues a guided restart would fix.
VoiceApp chat
Contract-renewal and win-back outreach
Every renewal-window customer gets a conversation with policy-bounded offers; save rate measured weekly.
In a saturated market, the renewal window is where the bundle either compounds or breaks apart.
Friction today: Outbound renewal calls are capacity-limited; lapsing contracts get an SMS at best.
VoiceWhatsAppSMS
Watch the change

Converged billing and plan service line (csl / 1O1O / Netvigator): today vs the agentic model

Scenario: A retired Netvigator-and-csl household calls about a bill that rose after a promotion expired; the agent, in patient Cantonese, explains the change, re-bundles within the approved matrix, fixes the Wi-Fi complaint with a guided router check, and confirms the new monthly total — one call, two product lines, no transfer.
Today
same interaction, two worlds
Agentic layer
Languages served
2–3 staffed
10+ in one deployment
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
  • · Languages served: Platform capability: Gemini + Chirp speech
  • · 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 chatWhatsAppSMS

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 · HKT
BSSBillingCRMOSS / network diagnosticsField-service schedulingOffer matrix

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

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 HKT'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 HKT: Billing service plus broadband technical triage plus contract-renewal retention are three well-bounded workflows across a shared customer base — multi-workflow Scale scope with BSS and OSS integration depth.

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: BSS, Billing, CRM
  • · A named business owner for converged billing and plan service line (csl / 1o1o / netvigator)
  • · Security review counterpart and policy sign-off (BSS scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“HKT's moat is the converged household; a frontline that actually serves the household as one relationship — in its own language — is the operational expression of the bundle strategy.”

CIO / CTO

“A governed agent layer over BSS and diagnostics APIs replaces a patchwork of product-line IVRs with one platform decision — bounded integration, full auditability, PDPO-grade controls.”

COO

“Truck rolls and long technical calls for restart-grade faults are your quietest cost leak; in-conversation triage cuts both while freeing engineers for real faults.”

Head of Consumer / Customer Service

“Your base skews older and phone-first exactly as service labor gets scarcer; elastic Cantonese-quality capacity is the staffing model that tracks your demographics.”

Chief Risk / Compliance Officer

“PDPO-aligned processing, approved-offer enforcement on renewals, 100% logging — auditability across every product-line conversation, not sampled QA.”

CFO / Procurement

“Saturated-market economics make cost per contact and churn the two numbers that move EBITDA; the pilot measures both against your baseline in one quarter.”

Outreach

Pre-built offer emails for HKT

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 incumbent converged operator — mobile (csl, 1O1O), the city's largest fixed broadband base, pay-TV, payments and The Club loyalty — a household-penetrating service estate with trilingual volume across every product line.

30 / 60 / 90-day plan
  • Day 0–30: Workshop with consumer service leadership: baseline cross-product contact volumes and truck-roll rates, then scope a Scale pilot on the converged billing line.; confirm sponsor and baseline data access; validate: How service operations are split across product lines today
  • 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; converged billing and plan service line (csl / 1o1o / netvigator) pilot in build; success thresholds locked with the Head of Consumer / Customer Service
Recommended next step

Workshop with consumer service leadership: baseline cross-product contact volumes and truck-roll rates, then scope a Scale pilot on the converged billing line.

Entry: Converged billing and plan service line (csl / 1O1O / Netvigator) · 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.