VietnamTelecom / conglomerateTransform · $200K
Viettel

70 million subscribers, ten markets, one conversation layer: agentic service for the Viettel group

Give Viettel a sovereign-deployable agentic communications platform that serves prepaid billing, retention, and enterprise support at home — then travels to Metfone, Unitel, Mytel and its other international carriers.

Entry use case
Prepaid balance, package & recharge conversations
Expected outcome
Shift the highest-volume contact class to in-channel resolution and in-conversation recharge, at a cost per contact that respects prepaid ARPU
Recommended next step
Executive briefing with Viettel Telecom and Viettel IDC on a sovereign-aligned reference architecture, then scope a prepaid-recharge pilot in one region.
What we understand

Viettel's operating reality

Viettel is Vietnam's largest mobile operator, military-owned, with roughly 70M domestic subscribers and international operations in around 10 markets including Metfone (Cambodia), Unitel (Laos), Mytel (Myanmar) and African carriers.

Public fact

Google and Viettel have publicly announced cooperation on cloud and AI, and Viettel IDC operates as an authorized Google Cloud partner/reseller in Vietnam.

Public fact

Viettel positions itself as Vietnam's sovereign-technology champion — Viettel Cloud, Viettel AI — so deployment architecture must respect in-country hosting and national-champion optics.

Public fact

A predominantly prepaid base means billing, package, and recharge questions dominate contact volume at a cost per human call that can exceed monthly ARPU.

Reasoned inference

One agentic platform standardized in Vietnam then replicated to international OpCos would let Viettel amortize the build across ten markets and a dozen languages.

Seller hypothesis — validate

Viettel Money and digital-services growth adds a compliance-sensitive fintech support surface under SBV oversight.

Reasoned inference

Google–Viettel cooperation on cloud and AI is publicly announced, and Viettel IDC is an authorized Google Cloud partner in Vietnam — a rare pre-existing bridge into a sovereign-minded state champion.

Publicly reported Google Cloud relevance

Validate with the account team before outreach: Sovereignty requirements: which components must run on Viettel Cloud · Contact-volume split across mobile, broadband, and Viettel Money · Which international OpCo would pilot replication first

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: Viettel operates its own AI arm (Viettel AI, including Vietnamese speech and chatbot products), Viettel Cloud, and a sovereign-technology mandate — it will insist on owning meaningful parts of any stack it deploys at national scale. The winnable ground is Gemini model quality, multilingual speech, and governance tooling embedded into Viettel-operated platforms, not a turnkey platform sale.

Why they won't build the full stack: Even with real AI teams, production-grade agentic orchestration, evaluation, and action execution grounded in BSS at 70M-subscriber scale is faster co-built than built alone — and Viettel's ambition to export capability to ten OpCos benefits from a hardened partner layer it can operate under its own brand.

What management is signalling

As a military-owned state champion, Viettel publicly frames AI, semiconductors, and sovereign cloud as national-mission investment areas rather than quarterly earnings levers.

Inferencerecent public statements (validate) · 2025

GTM implication: Sell a sovereign co-build Viettel can claim and export — Gemini and governance inside Viettel-branded infrastructure, not a vendor platform on top of it.

What already exists (don't pitch this)
  • Viettel AI's own Vietnamese ASR/TTS and chatbot products
  • Viettel Cloud sovereign infrastructure
  • My Viettel self-care app
  • Large in-house call-center operations
What customers still can't do end-to-end (pitch this)
  • →Agentic action execution grounded in BSS/OCS rather than scripted bots
  • →Evaluation and governance tooling for 100% interaction scoring
  • →Khmer, Lao, Burmese and other OpCo language coverage from one deployment
  • →Replication architecture across international OpCos
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Prepaid billing & recharge
Line-recognized answers and in-conversation recharge in Vietnamese; lapse-prevention nudges under consent rules.
The single largest contact class across ~70M subscribers; every human-handled balance call destroys prepaid margin.
Friction today: DTMF IVR plus overloaded hotlines; recharge requires channel-switching that drops conversions.
VoiceZaloSMSApp chat
Churn-risk retention
Two-way retention conversations with offers from an approved matrix; save-rate attributed per cohort.
MNP competition with VNPT and MobiFone concentrates on high-ARPU segments.
Friction today: SMS blasts and capacity-limited outbound teams reach a fraction of the at-risk base.
VoiceZalo
Broadband install & fault support
Proactive outage and appointment updates; guided diagnostics that avoid avoidable truck rolls.
FTTH growth is a strategic revenue line; truck rolls and repeat fault calls are its cost anchor.
Friction today: Dispatch status is opaque; customers call repeatedly for the same outage.
ZaloVoice
Enterprise & SME service desk
Entitlement-aware enterprise support with SLA-tracked escalation.
Viettel Solutions sells digital transformation to government and enterprise; its own service experience is the demo.
Friction today: B2B tickets flow through email and account managers with no conversational front door.
VoiceWeb chatEmail
Watch the change

Prepaid balance, package & recharge conversations: today vs the agentic model

Scenario: A prepaid subscriber's data pack expires mid-month; the agent explains usage in Vietnamese, offers the right renewal, and completes recharge in the same Zalo thread.
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
VoiceZaloSMSApp chatWeb chatEmail

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 · Viettel
BSS/OCSPayment gatewayCRMChurn modelOffer matrixOSS/field serviceTicketingB2B CRM

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

Trust & languages
VietnameseEnglishKhmerLaoBurmese

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 interactions8.0M
Seller assumption — replace in discovery
Current cost per interaction ($)$0.6
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$4.8M
Current operating cost / mo
$13.2M
Modelled gross benefit / yr
0.2 mo
Payback on Transform
71%
3-yr ROI (modelled)
Automated/assisted interactions per month4.4M
Modelled AI run-cost per month (usage + cloud, system estimate)$1.5M
New monthly operating cost$3.7M

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

Recommended package

Transform — $200K implementation

Transform · $200K · A broader enterprise deployment14–20 weeks phased across units

Why this package for Viettel: Multiple business units (mobile, broadband, Viettel Money, enterprise) and a multi-country replication path warrant an enterprise deployment with a governance framework from day one.

Included
  • 7–10 channels
  • Multiple inbound + outbound workflows
  • Complex enterprise integrations
  • Multiple business units or geographies
  • Advanced agent orchestration
  • Enterprise grounding
  • Governance & evaluation framework
  • Role-based human supervision
  • Custom analytics & optimization
  • Production hardening + managed rollout plan
Not included
  • ✕Usage & consumption (billed separately)
  • ✕Ongoing managed operations (contracted separately)
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/OCS, Payment gateway, CRM
  • · A named business owner for prepaid balance, package & recharge conversations
  • · Security review counterpart and policy sign-off (BSS/OCS scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“Viettel industrializes national technology. An agentic service layer built here and exported to your ten OpCos is exactly that story — Vietnamese engineering serving tens of millions across Asia and Africa.”

CIO / CTO

“The Google–Viettel cooperation and Viettel IDC partnership give us an architecture path that respects sovereignty: sovereign-deployable components where required, Gemini intelligence where permitted.”

COO

“Peak-day call volumes stop dictating headcount. Elastic conversational capacity absorbs promo and outage spikes across mobile and broadband from one platform.”

Director, Viettel Telecom Customer Care

“Balance and package calls leave your queues; your agents keep complex complaints with full context. Every conversation is scored — coaching finally has data.”

Chief Risk / Compliance Officer

“Consent-governed outreach, in-country data handling under Decree 13, and complete interaction logs — auditable by design across every OpCo you replicate to.”

CFO / Procurement

“At prepaid ARPU, human-assisted contacts are structurally uneconomic. This moves the dominant contact classes to a cost point that scales across 70 million subscribers — then amortizes again internationally.”

Outreach

Pre-built offer emails for Viettel

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

Vietnam's largest telecom with ~70M domestic subscribers plus international carriers across Asia and Africa; an existing public Google–Viettel cloud/AI cooperation and a state-champion mandate to industrialize AI make it the anchor Vietnam account.

30 / 60 / 90-day plan
  • Day 0–30: Executive briefing with Viettel Telecom and Viettel IDC on a sovereign-aligned reference architecture, then scope a prepaid-recharge pilot in one region.; confirm sponsor and baseline data access; validate: Sovereignty requirements: which components must run on Viettel Cloud
  • Day 31–60: architecture & security review with the platform team; Tilicho Labs scoping on Voice + Zalo; pilot scope signed
  • Day 61–90: Transform package kickoff; prepaid balance, package & recharge conversations pilot in build; success thresholds locked with the Director, Viettel Telecom Customer Care
Recommended next step

Executive briefing with Viettel Telecom and Viettel IDC on a sovereign-aligned reference architecture, then scope a prepaid-recharge pilot in one region.

Entry: Prepaid balance, package & recharge conversations · Transform package · 14–20 weeks phased across units. 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.