All articles
AutomationNovember 12, 20269 min read

WhatsApp Business API automation: follow-ups, order confirmations and support without getting banned

How the WhatsApp Business Platform works (templates, the customer service window, opt-in, quality rating) and how to automate confirmations, reminders and support without losing your number.

WhatsApp automation that does not get your number restricted runs on the official WhatsApp Business Platform (the API), starts conversations only with approved templates and only with people who agreed to receive them, and replies in free form only inside the window that opens when a customer writes first. Within those rules you can automate order confirmations, delivery updates, reminders, follow-ups and first-line support. Numbers get restricted mostly for the opposite: unofficial tools, purchased lists and messages people never asked for.

What is the difference between the WhatsApp Business app and the Business Platform (API)?

The WhatsApp Business app is a free phone app for a small business. A person answers by hand; there is a business profile, a catalog, labels, quick replies and simple greeting and away messages. It is enough while one or two people handle all the chats.

The WhatsApp Business Platform is an API with no inbox of its own. Your CRM, bot or helpdesk connects to it and sends and receives messages programmatically, either directly through Meta's cloud API or through a solution provider. It is built for volume, for several operators on one number, and for automation tied to your data.

The platform is paid: Meta charges for messages, and the rates depend on the message category and the recipient's country. Both the rates and the billing model itself have changed more than once, so rely on Meta's current pricing page rather than on articles, this one included.

What are message templates and the customer service window?

A conversation can start in two ways, and the rules for them differ.

The business writes first. You can only send a template: a message with fixed text and variables (name, order number, date) that Meta has approved in advance. Templates fall into categories (at the time of writing: marketing, utility and authentication), and the category affects both the cost and how strictly the template is reviewed. A template can be rejected if it is vague, misleading or does not match its declared category.

The customer writes first. Their message opens a customer service window: a limited period during which you can reply in free form, with text, files and buttons, and without templates. Each new message from the customer restarts the window. Once it closes, only templates remain.

The length of the window, the template categories and the limits on how many conversations you can start per day are set by Meta and revised from time to time. Design the automation so that these are settings, not assumptions baked into the code.

Why do you need the customer's opt-in?

Meta's policy requires a business to have the person's consent to receive its messages on WhatsApp. A phone number sitting in your database is not consent.

In practice, opt-in is collected like this:

  • a checkbox or a clear line in the order or booking form that names WhatsApp explicitly;
  • a "get updates on WhatsApp" button on the website or in the customer account;
  • a QR code at the point of sale that opens a chat with you.

Keep a record of when and how consent was given. And offer a simple way out: replying "stop" should really work and remove the person from your mailings.

What is worth automating on WhatsApp?

  • Order confirmation: items, total, address, with "confirm" and "change" buttons.
  • Delivery updates: handed to the courier, on the way, delivered.
  • Abandoned-request follow-up: a person left a request or started checkout and went quiet. One polite message with a link to continue, provided there is consent.
  • Reminders: about an appointment, a payment, a service that is about to expire.
  • FAQ with an AI assistant: inside the service window the assistant answers from your knowledge base. How such assistants are built is covered in our article on support chatbots.
  • Handover to a human: when the question is unusual or the customer is unhappy, the chat goes to an operator together with the conversation history.

The general rule: automate the messages the customer is waiting for. The closer a message is to something the person just did, the more calmly it is received.

What is the quality rating, and why do numbers get restricted?

Every number on the platform has a quality rating. Meta calculates it from how recipients react to your messages: whether they block you and whether they report you as spam.

When the rating drops, the consequences build up gradually: individual templates may be paused or disabled, the limit on conversations you start yourself stops growing or is lowered, and after serious or repeated violations the number or the whole account is restricted. A new number starts with a small limit that grows as long as quality stays high.

What usually causes trouble:

  • sending to lists that were bought or collected without consent;
  • promotion disguised as a service message;
  • messaging too often, with the same text for everyone;
  • no way to unsubscribe.

A separate cause is unofficial tools that automate the regular app or WhatsApp Web. That violates WhatsApp's terms of service: such numbers get banned, and you should not count on getting them back.

How do you connect WhatsApp to a CRM?

The point of automation is that messages are triggered by events in your data, and the answers flow back into it.

  • Triggers from the CRM: an order or deal changes status, and the matching template goes out with the data filled in.
  • Incoming messages in the customer card: a message is matched to a contact by phone number, and the manager sees the whole thread next to the deal.
  • Bot results in fields: a confirmation, a new date or a reason for refusal is saved as data instead of staying buried in chat text.
  • Message statuses: the platform reports whether a message was delivered and read. Undelivered ones are worth recording and moving to another channel.

Two practical details that often trip teams up: phone numbers have to be stored in one international format, and consent belongs in a separate field with a date. More on linking systems is in our article on CRM integration; the scenarios themselves we usually build as an automation project.

How do you get started with the API?

  1. A number. You need a number that can receive an SMS or a call for verification. Whether it can stay in the app at the same time depends on Meta's current rules, so check before moving a number with live chats.
  2. Business verification. You will need a Meta business account; for full use the company usually has to be verified with documents, and the display name goes through approval. This takes time, so plan for it.
  3. Templates. Start with a few utility ones: confirmation, delivery, reminder. Write them specifically and without sales language.
  4. A small pilot. One scenario, customers who opted in, modest volume. Watch delivery, replies, blocks and the quality rating, and only then expand.

What mistakes are typical?

  • Treating WhatsApp like an email newsletter. A personal messenger forgives far fewer unwanted messages.
  • Sending notifications from a number nobody reads. People reply to notifications, and those replies have to land somewhere.
  • A bot with no way to reach a human. A customer who cannot get through to an operator blocks the number.
  • Forgetting about the service window. The operator answers too late and the message does not go out. You need a fallback template that reopens the dialogue.
  • One number for everything. Reactions to promotional campaigns affect the rating of the same number that sends your order confirmations.
  • Hard-coding platform rules. Meta changes them, and an update should not mean rebuilding the system.

When is a Telegram bot or email the better channel?

WhatsApp is not the only channel, and not always the best one.

  • A Telegram bot fits when your audience already uses Telegram. The bot can write to anyone who started it, with no template approval, and the interface is richer: buttons, menus, mini apps. See our article on Telegram bots for business.
  • Email is better for long messages, documents, invoices and newsletters where an instant reaction is not needed. It has no service window, and a letter is easy to find a month later.
  • A phone call is needed when you want an answer now and a message may go unread. Routine calls can be taken over by an AI voice agent.

Choose by where your customers already are. A combination often works: WhatsApp for statuses and short questions, email for documents.

Where to start

Write down the messages your staff send to customers by hand every day, and mark the ones tied to an event: order created, appointment tomorrow, request left unanswered. Those are the first candidates for automation. With that list, tell us about the task: we will suggest which scenario to pilot first and what needs to be prepared for it.

FAQ

Can I connect an existing WhatsApp number to the API?

Often yes, but moving it may affect how the number works in the app and what happens to chat history. The rules change, so check them before migrating; many businesses start with a new number.

Can I send promotional broadcasts through the WhatsApp Business API?

Yes, as approved marketing templates and only to people who opted in. Recipient reactions affect the quality rating, so segment the audience and limit frequency.

How long does template approval take?

Templates are reviewed by Meta and the timing is not guaranteed: sometimes it is quick, sometimes it takes longer. Submit templates in advance and do not plan a launch for the day of submission.

What if we need to reply after the service window has closed?

Send an approved template inviting the customer to continue the conversation. Once they reply, the window opens again and you can write in free form.

Do I need a solution provider, or can I connect directly?

Both options exist: directly to the cloud API from Meta, or through a provider that adds a shared inbox and support. The choice depends on whether you have developers and which systems you already use.

Can an AI assistant answer customers on WhatsApp?

Yes. Inside the service window it answers from your knowledge base and hands the chat to an operator when a question goes beyond it. Like any sender, it can start a conversation only with a template.

Shall we discuss your project?

Tell us about it — we'll come back with an estimate and a proposal.

WhatsAppTelegram