MalaysiaTelecomLaunch · $50K
CelcomDigi

Two networks became one; now make every subscriber conversation feel like it: post-merger service for CelcomDigi

Win a contained, measurable workflow — dual-brand billing and prepaid service in Malaysia's four languages — and let results argue for the bigger agentic platform conversation.

Entry use case
Dual-brand billing & prepaid service resolution
Expected outcome
Deflect the dominant billing and top-up contact classes across Celcom and Digi brand bases with grounded, multilingual in-channel resolution
Recommended next step
Propose a billing-service pilot on one brand base with cost-per-contact and deflection baselines agreed upfront.
What we understand

CelcomDigi's operating reality

CelcomDigi, formed by the December 2022 merger of Celcom and Digi, is Malaysia's largest mobile operator with roughly 20M subscribers and has publicly completed extensive network integration.

Public fact

CelcomDigi has publicly announced AI collaborations including with AWS (generative AI) and SK Telecom, plus an AI Experience Centre — the AI agenda is real and competitive.

Public fact

Its enterprise arm publicly distributes Google Workspace to business customers, so a commercial Google relationship exists at the reseller level.

Public fact

Dual-brand tariff structures post-merger generate billing-confusion contacts across both legacy bases.

Reasoned inference

Malaysia's multilingual prepaid base (including migrant-worker segments) is underserved by staffed language coverage — a differentiated wedge incumbents' pilots have not claimed.

Seller hypothesis — validate

CelcomDigi's enterprise arm publicly distributes Google Workspace to Malaysian businesses — a commercial Google relationship to build on, though its announced AI collaborations to date run through AWS and SK Telecom.

Publicly reported Google Cloud relevance

Validate with the account team before outreach: Where AWS/SKT collaborations already claim the CX roadmap · BSS consolidation status and API access across legacy stacks · Migrant-segment size and language mix in the prepaid base

Build vs buy

Why we have a right to win here

Partner-led target

Technically capable but needs industry workflows, integration, acceleration, or managed operations

Evidence: CelcomDigi's announced AI moves — AWS generative-AI collaboration, SK Telecom partnership, an AI Experience Centre — are themselves partner-delivered, revealing an orchestrate-not-build posture. Telco platform buying is the norm, and the merger integration consumes the internal engineering capacity that a build would need.

Why they won't build the full stack: BSS consolidation across two legacy stacks is the engineering priority; a conversational platform build would compete for the same people. The open wedge is a bounded, bought workflow that coexists with the incumbent AI tracks.

What management is signalling

Merger integration savings and network-consolidation progress are standing items in results briefings.

Inferencerecent investor communications (validate) · 2025

GTM implication: Position a billing-deflection pilot as integration-synergy delivery with hard baselines — auditable savings, not another AI announcement.

What already exists (don't pitch this)
  • Celcom Life and MyDigi apps across both brand bases
  • AI Experience Centre and announced AWS/SKT AI collaborations
  • IVR and chatbot estate per legacy brand
  • Enterprise arm distributing Google Workspace
What customers still can't do end-to-end (pitch this)
  • →Brand-aware billing answers grounded across both legacy BSS stacks
  • →Bengali, Burmese, and Nepali coverage for the migrant prepaid segment
  • →In-channel top-up and plan-change execution
  • →Deflection and cost-per-contact attribution against baselines
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Dual-brand billing & top-up service
Line-recognized, brand-aware billing answers in four languages with in-conversation top-up and plan changes.
The largest contact class across 20M subscribers, complicated by two legacy tariff worlds.
Friction today: IVR trees per brand; billing explanations depend on which legacy system the agent knows.
VoiceWhatsAppApp chat
Prepaid migrant-segment support
Self-service in the segment's languages; top-up frequency and churn measured per cohort.
Migrant workers are a loyal, sizeable prepaid segment no roster can serve in Bengali, Burmese, or Nepali.
Friction today: These customers rely on shop intermediaries for basic account tasks.
VoiceWhatsApp
Home-fibre appointment & fault support
Proactive appointment management and guided diagnostics; avoidable dispatches filtered.
Fixed-wireless and fibre growth adds truck-roll economics to the service base.
Friction today: Install reschedules and outage questions require agent calls.
WhatsAppVoice
Watch the change

Dual-brand billing & prepaid service resolution: today vs the agentic model

Scenario: A legacy-Celcom customer disputes a post-merger plan charge; the agent explains it against both tariff structures in Mandarin and applies the goodwill credit policy in one call.
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
VoiceWhatsAppApp chat

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 · CelcomDigi
Converged BSSLegacy billingPaymentsOCSField serviceOSS

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

Trust & languages
Bahasa MalaysiaEnglishMandarinTamil

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

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 CelcomDigi'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 CelcomDigi: Given incumbent AI partnerships, a Launch-scoped pilot on one high-volume workflow with hard baselines is the credible wedge; expansion follows evidence.

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: Converged BSS, Legacy billing, Payments
  • · A named business owner for dual-brand billing & prepaid service resolution
  • · Security review counterpart and policy sign-off (Converged BSS scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“The merger promised Malaysia a better operator, and your AI ambitions are public. A frontline workflow with hard before/after numbers is the fastest way to make both claims visible to subscribers.”

CIO / CTO

“This is a bounded, interoperable pilot — agents grounded in your BSS with clean APIs, coexisting with your AWS and SKT tracks rather than competing with them.”

COO

“Billing deflection across both brand bases from one deployment, measured against your current cost per contact — an operational result inside two quarters.”

Chief Marketing Officer (Consumer)

“Serving prepaid customers in Bengali, Burmese, or Nepali is a segment play nobody in the market has claimed — loyalty in a base competitors treat as churn-commodity.”

Chief Risk / Compliance Officer

“PDPA consent and MCMC consumer-protection expectations enforced in configuration, with full interaction logs across both legacy brand systems.”

CFO / Procurement

“A Launch-scoped engagement priced against one workflow's deflection baseline — small enough to run alongside existing AI programs, measured enough to justify or kill expansion.”

Outreach

Pre-built offer emails for CelcomDigi

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

Malaysia's largest mobile operator (~20M subscribers post Celcom-Digi merger) with public AI ambitions — but its announced AI partnerships run through AWS and SK Telecom, so entry is a focused, outcome-priced workflow win rather than a platform land.

Recommended next step

Propose a billing-service pilot on one brand base with cost-per-contact and deflection baselines agreed upfront.

Entry: Dual-brand billing & prepaid service resolution · 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.