Integration is a communications problem at national scale: network migrations, plan changes, and churn risk across three brands. An agentic layer absorbs the surge and defends the synergy case.
XL Axiata and Smartfren completed their merger in April 2025, forming XLSmart, Indonesia's third telco with roughly 73M subscribers and 2025 revenue around Rp42.5 trillion.
Public factManagement has publicly emphasized integration milestones and synergy targets, with network and brand consolidation progressing through 2025–2026.
Public factNetwork consolidation means cell-site changes and plan migrations that customers experience as dropped coverage and confusing SMS — a classic churn trigger.
Reasoned inferenceThree consumer brands (XL, Axis, Smartfren) mean fragmented care stacks and duplicated BPO contracts that the synergy case must rationalize.
Reasoned inferenceSynergy pressure makes opex-per-subscriber the most receptive metric in the building right now.
Seller hypothesis — validateValidate with the account team before outreach: Which legacy care stack (XL or Smartfren) survives, and its API readiness · Migration calendar and the regions with the highest churn exposure · Existing BPO contracts' terms and exit windows
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: A freshly merged operator mid-integration has no engineering bandwidth for a conversational-AI build — network and stack consolidation consume the roadmap; XLSmart will buy outcomes that defend the synergy case it reports to shareholders.
Why they won't build the full stack: Building during integration would put an internal platform project on the critical path of merger synergies; a partner layer above three legacy care stacks delivers a unified frontline now and keeps stack consolidation a backend decision instead of a customer-facing risk.
Post-merger communications emphasize integration milestones and synergy delivery, implying opex-per-subscriber and churn-versus-plan are the metrics leadership is judged on quarter to quarter.
GTM implication: Sell into the synergy bridge: consumption-priced conversations replacing duplicated BPO contracts is a reportable synergy line item.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Migration & transition communications Two-way proactive conversations that explain each subscriber's specific change and resolve follow-ups instantly. | Every migrated site and sunset plan generates confusion contacts and churn risk that the synergy model did not fully price. Friction today: One-way SMS blasts; confused subscribers flood call centers or silently port out. | WhatsAppVoiceSMS | |||
Recharge & billing service across brands A single governed conversation layer serving all three brands' balance, package, and payment intents. | One agentic layer over three brands' charging stacks is faster than harmonizing three care operations first. Friction today: Separate IVRs, apps, and BPO desks per legacy brand. | VoiceWhatsAppIn-app | |||
Port-out save desk Immediate conversational intervention on port-out signals with matrix-bounded offers. | Merger uncertainty is a competitor acquisition campaign waiting to happen. Friction today: Port-out signals surface too late for capacity-limited save teams. | VoiceWhatsApp |
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 XLSmart (XL Axiata–Smartfren)'s measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for XLSmart (XL Axiata–Smartfren): Migration comms plus recharge/billing service across merged brands is a two-to-three-workflow, multi-channel deployment — squarely a Scale engagement during the integration window.
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 market is judging XLSmart on integration execution. Subscriber-facing migration conversations done well are the most visible execution proof there is.”
“One agentic layer above three legacy care stacks gives you a unified frontline now, and makes the eventual stack consolidation a backend decision instead of a customer-facing risk.”
“Every network cutover has a contact-volume shadow. Proactive two-way comms shrink that shadow and keep your BPO seats flat through the migration calendar.”
“Churn above plan is the silent killer of merger math. Attributed save conversations give you a lever you can actually pull, week by week.”
“Consistent, logged, consent-governed messaging across all three brands eliminates the conduct variance of three separate care operations.”
“This substitutes consumption-priced conversations for duplicated BPO contracts — a direct line item in the synergy bridge you report to shareholders.”
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 April 2025 merger created a ~73M-subscriber #3 in active integration — network migration, brand consolidation, and synergy targets make communication volume and cost pressure spike simultaneously.
Brief the integration office: map the next two quarters' network-migration calendar to a proactive-communications pilot in one region.
Entry: Network-migration and plan-transition communications · 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.