What “lead follow-up automation” actually means
Buyers often ask for “AI that talks to leads.” What they need first is glue: a webhook that never silently drops, a CRM row that sales will open, and a first message that does not violate WhatsApp policy. AI classification can sit later for lead scoring or draft replies — it is optional for week one.
Define success in numbers before choosing logos: median minutes from form submit to first WhatsApp, percent of leads with owner assigned within one hour, and duplicate rate under a few percent. Those KPIs survive tool swaps.
If marketing runs festival campaigns, design for spike volume and provider rate limits — a flow that works at 20 leads/day can stall at 200 without queues and alerts.
The minimum viable path
Source → validate phone → dedupe → CRM create/update → WhatsApp template → owner alert. Everything else (nurture sequences, AI scoring, multi-brand routing) is phase two.
- One template category per use case (utility vs marketing)
- One CRM module as source of truth
- One human escalation channel
What is not follow-up automation
A shared WhatsApp Business app on one phone is not automation. A Zap that only appends to Sheets without owner assignment is staging, not sales enablement. A chatbot that cannot hand off with context is a dead end.
Meta and Google lead sources that Indian SMEs actually use
Meta Lead Ads and Google Lead Form Extensions dominate paid capture for local services, education, clinics, and B2B. Website forms and landing pages still matter for branded search. Each source has different payload shapes — map fields once in a staging step rather than rewriting CRM logic per channel.
Meta webhooks can retry; Google lead forms may land via email or partner connectors depending on setup. Document the exact trigger your ops team can replay when a campaign manager changes the form.
UTM and campaign IDs belong in CRM custom fields from day one. Without them, marketing cannot attribute which ad creative deserved budget after automation “worked.”
Meta Lead Ads quirks
Phone formats vary (91 prefix, spaces, leading zeros). Normalize before dedupe. When Meta renames a question label, your field map breaks — version forms carefully and keep a staging Sheet for the first week of a new creative.
Website and landing forms
Prefer a webhook or server-side handler over scraping thank-you pages. If the site is WordPress with a plugin that only emails, upgrade the capture path before automating — do not build Playwright around a broken form.
Dedupe rules that prevent double WhatsApp blasts
The fastest way to burn trust is two templates for the same phone within minutes because Meta retried and the website form also submitted. Dedupe on E.164 phone first, email second, and optionally a short time window (e.g. 24 hours) for “same campaign” collisions.
Decide update-vs-create policy: returning leads should update the existing CRM record and alert the previous owner unless territories changed. Blind creates produce parallel deals and confused salespeople.
Log the dedupe decision (created / updated / skipped) into a CRM note or automation log field so audits answer “why no message?” without guessing.
- Normalize +91 and strip spaces before compare
- Blocklist test numbers used by agencies
- Skip WhatsApp if status is Already Converted or Do Not Contact
- Alert ops when dedupe skip rate spikes (often a form bug)
Sheets staging vs CRM-first
Some teams stage raw leads in Sheets for a week while sales validates field quality, then promote clean rows to CRM. That is fine temporarily — permanent Sheets-as-CRM is how follow-ups die. See when to stop using Sheets as CRM.
CRM write path: fields, owners, and SLAs
Automation fails when CRM fields are optional chaos. Agree on mandatory: phone, source, campaign, city, product interest, and owner. If sales refuses to open records without those, fix definitions before you buy more zaps.
Owner routing can be round-robin, city-based, product-based, or “last owner wins.” Encode the rule in the workflow, not in a WhatsApp group argument. For Zoho-heavy stacks, patterns live in Zoho CRM automation.
Write status transitions deliberately: New → Contacted only when a human or verified session reply happens — not when the template merely accepted by the provider.
Owner alert design
Slack/email alerts should include lead name, phone deep-link, CRM URL, and template sent. Avoid dumping full PII into public channels — use private sales channels and least-privilege bots.
SLA timers
A second reminder at 30–60 minutes if status is still New catches leads that fell through during lunch or festival rush. Keep reminders sparse; spammy internal alerts get muted.
WhatsApp templates, windows, and human handoff
Outside the 24-hour customer care window, outbound needs approved templates. Marketing templates have stricter rules than utility. Work with a legitimate provider — details on WhatsApp Automation.
First message should set expectation: who you are, why you are writing, and a clear next step (call back, reply YES, book slot). Avoid dumping a brochure PDF as the first touch.
After the buyer replies, humans or a scoped chatbot continue inside the session. Log handoff so the next agent sees prior template content.
Template variables that break in production
Empty name fields produce awkward “Hi ,” messages. Fallback to “there” or skip the name variable. Never put prices in template variables unless finance owns the source — stale offers create disputes.
When a chatbot belongs in this path
After-hours FAQ, course eligibility quizzes, or appointment slot picking. Not as a replacement for sales on high-ticket B2B. Compare website chatbot vs WhatsApp.
Choosing Zapier, Make, or n8n for the glue
All three can implement the path. Zapier wins when you need speed and a non-technical owner at modest volume (packages from ₹15,000 OTP). Make shines for visual branching and hosted ops. n8n wins when task bills hurt or you want self-host control (from ₹18,000 OTP). Deep comparison: n8n vs Zapier vs Make.
Do not pick by logo loyalty. Pick by who edits day two, monthly run volume, and whether credentials can live in US SaaS. Tool shortlist context: best AI automation tools for SMEs.
Hybrid stacks are fine: keep a simple zap for one form, move branchy multi-city routing to n8n — document which webhook is canonical to avoid double creates.
Signals to leave Zapier later
Task invoices climb after every campaign, Paths become unreadable, or compliance wants data on infrastructure you control. Migration playbook: Zapier to n8n without breaking CRM.
Compliance, consent, and audit trails in India
Store opt-in source (lead form checkbox, website consent, inbound message). Template sends without a lawful basis are how accounts get restricted. Keep retention policy for phone numbers — finance and legal should co-sign.
Enterprise buyers ask for data flow diagrams: which subprocessors touch PII, where logs live, who can export. Self-hosted n8n can help with residency narratives but does not replace process discipline — see self-host n8n in India.
Never share production API tokens in founder WhatsApp groups. Rotate keys when staff leave. Least privilege is cheaper than an incident write-up.
- Opt-in proof field on CRM
- Template name + message ID logged
- Do-not-contact list synced daily
- Weekly sample audit of 10 random leads
What we refuse to build
Unofficial WhatsApp APIs, scraped contact lists without consent, and “blast 10,000 numbers overnight” campaigns. If that is the brief, the right answer is no — then redesign a compliant acquisition path.
Common SME mistakes we fix from Chennai
Duplicate webhooks from Meta and a CRM native integration both creating deals. No dedupe. Templates fired for every status change. Owner alerts in a 200-person Slack channel. Sheets as permanent CRM with five conflicting “master” tabs.
Another frequent failure: marketing changes form questions without telling ops, so automation maps empty fields and sales gets “Unknown” leads at midnight. Version forms and freeze field IDs during campaigns.
Tool churn mid-campaign — switching providers during a festival sale without parallel run — creates silent gaps. Change windows with rollback, not heroics.
Mistake: automating a broken sales process
If nobody calls leads even when notified, automation only accelerates noise. Fix response culture and SLA before adding a third nurture sequence.
Mistake: measuring vanity metrics
“500 templates sent” is not success if reply rate and booked calls did not move. Tie dashboards to CRM stages and revenue, not message counts.
Implementation timeline and owner checklist
Typical scoped build: discovery → field map → provider setup → workflow → template approval wait → parallel test → go-live → one-week hypercare. Template approval alone can add days — plan marketing calendars accordingly. Duration ranges: how long AI automation takes.
Handover includes credential inventory, pause switch, replay steps, and who to call when Meta changes payloads. Hiring criteria: how to hire an AI automation company in India.
- Freeze CRM fields for the first live week
- Keep a kill switch for WhatsApp sends
- Sample 20 test leads across cities and products
- Schedule a 30-day review of duplicate rate
Brevia package floors for this use case
Zapier path from ₹15,000 OTP; WhatsApp-centric or n8n/Make builds from ₹18,000 OTP. Playwright only if a portal lacks API (from ₹25,000 OTP). Cost context: AI automation cost in India.
How to start with Brevia from Chennai
Bring one lead source, your CRM (or honest admission that Sheets is the CRM), monthly lead volume, and who will own day-two edits. We recommend tool and sequence after that — not before.
Specialty pages: WhatsApp Automation, n8n, Zapier, Make, Chatbot Development. Book via consultation or contact.
What we deliver in the first engagement
One production path with runbook, logged templates, owner alerts, and a clear list of phase-two ideas you should not buy yet. Restraint is part of the service.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.