One reviewable lead record
Bring approved lead context into a clear record instead of relying on memory and scattered chat history.
WhatsApp + lead CRM · Founding-client pilot
A focused pilot for interior designers and civil contractors handling leads from calls, ads, Instagram, WhatsApp, and referrals—and losing track of the next action.
WACRM is a working demo; automatic channel ingestion is not yet implemented.
No public office address claimed.
The operational view
A prospect can call, reply to an ad, send an Instagram message, move to WhatsApp, and share details across several conversations. When status, owner, context, and next follow-up live in different places, serious enquiries become difficult to recover.
What we can build
Bring approved lead context into a clear record instead of relying on memory and scattered chat history.
Define practical states such as new, contacted, qualified, site visit, proposal, won, lost, and follow-up.
Make next action, responsible person, and follow-up date visible rather than implied.
Map message templates, consent, escalation, opt-out, and CRM updates after platform access is confirmed.
Pilot path
Review five recent enquiries from first contact through current status and next action.
Agree stages, owners, qualification fields, reminder rules, and exception handling.
Use approved test data to demonstrate the workflow before connecting live channels.
Check whether ownership and follow-up become easier to see; publish no result without evidence.
Working demo
Current demo covers lead creation, pipeline movement, ownership, and follow-up visibility. It does not currently promise automatic ingestion from WhatsApp, phone calls, Meta ads, Instagram, or referrals.
Boundaries
Direct answers
Not yet. WACRM currently demonstrates lead, pipeline, and follow-up management using one reviewable lead record, defined pipeline stages such as new, contacted, qualified, site visit, proposal, won, and lost, and visible ownership with reminders. Each live channel, including WhatsApp, phone calls, Meta ads, Instagram, and referrals, requires separate access, platform rules, consent, and failure-state discovery before it can be connected, and the pilot begins with test or explicitly approved data rather than live traffic.
Their enquiries often arrive through several channels and move through qualification, visits, proposals, and long follow-up windows. This is a working hypothesis that the founding-client pilot will test.
No blanket autonomy is promised. Pilot scope defines approved templates, human handoff, opt-out, exceptions, and which actions require review.
A working WACRM demo shows the proposed lead-to-pipeline-to-follow-up workflow: lead creation, pipeline movement across defined stages, ownership assignment, and follow-up visibility. It does not currently promise automatic ingestion from WhatsApp, phone calls, Meta ads, Instagram, or referrals, and there are no client outcome metrics yet. The founding-client approach starts by tracing five recent leads from first contact through current status, then designs and configures the pipeline against that real data before any reliability review is published.
Start with context
Useful first WhatsApp message: current process, lead or product volume, biggest handoff problem, tools already used, and ideal next step.