MTR is Hong Kong's circulatory system — millions of daily rail journeys plus the malls, offices and housing estates built above the stations — and every fare question, lost-property call, tenancy request and disruption inquiry lands on service teams staffed for the median day; an agentic frontline that answers in Cantonese, English or Mandarin, resolves routine transit and tenancy service in-conversation, and scales instantly when incidents spike is how a publicly scrutinized operator keeps service standards visibly rising while costs don't.
MTR Corporation operates Hong Kong's metro network with millions of passenger journeys daily, alongside a rail-plus-property model spanning shopping malls, offices and residential developments.
Public factMTR holds a majority stake in Octopus Holdings, whose stored-value card underpins fares and everyday payments across the city — making MTR adjacent to enormous payment-linked service volume.
Public factService disruptions draw intense public, media and Legco scrutiny, with fare-adjustment mechanisms and performance penalties keeping service standards politically visible.
Public factTourist inflow from the mainland and overseas adds Mandarin- and English-heavy inquiry volume on fares, routes and airport services.
Reasoned inferenceProperty management and mall tenancy generate a parallel service stream — maintenance requests, leasing inquiries, resident services — likely handled by separate teams with separate stacks.
Seller hypothesis — validateLost-property and fare-dispute contacts are high-volume, low-complexity classes ideal for in-conversation resolution.
Reasoned inferenceValidate with the account team before outreach: Actual hotline and station-inquiry volumes and incident-day multipliers · How property-management service is organized and its contact volume · Octopus Holdings' separate service estate and whether it's in scope · Public-sector-style procurement requirements and timelines
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: MTR is an engineering-led operator in rail systems, not software — its digital estate is vendor-built, it has no LLM program, and trilingual conversational AI for passenger and tenant service is a clear governed procurement.
Why they won't build the full stack: Corporate engineering is consumed by railway assets, signalling modernization and property development; building conversational AI in-house is outside every mandate, while a bought platform with human gates delivers visible service improvement the fare-adjustment-era public narrative needs now.
MTR operates under fare-adjustment and service-performance mechanisms that keep fares regulated and service standards publicly scrutinized, while property development funds the model.
GTM implication: Revenue is regulated but cost-to-serve is not — sell measurable service-cost reduction with visibly better passenger service as the politically safe efficiency lever.
Tourism recovery and mainland visitor flows are lifting inquiry volumes in Mandarin and English across the network.
GTM implication: Trilingual elasticity serves the visitor economy Hong Kong is publicly courting — validate visitor-inquiry share with the account team.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Passenger service hotline Routine passenger service resolved in-conversation in three languages; incident spikes absorbed elastically. | Fares, Octopus-linked queries, lost property and service status are the structural volume of a system moving millions daily. Friction today: Peak and incident-day calls queue; tourists hit language mismatches; lost-property follow-ups repeat for days. | VoiceApp chatWeb | |||
Incident and disruption communication Consistent, live service-status conversations at unlimited capacity; staff freed for on-platform response. | Disruption response defines MTR's public reputation and regulatory standing more than any other touchpoint. Friction today: Incident-day inquiry spikes melt hotline capacity exactly when accurate, calm answers matter most. | App chatVoiceSMS | |||
Property and tenant services desk Requests logged, tracked and statused in-conversation; management offices work from structured queues. | Malls, offices and residences above the stations generate maintenance, leasing and resident-service volume year-round. Friction today: Tenant requests route through management-office phone trees and paper-era processes. | 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 MTR Corporation's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for MTR Corporation: Passenger service plus property-tenant servicing are two distinct, well-bounded workflow families across one brand — multi-workflow Scale scope with clean integration boundaries.
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.
“MTR's licence to operate is public confidence; service that answers instantly in three languages — especially on the bad days — is confidence made tangible, at a cost profile the fare mechanism doesn't punish.”
“A governed agent layer over service-status, fare and property APIs consolidates fragmented hotlines into one auditable platform — bounded integrations, no core-system change.”
“You staff for the median day and get judged on the incident day; elastic capacity absorbs the spike while your people handle the platform, not the phones.”
“Lost property, fares and status are your volume; resolving them in-conversation transforms wait times and lets station staff serve passengers face to face.”
“PDPO-aligned processing, approved-language enforcement on incident communication, 100% logging — consistent public messaging with an audit trail, even at spike volume.”
“Fare revenue is regulated; costs are not — measured cost per resolved contact across rail and property service is a controllable line this pilot quantifies in one 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 rail-plus-property operator that moves millions of passengers daily and manages malls, offices and residences across Hong Kong — Octopus-adjacent service volume across transit, tenancy and township life, under permanent public and Legco scrutiny.
Workshop with customer experience leadership: baseline hotline volumes and incident-day multipliers, then scope a Scale pilot on the passenger service line.
Entry: Passenger service hotline (fares, Octopus-linked queries, lost property, service status) · 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.