Bukalapak's future is Mitra warungs and virtual products; every failed top-up or stuck settlement is lost revenue for a micro-entrepreneur — an agentic support desk keeps the network alive at profitability-era cost.
Bukalapak discontinued physical-goods marketplace sales in early 2025, pivoting to virtual products (phone credit, data, electricity tokens, bill payments) and digital services.
Public factThe Mitra Bukalapak network — millions of warungs and small retailers — remains operational and is central to the O2O strategy.
Public factManagement framed the pivot as a profitability move; cost discipline now governs vendor decisions.
Public factVirtual-product transactions fail in real time (operator outages, token delays); each failure is an urgent, revenue-blocking support event for a Mitra.
Reasoned inferenceMitra owners are phone-and-WhatsApp-first users spread across the archipelago, often outside major cities.
Reasoned inferenceValidate with the account team before outreach: Post-pivot support volumes and current cost per Mitra contact · Virtual-product partner APIs available for real-time status grounding
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: Post-pivot Bukalapak retains competent engineering, but the profitability mandate rules out platform side-builds; it will buy a tightly scoped Mitra-support outcome at predictable cost from a partner it can hold to pilot metrics.
Why they won't build the full stack: Every engineering sprint now serves the virtual-products P&L; voice-AI infrastructure is exactly the kind of non-core build the pivot was executed to eliminate.
The exit from physical-goods e-commerce was framed to investors as a profitability move, implying cost per active Mitra and contribution margin are under standing scrutiny.
GTM implication: A fixed-price Launch pilot with consumption usage matches the cost-discipline mandate exactly — no platform commitment required.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Mitra transaction & settlement support Instant grounded answers on transaction state, guided resolution, and proactive settlement updates. | Warung owners live on transaction margins; a stuck electricity token or unsettled balance stops their trading day. Friction today: Hotline and chat queues; resolution requires manual checks across product partners. | WhatsAppVoiceIn-app | |||
Mitra activation & product adoption Conversational activation nudges and how-to guidance that raise products-per-Mitra. | Revenue per Mitra depends on how many virtual products each warung actively sells. Friction today: Onboarding to new products is self-serve; adoption stalls silently. | WhatsAppVoice |
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 Bukalapak's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Bukalapak: A focused, single-workflow pilot on Mitra support matches the company's post-pivot cost discipline and proves value before any wider scope.
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.
“The pivot bet the company on Mitra economics. Support quality is now a revenue driver — every resolved issue keeps a warung transacting on Bukalapak instead of a rival app.”
“A single-workflow Launch pilot integrates only the Mitra platform and settlement APIs — small surface, fast proof, no distraction from the post-pivot roadmap.”
“Support cost per active Mitra is a number you can now cut while improving resolution speed — the pilot reports both.”
“Warungs churn to whichever app fails them least. Instant transaction support in their own language is a retention lever your competitors' hotlines cannot match.”
“Payment-adjacent support conversations are fully logged with policy-bounded actions — cleaner evidence than hotline recordings sampled after the fact.”
“A fixed Launch package with consumption pricing fits the profitability mandate: you pay for resolved conversations, not idle seats.”
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.
Post-pivot Bukalapak is smaller and margin-focused after exiting physical-goods e-commerce in early 2025, but its Mitra warung network is a genuinely strong dealer-support fit at modest deal size.
Launch-package proposal to Mitra leadership: automate transaction-status and settlement support for one region's warung network in eight weeks.
Entry: Mitra Bukalapak transaction and settlement support · Launch package · 8–10 weeks to a live, measured pilot. 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.