New: a free AI proposal + interactive prototype for Malaysian SMEs this quarter.
Retail

One WhatsApp number, app and AI together: how coexistence works for a Malaysian SME

Coexistence lets a Malaysian SME keep its WhatsApp Business App on staff phones while an AI agent answers routine enquiries on the same number. Here is what stays manual, how the hand-over should work and what to ask a provider.

Codech Solutions builds AI agents, document automation and business insights for SMEs in Malaysia and Hong Kong. This guide explains how one WhatsApp number can serve both your staff and an AI agent.

Many Malaysian SMEs run their customer service on one WhatsApp number. The clinic receptionist confirms appointments on it, the shop assistant answers stock questions on it, and the distributor's sales team takes repeat orders on it. That number is usually tied to the WhatsApp Business App on one or two phones.

Until recently, adding an AI agent to that number meant a hard choice. Moving the number to Meta's WhatsApp Business Platform (the Cloud API) opened it to automation, but staff lost the familiar app on their phones. Many owners decided the trade was not worth it.

Meta now supports what it calls coexistence: the same number can stay on the WhatsApp Business App while also being connected to the Cloud API. Training providers have started explaining the approach to Malaysian businesses, for example in this guide to a coexistence strategy, and large local firms are putting AI assistants in front of customers, as CelcomDigi has done with Sophia AI. This article explains, in plain terms, what coexistence means for a smaller business: what stays manual, what an agent can answer, how the hand-over to a person should work, and what to ask a provider before you sign anything.

A shop owner and a staff member behind a homeware shop counter, each holding a phone and handling customer messages together.
A clinic receptionist in Kuala Lumpur replying to a patient on her phone at the front desk

What coexistence actually is

Coexistence lets one WhatsApp number run on the WhatsApp Business App and Meta's Cloud API at the same time. Your staff keep replying by hand on their phones, while software such as an AI agent sends and receives messages on the same number. Customers see a single conversation, and both sides can read everything that has been said.

In more detail, it links two things to a single phone number.

  • The WhatsApp Business App, which your staff already use on their phones. They keep replying by hand, as they do today.
  • The Cloud API, which lets software send and receive messages on the same number. This is where an AI agent or an automated notification connects.

Customers see one number and one conversation. They do not need to know whether a reply came from your receptionist or from the agent. Messages sent by either side appear in the same chat, so your staff can read what the agent said before stepping in.

The connection is normally set up by a Meta business solution provider or a developer working through Meta's onboarding flow. Your existing number, profile and contacts stay in place.

Why it matters for a small business

The old choice between the app and the API was really a choice between control and capacity. Coexistence removes most of it.

Staff keep the app they know

Front-line staff do not need new software or new habits on day one. The receptionist who knows every regular patient by name can keep handling the conversations that need that knowledge.

Routine questions stop piling up

Most SMEs answer the same handful of questions many times a day: opening hours, prices, stock, delivery areas, booking slots, how to pay. These are the messages an agent can take, including after hours, while staff deal with the rest.

You can start small and back out

Because the app keeps working, you can switch the agent on for a narrow set of questions, watch how it performs, and widen its scope only when you are satisfied. If it does not work for your business, your staff are still on the app they always used.

What stays manual, and what the agent answers

The most useful planning step is to decide, before anything is built, which conversations belong to people and which to the agent. Here is how that split often looks for three kinds of business. Treat these as examples to adapt, not rules.

A dental clinic receptionist speaking in person with a patient at the front desk, a phone lying face-down beside an appointment book.

Clinic

  • Agent: opening hours, doctor schedules, booking and rescheduling within available slots, directions, what to bring for a first visit.
  • Person: anything about symptoms, test results, medication or fees for a specific patient. A clinic agent should never give medical advice.

Retail shop

  • Agent: stock checks against your current list, prices, delivery areas and charges, order status, return policy.
  • Person: complaints, refunds, custom orders, bulk discounts and any customer who is clearly upset.

Distributor

  • Agent: repeat orders for standard items, price list questions, delivery schedules, sending a copy of an invoice or statement.
  • Person: credit terms, special pricing, overdue accounts and new trade customers.

A simple test helps: if a trained new hire could answer the question from a written sheet in their first week, the agent can probably answer it too. If the answer depends on judgement, a relationship or money outside the price list, keep it with a person.

How the hand-over should work

The hand-over from agent to person is where most of the value sits, and where most poor setups fail. Get it right and customers barely notice. Get it wrong and they repeat themselves, or worse, wait for a reply that never comes.

1. The agent knows its limits

Write down the topics it must not answer. When one comes up, it says plainly that a member of staff will reply, and stops.

2. The conversation is flagged, not lost

The chat is marked for a person, ideally with a short summary of what the customer wants. Because staff see the same thread in the app, they can read the history instead of asking again.

3. Someone is responsible for the queue

Name who picks up handed-over chats during opening hours, and what the agent tells customers outside them. An unanswered hand-over is worse than no agent at all.

4. The agent steps back

Once a person replies, the agent should stay quiet in that conversation until the matter is closed. Two voices answering the same customer is confusing.

What to ask a provider before you start

Coexistence is a Meta feature, and the exact conditions, supported features and onboarding steps are set out in Meta's own developer documentation. They can change, so check the current version with your provider rather than relying on a blog post, including this one. These are the questions we would ask.

  1. Is my number eligible? Ask whether your current app version, country and account meet Meta's current requirements for coexistence.
  2. Which app features change? Some features on the phone may behave differently or stop working once the number is connected to the API. Ask for the current list in writing, and check it against how your staff use the app today.
  3. What happens to chat history? Ask whether existing conversations carry over and how far back.
  4. Who owns the account and the data? The WhatsApp Business account and the conversation data should belong to your company, not to the provider.
  5. How are messaging charges billed? Meta charges for some types of business-initiated messages through the API. Ask how your provider passes these on and whether there is a mark-up.
  6. Where is personal data stored, and who can see it? Customer names, phone numbers and messages are personal data under Malaysia's Personal Data Protection Act 2010. Ask where the agent's data is kept, for how long, and how access is controlled.
  7. Can the agent read my real information? Stock, prices and booking slots should come from your own systems, not a document that someone forgets to update. Our integrations page shows the kinds of systems this usually involves.

A sensible first month

Pick one narrow job, such as booking confirmations or stock questions. Write the answers the agent may give and the topics it must hand over. Run it for a few weeks while staff watch the conversations in the app, and count three things: how many chats the agent closed alone, how many it handed over, and how many it got wrong. Those numbers, from your own business, tell you whether to widen it.

Two colleagues in a small warehouse office planning their first weeks with a printed checklist and a wall calendar.

For retail-specific examples, see our retail page, and for how we scope and run pilots, our how we work page.

Next step

If you would like to know whether your WhatsApp number and processes are ready for an agent, book an AI audit. We will look at the questions your team answers most often, which of them an agent could take, and what the hand-over to your staff should look like.

Frequently asked questions

Can my staff keep using the WhatsApp Business App if we add an AI agent?

With coexistence, yes. The same number stays on the app on staff phones while software connects through Meta's Cloud API. Check your number's eligibility and the current feature list with your provider first, as Meta sets and updates the conditions.

Will customers know whether they are talking to a person or the agent?

They see one number and one conversation. We recommend the agent says plainly when it is handing over to a member of staff, so customers know a person will reply.

What should an AI agent not answer for a clinic?

Anything about symptoms, test results, medication or a specific patient's fees. A clinic agent should handle logistics such as hours and bookings and pass clinical questions to staff.

Does using an AI agent on WhatsApp involve personal data rules?

Yes. Customer names, numbers and messages are personal data under Malaysia's Personal Data Protection Act 2010. Ask your provider where data is stored, for how long and who can access it. This is not legal advice.

How do we know if the agent is working?

Count how many chats it closes alone, how many it hands over and how many it gets wrong over a few weeks, and compare with how your team handled the same questions before.

Free AI proposal + interactive prototype · no obligation

Want this working in your business?

Book a free 45-minute call. We send a free AI proposal and an interactive prototype within 1 to 2 weeks.

Free AI Proposal & Prototype

Get a free AI proposal and a prototype you can try

We reply within one business day.

By sending this form, you agree to our Privacy notice.