Four fields before anyone spends a Saturday slot

Definition

Lead qualification is the job of writing BHK, budget, locality, and timeline onto the Booking, matching knowledge-base inventory, and only then offering an appointment-skill slot — so brokers do not fly to site on a portal screenshot.

“Interested” is not a budget

Launch teasers collect replies. Analytics still treat conversion as reply rate. Phone “replied” is speech-to-text after the script. If you offer Saturday 11 to everyone who typed ok, Insights will later show Saturday-slot saturation. Qualification is the gate. Adaptive nurture that waits until they qualify is not shipped — keep the conversation agent on the thread or author a drip yourself.

Omnichannel sequence

Web or portal capture already happened. WhatsApp (or web chat) qualifies. Voice confirms the visit in the next job.

How it runs in CoPulse

Conversation agent plus appointment skill. Workflows on enter Qualified can notify inventory owners. Drips only if they went silent after qualifying. 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

Knowledge PDFs per project. Calendars before you offer slots. Wallet for in-session and later templates.

Whitefield 3BHK that only said “interested”

Launch campaign shows Replied. Qualifier refuses the slot until 3BHK / 90L / Whitefield / 60 days sit on the deal. Knowledge sends Tower B. Visit Scheduler offers Saturday 11 and Sunday 10. Operator added Sunday after last week’s Insights cue — the product did not auto-open slots. Workflow moves to Qualified then Site visit booked when the calendar holds.

Click-path: inbox thread; Booking fields; Agents → Studio knowledge; appointments pane. Illustrative blitz funnel: 38% qualified of reached (template estimate). Human handoff if they argue vastu. Pricing: brochure WhatsApp debits the wallet.

Operators assemble this job on the Project. Click-path remains Agents → Studio (RE Qualifier + appointment skill) → knowledge upload → Setup → Customers → Pipeline → Router → calendars → Library for closed-window follows. Keep the quotable definition in the brief for the team: Lead qualification is the job of writing BHK, budget, locality, and timeline onto the Booking, matching knowledge-base inventory, and only then offering an appointment-skill slot — so brokers do not fly to site on a portal screenshot. 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, Qualified stage, WhatsApp overlay, Brokers, 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 qualification 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)

Qualify hops. Capture and visit booking are siblings. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Qualified 38% is a library estimate from Site-visit booking blitz. 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.