Tracker

The problem

Most mandate opportunities leak across society WhatsApp groups, owner-direct outreach, and disjointed CRM exports. By the time a sales head sees them, the seller has signed with a competitor or the buyer has already moved on.

What Tracker owns

• 01Continuously surfaces sell-side mandate candidates from web, CRM, RWA partnerships, and consent-gated society groups.
• 02Picks up inbound buy-side leads from web forms, listing-syndication replies, and partner-portal submissions.
• 03Deduplicates against existing mandates and customer journeys so the same lead doesn't get worked twice.
• 04Scores every candidate against the city + project ICP and routes the high-score ones to a human RM.

Sample input / output

{ city: 'mumbai', source: 'rwa_whatsapp', payload: '...message text...' }

{ candidate_score: 0.84, mandate_draft: { ... }, recommended_rm: 'rm_uid', rationale: 'High-floor 3BHK in anchor society, owner motivated' }

Status & roadmap

Registry seeded as `scout` in the agents table; runtime stub throws not_implemented. Ready to be wired once Sprint 1 (TruOS event bus) lands.

To build

• ·Source connectors per channel (society groups, partner portals, broker feeds)
• ·Dedup logic against `mandates` + `customer_journeys`
• ·ICP-based scoring with explainable rationale
• ·Hand-off action that creates a Coach card for the assigned RM