Leads go cold after form submission

What this looks like from the inside

• Marketing reports lead volume up; sales says the leads are bad.
• Reps say they called; the CRM shows one attempt, three days later.
• Leads submitted on Friday evening are first touched on Monday afternoon.
• The team's best follow-up happens for the leads they personally like the look of.
• Nobody can state the median time from submission to first genuine contact.

Find where the time is actually going

Before changing anything, measure four intervals on the last hundred leads. Most teams assume the loss is in rep effort; it is usually in the first two intervals, which are entirely structural.

Why it happens

1. No automatic owner. A record with no owner belongs to a queue, and queues do not feel urgency. Assignment must happen at creation, with a defined fallback.
2. No written standard. 'Fast' is not a standard. A standard is a number, applied to a defined event, with a consequence when it is missed.
3. No task created. If the process depends on someone remembering, it degrades under load — which is exactly when volume is highest.
4. No out-of-hours behaviour. Most inbound arrives outside the window the process assumes. Decide explicitly what happens then, including an automated acknowledgement that sets expectations honestly.
5. Breach is invisible. If a missed response only shows up in a monthly report, it is not a control, it is an autopsy.

The fix, in order

1. Assign at creation

   Every record gets an owner within seconds using explicit rules — territory, source, product, or round-robin with availability. Include a named fallback owner for every rule so nothing lands in an unowned state.

2. Set one response standard and publish it

   For example: first genuine contact attempt within fifteen minutes during business hours, and within the first hour of the next window otherwise. One number, agreed by sales leadership, visible to both teams.

3. Create the task automatically

   The CRM creates the follow-up task with the due time when the record is created. The rep should never have to construct their own queue from a list view.

4. Acknowledge instantly, honestly

   An immediate confirmation that states when a human will respond. It is a courtesy, but it also buys the window the team needs — as long as the promise matches the standard.

5. Escalate the breach, not the lead

   At the standard plus a margin, notify the owner's manager. Escalating to the manager rather than reassigning quietly is what makes the standard real.

6. Define the attempt sequence

   Three to five attempts across at least two channels, spaced over days, with a defined stop. Most leads are lost after a single attempt, and most teams have no written sequence at all.

7. Report breaches weekly

   One list: leads that breached the standard, by owner, this week. Reviewed in the existing sales meeting. Nothing else needs to be added to the agenda.

What to expect

The honest framing: this work recovers leads you already paid for. The size of the recovery depends entirely on your current leakage, which is why the lead response leakage calculator uses only your own numbers — never an industry multiplier — to size the gap before you commit effort.

• Percentage of leads with zero contact attempts trends to near zero.
• Median time to first genuine contact is measured in minutes and visible to both teams.
• Every breach has an owner and a manager who saw it that week.
• The attempt sequence is written down, and adherence is visible in the CRM.

Mistakes I keep meeting

• Buying a speed-to-lead tool before defining ownership. The tool dials faster into the same ambiguity.
• Setting a standard nobody staffed for. A fifteen-minute promise with one rep covering three time zones is theatre.
• Measuring first activity instead of first contact. Logging a call that nobody answered is not contact, and counting it hides the problem.
• Punishing reps for a structural failure. If assignment is manual and tasks are not created, the process failed before the rep did.

Related work

The full implementation sequence is in the lead routing playbook. If the underlying record quality is also suspect, fix the CRM nobody trusts first — routing rules on top of duplicate records create two owners and one embarrassed customer.