The Asiana integration hands Korean Air the region's hardest service problem: every schedule consolidation, mileage conversion and cabin-product change generates confused, anxious contacts from two loyalty bases at once; an agentic frontline that rebooks across both networks and answers SKYPASS-conversion questions consistently is the difference between an integration passengers forgive and one they punish.
Korean Air completed its acquisition of Asiana Airlines and is absorbing the brand, with the combined mega-carrier operating under the Korean Air name and Asiana's operations folding in through 2026-2027.
Public factMileage integration is politically sensitive: Korea's FTC has publicly intervened on the Asiana-to-SKYPASS conversion terms, ordering revisions to protect Asiana members' interests.
Public factIntegrating fleets, schedules and cabin products creates a multi-year wave of itinerary changes, equipment swaps and policy questions across both customer bases.
Reasoned inferenceKorean honorific service register and Japanese/Chinese/English visitor-language coverage are simultaneous quality bars for a carrier hubbing Incheon transfer traffic.
Reasoned inferenceIntegration-period contact volume likely runs multiples of baseline, with mileage-conversion and schedule-change questions dominating queues.
Seller hypothesis — validateLCC subsidiaries (Jin Air absorbing Air Busan and Air Seoul) add a parallel low-cost integration with its own service surge.
Public factValidate with the account team before outreach: Integration-milestone calendar and expected inquiry waves by phase · FTC-approved conversion terms status and how policy updates propagate to service channels · Incumbent contact-center stacks on both the Korean Air and former-Asiana estates · PIPA and aviation-regulatory constraints on automated outbound to affected passengers
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: Korean Air is an operations-first flag carrier whose IT change runs through the PSS estate and system integrators, with its technology capacity now consumed by the largest airline-systems integration in Korean history — there is no internal AI-platform program, making conversational AI a clear governed buy timed to the merger.
Why they won't build the full stack: No airline mid-merger builds conversational-AI infrastructure: every engineering hour is committed to consolidating two PSS, loyalty and operations estates under regulatory deadlines; a bought platform rides above both estates and delivers integration-period capacity now, then scales down as the surge passes.
Korean Air's Asiana integration is proceeding on a public timeline — brand absorption through end-2026, combined mega-carrier launch targeted for 2027 — with Korea's FTC publicly ordering revisions to the Asiana mileage-conversion plan to protect members.
GTM implication: The mileage-conversion desk is a compliance-critical, board-visible workflow with a hard external clock — sell policy-exact automated answers as regulatory risk management, not just cost reduction.
Integration costs and merger-period operational complexity likely pressure margins through the combined-carrier launch window.
GTM implication: Position usage-based agentic capacity as the merger-shaped cost model: absorbs the surge, no permanent headcount, measurable per integration milestone.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Mileage-integration and SKYPASS conversion desk Policy-exact conversion answers at unlimited capacity, updated centrally the day rules change; complex cases escalate with full context. | Mileage conversion is the most emotionally charged, FTC-watched element of the merger; inconsistent answers become regulatory and press incidents. Friction today: Conversion ratios, elite-status mapping and award-seat questions flood queues; answers vary by agent and change as FTC-ordered revisions land. | VoiceApp chatKakaoTalkWeb | |||
Integration rebooking and schedule-change service Proactive schedule-change outreach with rebooking options in-channel; call waves absorbed without integration-period surge hiring. | Network consolidation re-times and re-equips thousands of itineraries; every change is a contact from a passenger who didn't choose it. Friction today: Schedule-change notifications trigger call waves; rebooking across two PSS estates requires specialist agents. | App chatSMSVoice | |||
Disruption rebooking and refund-status service Proactive disruption rebooking in Korean, English, Japanese and Mandarin; refund status self-served in-channel. | Business-as-usual disruption still runs underneath the merger; queues doubled by integration questions melt on weather days. Friction today: Disruption spikes stack on integration volume; refund-status repeat calls persist for weeks after each event. | App chatSMSVoice |
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 Korean Air's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Korean Air: Integration touches every service surface at once — loyalty migration, network-consolidation rebooking, disruption handling across two fleets — justifying a multi-workflow enterprise deployment timed to the merger calendar.
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 merger's success will be judged by whether two loyalty bases feel kept or captured; consistent, instantly available integration service is the cheapest trust insurance the combined carrier can buy — and the FTC is watching exactly this.”
“You're consolidating two PSS and loyalty estates anyway; a governed agent layer above both gives passengers one consistent conversational front while the systems merge underneath on their own timeline.”
“Integration volume stacks on baseline operations for years; elastic agentic capacity absorbs the merger surge without hiring a workforce you must shed when integration completes.”
“Mileage-conversion questions are your queue-melter and your compliance risk; an agent that gives policy-exact answers updated centrally the day FTC revisions land removes both at once.”
“With the FTC actively supervising conversion terms, 100% logged, script-governed conversations are regulatory evidence — auditability no surge-hired human floor can match, PIPA-aligned throughout.”
“Integration service costs are one-time-shaped but multi-year long; usage-based agentic capacity matches the curve exactly, and the pilot measures cost per integration contact against your own baseline.”
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 flag carrier is executing the Asiana absorption — two fleets, two loyalty programs and two service organizations merging into one mega-carrier under FTC scrutiny — a once-in-a-generation surge of disruption, rebooking and loyalty-migration service volume.
Integration-program briefing with SKYPASS and service leadership: baseline conversion-inquiry volumes, then scope a Transform deployment timed to the next mileage-integration milestone.
Entry: Mileage-integration and SKYPASS conversion desk · Transform package · 14–20 weeks phased across units. 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.