VietnamBroadband / ISP & pay-TVLaunch · $50K
FPT Telecom

Fewer truck rolls, faster fixes: agentic broadband support for FPT Telecom's fiber and FPT Play base

Deploy a Vietnamese-first agentic service layer for outage communication, guided diagnostics, and appointment management — cutting avoidable truck rolls and repeat fault calls across the fiber base.

Entry use case
Fault diagnosis & outage communication
Expected outcome
Deflect repeat outage calls with proactive updates and resolve router-level issues conversationally before dispatching technicians
Recommended next step
Quantify outage-window repeat-call volume with the care team and scope a one-region fault-handling pilot on Zalo.
What we understand

FPT Telecom's operating reality

FPT Telecom, part of FPT Corporation, is one of Vietnam's leading broadband providers with millions of fiber subscribers plus the FPT Play TV/streaming service and the Hi FPT self-care app.

Public fact

Parent FPT Corporation is itself a major technology-services exporter with publicly announced AI investments — internal build appetite is real, which shapes how to position an external platform.

Public fact

ISP contact volume concentrates in outage windows: one neighborhood fault generates hundreds of identical calls that proactive messaging could suppress.

Reasoned inference

A meaningful share of technician dispatches are avoidable router-restart or configuration issues resolvable in a guided conversation.

Reasoned inference

Bundled upsell (broadband + FPT Play + camera) via service conversations is an untested revenue lever.

Seller hypothesis — validate

Validate with the account team before outreach: OSS/network-status API availability for area-level outage detection · Share of dispatches closed with no physical fault found · Group-level build-vs-buy stance on conversational AI

Build vs buy

Why we have a right to win here

Co-build target

Strong internal engineering — sell infrastructure, models, governance, or selected capabilities

Evidence: Parent FPT's FPT.AI already sells conversational AI — chatbots and voicebots — commercially in Vietnam; the group will not buy a competing stack. The realistic entry is selling Gemini model quality, multilingual speech, and governance capabilities that slot inside FPT.AI-run deployments rather than displacing them.

Why they won't build the full stack: FPT does build — but frontier-model reasoning, production evaluation frameworks, and elastic multilingual speech are capabilities FPT.AI cannot replicate economically. Co-building keeps FPT the platform owner while Google supplies the intelligence layer, which the group can also resell.

What management is signalling

FPT Corporation publicly reports double-digit technology-services growth and heavy AI investment, including an announced AI-factory partnership with NVIDIA.

Reported factFPT public results announcements · 2024–2025

GTM implication: Position Gemini models and governance inside the group's own AI stack — a story FPT can resell to its clients, not a platform displacement it will resist.

What already exists (don't pitch this)
  • FPT.AI conversational platform (commercial chatbots and voicebots)
  • Hi FPT self-care app
  • In-house call-center operations
  • Group-level AI investment programs
What customers still can't do end-to-end (pitch this)
  • →Frontier-model reasoning for multi-step fault diagnostics
  • →Production-grade evaluation and governance tooling for 100% scoring
  • →Agentic action execution in OSS/field-service systems beyond scripted flows
  • →Elastic speech quality under outage-storm load
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Fault diagnosis & outage communication
Proactive outage notices by area, guided diagnostics in Vietnamese, dispatch only when physically necessary.
Outage-window call storms and avoidable truck rolls are the two largest controllable costs in ISP service.
Friction today: Customers call repeatedly during outages; agents re-explain the same status; simple faults still create dispatches.
ZaloVoiceHi FPT app
Appointment & installation management
Confirmations with one-tap reschedule against live technician calendars.
Missed installation windows waste technician capacity and start relationships badly.
Friction today: Reschedules require calls; no-shows are discovered at the door.
ZaloSMSVoice
Billing & retention conversations
Policy-bounded renewal offers in two-way conversations; save rates attributed.
Contract-end churn in competitive urban areas is offer-sensitive and time-sensitive.
Friction today: Retention outreach is capacity-limited and untargeted.
ZaloVoice
Watch the change

Fault diagnosis & outage communication: today vs the agentic model

Scenario: A district-level fiber cut triggers proactive Zalo notices to every affected home; the agent handles 'when will it be fixed' individually while dispatch works the splice.
Today
same interaction, two worlds
Agentic layer
First-contact resolution
deferred via tickets
in-conversation actions
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
  • · First-contact resolution: Process design: agent acts in systems of record
  • · 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
ZaloVoiceHi FPT appSMS

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 · FPT Telecom
OSS/network statusTicketingField-service schedulingBillingCRMOffer matrix

API access to these systems is the critical-path dependency.

Trust & languages
VietnameseEnglish

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.5M
Seller assumption — replace in discovery
Current cost per interaction ($)$0.6
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$900K
Current operating cost / mo
$2.5M
Modelled gross benefit / yr
0.2 mo
Payback on Launch
71%
3-yr ROI (modelled)
Automated/assisted interactions per month825K
Modelled AI run-cost per month (usage + cloud, system estimate)$289K
New monthly operating cost$694K

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 FPT Telecom's measured baseline. Package price covers implementation only; recurring usage billed separately.

Recommended package

Launch — $50K implementation

Launch · $50K · A focused, fast production pilot8–10 weeks to a live, measured pilot

Why this package for FPT Telecom: A single high-volume workflow (fault and outage handling) with one OSS/ticketing integration is the fastest credible proof inside a technically sophisticated group.

Included
  • Up to 3 channels
  • One priority workflow
  • Limited enterprise integrations (1–2 systems)
  • API credential & security setup
  • Core conversational + workflow configuration
  • Basic analytics
  • Controlled production pilot with defined success criteria
Not included
  • ✕Usage & consumption (billed separately)
  • ✕Additional workflows
  • ✕Multi-geography rollout
  • ✕Managed operations
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: OSS/network status, Ticketing, Field-service scheduling
  • · A named business owner for fault diagnosis & outage communication
  • · Security review counterpart and policy sign-off (OSS/network status scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“FPT sells digital transformation to the world; your own subscriber experience is the reference case. An agentic service layer makes FPT Telecom the group's flagship AI-operations story.”

CIO / CTO

“This complements the group's AI stack rather than replacing it — Gemini-grounded agents on your OSS and ticketing systems, deployable in weeks, with your teams owning the roadmap.”

COO

“Truck rolls are your unit-cost anchor. Guided diagnostics that filter avoidable dispatches pay for the platform on their own.”

Head of Customer Care

“Outage days stop being all-hands emergencies: proactive area notices suppress the storm, and your agents handle only the cases that need judgment.”

Chief Risk / Compliance Officer

“Consent-governed Zalo outreach under Decree 13, with complete interaction logs — proactive messaging that stays inside Vietnam's data-protection lines.”

CFO / Procurement

“A fixed-scope Launch pilot measured on two numbers you already track: repeat-call rate during outages and avoidable-dispatch share.”

Outreach

Pre-built offer emails for FPT Telecom

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 3 — longer-term / partner-led

Why this tier

Major Vietnamese ISP with millions of broadband and FPT Play subscribers; strong inbound-service fit, but deal size is moderate and the FPT group's own AI ambitions mean the entry must position Tilicho + Gemini as accelerant, not competitor.

Recommended next step

Quantify outage-window repeat-call volume with the care team and scope a one-region fault-handling pilot on Zalo.

Entry: Fault diagnosis & outage communication · Launch package · 8–10 weeks to a live, measured pilot. 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.