The right lead, to the right broker, in 60 seconds.
Territory, language, current load, and past conversion all factor in. Round-robin when fair matters. Weighted when revenue matters. Spillover when speed matters.
Shipped in sf_p315. 14-day free trial, no card.
Territory-aware from minute one
Plot brokers on a map. Plot projects on a map. Inbound leads land with the broker whose territory matches the buyer's pincode or the project they enquired about.
- Pincode + locality + project triangulation
- Custom territories per builder
- Cross-territory escalation when no match
- Per-broker active radius override
Language match — buyer + broker
A buyer enquiring in Marathi gets a Marathi-speaking broker. Same for Hindi, Tamil, Telugu, Kannada, Bengali. Reduces drop-off in the first 24 hours.
- Buyer language detected from message + form
- Broker languages on profile
- Fallback chain: native → regional → English
- Translation hand-off if no match
Load-balanced — nobody gets crushed
Each broker has a configurable cap on open leads. Once they're at capacity, the engine routes around them. Manager can pause a broker without losing the queue.
- Per-broker open-lead cap
- Auto-pause on out-of-office
- Manager override with audit
- Caller availability + on-call awareness
Weighted by conversion track record
Brokers who close the lead-source you're assigning get more of those leads. Trailing 90-day window. Auto-rebalances. Newcomers get a shadow allocation so they learn.
- Per-source close-rate weighting
- Trailing 90-day window, decayed
- Shadow allocation for ramp-up brokers
- Manager can pin a high-value lead manually
Round-robin / weighted / spillover
Pick the mode that fits the source. Walk-ins: round-robin. 99acres high-intent: weighted. After-hours: queue-and-fan-out at 9 a.m. The engine just runs.
- Per-source mode selection
- Spillover threshold + target queue
- After-hours queue, morning fan-out
- Holiday-aware queue draining
Pause, reassign, recover — gracefully
Broker called in sick? Pause them — leads route around. Returning tomorrow? Resume — the queue picks up where it left off. No orphan leads.
- One-tap pause from manager dashboard
- Reassign in bulk with notification
- Recovery audit: who got which lead, when, why
- Lost-lead recovery: auto-reroute after N hours of silence
Routing rules are tenant-encrypted; the engine evaluates them on tenant-controlled keys. Lead PII used for routing (pincode, language) is decrypted only inside the per-tick PLAINTEXT_WINDOW and re-encrypted before any audit-log write. SaudaFlow staff cannot read which broker got which lead or why.
See it for yourself.
14 days, full features, no card. Your keys, your data, your CRM.