Where your enquiries go after someone fills in the form

The dashboard says forty enquiries this month, up from thirty last month. That number gets reported upward as progress. What rarely gets reported is how many of those forty ever received a reply, how many replies went out in under an hour versus three days later, and how many simply sat in an inbox until the lead went cold on their own. The count measures the front door. It says nothing about the hallway behind it.

The five places an enquiry usually goes missing

An enquiry submitted on a website form typically passes through five handoffs: the form itself, an email notification, a person who reads that email, a reply, and a follow-up if the first reply goes unanswered. Each handoff is a place it can stall — a notification going to a shared inbox nobody owns, a reply that answers the question but never asks for the next step, a follow-up that was supposed to happen on day three and quietly never did. None of these failures show up in a lead count. They only show up when someone actually opens the thread and reads it end to end.

A trace is more useful than a dashboard

Pick ten enquiries from the last month — a mix of ones that converted and ones that didn't — and write down, for each, how long the first reply took, who sent it, and what happened after. This takes under an hour and usually surfaces the real bottleneck faster than any report: a particular hour of the day nobody checks the inbox, a particular enquiry type nobody feels confident replying to, a follow-up step that exists on paper but not in practice. The fix is almost always specific and small once you can see it — a notification rule, a named owner, a two-line template — not a new system.