Lead Pond Hygiene

Summary

The team-wide lead pond is the open-fishing destination for any lead that ages past its initial assignment window — Spark-page leads after 30 min (showcase-lead-routing), Zillow leads that hit stage-lag / dark-pool thresholds, and any FUB lead an agent doesn't claim. Pond leads are first-to-contact wins. As of 2026-05-22, Fred flagged ~100 high-quality pond leads (less than a week old, good price points) sitting unworked — the "where leads go to die" zone — and pushed a real-time fix to pond membership lists to make sure every agent has access to the correct ponds.

The pond is not overflow — it's an active source

Fred's framing (2026-05-22): "How would you like 100 leads today that are less than a week old that are all good price points? Got your attention?"

The pond is filled by three streams:

"Sleeping on the pond" — treating it as overflow / dead-lead bucket instead of fishing it daily — is the operational failure mode that triggered Fred's 2026-05-22 push.

How the pond works (mechanic)

• First to contact wins. Pond leads have no assigned agent. The first agent who reaches the lead (call, text, email — counts only if it actually went out) owns the lead.
• Pond access is FUB smart-list controlled. Each pond is a smart list with a specific agent membership. If an agent isn't on the list, they don't see the leads.
• Pond access must be re-audited. Membership drifts over time (new agents not added, departed agents not removed, pond definitions changed). Fred's 2026-05-22 audit was triggered by the discovery that the membership lists were stale.

"Where leads go to die" — the failure mode

When nobody fishes the pond:

• Leads age out — past 14 days they fall out of speed-to-lead-protocol Phase 1 Active Pursuit windows where contact rates exceed 70%.
• High-value leads (good price points, fresh) get treated identically to nurture leads, wasting the front-end lead-acquisition spend (Zillow Preferred fees, Spark ad budget, organic acquisition effort).
• The team loses the asymmetric upside of free leads → effectively burning the same dollars twice.

Math at the 2026-05-22 reference point: 100 fresh pond leads × team conversion (4-5%) = 4-5 deals available for zero ad spend.

"Squatter behavior" — the claim-and-ghost failure mode (2026-06-03)

A second, distinct failure mode surfaced in Fred's 2026-06-03 Realtor/OpCity program review. It's not under-fishing the pond — it's claiming leads and then never working them, which is worse because it removes the lead from the open pool while producing zero activity.

The 2026-06-03 backlog, on the Realtor/OpCity program alone:

Squatter behavior defined (Fred): "Either claim and never contact, OR claim and never log a contact — keeping you 'off platform' and making it impossible to track activity." Logging contacts in FUB is the visibility mechanism; an unlogged contact is, for accountability purposes, no contact at all.

The accountability doctrine

Fred's framing: with ~200 contact attempts per agent per 90 days as the team average and hundreds of leads sitting unworked, an unprofitable program is "an agent skill, will, or capacity issue, not a lead issue" — the live-call cohort closes at a high percentage. The forward rule:

Those who claim, contact, and convert get more cracks. Those who don't claim, don't log contacts, or don't engage get fewer.

This is the meritocratic backstop to first-to-contact-wins: access is equitable, but future allocation follows demonstrated work.

Overflow is a recruiting asset, not just a backlog

Because supply structurally exceeds the team's current capacity to work it, Fred reframed the backlog as an attraction/rev-share opportunity: agents have explicit permission to use overflow leads to hire, attract, and partner (including off-team / off-brokerage attraction conversations on Realtor leads). "Not many agents get their phones to ring like this." The geographic-gap play — hand a lead you can't serve to a closer/more-dedicated agent — is the same move that grew Zillow connections 120/mo → 370/mo by proving showing capacity. See realtor-com-lead-routing and nurture-pipeline-management.

Agent operating rule

• Fish the pond daily. Spend 10-15 min checking pond smart-lists alongside your assigned leads.
• Phase 1 Active Pursuit applies. Pond leads get the same 6+ contact attempts in the first 14 days as auto-assigned leads — see speed-to-lead-protocol.
• Call first. Pond leads are first-to-contact wins. Text-only attempts may not register as a claim — make the call to lock the lead.
• Update FUB. Once you've made contact and claimed, update FUB status immediately so other agents don't double-pursue.
• Don't squat. If you claim a lead, log a contact. Claiming without working it removes the lead from the open pool while producing zero tracked activity — the worst outcome for the team. If you can't work it (wrong market, no capacity), don't claim it — or hand it to an agent who can.

Pond membership audit (Fred's 2026-05-22 push)

Fred's directive: "I'm going to make sure everyone is added to the correct ponds RIGHT NOW."

What this means operationally:

• Pond smart-list membership is being verified against the current roster.
• Agents who should have pond access but don't will be added.
• Departed / inactive agents will be removed (preserves the first-to-contact-wins integrity — dead memberships create phantom competition for live leads).

Action for agents:

• After the audit, confirm you can see the pond smart-lists in FUB. If not, surface it immediately — don't assume membership is correct.
• The Loom video (https://www.loom.com/share/3c8b61c80db64cb3885a0d0a39d79d75) is the 5-min team explainer of how the pond works — required viewing.

Related

• showcase-lead-routing — The 15/15/30 routing rule that feeds Spark leads into the pond after T+30 min
• speed-to-lead-protocol — Phase 1 Active Pursuit cadence applies to pond leads, not just assigned leads
• realtor-com-lead-routing — Companion routing-state-matters story (license filters silently de-routing leads) + source of the 2026-06-03 priority-callback / squatter-backlog data
• nurture-pipeline-management — Why most pond/nurture leads are long-horizon "lotto tickets" and how to work them as a 90+ day pipeline rather than discard them
• zillow-flex-program — Source of stage-lag pond spillover via Themis Detector 2
• seneca-adoption — Themis Detector 2 + FUB Zillow hygiene automation that auto-feeds the pond
• roster — Canonical agent list that pond smart-lists should mirror
• zillow-preferred-performance-standards — Rejecting junk/scam leads is database tidiness, not a metrics penalty (Fred, 2026-06-05)