WhatsApp Automation That Follows Up While You Sleep

Set the follow-up once and it runs without you. A drip sequence spaced over days, a conversation flow that answers on its own, or a rule that fires the second a lead arrives. Every message goes out on the Official WhatsApp Business API.

Included on every plan. No feature tiers and no upgrade fee.

The Waplify drip sequence wizard on step one of three: a named sequence with its internal description, and two audience choices side by side, Send to a fixed list selected and Auto-enroll on event beside it, with an explainer panel showing messages going out on day one through day five

The short answer

What is WhatsApp automation?

WhatsApp automation is software that sends and answers WhatsApp messages on its own, using rules you set once instead of someone typing each message. On the Official WhatsApp Business API from Meta it covers three jobs: scheduled follow-up over days, replies to an incoming message, and messages that fire when something changes in your data.

A drip sequence

Up to 7 approved templates, each with its own delay, sent to one contact at a time over days or weeks. The first message goes out on enrollment, the rest follow the schedule.
A conversation flow

A no-code flow that replies to an incoming message, asks a question, saves the answer, branches on it, and hands over to a person when the conversation needs one.
A campaign

One message to a whole list at once. Not automation in the same sense, and the right tool when you have an announcement rather than a journey.

The problem

The first message always goes out. The fourth one never does.

Almost nobody buys on the first message. Almost every business stops after it, because the follow-up is somebody remembering to do it.

Follow-up depends on a person being free

Evenings, weekends and busy afternoons are gaps in the queue. A lead that arrives at 9pm gets answered whenever somebody next opens the tab, and by then they have messaged three other suppliers.
Interested leads go quiet and stay quiet

Somebody asks for a price, gets it, and says nothing. There is no second message and no third, so the enquiry sits in the list until it is too old to be worth calling.
The reminder system is a spreadsheet

A tab of numbers, a column of dates, and a person copying and pasting the same message. It works until the list outgrows the person, and there is no record of who got what.

Four ways to automate

Pick the one that matches the job

Four separate features, not four names for one thing. Most businesses end up running all four at once on the same contact list. Each card below opens the page for that feature.

Drip sequences

Scheduled follow-up. Up to 7 approved templates, a delay of up to 30 days before each one, and a journey that can run up to 90 days. Built for welcome series, lead nurture and re-engagement.
Conversation flows

Rule-based, no-code, and always on. Ask a question, save the answer, branch on it, check business hours, call your own API, then assign the chat to a person. Built on the visual flow builder.
Triggers

What starts an automation without anyone pressing send: a keyword, a button tap, a Click-to-WhatsApp ad, a contact record changing, or a webhook from any outside tool.
Connectors

Google Sheets both ways, SMTP email from inside a flow, and IndiaMART enquiries arriving as contacts. Anything else connects on the REST API and webhooks.

The controls

Automation you can leave running

Automation that cannot be steered is just a faster way to annoy people. These four controls are the difference, and each one is a setting in the product, not a promise.

A send window your customers do not resent

Pick the days and hours follow-ups may go out in, in your own timezone. Anything due at 11pm waits for the morning.
It stops the moment a human is needed

Stop on reply is on by default. The moment a customer writes back they leave the sequence and land in your team inbox.
Reporting that names the failure

Sent, delivered, read, replied and failed for the whole sequence, then the same breakdown per step. Open a failed count and it names the reason.
Consent enforced at every entry point

Enrollment is gated on opt-in, and an opted-out contact cannot be pulled back in by any trigger, including an outside webhook.

Every message on the Official WhatsApp Business API

Automation through a Meta Business Partner, on approved templates, with no markup on Meta fees.

How the API works Book a demo

How to set it up

Four steps to your first automated follow-up

No developer, and nothing to install. If your templates are already approved, this is an afternoon.

Get your templates approved

Every automated message uses a WhatsApp template Meta has approved. Write the two or three you need and submit them. This is the only step with a waiting period.
Decide who enters

Either pick a fixed audience of contacts, groups or a filter, or write an auto-enroll rule so contacts join in real time as they are created or updated to match it.
Build the journey

Add up to 7 steps. Pick a template for each, map contact fields into its variables with a fallback, and set how long to wait before it sends.
Set the window and launch

Choose the days and hours follow-ups may send, decide whether a reply ends the journey, then run it now or schedule it up to 90 days ahead.

What people run

The four automations that pay for themselves first

New lead, answered in seconds

An enquiry from an ad, a form, a sheet or IndiaMART creates the contact, and the contact-created rule sends the first reply before anyone has opened the tab. Follow-ups continue for the next few days if nobody replies.
Onboarding that finishes itself

A welcome message on day zero, the setup steps on day one, and the thing most customers get stuck on by day three. Turn on wait-for-delivery so the steps arrive in order even if a phone was offline.
Quiet customers, brought back

Tag the contacts who have gone quiet and let the auto-enroll rule pick them up as the tag is applied. Two or three spaced messages, and anyone who replies leaves the sequence and lands in the inbox.
Status updates nobody has to send

A status change in your own system sends a webhook, the flow starts, and the customer hears about the order, the appointment or the renewal without anyone being asked to remember.

FAQ

WhatsApp automation questions, answered

The ones that come up before anyone asks about features.

1. Is WhatsApp automation legal?

Yes, when it runs on the Official WhatsApp Business API from Meta and the recipient has opted in. That is the channel Meta built for business messaging, and Waplify is a Meta Business Partner. What is not allowed is automating the consumer app or a personal number through an unofficial library or a browser script: those break the WhatsApp Terms of Service and the usual outcome is a banned number. Waplify sends only through the Official API, only on templates Meta has approved, and only to contacts who have opted in. See how the API works, or the longer read on automation ethics and compliance.

2. Can you automate sending WhatsApp messages?

Yes, in three ways. A drip sequence sends up to 7 approved templates to each contact on a delay you set. A conversation flow replies automatically when someone messages you or taps a button. A trigger starts either of those when something happens: a Click-to-WhatsApp ad, a contact record changing, a new row in a Google Sheet, or a webhook from any tool that can send one. All three run on the Official WhatsApp Business API.

3. Is WhatsApp automation free?

The free WhatsApp Business app does a small part of it: a greeting message, an away message, and quick replies you tap yourself. It cannot run a multi-step follow-up, it cannot branch on an answer, and it cannot be triggered by another system. Anything beyond those basics needs the WhatsApp Business API, which is a paid platform plus Meta conversation charges. Waplify passes Meta fees through with no markup, and every plan includes every feature on this page. See pricing.

4. Do I need approved message templates?

Yes, for any message your business starts. WhatsApp requires that outbound messages outside an open 24-hour conversation use a template Meta has reviewed. This is the rule that keeps a number healthy, so it is worth treating as a feature rather than a hurdle. Replies inside an open conversation, which is most of what a conversation flow sends, do not need one.

5. What is the difference between a drip sequence and a chatbot flow?

A drip sequence is scheduled and outbound: each contact moves through up to 7 messages on their own timeline, spaced by delays you set, whether or not they reply. A conversation flow is reactive and interactive: it runs when someone messages you, asks questions, saves the answers, branches on them, and can hand the chat to a person. Neither is a campaign, which sends one message to a whole list at once. Sequences answer "keep following up". Flows answer "reply properly without me".

6. Can I automate birthday or renewal reminders?

Not from a date field yet. Waplify has no per-contact date trigger, so a flow cannot fire on its own on someone's birthday. Two things do work today: a rule that fires when a contact is created or updated, so updating a status or applying a tag starts the journey, and a webhook from any outside scheduler, which lets your own system decide the date and call Waplify on the day.

7. When do automated messages actually send?

Inside the send window you set, in your workspace timezone. The default is 9:00am to 9:00pm, so a message due at 11pm waits for the morning rather than waking someone up. Step one is the exception: it sends the moment a contact is enrolled, so somebody who has just written to you never waits.

8. What reporting do I get on a sequence?

Enrolled, sent, delivered, read, replied, clicked and failed for the whole sequence, then the same breakdown for every individual step, so you can see which message loses people. Open a failed count and it lists the real reasons with WhatsApp own explanation. The contact log exports to CSV. One honest limit: clicked counts quick-reply button taps only, because WhatsApp does not report taps on link buttons to anyone.

9. How does a contact leave an automation?

A reply ends it by default, and so does a STOP keyword, a block, or an opt-out recorded at Meta. Whichever it was is logged as the exit reason, so the report tells you why somebody stopped rather than just that they did. An opted-out contact cannot be started into a flow again by any trigger, including a webhook from an outside system.

10. What happens when a customer replies?

By default they leave the sequence and the conversation appears in the shared team inbox so a person can take over. That is the "stop on reply" setting and it is on unless you turn it off. Switch it off for purely transactional journeys where no reply is expected, and the scheduled messages keep going while their replies still arrive in the inbox as normal.

11. How many messages can one sequence send?

Up to 7 steps. Each step waits up to 30 days before it sends, measured from the previous message, and a contact's whole journey can span up to 90 days. Step 1 always sends immediately when the contact is enrolled, so only the follow-ups wait for your send window. Each contact is enrolled at most once per sequence, so nobody receives it twice. The full sequence documentation covers every setting.

12. Will automated messages get my number banned?

The ban risk people have heard about comes from automating the consumer app or a personal number with unofficial tools. Sending through the Official WhatsApp Business API on approved templates, to contacts who opted in, is the sanctioned path and is what Waplify does. Quality still depends on how you use it: message people who asked to hear from you, honour opt-outs, and keep the content close to what the template was approved for.

13. Does WhatsApp automation work without the Business API?

Not in any way worth building on. Tools that drive WhatsApp Web or a phone through an unofficial library work until Meta notices, and the number is usually what pays for it. There is no delivery reporting, no template approval, and no support when it stops. The Official WhatsApp Business API exists precisely because businesses needed a sanctioned way to do this, and it is the only channel Waplify uses.

Limited Time Deal