How to Build a WhatsApp Lead Qualification Bot for Coaches (No Code Required)

Most coaches spend hours chasing leads who were never going to buy. A properly built WhatsApp qualification bot — using WATI and Make.com — filters the time-wasters out automatically and puts only warm, pre-screened leads on your calendar.

Why WhatsApp, and Why Now

WhatsApp has a 98% open rate. Email has, depending on your list, 20–35% if you're lucky. For coaches selling high-ticket programs — anything above ₹50k or $600 — the speed at which you respond to a new lead is one of the biggest conversion levers you have. Most coaches respond hours later, by email, and wonder why the prospect went cold.

The system I build for clients at Systrify flips this entirely. When someone fills out your lead form — whether it's on your website, a Meta ad, or a Linktree — they immediately get a WhatsApp message within 60 seconds. Not a generic "thanks for enquiring." A structured conversation that asks them the three things you actually need to know before you get on a call: budget, timeline, and their core problem.

By the time they hit your calendar, they've already told you everything. Your discovery call becomes a closing call.

The Tools You Need (and What Each One Does)

You need two tools to build this: WATI and Make.com. Here's how they divide the work.

WATI is a WhatsApp Business API platform. It gives you a verified WhatsApp business number, lets you build interactive message templates (with buttons and quick replies), and provides a webhook that fires every time a lead responds. It costs around $49/month on the starter plan and connects to the official Meta WhatsApp Business API — meaning your messages come from a verified green-tick number, not a grey-market scraper. There are alternatives like Interakt and AiSensy, but WATI has the cleanest Make.com integration.

Make.com is your automation backbone. It listens for new leads (from your form, your CRM, your ad platform), triggers the WATI conversation, reads the responses, and routes qualified leads into your calendar tool and your CRM. If you've already got a Make account from other workflows, you can add this as a new scenario.

Optional but recommended: Calendly or GHL's booking widget for the final booking step, and HubSpot or GoHighLevel as the CRM where qualified leads land.

Building the Flow: Step by Step

Here is the exact scenario I build for coaching clients. It assumes your leads come in via a Typeform or a GHL form — adjust the trigger module if yours is different.

• Step 1 — Trigger: Watch for new form submissions. In Make.com, add a Typeform or Webhooks module as your trigger. Set it to watch for new submissions. Each submission passes through the lead's name, email, and phone number.
• Step 2 — Send the opening WhatsApp message via WATI. Add a WATI module: "Send Template Message." Select your pre-approved template (you'll need to create this in WATI's dashboard first — a simple "Hi [name], I saw your enquiry about [program]. Are you open to a quick chat on WhatsApp?" with a Yes/No button). WATI handles the delivery instantly.
• Step 3 — Listen for the reply with a WATI Webhook. Create a new webhook in WATI's dashboard that fires when a contact replies. In Make.com, add a WATI "Watch Messages" trigger module and connect it to this webhook. When the lead taps "Yes," the scenario resumes.
• Step 4 — Send the qualification questions. Add three sequential WATI "Send Message" modules. Each one asks a single question and waits for a reply: (1) "What's your main challenge right now?" (free text), (2) "What's your budget range?" (button options: Under ₹50k / ₹50k–₹1L / ₹1L+), (3) "How soon are you looking to start?" (button options: This month / Next 30 days / Just exploring). Collect the responses using Make.com's variable storage between steps.
• Step 5 — Score and route the lead. Add a Router module in Make.com. Set conditions: if budget is "₹1L+" AND timeline is "This month" → qualified route. Everything else → nurture route. The logic here is simple but powerful — you stop spending time on leads who are browsing.
• Step 6 — Qualified leads get a booking link via WhatsApp. On the qualified route, send a final WATI message: "Perfect — sounds like a great fit. Here's a link to book a 30-minute call with me: [Calendly link]." Then add a HubSpot or GHL module to create the contact and tag them as "Qualified - WhatsApp Bot."
• Step 7 — Nurture leads go into a sequence. On the nurture route, add the lead to a GHL or ActiveCampaign nurture sequence tagged "WhatsApp - Not Ready." They get a different email flow — educational content, case studies, no hard sell.

Total build time if you've used Make.com before: 90 minutes. Total modules: around 12. Monthly cost to run: ~$49 WATI + whatever Make plan you're on. The first qualified booking this saves you time on pays for six months of the tool.

The One Mistake That Kills These Bots

I've seen coaches build this flow and get no responses. Almost always, it's the same problem: the opening message reads like a robot wrote it. Meta's template approval process means you need pre-approved messages, but that doesn't mean they have to sound corporate.

The best-performing opening message we've tested at Systrify is casual and specific: "Hey [First Name] 👋 — Harsh here from [Program Name]. Just saw your enquiry. Are you on WhatsApp for a quick chat?" With two buttons: "Yes, let's go" and "Email is better." The word "quick" does a lot of heavy lifting — it lowers the barrier. The personalisation (first name, program name) signals this isn't a blast message.

The other mistake: asking too many questions in one message. Break it up. One question per message, wait for the reply. People respond to conversations, not surveys. WATI's interactive message format (buttons instead of free text where possible) also dramatically increases completion rates — people are lazy, and a tap beats typing every time.

If you want to see the exact message templates we use, or want us to build this for your business, that's exactly the kind of system we set up at Systrify — usually in a single build session.