CLP serves the large majority of Hong Kong's households and businesses under a regulated-return regime where service quality is a public obligation and cost discipline a permanent one — and the energy transition keeps adding billing complexity: new tariffs, rebates, feed-in payments, EV charging and efficiency programs; an agentic frontline that explains bills in plain Cantonese, executes account changes in-conversation and scales through typhoon-outage inquiry spikes is the service model that matches both the regulatory bargain and the demographic reality.
CLP Power supplies electricity to Kowloon, the New Territories and most of Hong Kong's population under the Scheme of Control framework agreed with the government.
Public factThe Scheme of Control ties permitted returns to assets and obligations, with tariff adjustments and customer-facing performance politically visible at every review.
Public factDecarbonization commitments and energy-transition programs — feed-in tariffs, efficiency subsidies, EV infrastructure — are adding product and billing complexity to a once-simple utility relationship.
Public factThe residential base includes a large elderly, Cantonese-first segment for whom phone remains the only real service channel; bill-shock moments after tariff changes drive contact waves.
Reasoned inferenceTyphoon and extreme-weather events create outage-inquiry spikes that fixed hotline capacity absorbs badly.
Reasoned inferenceMove-in/move-out account churn in a dense rental market generates steady transactional volume well-suited to in-conversation completion.
Seller hypothesis — validateValidate with the account team before outreach: Actual billing-line volumes and tariff-change contact multipliers · Outage-day inquiry spikes and current absorption capacity · Regulatory or Scheme-of-Control considerations on automated customer communication · Incumbent contact-center stack and refresh timeline
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: CLP is an asset-and-operations utility whose IT runs through vendors and integrators; it has digital-utility initiatives but no internal AI platform capability, and Cantonese-first conversational AI is a straightforward governed procurement.
Why they won't build the full stack: Utility engineering is committed to grid reliability and decarbonization capex; building voice AI in-house is outside every regulated mandate, while a bought platform with human gates delivers measurable service economics a Scheme-of-Control review can point to.
CLP operates under the Scheme of Control with tariff adjustments and customer-facing performance publicly scrutinized, while decarbonization investment raises the political sensitivity of customer bills.
GTM implication: Bill-explanation quality and service cost are both regulator-visible — sell the frontline as service improvement and efficiency in one regulated-era package.
Energy-transition programs are adding billing and product complexity that drives explanation-heavy contact volume.
GTM implication: Each new program adds conversation load — position the platform as the adoption channel for the transition agenda itself.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Billing and account service line Bills explained in plain Cantonese and changes executed in-conversation; queues and repeat contacts drop. | Bill explanation, tariff questions, payment arrangements and move-in/move-out changes are the structural volume of millions of accounts. Friction today: Older callers queue for bill explanations; account changes require forms and callbacks. | VoiceApp chatWeb | |||
Outage and typhoon inquiry surge line Live, consistent outage-status conversations at unlimited capacity; crews communicated about, not interrupted. | Extreme-weather response is the utility's most public service moment and its worst capacity mismatch. Friction today: Outage-day call spikes melt the hotline exactly when accurate restoration answers matter most. | VoiceSMSApp chat | |||
Energy-transition program outreach Program eligibility explained and applications guided in-conversation; adoption measured per campaign. | Feed-in tariff, efficiency-subsidy and EV-charging programs need explanation-heavy adoption conversations at scale. Friction today: Program awareness runs on leaflets and web pages; interested customers can't get questions answered easily. | VoiceWhatsAppWeb |
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 CLP Power's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for CLP Power: A focused pilot on the billing and account line — the dominant volume class — proves economics fast in a conservative, regulated utility before expanding to outage communication and program outreach.
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 Scheme of Control bargain is reliability plus reasonable cost plus visible service; agentic Cantonese-first service is the customer-facing proof point that the transition era isn't coming at customers' expense.”
“A governed agent layer over CIS and outage systems modernizes the service surface without touching regulated core systems — bounded integration, PDPO-grade controls, full auditability.”
“Tariff-change waves and typhoon spikes are your two worst staffing problems; elastic capacity absorbs both without carrying peak cost year-round.”
“Bill-explanation calls dominate your queues and defeat your IVR; an agent that explains charges patiently in Cantonese changes satisfaction and handle economics at once.”
“Approved-language enforcement on tariff and program explanations, human gates on hardship arrangements, 100% logging — regulator-ready evidence of consistent customer treatment.”
“Under regulated returns, operating efficiency is the lever you own; a Launch pilot quantifies cost per resolved contact against baseline in one quarter with bounded spend.”
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.
Hong Kong's largest electricity utility serving Kowloon and the New Territories under the Scheme of Control — millions of accounts, an energy-transition agenda adding tariff and product complexity, and an aging, Cantonese-first customer base that calls.
Launch-scoped proposal to customer service leadership: pilot the billing and account line ahead of the next tariff-adjustment announcement, measured on resolution rate and cost per contact.
Entry: Billing and account service line · Launch package · 8–10 weeks to a live, measured pilot. 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.