LG Uplus already chose Gemini for its consumer AI agent ixi-O, which makes the strategic argument for a Gemini-powered service frontline internal consistency rather than vendor persuasion; deploying agentic automation on its billing, retention and technical queues turns the challenger carrier's AI-agent brand into operational economics — the third player's classic path to margin parity with SKT and KT.
LG Uplus, the LG-affiliated #3 Korean carrier, has publicly committed to transforming into an 'AX company', with announced multi-billion-dollar AI investment plans.
Public factLG Uplus's ixi-O AI call assistant publicly integrates Google's Gemini models under an announced partnership, and its ixi-GEN model builds on LG Group's Exaone LLM for telecom-specific services.
Public factAs the #3 carrier, LG Uplus runs structurally thinner margins than SKT and per-subscriber economics that reward cost automation more than either rival.
Reasoned inferenceThe consumer AI-agent strategy (ixi-O on smartphones) is a brand differentiator aimed at younger subscribers — service-experience quality is part of the same positioning.
Public factBundle billing across mobile, broadband and IPTV generates the same legacy-complex volume as its larger rivals but with less internal platform capacity to automate it.
Reasoned inferenceRetention outreach likely covers only a fraction of expiring-contract cohorts on current outbound capacity.
Seller hypothesis — validateLG Uplus has publicly announced a partnership with Google to integrate Gemini models into its ixi-O AI call assistant — a named, public Google AI relationship this proposal extends into service operations.
Publicly reported Google Cloud relevanceValidate with the account team before outreach: Scope and exclusivity of the existing Google/Gemini partnership around ixi-O · Which service workflows LG Uplus plans to automate with ixi-GEN internally · Retention-cohort sizes and current save-desk coverage · LG Group (Exaone) platform preferences in procurement
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: LG Uplus builds real AI assets — ixi-GEN on LG's Exaone, the ixi-O agent — but has publicly chosen to power ixi-O with Google's Gemini rather than build frontier models alone; that pattern is exactly partner-led: LG Uplus owns product and brand, partners supply model and platform depth, and the frontline deployment extends a partnership that already exists.
Why they won't build the full stack: The #3 carrier cannot outspend SKT's and KT's internal AI programs; its published strategy is leverage — LG Exaone plus Google Gemini plus partners — and a bought agentic frontline on that same pattern delivers margin relief quarters sooner than any internal platform could.
LG Uplus has publicly committed roughly $2 billion to its AX transformation and showcased its ixi-O agent strategy — including the Gemini integration — at successive Mobile World Congress events.
GTM implication: The frontline proposal is the operational chapter of a strategy already announced — sell continuity, not conversion.
As Korea's #3 carrier, LG Uplus faces persistent margin and ARPU pressure in a saturated market, with cost efficiency a recurring investor theme.
GTM implication: Lead with per-contact economics: the thinnest-margin carrier gains the most from every automated conversation.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Billing and plan service line Billing and plan changes resolved in-conversation with transactions executed; peak absorption at usage pricing. | Routine billing is the #3 carrier's structural volume, carried at margins thinner than either rival's. Friction today: Billing-cycle peaks melt queues; plan-change journeys break between app and phone; per-contact costs pressure a tighter P&L. | VoiceApp chatKakaoTalk | |||
Retention and contract-renewal desk Full expiring-cohort coverage with policy-bounded offers; port-out economics measurably bent. | In a saturated three-carrier market, expiring-contract cohorts are the revenue battlefield; coverage decides share. Friction today: Save teams reach a fraction of at-risk subscribers; number-portability makes switching frictionless for competitors to harvest. | KakaoTalkVoiceSMS | |||
Broadband and IPTV technical triage Diagnosis with line data in-conversation, guided fixes, dispatches reserved for hardware failures. | Home-connectivity issues drive long handle times and truck rolls a diagnosing agent can often prevent. Friction today: Scripted triage misdiagnoses; truck rolls dispatch for software-fixable issues. | VoiceApp chat |
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 LG Uplus's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for LG Uplus: Billing service plus retention are two urgent workflows for a #3 carrier fighting for margin; Scale's multi-channel scope fits, and the existing Google AI relationship shortens the architecture conversation.
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.
“LG Uplus told the market it is becoming an AX company and chose Gemini for its flagship consumer agent; running the same intelligence on your own frontline is the operational proof of that strategy — and the margin lever a #3 carrier needs most.”
“Your architecture already speaks Gemini through ixi-O; extending governed agentic automation to service queues rides the same model family and partnership rails — the shortest integration path in Korean telecom.”
“Thinner margins make your per-contact economics the most automation-rewarded of the three carriers; elastic capacity on billing and triage cuts the cost base SKT and KT can outspend you on.”
“Peak-day queue melt and truck rolls for software problems are your two worst numbers; a diagnosing, transacting agent attacks both in one deployment.”
“PIPA-aligned outreach windows, approved-offer governance and 100% logging — retention automation with conduct evidence built in from day one.”
“The pilot measures cost per contact and save-rate lift against your own baselines within a quarter; usage pricing means the cost curve tracks volume, not headcount plans.”
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.
Korea's #3 carrier has publicly built its AI-agent strategy on Google's Gemini — the ixi-O call assistant integrates Gemini models under a announced Google partnership — making it the one Korean telco where a Gemini-powered frontline extends an existing, public technology bet rather than fighting an internal stack.
Strategy-alignment session with AX and customer-service leadership: position the frontline deployment as the operational extension of the announced Gemini partnership, then baseline the billing line for a Scale pilot.
Entry: Billing and plan service line · 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.