WhatsApp chatbots for business: what works in Indonesia
By Apex Horizon Digital
In Indonesia, WhatsApp is not a channel: it is the channel. Customers ask about prices, stock, delivery, and complaints in the same thread where they talked to your admin last month. That volume is exactly why chatbots are tempting, and exactly why a bad one is so damaging: it stands between your customer and the answer. Here is what we have learned building support bots that people actually keep using.
Key takeaways
- Ground answers in approved business documents instead of the open internet.
- Treat human handoff as a core feature, not an exception path.
- Automate repetitive, measurable service work rather than every conversation.
Ground the bot in your documents, not the internet
A support bot should answer from your knowledge base (price lists, SOPs, product sheets, FAQs) and say so. Grounded answers with a visible source ("from: Delivery policy §2") do two things: they keep the bot from inventing answers, and they give your team a way to fix wrong answers by fixing the document.
The handoff is the feature, not the fallback
Every good bot knows when to stop. Low confidence, an angry tone, a payment dispute: these should route to a human immediately, with the conversation history attached so the customer never repeats themselves. In practice the handoff design determines whether your team trusts the bot. A bot that hoards conversations it cannot handle creates more work than it saves.
Measure deflection, not conversations
The vanity metric is "conversations handled". The real metric is deflection: questions fully resolved without a human, without a repeat contact in the following days. Conversation logs and analytics should make this visible per topic, so you know whether to improve the knowledge base, the bot, or the product.
A realistic scope for a first bot
Start with the top ten questions your admins answer every day: they usually cover most of the volume. Wire the bot to WhatsApp, ground it on the documents that answer those questions, design the handoff, and launch. Expanding to order status lookups or appointment booking comes after the basics have earned trust.