WhatsApp for business operations in Malaysia, beyond the chatbot

In Malaysia, WhatsApp is not a marketing channel. It is where the work actually happens. Orders, approvals, supplier chasing, internal coordination, all of it runs through chat whether the org chart says so or not.

Most automation available locally treats this as a customer service problem. A bot answers frequently asked questions and hands off to a human when it cannot. That is useful, and it is also a fraction of what the channel could carry.

The difference in one example

Someone messages: "Need 50 units of steel rod for Project A."

A chatbot replies with a link to the procurement form, or tells someone in purchasing to look at it.

An operational system checks current stock, compares supplier pricing, drafts the purchase request against the right project code, and routes it to whoever has approval authority for that amount. The reply that comes back is the outcome, not an acknowledgement.

There are five worked examples of this on the main site.

Why the interface choice matters

Every internal system fails the same way. It gets rolled out, people are trained, and within two months half the team is back to messaging each other because it is faster.

Building on a channel people already use removes that failure mode. There is no adoption curve because there is nothing new to adopt. The behaviour change you are asking for is zero.

What it needs behind it

The chat layer is the easy part. What makes it work is everything underneath:

• Read and write access to the systems that hold the answer. Stock levels, project codes, leave balances, order status.
• Knowing who is allowed to approve what, and at what value.
• A record of what happened, written back to the system of record rather than sitting in a chat thread.
• A clear escalation path when the request is ambiguous or the value is high.

Language is not a footnote

Malaysian teams do not message in clean English. They mix Malay, Mandarin, Tamil and English, often in the same sentence, with plenty of shorthand. "Order late already ah" is a normal message. A system that only handles formal English will fail on the first real conversation.

Where to start

Pick one process where the bottleneck is coordination rather than judgement. Order status, leave requests and stock enquiries are usually the clearest starting points, because the answer already exists in a system and the delay is entirely in someone going to look it up.

Not sure which process to start with? There is a checklist.