Lead follow up audit for real estate teams

BF

The BrokerFold Team — Product + Engineering

Last reviewed

On this page
Working through records late in an empty office — the audit that finds where leads went quiet

Every team lead suspects it: somewhere in the database, paid-for leads are dying untouched. The suspicion is almost always correct — and almost always in a different place than guessed. A follow-up audit replaces the suspicion with a list. Here are the ten checks, each one a query against your CRM, each finding pointed at a specific fix.

Points 1–3: The intake checks

1. Untouched fresh leads. Count leads from the last 30 days with zero logged contact attempts. This is the rawest leak and the easiest query; anything above a rounding error means your assignment rules or SLA enforcement failed, not your agents’ intentions. 2. Speed-to-lead distribution. Not the average — the distribution. Median response time can look fine while a fat tail of six-hour responses hides inside it. Slice by hour of day and you will usually find the leak concentrated in evenings and weekends. 3. Stale claims. Leads claimed but never contacted — grabbed in the notification rush, then shelved. If your claim window has no expiry, this check is where you discover why it needs one, per your rules of engagement.

Points 4–6: The persistence checks

4. Cadence collapse. For leads with one contact attempt, count how many got a second, a third, a fifth. Most self-reported “we follow up relentlessly” teams find a cliff after attempt two. 5. The dormant middle. Contacts with no activity in 90-plus days who are neither dead nor nurtured — the silent majority of most databases. These should be enrolled in automated nurture; if your platform runs nurture plans, this check becomes “who is enrolled in nothing.” 6. Disposition hygiene. Leads with no status at all — not working, not nurture, not dead. Undispositioned records are invisible to every report, which makes this check the one that keeps the other nine honest.

Points 7–9: The system checks

7. Source leak-down. For each lead source, compute the funnel: received → contacted → appointment. A source converting at half the blend either has a quality problem or gets systematically slower follow-up — agents learn quickly which leads “aren’t worth it,” and the numbers show whether that belief is cause or effect. The plumbing for this view is lead source tracking. 8. Reassignment outcomes. Do rescued leads — reassigned after forfeiture — actually get worked, or do they die a second death in the new owner’s queue? A pool that recycles leads into the same neglect is theatre. 9. Automation coverage. What fraction of new leads receive an instant automated first touch, at any hour? Anything under everything is a configuration gap, and it is the cheapest fix on this list.

Point 10: The mystery shop

Numbers describe; experience convicts. Have someone the team doesn’t know submit a real enquiry on your site on a Tuesday evening: what arrives, how fast, from whom, and how the third day feels. One mystery shop per quarter grounds the audit in the thing the audit is for.

Turning findings into fixes

Rank the ten findings by leads lost, pick the top two, and fix causes rather than exhorting effort: untouched leads point at routing and escalation; cadence collapse points at automation carrying the long tail (the structure in team lead follow up); disposition rot points at required fields. Then put the two worst checks on a standing weekly report so regression is loud. On BrokerFold, the audit queries run against activity that logs itself as agents work, which removes the classic audit objection — “the data’s not in the CRM” — by making the CRM where the work already happens. The per-agent view of these same findings feeds your accountability reviews; the audit is the team-level X-ray, and quarterly is often enough to keep it honest.

Frequently asked questions

How often should a team audit its follow-up?

A full ten-point audit quarterly, with two of the checks — untouched leads and stale claims — running as standing weekly reports. Quarterly is frequent enough to catch drift before it costs a season, rare enough that the audit stays an event people take seriously.

Who should run the audit — the team lead or an outsider?

The team lead runs it, but the mystery-shop check (point ten) needs someone whose voice and email the team won't recognize. Everything else is CRM queries, and keeping those in-house builds the lead's fluency with their own data.

What's a normal amount of lead leakage?

Every team leaks — the question is where and how much. In our experience the first audit is reliably humbling, with the untouched-lead and dormant-database checks producing the worst findings. Treat the first pass as your baseline, fix the top two leaks, and re-measure next quarter rather than chasing all ten at once.

Keep reading

Fold your stack into one.

14 days free. No credit card. Your data stays yours.