What is WhatsApp Business API?
WhatsApp Business API refers here to the WhatsApp Business Platform, Meta’s business messaging option. It has defined message categories, delivery-based charges and a customer service window. These rules govern customer replies and automated workflows. A connection alone does not explain which messages you can send or what a conversation will cost.
Keep the messaging route separate from the software doing the work. A chatbot is an automated conversation system. An API is an interface used by software. WhatsApp Web is the environment used by the computer-based worker covered later. These terms are not interchangeable.
For a business in Malaysia or elsewhere, start with the task: answering enquiries, supporting customers or handling follow-up. Establish the connection method, messaging rules and charging basis before choosing software.
WhatsApp Business app vs API vs WhatsApp Web
Use this comparison to distinguish the routes, not rank them. Platform messaging rules and the behaviour of Terabot’s WhatsApp Web worker are covered below. Business app pricing, account limits and automation permissions need separate confirmation.
The number of people using a system is different from the number of automated workers. A plan offering unlimited workers does not establish WhatsApp’s user or device limits. Ask about each separately.
Use the table as a procurement checklist. Confirm who needs access, whether automation is permitted for the chosen method, and which messaging rules apply. Do not assume that a WhatsApp Web workflow is an official API integration, or that Platform templates apply unchanged to another route.
| Route | Who it is for | Cost | Automation allowed | Number of users | Templates |
|---|---|---|---|---|---|
| WhatsApp Business app | Assess against your team's messaging needs | Needs confirmation | Needs confirmation | Needs confirmation | Requirements need confirmation |
| WhatsApp Business Platform (API) | Businesses planning messaging around Platform rules | Charged when messages are delivered; free allowances apply | Check the intended workflow against Platform rules | Needs confirmation | Non-template messages only within the 24-hour customer service window |
| WhatsApp Web | Teams considering a worker operating the web interface | Web access pricing needs confirmation; Terabot's worker prices are announced at launch | WhatsApp's terms restrict automated use | Needs confirmation | Platform template rules should not be assumed to authorise Web automation |
Cloud API and Business Solution Providers: what to clarify
When evaluating WhatsApp Cloud API or a Business Solution Provider, ask the supplier to identify the exact connection method. Confirm Cloud API hosting, provider responsibilities, onboarding steps and provider fees separately from Platform pricing and messaging rules.
Ask who supplies the messaging connection, who supplies the inbox or chatbot, and who handles problems. Request a clear explanation of any charges beyond Meta’s delivered-message charges. Treat these as procurement questions, not assumptions about a particular provider.
Ask how the software handles the customer service window and message categories. A useful proposal should explain the complete workflow, not merely use the label “API”. Compare the messaging connection, automation logic and commercial agreement separately.
Templates, the customer service window and opt-in
The Platform allows non-template messages only within the 24-hour customer service window. Build this restriction into the workflow. Do not treat every customer conversation as an unrestricted channel or plan to use non-template messages outside that window.
This rule does not cover every template requirement. Before implementation, confirm the applicable template process and permissions with your Platform supplier. Having a template does not prove that every intended use is permitted.
Make opt-in a deliberate business requirement. Record whether the customer wants the intended communication. Do not assume that having a phone number establishes consent. This is a planning recommendation, not a complete statement of Meta’s API opt-in policy. For Terabot’s WhatsApp Web worker, opt-in contacts and a WhatsApp Business number are specifically recommended.
Message categories and delivered-message pricing
The five pricing categories are marketing, utility, authentication, service and Meta Business Agent. Message charges apply when messages are delivered. For budgeting, separate delivered-message charges from the cost of your software or service.
Do not assume every customer interaction has the same charging basis. Rate cards distinguish message categories and markets. Country rates are not reproduced here. A Malaysia budget and a global budget should each use the applicable official rate card, not a rate from another market.
The pricing details were checked 6 October 2026. Before committing to a workflow, identify the expected categories and ask how the supplier reports delivered messages. For Meta Business Agent, confirm the relevant usage-based charging details separately. Do not treat it as another ordinary message rate.
Free allowances and how they apply
Pricing provisions include a 72-hour free entry point window associated with click-to-WhatsApp ads or a Facebook Page call-to-action. They also include the first 1,000 service messages per month free per business phone number. Keep these separate in your cost model.
Do not confuse the free entry point window with the 24-hour customer service window. The first is a pricing provision. The second limits when non-template messages can be used. A free pricing window does not override messaging rules.
The service-message allowance is not a general allowance for every category. Ask how the supplier identifies qualifying messages and reports usage against the allowance. Meta’s pricing provisions do not establish whether a separate software supplier charges for its own service.
What is a WhatsApp chatbot?
A WhatsApp chatbot is software designed to carry out an automated conversation on WhatsApp. The term describes conversational behaviour, not a connection method. Ask what the chatbot does and how it accesses WhatsApp. Both affect the workflow and its risks.
Separate conversation quality from task completion. Answering a question is different from completing a task in a CRM, email account or spreadsheet. Define the expected outcome so you can assess a system by the work it completes, not just its replies.
For an agent-focused next step, see the WhatsApp AI agent guide. Keep the access method central to your evaluation. A capable conversational system does not, by itself, establish official API access or permission to automate a particular WhatsApp interface.
Where Terabot fits: a worker using WhatsApp Web
Terabot (our product), by AITG (our company), provides AI digital workers for businesses. Each worker gets its own computer: a private virtual machine. Workers operate around the clock in apps a team already uses, including CRM, email, WhatsApp Web, spreadsheets and web apps. Available worker types include Sales, Support, Back office, Computer-use and WhatsApp workers.
On WhatsApp, the worker replies to customer chats through WhatsApp Web on its own computer. It is not the official WhatsApp Business API and never sends bulk messages. WhatsApp’s terms restrict automated use, so a WhatsApp Business number and opt-in contacts are recommended. This route carries terms-of-service risk.
Monthly plans include unlimited digital workers and differ by AI and computer usage. Prices are announced at launch. Businesses can request an invitation to the private preview if they want an agent that does the work.
A practical decision checklist for Malaysia and global teams
Choose the messaging route before comparing automation features. If you need the official Platform, ask for explicit confirmation that the connection uses it. If the system operates WhatsApp Web, assess it as a separate route with restrictions on automated use.
Define the work. Specify whether the system should answer chats, complete tasks in other apps or both. Decide what should happen when a request falls outside the planned workflow. Document these requirements rather than assuming the capabilities exist.
Request a cost breakdown that separates message categories, delivered-message charges, free provisions and supplier charges. For Malaysia and global operations, check the applicable market rates rather than assuming they are interchangeable. Confirm user access and template handling separately. Your team should be able to explain the connection, the work and the commercial terms in plain language.
Last updated October 6, 2026