Lead Leakage Audit: Find Where Your Enquiries Disappear

Leakage is not one problem. It is seven small ones, each with its own measurement and its own fix. Work through them in this order, because the earlier leaks make the later measurements meaningless.

Step one: pick a week and stick to it

Choose a normal week from the recent past, not the current one, and use the same seven days for every measurement. Mixing periods is the fastest way to produce numbers that argue with each other.

Step two: count arrivals at source

Go to each channel individually. Website form submission emails. The business messaging inbox. The call log on the published number, including missed calls. The walk-in register. Any marketplace or listing platform. Write the count for each. Do not use the CRM for this step, because the whole purpose is to find out what the CRM never learned about.

Step three: reconcile against the CRM

Count records created in the CRM during the same week, split by source. Subtract. As an illustrative example, if your call log shows sixty two inbound calls to the published number and your CRM shows thirty one call-sourced records, roughly half your calls are not becoming records. That gap is the number to fix first, and it is usually caused by missed calls that nobody calls back rather than by anyone being careless.

Step four: measure speed on what you did capture

Take the captured records and calculate the median time to first human reply, split by channel and by working hours against out of hours. Then look at the worst decile, because that tail is where the angriest customers and the loudest reviews come from.

Step five: sample the follow-up

Pull thirty records at random from that week and read them. Count how many have exactly one contact attempt, how many have a dated next action today, and how many have notes a colleague could act on. This step takes twenty minutes and tells you more about your sales process than any dashboard.

The audit produces a shape, and the shape prescribes the fix. A big capture gap with good response speed means your team is competent and your plumbing is broken; fix the plumbing and results improve immediately with no behaviour change. Good capture with poor speed means the plumbing works and the queue has no owner. Good capture and speed with a large single-attempt count means you have a cadence problem, which is the most rewarding one to fix because the enquiries are already inside the building.

The trap of fixing the interesting leak

Teams gravitate to the leak that is most fun to work on, which is almost always nurture: sequences, content, scoring. Resist it until capture and speed are clean. Every hour spent on nurture while half your calls are going unanswered has a negative return, because it makes the funnel look busier without adding a single conversation.

Highest return for lowest effort: an automatic acknowledgement on every channel, a missed call that creates a task, and a mandatory next-action date. Those three can usually be turned on in an afternoon and they close the two largest leaks. Medium effort: consolidating channels onto a single business number, which requires updating listings and signage but ends the personal phone problem permanently. Higher effort: rewriting the follow-up cadence and training the team on it, which is worth doing once the earlier fixes have stopped the bleeding.

Put the audit in the calendar for ninety days later and run it identically. Compare the seven numbers. If the capture gap has reopened, the fix depended on a person rather than on the system, and it needs to be rebuilt as something automatic. A leakage audit is not a project you finish; it is a small recurring check that keeps an expensive problem visible.

Related reading: lead management software, WhatsApp CRM, built-in dialer, sales automation, CRM for small business, and features.