Growth campaigns
Win-back creative. Exclude Booked and construction.
Dormant is a 60-day inventory problem, not a one-off template
Dormant 60-day buyers who toured but did not close get a fresh inventory angle and a new visit, using campaigns plus voice, not a one-off template. The library playbook Cold-buyer win-back already says that: WhatsApp plus phone, stages Dormant → Re-engaged → Visit re-booked → Closed. This CRM column is where those Bookings live. It is not a synonym of the playbook URL and not an autonomous “until they book” switch — success is still sends and reads.
- 60+ days after tour
- Campaign + Visit Caller
- New visit or lost
One “we miss you” template is how dormant lists rot
Ops dumps everyone quiet into Dormant and fires a single marketing template. No new inventory, no voice, no calendar. The library playbook segments 60+ days, localises price-drop or new units, then books a fresh site visit. Insights will not auto-build this audience from campaign Interested (that state is not first-class). You query CRM (last visit, stage, idle days) or a static list. Adaptive nurture is not shipped. SMS win-back is not live. Do not mix this column with construction buyers who are supposed to be quiet between slabs.
Segment, send, talk, rebook
WhatsApp campaign, then phone qualification/visit, same as the library template channels.
- Define dormant e.g. Visited, no token, 60 days. Project convention.
- Campaign Growth WhatsApp to matched inventory. Wallet preview. Approved template.
- Voice Visit Caller / qualifier call. Replied ≠ re-engaged intent.
- Exit Back to Site visit booked on a new calendar event, or lost. Do not loop forever.
How it runs in CoPulse
Growth campaign is the opener. Conversation agent handles replies. Voice is hop two. Autonomous tasks can run a similar list after plan approve but still will not stop on visit booked — prefer campaigns plus workflows if you need stage moves. Three systems, no shared stop-when-booked contract.
Voice
Library Visit Caller role. Agent Studio greeting.
Workflows
On enter: add to win-back audience. On reply: notify RM.
Autonomous agents
Optional list outbound. Operator picks templates. Success = sends/reads.
Operator setup
CRM query or list. Library templates. Phone connected. Wallet for a 318-person demo-sized audience.
Customers filter → stage Dormant → Growth campaign → Library → Agents → Studio Visit Caller → Workflows → wallet preview. Do not add SMS.
Whitefield 3BHK, toured in March, silent since
Ops moves (or a 60-day workflow moves) the Booking to Dormant / re-engage. Growth sends the library-style “prices shifted — 5 new 3BHKs” template. She replies; conversation agent offers Sunday because Saturday is still saturated. Visit Caller confirms. Card returns to Site visit booked — a new visit, not a resurrection of the March Saturday. If autonomous had been used instead, ops would still have to move stages by hand or workflow; the task report would show reads, not visits.
Click-path: pipeline filter Visited idle 60d; move stage; Growth; phone; kanban Site visit booked. Playbooks visited-not-booked vs cold-buyer-winback are jobs with different timing; both may pass through this column. Pricing: campaign plus voice on the Organization wallet.
Win-back vs neighbouring columns
Exit is a new visit or an honest lost — not “template delivered.”
| Stage | Automation | Human | Channel hops | Exit criteria |
|---|---|---|---|---|
| Dormant / re-engage | Win-back campaign, optional autonomous send | Inventory pick, RM | WhatsApp + voice | New visit or lost |
| Visited | 48h EMI loop | Same tour | Too early for 60d | |
| Site visit booked | Reminders | Capacity | WhatsApp + voice | Where rebooks land |
| Construction / handover | Milestones | Possession | Not dormant shoppers |
Jobs that empty this column
Win-back is the primary job. Visited-not-booked may feed it earlier.
Frequently asked questions
60 days, three systems, and not mixing after-sales silence.
Is 60 days required?
It is the library playbook’s example. Your project can use another idle rule in workflows.
Will autonomous stop when they rebook?
No. Count sends/reads. Move the Booking with a workflow or by hand.
Interested list from the last launch?
Interested is not a first-class CRM state yet. Use stage, last visit, and lists you saved.
SMS win-back?
Coming soon. WhatsApp + voice today.
Same as construction silence?
No. Booked-under-construction buyers belong on construction/handover, not this shopper column.
Workflow on enter?
Add to the win-back audience and notify the owner. Agents → Workflows.
Wallet?
Preview before a few hundred templates plus calls. Pricing.
Related
Parent hub, sibling stages, CRM product, and jobs that move this column.
Real estate hub
Buyers & Tenants, Bookings, channels, and playbooks.
Back to hub →Visited
Where they were before they went quiet.
Open →Site visit booked
Where a successful win-back returns.
Open →Pipeline & CRM
Lists, pipeline filters, campaigns, and voice on one contact.
Product CRM →Wallet-only pricing
Win-back WhatsApp and Visit Caller minutes debit the Organization wallet.
See pricing →Treat dormant as a new visit job
Campaign with fresh inventory, voice to rebook, then land them back on Site visit booked — not a single “we miss you” send.
Get started free