Jetstar's whole model strips cost from every process except one: customer support still costs the same per call as a full-service airline; an agentic frontline that rebooks, refunds and answers at software cost is the missing piece of the LCC equation — and the shield that keeps lean staffing from becoming a headline every time weather hits.
Jetstar is the Qantas Group's low-cost carrier, flying domestic Australia and NZ, trans-Tasman and Asian routes, with a Japan joint venture — its brand promise is low fares enabled by relentless cost control.
Public factThe Qantas Group consolidated its LCC footprint, closing Singapore-based Jetstar Asia in 2025, sharpening focus on ANZ and Japan operations.
Public factThe Qantas Group suffered a major 2025 data incident traced through a third-party contact-center platform, putting vendor security architecture under board-level scrutiny.
Public factLCC unit economics make support cost-per-contact a first-order metric: a single human call can exceed the margin on a discounted fare.
Reasoned inferenceDisruption events (weather, ATC, engineering) create 10x contact spikes that a lean-staffed LCC absorbs worse than a full-service carrier.
Reasoned inferenceRefund and credit-voucher status queries likely form a large repeat-contact tail after every disruption wave.
Seller hypothesis — validateValidate with the account team before outreach: Qantas Group vendor-security requirements post the 2025 incident · Current disruption-day contact multipliers and abandonment rates · Group-level CX platform decisions shared with Qantas mainline
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: An LCC's entire operating philosophy is to buy proven capability cheaply rather than build it: Jetstar runs lean engineering focused on the booking funnel and ancillary revenue, and the Qantas Group's post-incident vendor-security reset favors a small number of governed, auditable platforms over internal experiments.
Why they won't build the full stack: Jetstar has neither the engineering bench nor the economic rationale to build conversational AI — every internal build competes with fares-and-ancillary product work, and disruption-day capacity is needed now, not after a multi-year platform program; a security-vetted buy is the only path consistent with LCC cost discipline.
The Qantas Group's multi-year transformation program has emphasized structural cost reduction and customer-experience remediation, with the 2025 third-party contact-center data incident putting vendor security architecture under board-level scrutiny.
GTM implication: Lead with governance: a security-vetted, fully-audited platform answers the board's post-incident question while delivering the LCC cost-per-contact math.
Group commentary continues to position Jetstar as the growth engine for price-sensitive and Asian leisure demand, with fleet renewal expanding capacity.
GTM implication: Growth on lean staffing widens the support-capacity gap — sell elastic disruption absorption as the enabler of Jetstar's expansion without linear headcount.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Disruption rebooking and refund-status service Proactive rebooking offers in-channel, live refund status, and disruption spikes absorbed without queue melt. | Disruption days define Jetstar's public reputation and are exactly when lean staffing fails hardest. Friction today: Cancellations trigger call floods; rebooking requires agents while refund-status calls recur for weeks after. | App chatSMSVoiceWeb | |||
Everyday booking-change and ancillary service Self-serve changes with correct fees applied in-conversation; human queue shrinks to genuine exceptions. | Changes, baggage and seat questions are the routine volume behind the fare-plus-ancillary model. Friction today: Fee rules and fare-difference math push simple changes into human queues. | App chatWebVoice | |||
Japan and Asia route multilingual desk Native-quality Japanese and English service at software cost across the network. | Jetstar Japan and Asian routes serve customers whose expectations are set by Japanese service standards, on an LCC budget. Friction today: Japanese-language support capacity is scarce and expensive relative to LCC economics. | App chatVoice |
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 Jetstar (Qantas Group)'s measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Jetstar (Qantas Group): Disruption handling plus everyday booking service across app, web and voice is classic Scale scope, with clean airline-system integration boundaries (PSS, disruption feeds, payments).
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.
“Jetstar strips cost from everything except conversations; agentic service completes the LCC model — and turns disruption days from brand damage into proof the low-fare promise includes being looked after.”
“Post the group's third-party contact-center incident, a governed platform with strict data boundaries and full auditability is the architecture answer to a question the board is already asking.”
“You staff for the median day and melt on the bad ones; elastic agentic capacity absorbs the 10x disruption spike without carrying that cost the other 350 days.”
“Refund-status repeat calls are your longest tail after every event; live status in-channel deletes that queue, and proactive rebooking deletes most of the rest.”
“Australian Privacy Act-aligned processing, tight vendor-data boundaries and 100% interaction logging — designed for a group that has just rewritten its third-party risk standards.”
“When a human call can cost more than the fare margin, automation is the unit-economics fix; the pilot proves cost per resolved contact against your own LCC 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.
The Qantas Group's LCC lives on cost discipline — cost-per-contact matters far more here than at the full-service mainline — and disruption events routinely melt its lean support capacity across Australia, NZ and Asia.
Scope a disruption-readiness pilot with Jetstar customer care: instrument one route bank, deploy proactive rebooking and refund-status flows before the next summer-storm season.
Entry: Disruption rebooking and refund-status service · 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.