How do I stop leads falling through the cracks?

Question

VX-N · Accepted Answer

Make it impossible for a lead to sit unowned and unscheduled. Every inbound gets captured to one place, assigned by rule rather than by whoever notices, and given a next action with a date — so nothing depends on someone remembering. Leads are rarely lost through carelessness. They are lost because ownership was ambiguous, the follow-up lived in a person's memory, and there was no single view showing what had gone quiet. The structural fix is a set of invariants the system enforces rather than policies people are asked to follow: no lead exists without an owner, no open lead exists without a next action and a date, and anything that misses its date surfaces automatically. People forget; invariants do not. Capture is where the leaks start, because inbound arrives through more channels than anyone lists when asked — the website form, but also the phone, the info@ inbox, a rep's personal email, social DMs, referrals mentioned in passing. Each channel that does not land in the system automatically depends on a human transcribing it, and transcription is exactly the step that gets skipped on a busy day. Wiring every source into one intake is unglamorous plumbing, and it is worth more than any follow-up sequence, because a sequence cannot chase a lead the system never saw. Assignment by rule matters more than the rule itself. Round-robin, by territory, by product line — any deterministic rule beats 'whoever notices first', because the shared-inbox model produces the worst of both worlds: everyone assumes someone else has it, and the fastest-grabbing rep cherry-picks. Speed is the other half: the first response should go out in minutes, automatically if needed, because a lead who inquired is comparing you against whoever else they contacted the same hour, and the responder who arrives first frames the conversation. Then instrument the quiet. A lead marked 'contacted' three weeks ago with no scheduled next step is functionally lost — it just has not been reported yet. A view sorted by 'longest since last activity, no future action' turns the invisible leak into a Monday-morning worklist, and it changes rep behaviour on its own, because going-quiet is now visible rather than private. Once the path is wired, the reporting is a byproduct: you can see exactly which stage is leaking instead of guessing, and the argument about whether the problem is lead quality or follow-up discipline gets settled by data instead of volume.