IndonesiaOnline travel (OTA)Scale · $100K
Traveloka

Absorb the disruption spikes of Southeast Asia's travel superapp — rebooking, refunds, and PayLater in one agentic layer

When airlines delay and typhoons hit, Traveloka's queues explode through no fault of its own; agentic disruption service turns its worst CX moments into its strongest loyalty proof.

Entry use case
Flight disruption reaccommodation and refund status
Expected outcome
Suppressed disruption call spikes and a collapse in refund-status repeat contacts
Recommended next step
Pilot design with customer operations: proactive disruption comms plus live refund status for Indonesian domestic flights ahead of the next peak season.
What we understand

Traveloka's operating reality

Traveloka is Southeast Asia's leading homegrown online travel platform, headquartered in Jakarta, spanning flights, hotels, activities, and financial services across multiple SEA markets.

Public fact

Pandemic-era refund backlogs were widely reported across the OTA industry and remain the archetype of Traveloka's CX risk: supplier-dependent refunds with opaque status.

Public fact

Disruption volume is structurally spiky — airline delays, weather, and volcanic-ash events in Indonesia create 10x contact surges that fixed staffing cannot absorb.

Reasoned inference

Traveloka PayLater adds a consumer-credit dimension with OJK-governed collections needs.

Reasoned inference

Multi-market operations (Indonesia, Vietnam, Thailand, and more) make multilingual service a scaling constraint on human-only models.

Reasoned inference

Validate with the account team before outreach: Current CCaaS/BPO footprint and surge-pricing exposure · Airline feed latency for disruption detection · Cloud platform posture for customer-facing AI workloads

Build vs buy

Why we have a right to win here

Co-build target

Strong internal engineering — sell infrastructure, models, governance, or selected capabilities

Evidence: A digital-native OTA with strong internal engineering that builds its own booking, payments, and app platforms — Traveloka will want to own the customer-journey and orchestration layer; the sale is models, voice infrastructure, and governance capabilities it will not build itself.

Why they won't build the full stack: Multilingual voice quality, telephony, OJK-compliant collections tooling, and evaluation infrastructure sit outside its product focus; the co-build line is clear — Traveloka owns journeys and experience, the platform supplies speech, grounding, and conduct tooling underneath.

What management is signalling

OTA investor narratives across SEA emphasize path-to-profitability and take-rate discipline, implying spiky service costs are a scrutinized line for Traveloka's stakeholders.

Inferencerecent investor communications (validate) · 2025–2026

GTM implication: Frame disruption automation as capping worst-month service cost — variable conversational capacity matched to variable demand.

What already exists (don't pitch this)
  • Traveloka app with in-app support and chatbot deflection
  • Multi-market CX operations across SEA
  • PayLater lending operations
What customers still can't do end-to-end (pitch this)
  • →Voice-grade disruption handling at spike scale
  • →Proactive refund-status communications across supplier pipelines
  • →OJK-conduct-evidenced PayLater outreach
  • →Consistent multilingual voice quality across SEA markets
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Flight disruption reaccommodation
Proactive disruption notice with live rebooking options offered and confirmed in-channel.
Disruptions are the deepest CX pain and the biggest driver of contact spikes for any OTA.
Friction today: Airline-side changes reach customers late; rebooking requires queue time exactly when queues are longest.
In-appWhatsAppVoice
Refund status & processing
Live refund-state answers with proactive stage updates, eliminating repeat status contacts.
Refund opacity is the single biggest trust killer; status calls dominate post-disruption volume.
Friction today: Supplier-dependent timelines communicated as 'wait 30–90 days'; customers call weekly.
In-appWhatsApp
Traveloka PayLater collections
Policy-timed conversational reminders with in-thread payment completion.
The credit book needs OJK-compliant early-bucket coverage without brand-damaging third-party collectors.
Friction today: Capacity-limited outreach; travel customers are mobile and hard to reach by dialer.
WhatsAppVoice
Watch the change

Flight disruption reaccommodation and refund status: today vs the agentic model

Scenario: A Jakarta–Denpasar flight cancels for ash cloud; every affected Traveloka customer gets rebooking options in-app within minutes, and the call spike never materializes.
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
In-appWhatsAppVoice

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 · Traveloka
Booking engineAirline/GDS feedsPaymentsRefund pipelinePayment gatewaysLending platform

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

Trust & languages
Bahasa IndonesiaEnglishThaiVietnamese

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 interactions2.5M
Seller assumption — replace in discovery
Current cost per interaction ($)$0.8
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$2.0M
Current operating cost / mo
$7.4M
Modelled gross benefit / yr
0.2 mo
Payback on Scale
127%
3-yr ROI (modelled)
Automated/assisted interactions per month1.4M
Modelled AI run-cost per month (usage + cloud, system estimate)$481K
New monthly operating cost$1.4M

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 Traveloka'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 Traveloka: Disruption service plus refund status plus booking changes span multiple channels and integrations — a Scale deployment matches an OTA's multi-supplier complexity.

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: Booking engine, Airline/GDS feeds, Payments
  • · A named business owner for flight disruption reaccommodation and refund status
  • · Security review counterpart and policy sign-off (Booking engine scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“Travelers remember who fixed the cancellation, not who caused it. Agentic disruption service makes Traveloka the brand that fixes it first — at spike-proof cost.”

CIO / CTO

“Gemini agents ground in your booking engine and supplier feeds; elastic conversational capacity finally matches the elasticity of your traffic.”

COO

“You staff for the p50 and melt at the p99. Move disruption and refund-status volume to agents that scale instantly and your workforce plan stops being a gamble.”

Head of Customer Operations

“Refund-status repeat contacts are your largest self-inflicted queue. Proactive stage updates make most of those calls never happen.”

Chief Risk / Compliance Officer

“PayLater outreach runs inside OJK conduct windows with full logging, and refund communications become consistent and auditable across markets.”

CFO / Procurement

“Disruption spikes currently force surge BPO pricing. Consumption-priced automation caps your worst-month cost, and the pilot quantifies it on one route network.”

Outreach

Pre-built offer emails for Traveloka

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

Southeast Asia's leading homegrown OTA with disruption-driven contact spikes across flights, hotels, and payments — high workflow fit, meaningful volume, digital-native buyer.

Recommended next step

Pilot design with customer operations: proactive disruption comms plus live refund status for Indonesian domestic flights ahead of the next peak season.

Entry: Flight disruption reaccommodation and refund status · 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.