IndonesiaBankingScale · $100K
Bank Mandiri

Extend Livin' by Mandiri's superapp ambition into every conversation — service, collections, and wealth in one governed voice layer

Deflect the servicing load that Livin's growth creates and run OJK-compliant conversational collections, so Mandiri's digital economics improve with scale instead of degrading.

Entry use case
Livin' servicing deflection with in-conversation actions
Expected outcome
Measured reduction in cost-per-contact and repeat calls across card, transfer, and account servicing
Recommended next step
Executive briefing with Livin' and contact-center leadership: quantify the top ten servicing intents and scope a deflection-plus-action pilot.
What we understand

Bank Mandiri's operating reality

Bank Mandiri is Indonesia's largest bank by assets, majority state-owned, with the Livin' superapp as its flagship retail channel alongside the Kopra wholesale platform.

Public fact

Livin' by Mandiri has grown to tens of millions of registered users with transaction values in the thousands of trillions of rupiah — every cohort adds servicing volume.

Public fact

The 14000 contact center and branch network still absorb high volumes of card, transfer-dispute, and account queries that the app cannot resolve end-to-end.

Reasoned inference

Consumer lending and credit-card books require collections that comply with OJK conduct regulation on contact hours and practices.

Reasoned inference

As a state-linked bank, Mandiri will weigh data-residency and sovereign-cloud posture heavily in any AI platform decision.

Reasoned inference

Validate with the account team before outreach: Cloud and data-residency policy for customer-facing AI at a state-linked bank · Incumbent CCaaS/IVR vendor and contract renewal timing for the 14000 center · Collections outsourcing mix and OJK audit findings, if any

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: Livin' proves genuine internal digital delivery, but Mandiri's build strength is app experiences on top of core banking — not speech infrastructure, agentic contact-center AI, or conduct-governed outbound at scale; it will buy industry workflows with deep integration support.

Why they won't build the full stack: A state-linked bank's engineering agenda is consumed by core modernization and superapp roadmaps; building voice AI, OJK conduct tooling, and evaluation infrastructure in-house has no strategic payoff versus partnering, and procurement governance favors accountable vendors.

What management is signalling

State-linked bank investor communications consistently emphasize digital-channel transaction growth and efficiency ratios, implying servicing cost per Livin' user is a watched metric as cohorts scale.

Inferencerecent investor communications (validate) · 2025–2026

GTM implication: Position deflection-with-actions as bending the cost-to-income curve as Livin' adoption compounds.

What already exists (don't pitch this)
  • Livin' by Mandiri superapp with tens of millions of users
  • Kopra wholesale digital platform
  • 14000 contact center and national branch network
What customers still can't do end-to-end (pitch this)
  • →In-conversation completion of servicing actions beyond app self-service
  • →Cross-channel context between app, call center, and branch
  • →Bahasa voice automation beyond IVR trees
  • →Proactive collections and wealth outreach at coverage scale
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Livin' servicing deflection
Identity-resolved, grounded answers with in-conversation actions for the top servicing intents.
App growth multiplies 'where is my transfer / card blocked' contacts that today land on 14000 agents.
Friction today: IVR trees plus re-authentication; agents swivel across core banking and card systems.
In-appWhatsAppVoice
Card and consumer-loan collections
100% early-bucket attempted contact within OJK windows, offers bounded by the approved matrix.
Early-bucket coverage protects consumer-book margins as unsecured lending grows.
Friction today: Dialer capacity limits day-1 coverage; offer consistency depends on the collector.
WhatsAppVoice
Livin' investasi & wealth outreach
Qualified, consent-based conversations that book RM appointments for higher-value products.
Cross-sell into deposits and investment products is a strategic retail priority.
Friction today: Outbound tele-sales capacity reaches a fraction of eligible customers.
WhatsAppVoice
Watch the change

Livin' servicing deflection with in-conversation actions: today vs the agentic model

Scenario: A Livin' user's transfer is stuck; the agent recognizes her, reads the live status from core banking, files the dispute, and pushes proactive updates — no 14000 queue.
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
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 · Bank Mandiri
Core bankingCard managementCRMCollections platformWealth platform

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

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 Mandiri'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 Mandiri: Multiple high-value workflows (servicing, collections, wealth outreach) across a single retail bank BU fit the Scale package; enterprise-wide governance can follow proof.

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 livin' servicing deflection 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

“Livin' won the digital-adoption race; the next race is unit economics. An agentic layer makes every incremental Livin' user cheaper to serve, not more expensive.”

CIO / CTO

“Gemini Enterprise agents ground every answer in your core systems with role-based controls and full logging — deployable within the data-residency posture a state-linked bank requires.”

COO

“Your 14000 center absorbs demand your app creates. In-conversation actions on the top ten intents take structural volume out, not just deflect it to callbacks.”

Head of Retail Banking (Livin')

“Servicing friction is the leak in the superapp funnel. Resolve card blocks and transfer disputes inside the conversation and Livin' engagement compounds instead of churning.”

Chief Risk / Compliance Officer

“OJK contact windows, approved offer matrices, and 100% conversation scoring are enforced in software — a stronger conduct evidence trail than sampled QA on human collectors.”

CFO / Procurement

“Fixed implementation packages, consumption-based usage, and a pilot instrumented on cost-per-contact — you see the P&L effect before enterprise commitment.”

Outreach

Pre-built offer emails for Bank Mandiri

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 1 — immediate strategic pursuit

Why this tier

Indonesia's largest bank by assets with a flagship digital franchise (Livin') of tens of millions of users — massive contact volume, strong digital ambition, and budget authority to move.

30 / 60 / 90-day plan
  • Day 0–30: Executive briefing with Livin' and contact-center leadership: quantify the top ten servicing intents and scope a deflection-plus-action pilot.; confirm sponsor and baseline data access; validate: Cloud and data-residency policy for customer-facing AI at a state-linked bank
  • Day 31–60: architecture & security review with the platform team; Tilicho Labs scoping on In-app + WhatsApp; pilot scope signed
  • Day 61–90: Scale package kickoff; livin' servicing deflection with in-conversation actions pilot in build; success thresholds locked with the Head of Retail Banking (Livin')
Recommended next step

Executive briefing with Livin' and contact-center leadership: quantify the top ten servicing intents and scope a deflection-plus-action pilot.

Entry: Livin' servicing deflection 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.