WhatsApp Business API sales automation: a step-by-step guide

WhatsApp Business API sales automation means connecting WhatsApp to your own software, so that incoming messages are gathered in one panel, common questions are answered automatically, warm leads are handed to a person and orders flow into your other systems. Unlike the free WhatsApp Business app, the API works for whole teams and plugs into your CRM — but it comes with Meta’s rules on reply windows, template messages and consent.

In many countries — including Türkiye, where we are based — a large share of small-business sales happens on WhatsApp. Questions arrive there, quotes go out there, orders are confirmed there. As volume grows, the same problems appear: unanswered messages, nobody quite sure who is talking to which customer, and opportunities that are never followed up. Below we explain what the API is, how it differs from the app and what we watch for, step by step, when automating a sales flow.

The WhatsApp Business app versus the API

The WhatsApp Business app is the free app you install on a phone. It is a good start for a small business, offering a profile, quick replies, labels and a catalogue. But it has limits:

• The number of people and devices that can use the same number at once is limited.
• Messages cannot be connected to other software — a CRM, an order system, reporting.
• Automation stops at quick replies and simple greeting messages.

The WhatsApp Business API is the interface through which Meta lets businesses connect to WhatsApp through software. It is not an app; it lets your own software, or a platform you use, talk to WhatsApp. With it:

• Several agents can talk to customers from the same number, in one panel.
• Messages can be passed automatically to your CRM, order system or accounts.
• Chatbots, automatic routing and triggered notifications can be built.

The core rules you need to know

Understand Meta’s rules before you use the API. Use that breaks them can lead to the number being restricted or shut down.

The customer service window. When a customer writes to you, a window opens in which you may reply freely — 24 hours from their last message. Within it you can answer questions, give prices and carry on the conversation.

Template messages. Outside that window — if you are sending the first message, say, or getting back to a customer days later — you may only send template messages that Meta has approved in advance. Templates are classified by purpose, such as order notifications, appointment reminders or promotional announcements, and pricing follows those categories. Meta revises its prices and categories from time to time, so we go through the current rate card together at set-up.

Consent. Before you send anyone marketing messages, they must have agreed to receive messages from you on WhatsApp. This is Meta’s rule — and good practice. It also sits comfortably with data-protection law such as the GDPR in Europe, or Türkiye’s KVKK, which is similar.

Setting it up, step by step

1. Business account and verification

The first step is to open a Meta Business account and have your business verified. Verification asks for company details and documents. This step directly affects how many messages you will be able to send later, and how trustworthy your account appears.

2. Number and display name

You choose the phone number to use with the API and the business name customers will see. The display name also goes through Meta’s approval. Depending on how the number has been used before — in the app, or on a personal account — the migration steps can differ, so we review its current state together before choosing.

3. Infrastructure: direct, or through a platform?

You can connect to the API directly through Meta’s own cloud infrastructure, or use a platform that manages it for you. The decision usually rests on a few questions. Which systems will messages flow into? How many agents will work on them? Does it matter where the data is held?

4. Receiving messages (webhook)

When a customer writes, Meta forwards the message to an address you specify — a webhook. This is the heart of the system: the message is stored, routed to the right agent or to the bot, and a record is opened in the CRM if needed.

5. Designing the conversation flows

The value of automation comes from well-designed flows. A typical sales flow runs like this:

1. A greeting and a few short questions to understand the need.
2. Automatic answers to frequent questions — price range, delivery times, payment options.
3. Handing a customer who is close to buying over to a person.
4. Automatic updates after a quote or an order.
5. A timely, rule-compliant template reminder to a customer who has gone quiet.

A bot that hands the conversation to a person straight away — whenever it does not know the answer or the subject is sensitive — matters as much to the customer experience as the automation itself. We go further into this in our article on customer service chatbots.

6. Connecting to other systems

The real time saving begins where WhatsApp stops working on its own: a new chat opening a customer record in the CRM, a confirmed order landing in the accounts, an automatic message to the customer when the parcel ships.

7. Measuring

How many messages came in, how quickly were they answered, how many became sales, which question is asked most? Without those numbers, you cannot tell whether the automation is working.

Bringing Instagram into the same panel

For many businesses, customer conversations do not happen only on WhatsApp — they flow through Instagram messages too. Meta’s Instagram API makes it possible to bring both channels into one panel, so that whichever channel a customer uses, the same team replies with the same history. Meta Cty, the platform we built, grew out of exactly this need: it gathers WhatsApp and Instagram conversations into one panel and automates the sales flow, with bulk messaging kept within Meta-approved standards. Instagram has its own rules, which we cover in our guide to Instagram DM automation.

Common mistakes

• Leaving everything to the bot. When a customer cannot reach a person, the sale slips away too.
• Sending bulk messages without regard for the rules. Unsolicited or overly frequent messages lower the number’s quality rating and can lead to restrictions.
• Not connecting messages to other systems. Using the API as nothing more than “a bigger WhatsApp” leaves the real gain on the table.
• Not measuring. You cannot improve flows without knowing what works.

Where to start

Our advice is to start small: first gather incoming messages in one panel and answer the handful of most frequent questions automatically. That alone noticeably shortens reply times for most businesses. CRM and order connections come next, and campaign and reminder flows last.

Frequently asked questions

Can we keep using the WhatsApp Business app alongside the API?

It depends on how the number is set up. Moving a number to the API can change how — or whether — the phone app can still be used with it. We check your number’s current state before anything is migrated, so there are no surprises.

Can we send bulk messages with the WhatsApp Business API?

Yes, within Meta’s approved template rules and only to people who have agreed to hear from you. Sending outside those rules can get a number restricted or closed, so we build the flows accordingly.

Do we have to change the software we already use?

Usually not. We first try to connect your existing systems; replacing one only comes up when it is genuinely necessary.

What happens if a connection breaks?

The flow pauses and notifies you; no data is lost. Once the issue is fixed, it resumes where it left off. Under monthly maintenance we also follow Meta’s API changes and adapt the flows.

If you want to automate your sales flow across WhatsApp and Instagram, see our automation and integration service or write to us. We start by reviewing your current set-up together and picking the step that will save you the most time.