WhatsApp automation: what it can and cannot do

For many customers in India, WhatsApp is the default way to talk to a business. It is no surprise that owners ask whether it can be automated: send order updates, answer common questions, remind people about appointments. Some of that is possible. Some of it is not, and some is possible but unwise.

This article describes the general picture. The details change as the platform changes its rules, so confirm current terms before you plan around a specific feature.

The WhatsApp Business app on a phone is a manual tool with a few conveniences such as quick replies and labels. Automation at scale uses the WhatsApp Business Platform, accessed through an API. Businesses typically reach it through an approved provider, and the setup involves a verified business account and a dedicated phone number.

This is a separate system from the app, with its own onboarding. A number used on the API generally cannot be used in the regular app at the same time, so decide which number will serve which purpose.

Business-initiated messages sent outside an active conversation generally use pre-approved message templates. Each template is reviewed against the platform's policies, and approval is not guaranteed or instant. Wording that looks promotional or misleading can be rejected.

Inside a conversation the customer has recently started, you have more freedom to reply. The rules about time windows and categories have changed over time, so check the current documentation rather than assuming.

Messaging through the API is not free. Pricing generally involves charges per conversation or per message depending on category, plus whatever your provider charges for access and tools. These rates are set by the platform and providers, change from time to time, and vary by country and message type.

We do not quote prices here because they would go out of date. When planning, ask your provider for the current rates, estimate your monthly volume, and include these fees as a running cost alongside hosting and maintenance.

Automation does best with messages that are expected, short and useful. Order confirmations, delivery updates, appointment reminders and payment links are typical examples. Customers who asked for the information are happy to receive it.

It cannot message people who have not agreed to hear from you. Platform policy and good practice both require consent, and bulk unsolicited messages risk blocked numbers and a damaged reputation. It cannot guarantee that a message is read, or that a template will be approved.

It also cannot replace judgement. A chatbot that fails to understand a complaint and answers cheerfully with the wrong menu makes things worse. Sensitive situations, such as disputes, refunds and upset customers, should reach a person quickly. A bot that pretends to be human is a bad idea, so say clearly when a customer is talking to an automated assistant.

Begin with one or two high-value, low-risk messages, such as order confirmations. Make opting out simple. Keep a log of what was sent to whom. Review replies regularly to see what customers actually ask, then improve your answers.

Treat WhatsApp as a potential integration target for your system, not a guaranteed feature. Access depends on your account's approval, your provider and the platform's rules at the time.

Before committing, ask a few direct questions of any messaging provider. Which message categories do they support, and how are they billed? How long does account verification usually take? What happens to your number and message history if you leave? Can conversations be handed to staff inside your own system?

Ask for current documentation rather than a sales summary, and keep a record of what you were told. Policies change, and a provider that is open about limits is easier to trust than one that promises everything. Also check whether support is available in your working hours.