How WhatsApp AI agents use tools and take actions

A knowledge base can explain your dispatch policy. A tool can check an order’s current status in your order system, provided the customer is allowed to see it. Those are different sources with different jobs.

A policy saying that orders usually leave the warehouse promptly is not evidence that this customer’s parcel has shipped. If the live record is unavailable, say that the status could not be checked.

Keep general information in a reviewed knowledge base. Check the integration’s documented actions for actions involving an individual customer’s records.

Developers call fetching information a read and changing it a write. Looking up a booking and moving it to another date need different permissions and checks.

For a change, confirm the intended record, the requested change and any required approval. Then check the business system’s response. Telling a customer “your booking has moved” before confirmation creates a promise the system may not have kept.

Some tasks belong with a person, especially when someone needs to approve a price or an exception. The sales workflow leaves a custom quote with the teammate who decides what work the quote includes.

Decide what the customer hears for each failure. Try these situations in your chosen system. They are suggested checks, not Waaru test results.

The Model Context Protocol, or MCP, gives AI applications a shared way to discover and call tools. The MCP tools specification describes tool names, the information each tool needs, its results and how it reports errors.

MCP is not a guarantee of a particular action. Each server offers its own set of tools. The application must still check permissions and the details supplied, and ask a person to approve an action when required. A tool’s description does not replace these checks.

The WhatsApp MCP guide explains how this relates to WhatsApp. Before planning a workflow, check that the service is running and supports the action you need.

No. The Waaru SDK for Node.js helps developers call the public API from their server. Its methods send messages, read conversations and delivery status, stream permitted media, and manage or verify callbacks. It does not provide order lookups or MCP tools.

Use the Node SDK guide and the official @waaru/sdk package for supported methods and examples. Published SDK beta.4 covers 32 operations. The REST API also has newer operations and fields; the SDK guide explains which version supports each one. Check each method’s required scope and keep its key on your server.

Choose one action and try it with made-up data in a test environment. Record what you expected, what happened, which system supplied the result and what the customer would hear if it failed. Never include secrets or customer records in a public test report.

Use the AI-agent test guide for the evaluation sheet and the handoff guide for requests a person must own.

Before adding more tools, check whether a fixed flow or an agent is the right fit. Check whether the customer’s task actually completed.