WhatsApp Business API Malaysia: What SMEs Need to Know

Joshua Chua · 4 August 2026

If you run a business in Malaysia, you probably use WhatsApp Business already. The app works fine for a solo operator. But at some point you outgrow it, and the next step is the WhatsApp Business API.

This post covers what that actually involves. The setup, the costs, the Meta requirements, and what I wish someone had told me before I started.

When the regular app stops being enough

The app works if you are solo and getting a few messages a day. You reply manually, send quick replies, done.

But the moment two people need to see the same messages, it breaks. Only one phone can be logged in. You cannot assign conversations. There is no shared history.

That is when businesses start losing track. Staff answers on their own number, and when they leave, the customers go with them.

The API turns WhatsApp from a single-user app into an actual business system. Multiple agents, one number. Shared inbox, automation, CRM.

Most people do not realise they have outgrown the app until they are already losing messages.

What the setup actually looks like

You need a Meta Business account. If you do not have one, I will set it up for you as an add-on. Then you register a new number under your account. You own the number, not me.

Meta verifies the business. Takes a day or two. Once that is done, I connect everything: chatbot, CRM, shared inbox, booking flows. I test it before it goes anywhere near your customers.

Your part is maybe 20 minutes. Providing business details, verifying the number. I handle the rest.

What about ban fears?

Bans happen to people using unofficial tools. Mod apps, scrapers, backdoor connections. Those should get banned.

The official API does not carry that risk. Your business is verified, your number is registered, Meta knows who you are. You are going through their front door, not sneaking through a window.

The approval process used to be slow. Weeks, sometimes. That is mostly fixed. Business verification takes a day or two. Template approvals about a day.

What Meta actually charges

Meta charges per conversation, not per message. A customer messages you, that opens a 24-hour window. You can send as many messages as you want inside that window for one fee.

Business-initiated conversations cost more than customer-initiated ones. For a Malaysian SME getting 50 enquiries a week, you are looking at roughly RM40-80/month in Meta fees.

This goes straight to Meta through your account. I include a USD 10/month credit for the AI chatbot usage on top of that.

Can a business keep their existing number?

The API needs a fresh number that is not already on WhatsApp. You cannot run both on the same number.

Coexistence is possible on the API itself, but for now I am not providing that. The system I use is registered under the owner's name. I am managing it for them. It is not an app I created, and it does not belong to me. It belongs to the customer who paid for it.

My product is a chatbot. Ideally, the owner should not have to check it or get stuck managing it. It should just work, and the owner can go about their day and focus on the work they are good at.

Your existing chats stay on the old number. You set up the new one, tell your customers, and everything goes through the API from there.

Some businesses keep the old number running for a transition period. They set an auto-reply on it pointing to the new one. After a month or two, traffic has moved.

What surprised me about the API

How much Meta controls the format. You cannot just send whatever you want, whenever you want. Outside the 24-hour window, you need pre-approved templates. There are categories for different message types.

It felt limiting at first. But that structure is what keeps deliverability high. Every message follows Meta's guidelines, so nothing gets flagged as spam. The restrictions that feel annoying are the same ones that make the channel trustworthy.