Cebu Pacific's growth math multiplies passengers faster than any service team can grow; agentic disruption comms, rebooking, and travel-fund service keep ULCC economics intact through every storm season and seat sale.
Cebu Pacific carried a record ~27M passengers in 2025, up around 10% year-on-year, cementing its position as the Philippines' largest budget carrier.
Public factThe airline has committed to major Airbus fleet growth, with a landmark narrowbody order reported at up to $24B list value — capacity that implies proportional service volume.
Public factThe Philippines averages roughly 20 tropical cyclones a year; weather disruption is an annual operating certainty for any Philippine carrier.
Public factPiso-sale promo events create booking and service surges that resemble e-commerce flash sales more than airline norms.
Reasoned inferenceRefund and travel-fund status inquiries likely dominate post-disruption contact volume, as with all LCCs.
Reasoned inferenceValidate with the account team before outreach: PSS API access for in-channel rebooking confirmation · Travel-fund system integration readiness · Current disruption-day contact volumes and BPO surge costs
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: A ULCC with a disciplined cost culture and no consumer-AI engineering organization; it buys fleet, systems, and services from vendors — service automation will be bought as a measurable outcome, not built.
Why they won't build the full stack: Every peso of engineering ambition goes to operations and fleet economics; conversational AI is a vendor category for an airline this lean, and speed to deployment matters ahead of each typhoon season.
Record ~27M passengers in 2025 (up around 10%) with net income more than doubling, and a firm order for 70 A321neos committing to sustained capacity growth.
GTM implication: Passenger growth is contractually committed via the order book while service capacity is not — sell elasticity so growth does not degrade disruption CX or ULCC unit costs.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Disruption notify & self-serve rebooking Affected passengers get options in-channel and confirm rebooking without touching a counter. | Typhoon cancellations strand thousands simultaneously; counters and hotlines cannot scale to the event. Friction today: Gate announcements and generic advisories; rebooking requires human queues at the worst moment. | In-appViber/WhatsAppSMSVoice | |||
Refund & travel-fund status Live status answers plus proactive stage updates from filing to credit or payout. | Post-disruption status calls are the airline's largest repeat-contact category. Friction today: Opaque timelines drive weekly follow-up calls and complaints. | Viber/WhatsAppIn-app | |||
Seat-sale surge support Elastic conversational support that resolves payment and booking issues during the surge itself. | Piso sales spike booking issues, payment failures, and change requests within hours. Friction today: Fixed support capacity meets flash-sale demand; abandonment and complaints spike. | In-appViber/WhatsApp |
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 Cebu Pacific's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Cebu Pacific: Disruption comms, refund/travel-fund service, and seat-sale surge support are multiple workflows across channels — Scale scope aligned to a growing network.
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.
“Your fleet order doubles the operation; your service model cannot double with it. Agentic disruption service is how passenger growth outruns headcount growth.”
“Integration is ops-control feeds plus the PSS — one architecture that then serves every new route and aircraft you add.”
“Every typhoon currently costs you counter chaos and melted hotlines. Proactive rebooking moves that load to software the moment ops control makes the call.”
“Passengers rebooked in-channel stay revenue; passengers queueing for refunds become detractors. The travel-fund status agent alone kills your biggest repeat-contact driver.”
“Consistent, logged passenger communications strengthen CAB consumer-protection compliance and complaint defense after every disruption event.”
“ULCC discipline applies to service too: consumption-priced conversations flex to zero on blue-sky days and absorb typhoon peaks without surge staffing.”
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 Philippines' largest low-cost carrier at a record ~27M annual passengers with an aggressive fleet-growth order book — structurally exposed to typhoon disruption with ULCC-thin service staffing.
Disruption-playbook session with customer-care leadership: wire ops-control triggers to a proactive rebooking pilot before the next typhoon season peak.
Entry: Typhoon/disruption notification & self-serve rebooking · 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.