Rebuild AirAsia's guest-support economics with agentic disruption handling, refund transparency, and MOVE super-app service — on the Google Cloud estate the group already runs.
Capital A (formerly AirAsia Group) spans the AirAsia airlines, the airasia MOVE travel super-app, BigPay fintech, and Teleport logistics; the group's aviation consolidation under the AirAsia Group structure has been publicly executed.
Public factAirAsia has a publicly reported, long-standing Google Cloud relationship, with cloud and data initiatives repeatedly showcased by both companies.
Public factPost-pandemic refund backlogs made AirAsia's refund-status opacity a publicly visible complaint theme — the scar tissue makes refund transparency a brand-repair lever, not just a cost line.
Public factThe existing AVA chatbot era taught the group both the value and the limits of scripted automation; guest frustration with deflection-style bots is well documented in app reviews.
Reasoned inferenceMOVE's OTA ambitions (hotels, rides, bundles) add non-flight service volume the airline-shaped support organization was never designed for.
Reasoned inferenceAirAsia's Google Cloud relationship is publicly reported and long-standing — the group has showcased cloud and data work with Google for years, making the platform conversation an extension, not a sale.
Publicly reported Google Cloud relevanceValidate with the account team before outreach: Current in-house chatbot roadmap and where it falls short · PSS and refund-pipeline API access across AOCs · Which market's disruption profile suits the pilot best
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: Despite the group's digital identity, its engineering is consumer-product-focused (MOVE, BigPay) and capital-disciplined after restructuring. The in-house AVA chatbot era demonstrated the limits of scripted self-build in guest support, and the long Google Cloud relationship makes buying on the existing estate the path of least resistance.
Why they won't build the full stack: Restructuring discipline caps platform-engineering spend, and guest-support economics need fixing now — before the next disruption season, not after a two-year build. Usage-based capacity also matches the spiky cost profile an LCC group cannot staff for.
Publicly completed restructuring, including PN17 status resolution and aviation consolidation under the AirAsia Group structure, with cost discipline and fleet reactivation central to the investor story.
GTM implication: Position usage-based support capacity as restructuring-aligned: fixed service cost becomes variable, and refund transparency repairs a publicly known complaint class.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Disruption rebooking & communication Affected guests messaged proactively with live rebooking options; one-tap confirmation; spike absorbed elastically. | Multi-AOC LCC operations concentrate disruption pain; lean staffing means spikes melt every channel at once. Friction today: Guests discover delays at the gate and queue in chat behind thousands of identical questions. | AppWhatsAppEmailVoice | |||
Refund status & case transparency Live, stage-by-stage refund status pushed proactively; repeat contacts and regulator complaints suppressed. | The historically dominant complaint class; opacity here taxes every new booking decision. Friction today: Cases cross airline entities and payment channels; status answers are vague by construction. | App chatWhatsAppEmail | |||
MOVE super-app service Product-aware resolution across flight and non-flight bookings in one conversation. | OTA-style bookings (hotels, bundles) now generate service volume needing OTA-grade support the group must build anyway. Friction today: Flight-shaped support processes mishandle hotel and bundle issues. | App chatWhatsApp |
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 Capital A (AirAsia)'s measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Capital A (AirAsia): Disruption, refunds, and MOVE service across app, WhatsApp, and voice — multi-airline AOCs and multiple languages — need a multi-workflow deployment; the existing cloud relationship accelerates integration.
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.
“AirAsia's story is digital disruption of travel — guest support is the chapter where the story has lagged the ambition. Agentic disruption handling closes that gap visibly, on the cloud you already bet on.”
“Your Google Cloud estate makes this an extension: Gemini Enterprise agents grounded in the PSS and refund pipeline, with Tilicho Labs handling the communications and integration layer.”
“Disruption days stop being all-hands failures — proactive rebooking suppresses the spike, and your teams handle only complex itineraries and duty-of-care calls.”
“Refund status becomes something guests watch, not chase. That single change removes your largest complaint class and its social-media shadow.”
“Consumer-protection obligations across multiple aviation jurisdictions handled with consistent policy application and complete logs — MAVCOM-style complaint reviews get evidence on demand.”
“Support staffing sized for disruption peaks is capital wasted 350 days a year; usage-based conversational capacity matches spend to actual disruption minutes.”
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 AirAsia group is one of Asia's largest LCC operations with a publicly long-standing Google Cloud relationship and an explicit digital ambition (airasia MOVE, BigPay, Teleport) — disruption support and super-app service are both structural needs.
Workshop with group guest-services leadership to baseline refund-status contact volume and scope a disruption-rebooking pilot on one AOC.
Entry: Disruption rebooking & refund-status resolution · 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.