What can you automate on WhatsApp without AI?

Ask whether two teammates following the same written instructions would take the same next step. If they would, the task may suit a configured workflow. If they need to negotiate, interpret an unwritten exception, or resolve conflicting information, keep a person involved.

A button labelled 'Reservations' gives a workflow an explicit route. A message saying 'We are bringing a group but our plans may change' needs more interpretation. You can still collect the basic enquiry details without pretending the full request has been resolved.

Choose a frequent request that your team already handles consistently. Use the list below to compare the work required. These are workflow design examples; check which steps your chosen software supports before building them.

Write the workflow in plain language first. A teammate should be able to walk through it without knowing the software. If a step says 'the system handles it', replace that phrase with the actual condition or action.

Copy this worksheet and fill it in for one task:

Consider an illustrative hotel enquiry. The task is to collect a reservation request for the reservations team. It is not to confirm a booking.

The customer selects 'Ask about a stay'. The workflow asks for arrival and departure dates, then the number of guests. It shows those details back for confirmation and offers 'Send enquiry', 'Change details' and a path to a person. Once the request reaches the receiving queue, the reply says: 'Your enquiry has been sent to reservations. The team will check availability and confirm the options here.'

If a date is missing or invalid, ask a specific clarification. If the customer asks for a negotiated group rate, pass the conversation to reservations. Do not keep collecting routine details while ignoring the request for a person.

This workflow needs no model-generated answer. Actual availability checks, room holds, payment collection and booking confirmation are separate actions that require supported integrations, permissions and their own failure handling.

AI may help when customers phrase the same question in different ways or need an explanation drawn from approved business information. Human authority is still needed for decisions your business reserves for its team. An AI interpretation should not turn a booking request into a confirmed reservation without an authoritative result.

Keep the first workflow as simple as the task allows. This follows the approach described in Anthropic's guidance on workflows and agents: choose predictable steps for well-defined tasks and add complexity when the task requires it. The worksheet here applies that principle to WhatsApp enquiry handling; it does not require Anthropic or any other AI provider.

Removing AI from a workflow removes the need for a model to generate its replies. It does not remove software setup, integration costs or Meta's applicable messaging charges. On Waaru, the platform is free and optional AI features are paid separately. Meta message charges remain separate.

Fixed rules must also respect consent, opt-outs and WhatsApp's messaging window. Outside 24 hours of the last customer message, the Business Platform requires an approved message template. Automation needs a clear escalation path. Check the WhatsApp Business Messaging Policy before planning outbound follow-ups.

Use an expected-result checklist before publishing. Test a completed request, but spend time on the paths where the customer gives an unexpected answer. Check what arrives in the receiving inbox, not only what the bot sends.

After launch, review where customers stop, repeat themselves or ask for a person. A completed flow is not automatically a resolved customer request. Use those observations to improve the specific step that failed before adding more branches.

For an inbound customer conversation, use the Logic Flow creation guide to map your questions, conditions and handoff. Check the supported nodes before promising an action. Waaru's separate Automation flows handle operational triggers and actions; their available steps should not be assumed to exist in every conversation flow. If you are still choosing the task, read the WhatsApp business automation overview alongside your worksheet.