Air New Zealand's demand is a tourism tide — southern-summer peaks, long-haul dependencies and weather that can strand a day's network — while engine-availability constraints have made every disruption harder to recover; an agentic frontline that rebooks proactively in the languages of its visitor markets absorbs the surges a fixed Auckland contact center cannot, at a cost a mid-sized carrier can defend.
Air New Zealand is the flag carrier hub-and-spoked on Auckland, heavily dependent on inbound tourism and long-haul connections to Asia and North America.
Public factThe airline has faced prolonged fleet-availability pressure from industry-wide engine maintenance issues, publicly cited as constraining capacity and resilience.
Public factAir New Zealand has publicly announced work with OpenAI, one of the first airlines to do so — AI adoption is on-strategy, and vendor pluralism must be the pitch frame.
Public factDemand and disruption both peak in the southern summer, when weather events can cascade across the whole domestic-international connection bank.
Reasoned inferenceVisitor-market passengers (China, Japan, Korea, US) need disruption help in their own languages, which a fixed NZ-based contact center cannot staff economically.
Reasoned inferenceRepeat refund- and credit-status contacts likely form a long tail after each disruption wave.
Seller hypothesis — validateValidate with the account team before outreach: Scope of the OpenAI collaboration and openness to multi-vendor AI · Disruption-day contact multipliers and current multilingual coverage · PSS integration constraints (Amadeus/other) for automated rebooking
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: Air New Zealand is AI-forward for its size — the publicly announced OpenAI collaboration shows appetite and some internal capability — but a mid-sized flag carrier does not build voice platforms; it partners for applied AI, and the pitch frame is vendor pluralism: a benchmarkable Gemini frontline for disruption and multilingual service alongside existing AI commitments.
Why they won't build the full stack: A carrier of this scale cannot fund or staff a production conversational-AI platform on top of fleet-constraint firefighting; its AI collaborations are applied-use-case partnerships, not platform builds, and seasonal surge capacity in Mandarin, Japanese and Korean is precisely what a bought platform delivers faster than any internal roadmap.
Air New Zealand has publicly cited prolonged engine-availability constraints (industry-wide maintenance issues) as limiting capacity and network resilience, alongside sustained inbound-tourism recovery in its visitor markets.
GTM implication: Fleet constraints make disruption more likely while tourism demand grows — sell elastic multilingual disruption care as brand protection precisely where operational risk is concentrated.
Cost-discipline programs likely continue while capacity constraints cap revenue upside, making surge staffing for seasonal peaks hard to justify.
GTM implication: Frame the Launch pilot as surge-staffing cost avoided plus saved rebookings, measurable within one southern-summer season.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Disruption rebooking and proactive passenger communication Proactive rebooking in the passenger's language; spike absorbed without surge staffing. | One weather event can strand international connections across the network; recovery speed is the brand. Friction today: Disruption floods a fixed contact center; international visitors queue in a foreign language at their worst travel moment. | App chatSMSVoiceEmail | |||
Multilingual visitor-market service desk Native-quality service across visitor languages, around the clock, at software cost. | Tourism NZ demand from Asia is the growth engine; service in Mandarin, Japanese and Korean is a competitive differentiator against one-stop Gulf and Asian carriers. Friction today: Non-English service depends on scarce specialist staff in limited time windows. | 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 Air New Zealand's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Air New Zealand: A focused disruption-workflow pilot fits a mid-sized carrier's budget and its existing AI vendor commitments; success creates the expansion case into everyday service and loyalty.
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.
“Air New Zealand's service reputation is a national asset under strain from capacity constraints; agentic disruption care protects the brand precisely where fleet issues make disruption more likely.”
“You've moved early on AI publicly; adding a Gemini-powered frontline for voice and disruption gives you best-of-breed pluralism and a live benchmark across platforms.”
“You cannot staff Auckland for February's worst day; elastic multilingual capacity absorbs the summer surge and the fog days without carrying the cost through winter.”
“Proactive rebooking in the passenger's own language turns your hardest days into loyalty stories — and deletes the refund-status tail that clogs your queues for weeks after.”
“NZ Privacy Act and Australian Privacy Act-aligned handling, full interaction logging and human gates on compensation — governance sized for a flag carrier's public accountability.”
“A Launch-scoped pilot fits a mid-sized carrier's envelope, and the ROI is concrete: surge-staffing cost avoided plus saved rebookings, measured in one summer season.”
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.
A beloved flag carrier whose tourism-dependent, long-haul network concentrates risk in seasonal disruption spikes — smaller absolute volume than the majors, and an existing public OpenAI collaboration means the entry is a focused, benchmarkable workflow, not a platform pitch.
Pre-summer planning session with customer care: scope a Launch pilot on disruption rebooking and Mandarin/Japanese service, live before the December peak.
Entry: Disruption rebooking and proactive passenger communication · Launch package · 8–10 weeks to a live, measured pilot. 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.