Portal ping to booked visit in 48 hours — one deal

Definition

Portal lead follow-up is the 48-hour job that takes a 99acres, MagicBricks, or Housing enquiry, writes it to New enquiry, qualifies on WhatsApp, books a calendar slot, reminds, and confirms on voice — all on one Booking.

Portal CRMs follow up like email inboxes

The portal already “has CRM.” The buyer still waits hours. CoPulse sits after the lead arrives. Import or paste, then this playbook. No invented portal webhook in marketing copy — operators still land the row. Dedup against website and Meta siblings. SMS is not the after-hours fallback.

Omnichannel sequence

Portal (source) → WhatsApp qualify → voice confirm → WhatsApp reminder. Email is unused unless NRI docs later.

How it runs in CoPulse

Matches the library playbook: RE Qualifier, Visit Scheduler, Visit Caller. Campaigns on WhatsApp for the opener. Workflows move stages. Autonomous is the wrong tool for a fresh portal inbound. 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

Gupshup + Plivo connected. Reminder template approved. Pipeline named.

Twenty Housing rows, two visits by Saturday

Friday 8 p.m. import. Workflow fires qualifier templates. Twelve reply in-session Saturday morning. Four pass four fields. Visit Scheduler books two Saturday 11s and two Sunday 10s. Visit Caller runs Friday for the Saturday pair. Ops watches kanban, not a portal dashboard. Illustrative: visit booked 18% of reached on the library funnel — your dump will differ.

Click-path: Customers import; Growth only if you batched a template; Agents → Studio Visit Caller greeting; inbox for the hot four. Brokers ICP uses this daily. Pricing: templates plus minutes on the Organization wallet.

Operators assemble this job on the Project. Click-path remains Setup → Channels WhatsApp and Phone → Library reminder template → Agents → Studio three roles → Workflows → pipeline → wallet preview for the dump size. Keep the quotable definition in the brief for the team: Portal lead follow-up is the 48-hour job that takes a 99acres, MagicBricks, or Housing enquiry, writes it to New enquiry, qualifies on WhatsApp, books a calendar slot, reminds, and confirms on voice — all on one Booking. 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, Site visit booked, 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 Portal lead follow-up 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)

Portal-specific hops on the shared blitz job. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Directly the Site-visit booking blitz conversion estimates. 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.