IndonesiaBankingScale · $100K
Bank Central Asia (BCA)

Keep the Halo BCA service standard while volume compounds — agentic service that acts, not a chatbot that deflects

Let BCA scale the country's most trusted banking service experience by giving customers grounded, in-conversation resolution in Bahasa Indonesia, with humans reserved for the moments that build loyalty.

Entry use case
Halo BCA inbound service with in-conversation actions
Expected outcome
Lower cost per contact and shorter resolution times without any drop in measured service quality
Recommended next step
Quality-first proof proposal to Halo BCA leadership: one servicing intent taken end-to-end with 100% scoring published against the current human benchmark.
What we understand

Bank Central Asia (BCA)'s operating reality

BCA is Indonesia's largest private bank, consistently ranked among the world's strongest banking brands, with a franchise built on transaction banking and service quality.

Public fact

Halo BCA is one of Indonesia's best-known contact-center brands, spanning voice, WhatsApp, and social channels, and already operates the VIRA virtual assistant.

Public fact

Tens of millions of mobile-banking customers (BCA mobile, myBCA) generate servicing contacts — card blocks, transfer disputes, limit changes — that still require human completion.

Reasoned inference

BCA's brand equity makes it more sensitive to AI service failures than to service cost — quality evidence will beat cost arguments.

Reasoned inference

Existing chatbot deflection likely plateaus at FAQ-level intents; in-conversation execution (block card, raise dispute) is the unopened frontier.

Seller hypothesis — validate

Validate with the account team before outreach: Current VIRA/chatbot stack, vendor, and containment ceiling · BCA's cloud posture and appetite for customer-facing GenAI · Which servicing intents Halo BCA leadership considers automatable without brand risk

Build vs buy

Why we have a right to win here

Partner-led target

Technically capable but needs industry workflows, integration, acceleration, or managed operations

Evidence: BCA's culture is service quality and operational conservatism; it adopts proven technology through partners — as the VIRA assistant shows — rather than building platform infrastructure, and a quality-evidence-led partner motion matches how it makes decisions.

Why they won't build the full stack: BCA's moat is trust and service consistency, not AI engineering; an in-house voice-AI build would put the brand on unproven internal tooling, whereas a governed partner platform lets it hold quality accountable contractually and roll back cleanly.

What management is signalling

Investor materials consistently emphasize transaction-banking franchise growth and best-in-class cost discipline, implying servicing volume compounds with every digital cohort while the quality bar stays fixed.

Inferencerecent investor communications (validate) · 2025–2026

GTM implication: Lead with quality evidence — 100% scoring against the human benchmark — and let the cost case follow; a cost-first pitch will stall in this culture.

What already exists (don't pitch this)
  • Halo BCA multichannel contact center
  • VIRA virtual assistant
  • myBCA and BCA mobile apps
What customers still can't do end-to-end (pitch this)
  • →In-conversation execution (card blocks, disputes, limits) beyond FAQ deflection
  • →24/7 voice-grade automation at the Halo BCA quality bar
  • →Cross-channel context continuity between app, chat, and voice
  • →100% interaction quality telemetry versus sampled QA
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Halo BCA service with actions
Top servicing intents resolved end-to-end in-conversation, with warm handoff and full context for the rest.
The service brand is a competitive moat; scaling it without diluting quality is BCA's core CX problem.
Friction today: VIRA-era deflection answers questions but cannot execute; complex intents still queue for agents.
VoiceWhatsAppIn-app
Credit-card lifecycle servicing
Card servicing completed conversationally within policy, disputes filed with proactive status.
Card activation, limit, installment-conversion, and dispute flows are high-volume and rule-bounded — ideal for governed automation.
Friction today: Each intent today ends in an agent queue or branch visit.
WhatsAppVoice
Mortgage & auto-loan lead follow-up
Minutes-fast qualification and appointment booking onto loan-officer calendars.
KPR and KKB campaigns generate leads that decay in branch queues.
Friction today: Speed-to-lead measured in days; follow-up depends on branch staff bandwidth.
WhatsAppVoice
Watch the change

Halo BCA inbound service with in-conversation actions: today vs the agentic model

Scenario: A BCA cardholder abroad gets her card blocked at midnight Jakarta time; the agent verifies her, unblocks within policy, and confirms — no queue, no time-zone gap.
Today
same interaction, two worlds
Agentic layer
First-contact resolution
deferred via tickets
in-conversation actions
Platform capability
Cost per contact
$13.50 median assisted
$1.84 median self-service
Benchmark
QA coverage
1–2% sampled
100% scored
Platform capability
Sources & assumptions
  • · First-contact resolution: Process design: agent acts in systems of record
  • · 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
VoiceWhatsAppIn-app

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 · Bank Central Asia (BCA)
Core bankingCard managementCRMDispute systemLoan origination

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

Trust & languages
Bahasa IndonesiaEnglish

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 interactions6.0M
Seller assumption — replace in discovery
Current cost per interaction ($)$1.1
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$6.6M
Current operating cost / mo
$29.7M
Modelled gross benefit / yr
0.0 mo
Payback on Scale
214%
3-yr ROI (modelled)
Automated/assisted interactions per month3.3M
Modelled AI run-cost per month (usage + cloud, system estimate)$1.2M
New monthly operating cost$4.1M

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 Bank Central Asia (BCA)'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 Bank Central Asia (BCA): BCA will demand production-grade quality across several channels at once (voice, WhatsApp, app); a multi-channel Scale deployment on two workflows matches its bar for service consistency.

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: Core banking, Card management, CRM
  • · A named business owner for halo bca inbound service with in-conversation actions
  • · Security review counterpart and policy sign-off (Core banking scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

CEO

“BCA's premium is trust and service. Agentic service protects that premium at scale — same standard at midnight as at noon, measured on every single interaction.”

CIO / CTO

“This extends the VIRA investment from answering to acting: grounded in core systems, least-privilege actions, every step logged to your standards.”

COO

“Halo BCA volume grows with every digital cohort. In-conversation actions on the top intents bend the staffing curve without touching the service bar.”

Head of Halo BCA / Customer Experience

“You are measured on quality, not just AHT. 100% interaction scoring gives you quality telemetry no sampled QA program can match.”

Chief Risk / Compliance Officer

“Actions execute only within approved policy bounds with human approval above thresholds — and the audit trail is complete by construction.”

CFO / Procurement

“Start with a fixed-price Scale implementation on two workflows; the pilot reports cost per contact and quality scores side by side so the trade-off is visible — there isn't one.”

Outreach

Pre-built offer emails for Bank Central Asia (BCA)

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

Indonesia's largest private bank with a service reputation it fiercely protects; enormous Halo BCA contact volume, but a conservative, quality-first culture means a careful proof-led motion.

Recommended next step

Quality-first proof proposal to Halo BCA leadership: one servicing intent taken end-to-end with 100% scoring published against the current human benchmark.

Entry: Halo BCA inbound service with in-conversation actions · 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.