Project 2 min read
WhatsApp Data Collection Automation
ManyChat WhatsApp automation recovering missing lead data.
Objective #
Two goals in one automation:
- Recover missing user data — email addresses and other incomplete fields from existing WhatsApp contacts
- Collect course information — scheduling preferences and related data through a guided conversational flow
Architecture #
Meta-approved WhatsApp template triggers outbound contact
ManyChat data-collection sequence activates on user reply
Email addresses, course preferences, scheduling availability
Google Sheets via ManyChat’s native integration
Workflow #
Technical Constraints #
| Constraint | Impact | Solution |
|---|---|---|
| Reply buttons hard-capped at 3 options | Cannot present many choices at once | Sequential branching with follow-up branches |
| No native multi-select interaction | Cannot collect multiple day availability in one interaction | Schedule broken into smaller decision steps |
| List messages unreliable | Alternative multi-option UI not production-safe | Stick to reply buttons with branching |
WhatsApp reply buttons cap at three options with no native multi-select — list messages proved unreliable, so scheduling and course preferences had to be broken into sequential branching steps.
Data Handling #
All responses stored in Google Sheets through ManyChat’s native integration. The real complexity was downstream field-mapping in a branching flow — values could be missed, duplicated, or inconsistently saved depending on the user’s path. Flow structure was designed to keep collected data consistent across all possible paths.
Branching conversational paths risk missed or duplicated field writes — flow structure was designed so email, course preferences, and scheduling data land consistently in Google Sheets regardless of which reply path a user takes.
Outcome #
A working WhatsApp automation system that re-engaged leads using approved template messaging, collected and validated missing data, captured scheduling preferences for course operations, stored all responses in a central Google Sheet, and transformed a platform limitation into a usable conversational workflow.