PhilippinesAirline (flag carrier)Scale · $100K
Philippine Airlines

Serving the diaspora on ultra-long-haul: agentic passenger care for Philippine Airlines

Give PAL an elastic disruption and passenger-service layer — proactive rebooking on transpacific routes, refund transparency, Mabuhay Miles service, and OFW-sensitive support in Taglish and English — that lifts full-service experience without post-restructuring headcount growth.

Entry use case
Proactive disruption notification & rebooking
Expected outcome
Absorb disruption spikes on long-haul and domestic networks with proactive multilingual rebooking and suppress refund-status contact volume
Recommended next step
Model last typhoon season's disruption contact spikes and refund-status share with the CX team, then scope a proactive rebooking pilot on transpacific routes.
What we understand

Philippine Airlines's operating reality

Philippine Airlines completed a US Chapter 11 restructuring in 2021, cutting debt and fleet, and has since returned to profitability under the Lucio Tan group's PAL Holdings.

Public fact

PAL is executing a major fleet renewal: it doubled its Airbus A350-1000 order to 18 aircraft (announced at Farnborough 2026) for nonstop transpacific and ultra-long-haul flying, alongside reported widebody commitments with Boeing.

Public fact

The OFW (overseas Filipino worker) base is a structurally distinctive passenger population: time-zone-dispersed, Messenger/Viber-first, price- and rebooking-sensitive, and generating service contacts around the clock that a Manila-hours contact center serves badly.

Reasoned inference

Typhoon season makes disruption handling an annual certainty at NAIA and Cebu hubs; proactive rebooking capacity determines whether disruptions become brand crises.

Reasoned inference

Refund and rebooking backlogs from the pandemic era left measurable trust damage; transparent, grounded refund status is a disproportionately valuable fix.

Reasoned inference

Mabuhay Miles modernization and ancillary revenue (seat selection, baggage) could take conversational commerce as an expansion surface after service workflows prove.

Seller hypothesis — validate

Validate with the account team before outreach: PSS and refund-pipeline API accessibility · Disruption-day volume multipliers and refund contact share · Messenger/Viber verified-channel and consent posture for proactive outreach

Build vs buy

Why we have a right to win here

Buy-led target

Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution

Evidence: A post-Chapter 11 carrier running lean, with IT on vendor airline systems and capital committed to fleet renewal, has neither the organization nor the appetite to build conversational infrastructure; it will buy a packaged, auditable layer with partner-owned delivery.

Why they won't build the full stack: Fleet renewal consumes capital and management bandwidth through 2030; the diaspora service gap costs loyalty every typhoon season in the meantime. Buying delivers before the next season; building delivers after the A350s do.

What management is signalling

PAL doubled its Airbus A350-1000 order to 18 aircraft at Farnborough 2026 (nine more plus rights for five), reinforcing the ultra-long-haul fleet-renewal strategy after its 2021 Chapter 11 exit.

Reported factJul 2026 order announcements / restructuring disclosures · Jul 2026

GTM implication: Fleet-led premium ambitions raise the service bar while capex discipline caps headcount — the exact gap an elastic service layer fills.

What already exists (don't pitch this)
  • PAL mobile app and web booking
  • Mabuhay Miles loyalty program
  • Contact center with social-channel support
  • Ultra-long-haul network and A350-1000 fleet renewal underway
What customers still can't do end-to-end (pitch this)
  • →Proactive multilingual disruption rebooking
  • →Refund-status transparency
  • →24/7 transpacific-time-zone service coverage
  • →Cross-channel context between hotline, Messenger, and airport desks
  • →Interaction-level QA
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Disruption notification & rebooking
Affected passengers messaged proactively with live rebooking options and one-tap confirmation; interline and duty-of-care complexity routed to specialists with context.
Typhoon-season certainty plus ultra-long-haul stakes: a missed Manila connection strands a Toronto-bound passenger for days, not hours.
Friction today: Passengers learn of cancellations at the airport; hotline queues peak exactly when Manila is asleep for North American callers.
MessengerViberAppSMSVoice
Refund & ticketing status service
Fare-rule-accurate answers and refund status grounded in the ticketing pipeline with proactive stage updates.
Post-pandemic refund trust damage makes this the most reputationally loaded contact class the carrier has.
Friction today: Refund status requires back-office checks; passengers call repeatedly across time zones and escalate on social media.
MessengerEmailVoiceApp chat
Mabuhay Miles & OFW service
Mileage claims resolved against flight records, award options offered conversationally, OFW documentation questions answered from governed sources 24/7.
Diaspora loyalty is PAL's structural advantage against Gulf and US carriers on Philippine routes; servicing it well is retention economics.
Friction today: Mileage-credit and award questions queue behind general service; OFW-specific needs (documentation, baggage allowances) are handled inconsistently.
MessengerViberVoiceEmail
Watch the change

Proactive disruption notification & rebooking: today vs the agentic model

Scenario: A typhoon cancels a Manila–Vancouver departure; every passenger gets rebooking options on Messenger before check-in opens, an OFW's onward domestic connection is protected automatically, and a Mabuhay Miles elite is moved to the next day's nonstop.
Today
same interaction, two worlds
Agentic layer
Disruption call spike
10× volume, melted queues
suppressed by proactive rebooking
Assumption
Cost per contact
$13.50 median assisted
$1.84 median self-service
Benchmark
QA coverage
1–2% sampled
100% scored
Platform capability
Sources & assumptions
  • · Disruption call spike: Operator-reported pattern (assumption); suppression measured in pilot
  • · Cost per contact: Gartner customer service cost benchmarks, 2024
  • · QA coverage: Platform capability: every interaction logged and evaluated
  • · Gartner, customer service cost benchmarks (2024): $13.50 median assisted vs $1.84 self-service per contact
  • · McKinsey, digital-first collections research: 20–25% NPL reduction among leaders; up to 40% opex reduction with gen AI
  • · Baymard Institute: ~70% average cart abandonment (meta-analysis)
  • · IAMAI–Kantar via IBEF (2025): 900M+ Indian internet users; 98% consume Indic-language content
  • · LeadSquared and vendor funnel studies: 78% of students choose the first institution to respond (directional, vendor data)
  • · HDI / ITSM operator benchmarks: $15–25 per L1 ticket; 40–60% of L1 volume is resets/status (validate per customer)
  • · Conventional-flow wait times and volumes are typical operator patterns — assumptions to replace with the customer's own baseline
  • · Agentic-flow behaviors (context retention, 100% logging, in-line policy checks) are platform capabilities, not projections
Recommended solution

One integrated stack, opinionated for this account

Channels · Tilicho Labs
MessengerViberAppSMSVoiceEmailApp chat

Voice & channel orchestration, telephony, conversational execution, session/state, routing, integration build. Capability coverage validated during implementation.

Intelligence · Google Cloud
Gemini reasoningEnterprise groundingWorkflow agentsMulti-agent orchestrationGoverned actionsEvaluation & analytics
Systems · Philippine Airlines
PSS/reservationOps/disruption feedPaymentsTicketing/PSSRefund pipelineCase managementLoyalty platformPSS

API access to these systems is the critical-path dependency.

Trust & languages
Filipino/TagalogEnglishCebuanoJapaneseMandarin

Identity-bound sessions, policy-bounded actions, 100% audit logging, human approvals at defined points, in-tenant intelligence.

Business case

The economics, with your numbers

Addressable monthly interactions700K
Seller assumption — replace in discovery
Current cost per interaction ($)$1.0
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$700K
Current operating cost / mo
$3.0M
Modelled gross benefit / yr
0.4 mo
Payback on Scale
180%
3-yr ROI (modelled)
Automated/assisted interactions per month385K
Modelled AI run-cost per month (usage + cloud, system estimate)$135K
New monthly operating cost$450K

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 Philippine Airlines's measured baseline. Package price covers implementation only; recurring usage billed separately.

Recommended package

Scale — $100K implementation

Scale · $100K · A multi-channel production deployment10–14 weeks to production across priority workflows

Why this package for Philippine Airlines: Disruption handling, refund/ticketing service, and Mabuhay Miles support across app, Messenger, Viber, and hotline is a multi-workflow deployment; transpacific time zones make 24/7 coverage non-negotiable from day one.

Included
  • 4–6 channels
  • 2–3 priority workflows
  • Multiple enterprise integrations
  • API credential & security setup
  • Advanced orchestration
  • Multilingual support
  • Agent Assist / human escalation
  • Production analytics
  • Expansion roadmap
Not included
  • ✕Usage & consumption (billed separately)
  • ✕Enterprise-wide governance build-out
  • ✕Multi-BU rollout
Recurring costs (separate from the package)

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.

Customer resources required
  • · API access + credentials for: PSS/reservation, Ops/disruption feed, Payments
  • · A named business owner for proactive disruption notification & rebooking
  • · Security review counterpart and policy sign-off (PSS/reservation scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO / President & COO

“The A350 order bets the airline on ultra-long-haul; the service experience must match the aircraft. Proactive multilingual disruption care is how a lean post-restructuring carrier delivers flag-carrier experience on a variable cost base.”

CIO / CTO

“One integration into the PSS, ops feed, and refund pipeline powers disruption, refund, and loyalty workflows — partner-delivered, without adding scope to the fleet-driven IT agenda.”

COO

“Typhoon-day spikes and transpacific overnight queries stop melting the hotline: absorbed elastically, 24/7, in the passenger's language — while your teams handle interline judgment calls.”

Head of Customer Care / Commercial

“The diaspora lives on Messenger and Viber; meeting them there with real booking context is a loyalty weapon against carriers who make them call Manila.”

Chief Risk / Compliance Officer

“Air-passenger-rights obligations and compensation policy applied identically on every contact, fully logged — evidence-ready for CAB complaints and consistent by construction.”

CFO / Procurement

“Fleet capex leaves no appetite for fixed service-cost growth; usage-priced conversational capacity converts disruption staffing to variable cost with auditable deflection.”

Outreach

Pre-built offer emails for Philippine Airlines

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.

Moment in the deal
Cold outreach — no prior conversation
Who it's addressed to
Cares about: The workflow itself and its daily failure modes
Register
Length
Draft — edit freely before sending
Open in 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 pursuit

Tier 2 — high-potential incubation

Why this tier

The flag carrier that exited Chapter 11 in 2021 and is now executing a major fleet renewal — including doubling its A350-1000 order to 18 for ultra-long-haul — serves the world's most geographically dispersed diaspora: disruption care, refund transparency, and OFW-focused multilingual service are structural needs its lean post-restructuring organization cannot staff.

Recommended next step

Model last typhoon season's disruption contact spikes and refund-status share with the CX team, then scope a proactive rebooking pilot on transpacific routes.

Entry: Proactive disruption notification & rebooking · Scale package · 10–14 weeks to production across priority workflows. Human fallback throughout; success thresholds agreed before build.

Start the pursuit

Research-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.