Automation by function

A complete lead follow-up system on WhatsApp with n8n

How to build the system that answers every enquiry in seconds, follows up on a schedule, stops when the lead replies and tells your team who to call.

By the RinooSol team Published ⁨5⁩ min read

Most enquiries are lost in the first day: the message sent at 9 pm that gets an answer at 11 am, the form entry nobody saw, the lead that got one reply and never a second. A follow-up system fixes the first day and the next week with four pieces: a place every lead lands, a first reply that goes out in seconds, a sequence that keeps going until the lead answers, and a list that tells your team who needs a call. This is how we build it on n8n with a WhatsApp API, and what you decide along the way.

What you need

  • One place for leads. A Google Sheet is enough to start: one row per lead, with columns for date, name, number, source, what they asked about, status and last contact. A CRM such as Zoho or HubSpot can take its place later without changing the workflow.
  • A WhatsApp number connected through an API, either a private Evolution API instance or the official platform; the comparison says which fits.
  • The sources. A website form, Facebook or Instagram lead ads, and the WhatsApp number itself. Each becomes a trigger.
  • An n8n instance to run it, managed or your own.

Piece 1: every lead lands in the sheet

Each source gets a trigger in n8n:

  • A Webhook trigger for the website form, with the form builder set to post to it.
  • The Facebook Lead Ads trigger for ad leads, which delivers the name, number and the campaign.
  • The WhatsApp API's webhook for new conversations, filtered to first messages from numbers not already in the sheet.

All three feed the same node: append a row. The row records the source and the campaign, which is what lets you see later which channel brings leads that buy, not just leads.

Piece 2: the first reply, in seconds

Immediately after the row is written, a send message node replies on WhatsApp in the language the lead wrote in: a thank-you, one line about what they asked for, and one qualifying question. Keep it to one question: "Which area are you looking in?" for an estate agency, "Which course interests you?" for a training centre. The answer comes back through the same webhook and is written to the row.

For a form or ad lead who has not yet messaged you, this first message is the one that has to respect WhatsApp's rules: they gave you the number for this purpose, so it is a reply to their enquiry, not a cold message. Keep it that way.

Piece 3: the sequence

A wait node holds the workflow for the interval you choose, then an if checks the row: has the status changed, or has the lead replied? If not, the next message goes out. A typical sequence for a product or course enquiry:

  1. Day 0: the instant reply.
  2. Day 2: a short message with the one thing most people ask next, such as the price range or the start date.
  3. Day 5: an offer to call, with a question that is easy to answer with one word.

Three messages over a week is enough. More becomes noise and risks the number. The timings and the texts live in a small settings sheet, so you can change them without opening n8n.

Piece 4: the sequence stops, and a person is told

The moment a reply arrives from a number in the sequence, the workflow sets the row's status to replied, ends the sequence for that number, and sends a WhatsApp message to the salesperson with the lead's name, number, what they asked and the full exchange. From here the conversation is human. If the salesperson does not log a call within a set time, a reminder goes to them, and after a second interval to a manager.

A lead can also be stopped by hand: change the status in the sheet to called or declined and the sequence ends. This is what keeps the list honest.

The outcomes column

Every lead ends as won, lost or waiting, with a date. Once a month, a scheduled workflow counts them by source and sends a summary: leads, replies, calls, deals per channel. This is the report that decides next month's ad spend, and it costs nothing to produce once the rows are there.

Mistakes we have seen

  • A long first message. A paragraph on WhatsApp reads as a brochure; one line and one question reads as a person.
  • No stop condition. A sequence that keeps sending after the lead replied, or after they bought, is the fastest way to lose both the customer and the number.
  • Follow-ups outside the lead's hours. Schedule the sequence to send during the day in the lead's timezone, not at 3 am because the workflow ran then.
  • Qualifying by questionnaire. Three questions before a human appears loses the lead. One question, then a person.

What it looks like built for you

The lead follow-up page shows the build for a training centre; the sales automation page the fuller pipeline it can grow into. A free consultation is where we map your sources and write the first message with you.

Read next

Tell us what you do by hand today

Book a free consultation and we will design the automation with you.

We reply in Arabic or English

Last updated: