How to automate WhatsApp lead follow-up into your CRM

Breakop Guides · 10 min read

Here's a request we hear in almost the same words from real-estate agencies, clinics, training centres and online stores: "When someone fills in our form, put them in the CRM, send them a WhatsApp message, and remind sales if nobody calls them."

It sounds small. In practice it's the difference between answering a lead in one minute and answering the next day — and a lead that waits a day has usually already talked to a competitor. This guide walks through how the automation works, which tools to use, and the mistakes that break it.

What we're building

Choosing the automation tool

Three tools do this well. The right one depends on volume, budget and where your data needs to live.

• Zapier — fastest to set up and the most ready-made connectors. Costs grow with the number of tasks, so it suits lower volumes.
• Make — visual, flexible with branching and error handling, and usually cheaper than Zapier for multi-step flows.
• n8n — can run on your own server, so data stays with you and volume doesn't drive the price the same way. Needs a bit more technical setup and someone to maintain the server.

If you're unsure: start with Make or Zapier to prove the flow in a week. Move to n8n if volume or data rules push you there.

The WhatsApp part: what you need to know first

Automated messages go through the WhatsApp Business Platform (the Cloud API), not the WhatsApp Business app on a phone. That means:

• You need a Meta Business account, a verified business, and a phone number dedicated to the API. Many companies connect through a provider (a "BSP") that handles setup and gives a shared inbox for the team.
• When you start the conversation — like our first reply to a form — you must use a pre-approved message template. Write it early; approval can take time and templates that read like spam get rejected.
• Once the lead replies, you can message freely for 24 hours. After that, you're back to templates.
• Meta charges for business-initiated template messages. Check current pricing for your country before you estimate costs.
• Only message people who gave you their number and agreed to be contacted — put a clear line about WhatsApp on the form.

Building it, step by step

Step 1 — One trigger per lead source

Start the workflow when a lead arrives: a webhook from your website form, the Meta Lead Ads trigger, or an incoming WhatsApp message. Normalise the fields straight away into the same shape: name, phone (in international format, e.g. +20…), email, source, product of interest.

Step 2 — Find or create in the CRM

Search the CRM by phone number first, then email. If the person exists, add a new deal or activity instead of creating a duplicate. Duplicates are the fastest way to make sales stop trusting the CRM.

Step 3 — Send the first WhatsApp message

Send your approved template with the lead's name and what happens next. Keep it short and human:

Hi {{name}}, thanks for your interest in {{product}}. {{agent}} from our team will call you today. You can reply here any time with questions.

Step 4 — Assign and notify

Assign the owner in the CRM and tell them where they already look — a WhatsApp group, Slack, email or the CRM app. Include the lead's details and a link to the record.

Step 5 — Wait, then check

Add a wait (say, 60 minutes during working hours), then check the CRM for a logged call or a status change. Nothing logged? Remind the owner. Still nothing after another hour? Tell the manager. This single step is usually worth more than everything else combined.

Step 6 — Weekly report

A scheduled workflow that counts leads by source, median time to first human contact, and conversion by source. Send it to management every Monday.

Mistakes that break it

• Phone numbers in five formats. Normalise to international format at the start, or search and WhatsApp both fail.
• No error path. When the CRM or WhatsApp is down, the workflow should retry and alert someone — not silently drop the lead.
• Messaging at 3 a.m. Respect working hours for reminders to staff, and think about it for customers too.
• Templates written last. Template approval is the slowest step. Start it on day one.
• Nobody owns it. Someone must get the error alerts and know how the flow works. Ask for a one-page description of the workflow when it's handed over.
• Never tested with real edge cases. Test a duplicate lead, a number without country code, an Arabic name, a form submitted twice, and a lead outside working hours before going live.

How long does it take?

For one lead source, one CRM and one WhatsApp number, an experienced automation specialist typically builds and tests this in a few days, plus however long Meta takes to verify the business and approve templates. Each extra source, routing rule or report adds time.