Give Alfamart an agentic layer across Alfagift loyalty service, order and delivery support, bill-payment/agent-banking queries, and franchisee operations — in Bahasa Indonesia and regional languages, at minimarket unit economics.
Sumber Alfaria Trijaya operates the Alfamart network — more than 18,000 minimarkets across Indonesia plus a growing Philippines joint venture with SM — one of the largest physical retail footprints in Southeast Asia.
Public factAlfagift, the loyalty-and-delivery app, is central to its digital strategy with a membership base publicly described in the tens of millions; stores fulfill app orders as hyperlocal delivery points.
Public factAlfamart counters function as financial touchpoints — bill payments, e-commerce cash payments, remittance and agent-banking services with bank partners — generating payment-status and transaction-dispute queries far beyond normal retail service.
Reasoned inferenceA largely franchised network means thousands of franchisee-operators generating supply, settlement, promo-execution, and equipment queries into HQ — a B2B service surface with direct sales-uptime economics.
Reasoned inferenceThin-margin convenience retail cannot fund human service at scale: only sub-dollar interaction economics make comprehensive customer and franchisee service viable at 18,000-store scale.
Reasoned inferenceLoyalty-data-driven proactive outreach (offer activation, lapsed-member win-back) could become a measurable revenue lever beyond service deflection.
Seller hypothesis — validateValidate with the account team before outreach: Alfagift platform API readiness and current support contact volumes · Payment-partner (bank/switch) data-sharing constraints for dispute grounding · Franchisee communication channels and pain-point ranking from ops leadership
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: SAT is a world-class retail operator whose technology investment goes into supply chain, POS, and the Alfagift app — not platform engineering. Conversational infrastructure with payment-grade logging is outside its build pattern; it procures and integrates.
Why they won't build the full stack: Retail margins fund store growth, not software platforms; the service gap is now, across three user populations at once. A bought layer on one integration backbone reaches consumer, payment, and franchisee surfaces faster than any internal program could reach one.
Management continues to guide on network expansion (hundreds of new stores annually) and digital/loyalty growth via Alfagift, while flagging cost pressure on thin retail margins.
GTM implication: Service load scales with stores and app adoption while margins forbid proportional headcount — the unit-economics pitch matches their own framing.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Alfagift order, delivery & loyalty service Order and points context loaded at hello; delivery issues resolved with store-level grounding; promo and points questions answered in-channel. | App-driven delivery and points are the digital growth story; service friction caps both. Friction today: Delivery-status, failed-promo, and points-balance questions route to a generic hotline blind to app context. | In-app chatWhatsAppVoice | |||
Bill-payment & agent-banking support Transaction status grounded across the payment chain, refund/retry initiated in-conversation, partner-bank cases routed with full context. | Payment-point trust is the franchise: a failed bill payment at an Alfamart counter must resolve fast or the customer stops using the rail. Friction today: Payment-status disputes require store, partner, and switch reconciliation that today happens by ticket. | WhatsAppVoice | |||
Franchisee & store-operations desk Settlement, delivery-schedule, and promo-execution answers grounded in ERP; equipment and exception cases routed and tracked; issue patterns reported to ops leadership. | Franchisee uptime is revenue: every hour a store waits on a settlement or supply answer is lost sales for both parties. Friction today: Franchisees call area coordinators; answers depend on who picks up; recurring issues go unclustered. | 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 Alfamart (Sumber Alfaria Trijaya)'s measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Alfamart (Sumber Alfaria Trijaya): Consumer loyalty service, delivery support, and franchisee/payment-service workflows are distinct high-volume surfaces sharing one integration backbone — a multi-workflow Scale deployment amortizes it immediately.
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.
“Alfamart's moat is proximity — physical and now digital. An agentic layer makes 18,000 stores feel like one responsive brand on WhatsApp, at interaction costs that respect minimarket margins.”
“One integration backbone into Alfagift, order management, and the payment switch serves consumers, payment users, and franchisees — partner-delivered, without diverting the retail-tech roadmap.”
“Payday and promo surges stop overwhelming the hotline, and franchisee questions stop routing through area coordinators' mobile phones — both absorbed elastically with full context.”
“Points, promo, and delivery service in-channel protects app engagement — and consent-based win-back outreach turns the loyalty base into measured incremental baskets.”
“Payment-service disputes get evidence-grade handling: every transaction conversation logged, partner-bank escalations documented, UU PDP consent enforced as configuration.”
“Sub-dollar interactions against thin-margin economics: implementation plus usage pricing, deflection and repeat-purchase lift both measured — no fixed service-cost growth as the network expands.”
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.
18,000+ minimarkets reaching deep into kampung Indonesia, an Alfagift loyalty app measured in tens of millions of members, franchisee and supplier networks, and counters that double as bill-payment and agent-banking touchpoints — a communication surface spanning consumers, franchisees, and financial-service users that no fixed contact center can cover.
Baseline Alfagift delivery/points contact volume and franchisee query load for one region, then pilot the consumer workflow on WhatsApp ahead of the next Ramadan surge.
Entry: Alfagift order, delivery & loyalty service · 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.