Playbook S.01 — WhatsApp lead capture and follow-up automation
Every WhatsApp enquiry, captured and followed up.
anymus wires WhatsApp into your CRM so every enquiry is captured, routed, and followed up automatically — no lead left sitting unread in a chat.
The manual loop.
For most Indian businesses, WhatsApp is where the leads actually arrive — and where they quietly die. Enquiries land in a personal chat, get a reply if someone's free, and then sink under the next hundred messages. Nobody knows how many leads came in this week, who replied, or which conversations went cold. The business runs on whoever remembers to scroll back.
The system handles it.
With the system in place, every WhatsApp enquiry becomes a CRM record the moment it arrives. The right person gets notified, a first response goes out immediately, and follow-ups fire on a schedule until there's an answer — while you see every open conversation and its status in one pipeline instead of someone's phone.
✳ If someone has to remember it, the system is broken.
Signs this playbook applies.
Field note:if two or more of these sound familiar, it’s worth a conversation.
Leads arrive on WhatsApp but live and die inside chat threads
First replies depend on who's free — sometimes hours, sometimes never
Nobody can say how many enquiries came in last week, or from where
Conversations go cold because no one remembered to follow up
From manual to running.
We map how the work happens today before automating any of it — fit first, software second.
Map the enquiry flow
We trace where WhatsApp enquiries come from — ads, the website, referrals — and what should happen to each type, before touching any tooling.
Connect WhatsApp to a CRM
Using the WhatsApp Business API, every incoming enquiry creates or updates a CRM record automatically, with the full conversation attached.
Automate the follow-up
Instant first responses, scheduled nudges, and routing to the right person — all triggered by real activity, with edge cases flagged for a human.
Launch & tune
We watch the first weeks of real conversations and tune the rules — timings, templates, routing — against what actually happens.
Fair questions, straight answers.
This playbook is delivered as part of Automation — the full chapter covers scope, process, and outcomes.
Common in
File S.01 — end of playbook