ANA's brand is omotenashi-grade service, but record inbound tourism means millions of passengers who need help in Mandarin, Korean, Thai and English from a contact center staffed for Japanese; an agentic frontline that rebooks proactively during typhoon season and serves every visitor language at native quality extends ANA's service promise to the demand actually filling its cabins.
ANA Holdings is Japan's largest airline group, operating full-service international and domestic networks plus LCC brand Peach, hubbed at Haneda and Narita.
Public factANA reported record operating revenues and profits in its recent fiscal year, driven substantially by international passenger demand and Japan's inbound-tourism boom.
Public factJapan's typhoon season and winter weather regularly disrupt dense domestic banks that feed international connections, creating 10x contact spikes.
Reasoned inferenceInbound visitors need service in Mandarin, Korean, Thai and English — languages a Japan-based contact center cannot staff economically at peak.
Reasoned inferenceJapan's service-labor scarcity hits airline contact centers and airports alike; keigo-quality Japanese for domestic passengers remains a non-negotiable brand bar.
Public factRefund and rebooking-status repeat contacts likely form a long tail after each disruption event, inflating handled volume well beyond incident counts.
Seller hypothesis — validateValidate with the account team before outreach: Current disruption-day contact multipliers and abandonment rates · Existing chatbot/CCaaS estate and PSS integration constraints for automated rebooking · Multilingual staffing levels and cost per non-Japanese contact · Group AI initiatives at ANA Holdings and any incumbent vendor commitments
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: ANA is an operations company, not a software company: its engineering capacity is committed to fleet, network and airport operations, and its digital estate is vendor-built around the PSS; there is no internal LLM program, so multilingual conversational AI at brand quality is a clear buy.
Why they won't build the full stack: Building keigo-grade Japanese plus visitor-language voice AI in-house would take years an inbound boom won't wait for, and airline IT budgets are consumed by PSS modernization and operational resilience; a governed platform with human gates delivers typhoon-season capacity this year, not in a roadmap.
ANA reported record operating revenues and profits for the year ended March 2025, with international passenger revenue at record highs driven by inbound-tourism demand and new international routes.
GTM implication: Service capacity is the bottleneck on a publicly celebrated growth engine — sell multilingual agentic service as the way to keep monetizing inbound demand without linear Japanese-staff hiring.
Japan's inbound-tourism recovery continues to set visitor records, and management commentary across Japanese carriers ties forward capacity growth to international demand.
GTM implication: Every added international frequency adds visitor-language service load — position the platform as scaling with the published route expansion plan.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Disruption rebooking and proactive passenger communication Proactive rebooking offers in the passenger's language before the gate announcement; disruption spikes absorbed without queue melt. | Typhoon-day recovery defines the service reputation of Japan's flag-quality carrier; queues at Haneda are brand damage broadcast live. Friction today: Cancellation waves flood phone and airport desks; rebooking requires agents while international visitors queue in a language mismatch. | App chatSMSVoiceWeb | |||
Inbound-visitor multilingual service desk Native-quality Mandarin, Korean, Thai and English service around the clock at software cost. | Inbound tourism is the growth engine of ANA's record results; visitor-language service is currently the weakest link in an otherwise premium journey. Friction today: Non-Japanese service depends on scarce specialist staff in limited windows; visitors default to airport counters. | App chatVoiceWeb | |||
ANA Mileage Club loyalty and account desk Routine loyalty service resolved in-conversation in keigo-grade Japanese; human desks reserved for complex itineraries. | The mileage program anchors Japan's most valuable travel loyalty base; routine award and status questions consume premium-desk capacity. Friction today: Award availability, upgrade and account questions queue behind urgent travel issues on the same lines. | 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 ANA (All Nippon Airways)'s measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for ANA (All Nippon Airways): Disruption handling plus a multilingual inbound-visitor service desk are two well-bounded workflows across app, web, voice and chat — classic Scale scope with clean PSS and disruption-feed integration boundaries.
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.
“Record results were built on inbound demand your service model wasn't designed for; agentic multilingual care extends omotenashi to the passengers actually driving the growth — and protects the premium brand on its worst weather days.”
“A governed agent layer over the PSS and disruption feeds gives one conversational platform for Japanese and visitor languages alike — bounded integration, full auditability, no rip-and-replace of the reservation stack.”
“You staff for the median day and melt in typhoon season; elastic agentic capacity absorbs the 10x spike without carrying that labor cost the other 350 days — in every language your cabins now carry.”
“Your hardest staffing problem is multilingual coverage at peak; an agent that rebooks in Mandarin at 2am and keigo at 8am removes the tradeoff between cost and coverage entirely.”
“APPI-aligned handling, human gates on compensation and goodwill, 100% interaction logging — service quality governance that matches ANA's brand bar, with audit trails sampled human QA never gave you.”
“Inbound growth is inflating service volume faster than revenue per contact; the pilot measures disruption-day cost and rebooking completion against your own baseline, with usage billed on consumption.”
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.
Japan's largest full-service carrier is riding a record inbound-tourism wave that its Japanese-staffed contact centers cannot scale to serve — disruption spikes plus multilingual visitor servicing at national-carrier volume make this the cleanest buy-led airline opportunity in Japan.
Pre-typhoon-season workshop with customer experience leadership: baseline disruption-day contact multipliers and multilingual coverage, then scope a Scale pilot on the disruption and visitor-service queues.
Entry: Disruption rebooking and proactive passenger communication · 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.