CRM playbook: run a weekly follow-up audit

Follow-up does not fail loudly. No alarm rings when a lead gets one call instead of the six-plus that conversion typically takes — the evidence for that number is in how many times should I follow up — it just quietly becomes someone else’s client. The audit is thirty minutes, weekly, same slot, that makes the silent failures visible — and it works because it repeats, not because it is clever.

Step 1: pull this week’s new leads

Every lead that arrived in the last seven days gets two checks: does it have an owner, and did it get a first touch? For anything that fails either, act now — and note which one failed, because the fix differs. No owner is a routing problem; no touch is a habit problem.

Step 2: clear the untouched list to zero

Filter to leads with an owner but no outreach logged. Each one leaves the list by an honest route: a call made now, a personal message sent now, or a scheduled task with a real date. On a team, this list is the accountability surface — the scorecards’ unactioned column counts exactly these, and the team version of this audit runs it in the open, per agent, with the evidence one click away.

Step 3: check the hot signals that got no answer

Some contacts told you they were heating up without filling a form — repeat visits, a favourited listing, sold-price research. Because the website and CRM share one system, those signals sit on the contact records; scan for strong recent ones with no outreach following them. A behavioural signal answered within a day is a warm conversation; the same signal discovered a month later is a listing that sold with someone else.

Step 4: read the routing misses

The lead timeline records when routing found no matching rule or no available agent. Every such note is a system bug wearing a lead’s name. Collect them, and fix the underlying rule — usually a missing catch-all or an over-narrow price band — so next week’s audit finds none.

Step 5: log the score

Write down three numbers each week: new leads, how many were untouched when you audited, and how many signals went unanswered. Trend beats snapshot — the numbers feed straight into the weekly ops review, where the system-level fixes get made.

What done looks like

A recurring thirty-minute block that actually recurs, an untouched list at zero when it ends, and no lead in the database that has been silent for a week without a decision attached. After a month of this, the audit gets shorter — because the fixes it forced are catching the slips upstream.

The mistake that costs the most

Auditing activity instead of silence. Counting the calls you made feels productive and proves nothing — busy weeks produce great activity numbers and still starve half the queue. The audit’s only job is finding the leads nobody touched, and it must start there every single week.