Scanning dormant database on new listing
| Activity | Without Reactivation System | With Phase 9 Active |
|---|---|---|
| New listing added | No connection to dormant database. Agents may manually check. Most past leads receive nothing. | ✓2,000 dormant leads scanned in 1.2 seconds. Matching buyers surfaced immediately. |
| Reactivation message content | Generic blast. "New properties available." 1-2% open rate. Unsubscribes compounding monthly. | ✓References buyer's original requirement specifically. "The 3-BHK in Kondapur at Rs. 1.1 Cr you asked about." |
| Agent oversight on outreach | Blasts go to entire list. No individual approval. Agent has no visibility on who received what. | ✓Every match reviewed individually. Agent approves, skips, or edits before anything sends. |
| Buyer response handling | Reply goes to inbox. Sometimes missed. Rarely logged back to the dormant lead record. | ✓Every response captured in CRM. Lead reactivated. Follow-up task created. Dormancy reason updated. |
| Monthly effort required | Manual review sessions requiring dedicated agent time that competes with live lead work. | ✓Zero scheduled effort. System triggers automatically on every listing. Agent reviews matches in 2 minutes. |
A drip sequence sends messages on a calendar schedule – “Day 30: Check in. Day 60: New properties.” It fires whether a relevant property exists or not. Phase 9 only fires when a matching listing actually enters your database. The buyer receives a message that says “the specific type of property you asked about 7 months ago just listed” – not a scheduled nudge. Calendar-based outreach gets ignored. Event-triggered outreach converts because it is already relevant when it arrives.
Yes – explicitly by design. No automated send happens without the assigned agent reviewing and approving the match card. The agent can approve, skip, or edit the message before it sends. If an agent skips a lead, that skip is recorded so the same lead is not resurfaced for that specific property. The next matching listing will generate a new match card.
The system stores the original requirement from Phase 3 CRM setup. If a buyer responds to any outreach and indicates their requirement has changed – “I need 4 BHK now” or “budget changed to Rs. 1.4 Cr” – the response is captured and the CRM record is updated. The next matching run uses the updated requirement. If the buyer never responds and the requirement is still the original brief, the match is still surfaced – but the agent may decide to skip and call first to verify.
Yes. Phase 1 (inventory database) is required because Phase 9 matches dormant leads against live inventory. Without a structured inventory database, there is nothing to match against. Phase 3 (CRM setup) is required because Phase 9 reads original requirements from the CRM. If the CRM does not store requirements in structured fields, the matching cannot run accurately. We scope Phase 9 after confirming Phase 1 and 3 are live and stable.
The matching engine uses Llama 3, an open-source model running on your own server. There is no per-scan fee, no API cost, and no third-party platform involved. The compute cost of a single 2,000-lead scan is negligible – significantly less than Rs. 1. The hosting cost is included in the monthly maintenance retainer that covers all active phases.