One buyer timeline before anyone opens Excel

Definition

Lead capture is the job of creating one contact and one Booking from every enquiry source — portal dump, web widget, Meta, walk-in QR, or CP WhatsApp — then starting qualification on that same timeline instead of a personal spreadsheet.

Every source invents its own inbox

Portals email a CSV. The website posts to a founder Gmail. Instagram sits in a personal DM. The site supervisor keeps a notebook. By evening three people are calling the same buyer. CoPulse is the Project inbox after the lead arrives: visitors can become leads from web chat, WhatsApp connects on Gupshup, Meta is Instagram and Messenger (and post comments, as on the home FAQ). You still import CSV v1 for portal dumps — there is no magic portal API in this playbook. Duplicate-leads is the sibling job that merges twins; this job is getting the first row to exist fast.

Omnichannel sequence

Omni buyer journey starts with inquiry from website, then WhatsApp qualify and brochure. Capture is that first hop plus CRM write. Voice and email wait until a slot or a file exists.

How it runs in CoPulse

Conversation agent is the runtime. A Growth campaign is the wrong first move if they just messaged you. Autonomous list send is for cold audiences you approve later, not this inbound pile. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. WhatsApp live catalog is Gupshup, not an invented Meta Cloud hop. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a shared inbox that vanishes when a broker leaves.

Operator setup

Organization wallet. Project channels. Real Estate labels: Buyers & Tenants, Bookings.

99acres CSV at 9:40 p.m. plus a widget ping

Ops imports twenty portal rows. Workflow opens WhatsApp (template if the number never wrote you — 24h window). A twenty-first buyer is already on the web widget; visitors → lead becomes the same New enquiry pattern without a second spreadsheet. RE Qualifier asks budget. Operator merges one duplicate in Customers. Click-path: Setup → Channels, Agents → Studio, Agents → Workflows, Customers kanban.

Library Site-visit booking blitz describes this family as: triage inquiries, qualify BHK and budget on WhatsApp, then book a visit. Capture stops at the first two beats. Visit Caller is a later playbook. Illustrative funnel on that template: Reached 100, Replied 62, Qualified 38, Visit booked 18, Visited 12 — estimates, not a promise. Pricing: each WhatsApp or voice hop debits the Organization wallet; creating a Booking does not.

Operators assemble this job on the Project. Click-path remains Setup → Channels (WhatsApp/Gupshup, Web, Meta, Email/SES, Phone/Plivo as needed) → Setup → Customers → Pipeline → Agents → Studio (RE Qualifier) → Router → Workflows on New enquiry enter → wallet top-up. Do not add SMS. Keep the quotable definition in the brief for the team: Lead capture is the job of creating one contact and one Booking from every enquiry source — portal dump, web widget, Meta, walk-in QR, or CP WhatsApp — then starting qualification on that same timeline instead of a personal spreadsheet. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. While you implement, keep the parent playbooks directory, New enquiry stage, Web overlay, Developers, Agent Studio, Growth campaigns, and wallet-only pricing in the same runbook. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Human handoff stays in the omnichannel inbox. Appointments and calendars are the visit truth when this job books time. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them under Agents → Workflows. The agent router keeps the wrong bot off this thread. Knowledge bases hold PDFs you uploaded. Preview the Organization wallet before a blast. Property managers should not paste sales token stages onto leasing jobs. The Lead capture playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on some leaves are library template estimates from Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back — not an SLA and not Insights. If this job mentions money, the Organization wallet is the meter. If it mentions a Saturday slot, Visit Caller and T-24h templates are in-product; cab dispatch is not. That is the honest operating manual for this URL.

Channel sequence (one job, not extra URLs)

Capture hops. Qualification and visits are sibling jobs on their own URLs. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Capture sits at the front of the Site-visit booking blitz template. These percentages come from CoPulse library playbook templates (Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back). They are not your project's Insights chart.