What is the WhatsApp Business API?

The WhatsApp Business Platform lets software support business messaging. It can connect conversations with team inboxes and business workflows, but the API itself does not organise your customer process.

Start a conversation

When a platform integration may help

Consider it when staff repeatedly copy message details into another system, cannot see who owns a request or need controlled updates from a business record. If a small team handles a modest number of conversations reliably, a simpler setup may be enough.

For example, a customer’s order reference could be matched to an approved status and routed to the responsible employee. Unknown customers, disputed orders and unclear requests should have a human path. This is an illustrative design, not a promise that every accounting package connects automatically.

Understand the messaging window

WhatsApp allows replies without a template within 24 hours of the user’s last message; outside that window, approved templates are required. Automated responses need a clear escalation route. Opt-in and opt-out rules still apply.

Design for the case where an update is ready after the window closes or a template is unavailable. Do not let a blocked message silently become a completed customer task.

WhatsApp Business Messaging Policy

Calculate costs from the actual message mix

Meta’s pricing page describes charges by delivered message, recipient market and category. Service messages are free, with additional free-message conditions and volume tiers described by Meta. Provider, inbox, automation and support fees can still apply.

Estimate each message category, destination market and monthly volume. Ask for the current rate card and distinguish Meta fees from the provider’s charges. Include exchange-rate assumptions and taxes in a rand budget. An old “cost per conversation” table is not a dependable current quote.

WhatsApp Business Platform: current pricing and message categories

Check the integration before committing

Identify who owns the business account and number, what access is required and who will maintain the integration. Test whether the intended business system exposes the exact records and actions you need.

Agree how to handle duplicate events, changed order details, failed delivery and a provider outage. Test permissions and use synthetic examples before connecting customer records. Confirm that relevant platform restrictions allow your specific activity; approval should never be assumed from the industry name.

Define what a working result looks like

A useful result is more than a successful outgoing message. A staff member should be able to see the request, responsible person, delivery outcome and next action, and recover when something goes wrong.

Aitsa can scope communication and admin workflows after a free initial conversation. The quote identifies the intended integrations, testing, account arrangements and separately payable platform costs.

Explore communication workflow integration

Sources and further reading

Prepared by Aitsa Integration. Updated 13 September 2026. These primary sources support the guidance; requirements and provider terms can change.

A useful place to start

More room for the work that moves you forward.

Bring a workflow to improve, a team that needs practical AI skills, or a decision about where to begin. Let’s find a useful next step.

Start a conversationA free first conversation. No commitment to a project.