Live Routing Decision & Intent Analytics Timestamp: Synced
Computed Lead Intent Score
Morgan Sterling • 98101 • $1,250,000
84 / 100
HOT INTENT
Scoring Weights: Tours (40%) + Saves (25%) + Repeat Views (20%) + Search Frequency (15%) - Dislike Penalty Target SLA: Contact within 5 minutes
AUTOMATED STAGE TRANSITION (CANONICAL CRM PIPELINE)
1. New Ingest
Auto-routed
2. Attempted
Twilio SMS 3m
3. Active / Qualified
Pre-approval OK
4. Showing
Tour calendar
5. Under Contract
Escrow opened
6. Closed
Commission split
AGENT ROSTER & CAPACITY SPREAD (SEATTLE / WA TIER)
Routing rule: Zip Match → Price Tier → Workload Balance
Algorithmic Decision Trace (Rule Evaluation Engine) 2.4ms evaluated

1. Lead Ingestion & Fail-Safe Architecture

Inbound leads from Zillow Premier Agent Webhooks, StreetEasy, and organic IDX portals pass through an API Gateway with rate-limiting and duplicate message deduplication using idempotency_key hashing.

A priority queue evaluates agent coverage arrays in PostgreSQL. If the primary assigned agent fails to initiate an SMS or phone call within 300 seconds (5 minutes), an escalation trigger reassigns the lead to the next eligible team member to preserve conversion rates.

2. PostGIS Spatial & Intent Scoring Engine

Property listings synced from MLS feeds using the RESO Web API are stored with PostGIS spatial geometries. Buyer polygon searches run index-accelerated point-in-polygon queries (ST_Contains) to alert clients within seconds of listing publication.

The Lead Intent Score synthesizes client behavioral telemetry. High-intent triggers (repeat views of the same property, price-drop interactions, tour bookings) boost score velocity and escalate notifications to senior brokers.

3. Transaction Pipeline & Compliance

Contracts execute through DocuSign REST API webhooks. Contingency clocks (Inspection, Appraisal, Financing) calculate critical milestone dates automatically based on mutual acceptance timestamps.

The brokerage commission split ledger cleanly divides Gross Commission Income (GCI) across brokerage cap thresholds, referral fees (e.g., Zillow Flex 35%), and franchise royalties before issuing wiring disbursements.

Frequently Asked Architectural Questions

How does the routing algorithm resolve ties between equally matched agents?

When multiple agents service the same zip code and price tier, the engine applies a tie-breaker: (1) Fewest active leads currently in New or Attempted Contact stages, (2) Longest elapsed time since last lead assignment (round-robin), and (3) Historic 15-minute lead response rate score.

Why choose PostgreSQL over a NoSQL document database for this CRM?

Real estate transactions require strict ACID guarantees. Escrow transactions, earnest money balances, and multi-agent commission splits cannot tolerate eventual consistency. Furthermore, PostgreSQL provides native PostGIS extensions for spatial property polygon searches and JSONB for flexible MLS custom fields.

How does the RESO Web API integration handle MLS photo replication and CDN caching?

Instead of downloading gigabytes of MLS photos synchronously, our worker daemon stores RESO Media CDN URLs with signed headers and pre-fetches low-resolution thumbnails to a Cloudflare Image Cache, reducing worker disk I/O by 85%.

Enjoy this tool? Build your own with Super