60-day silent tours: new inventory on WhatsApp, then voice

Definition

Cold-buyer win-back is the job of selecting contacts dormant 60-plus days after a tour, sending a localised price or inventory WhatsApp (and optional email), then using Visit Caller to book a fresh site visit — not a single “we miss you” template.

One nostalgia template is how dormant lists rot

Ops dumps everyone quiet into a blast. Library says localise and rebook. Interested is not a CRM state to filter on. Do not mix construction silence. SMS not live. Adaptive nurture not shipped.

Omnichannel sequence

WhatsApp campaign, voice, then Site visit booked again. Email optional.

How it runs in CoPulse

Campaigns + voice. Workflow on enter dormant. Autonomous list-based win-back is allowed here with honest metrics. Autonomous agents may send a list-based win-back after you approve the plan and pick an existing library template. Success today is sends, reads, or contacted — not visit booked or token paid. Move the Booking with a workflow or by hand. 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

Filter, templates, Plivo, wallet, pipeline dormant column.

Whitefield 3BHK toured in March, silent since

Move to dormant. Send library-style five new 3BHKs. She replies. Sunday because Saturday is saturated. Visit Caller confirms. Card returns to Site visit booked. If autonomous ran, ops still moves stages; report shows reads.

visited-not-booked is the shorter stall. Illustrative: Contacted 100, Re-engaged 22, Visit re-booked 8, Closed 3. Pricing: campaign + voice on the wallet.

Operators assemble this job on the Project. Click-path remains Customers filter → stage Dormant → Library → Growth → Studio Visit Caller → Workflows → wallet. No SMS. Keep the quotable definition in the brief for the team: Cold-buyer win-back is the job of selecting contacts dormant 60-plus days after a tour, sending a localised price or inventory WhatsApp (and optional email), then using Visit Caller to book a fresh site visit — not a single “we miss you” template. Autonomous agents may send a list-based win-back after you approve the plan and pick an existing library template. Success today is sends, reads, or contacted — not visit booked or token paid. Move the Booking with a workflow or by hand. While you implement, keep the parent playbooks directory, Dormant / re-engage, Phone 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 Cold-buyer win-back 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)

Win-back hops. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

From playbook-templates.ts re-reengage. 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.