Phase 1 — Measure the current state (2 to 3 days)
Pull the last 100 to 300 leads
Export creation time, source, owner, first activity time, first two-way contact and final disposition. If any of these are missing, that gap is your first finding.
Calculate four numbers
Percentage with zero contact attempts; median time to first attempt; median time to two-way contact; percentage assigned automatically. These four define the problem and later prove the change.
Split by source and hour of day
Leakage is rarely uniform. Out-of-hours and weekend submissions usually carry most of the damage, and a specific source often routes into a black hole nobody knew about.
Size the gap
Use the lead response leakage calculator with your own numbers. Take the result to sales leadership before designing anything — the design conversation is easier once the cost is on the table.
Phase 2 — Agree the rules (1 workshop)
One session, sales and marketing together, four decisions. Write them down in the room; unwritten decisions revert within a fortnight.
| Decision | Options | Default I recommend |
|---|---|---|
| Assignment basis | Round-robin, territory, product line, account owner, source | Account owner if known, else territory, else round-robin among available reps |
| Response standard | Minutes or hours from creation | 15 minutes in-hours; first hour of next window otherwise |
| Out-of-hours behaviour | Queue, on-call rota, automated acknowledgement | Automated acknowledgement stating the window, plus a queue with an owner assigned already |
| Escalation | None, owner reminder, manager alert | Owner reminder at standard, manager alert at standard plus 100 percent |
Record the outcome in the lead routing matrix template so the rules exist outside the automation tool.
Phase 3 — Build (3 to 5 days)
Assignment at creation
Rules evaluated in order, with a named fallback owner as the last rule. Never allow an unowned state — an unowned record has no clock and no accountability.
Task creation with a due time
The follow-up task is created by the system with the due time derived from the standard. The rep's task list becomes the queue; nobody works from a filtered view they built themselves.
Instant acknowledgement to the lead
Honest and specific: confirm receipt, state the window, give a direct channel for anything urgent. Do not promise a response time the rota cannot honour.
Availability handling
Round-robin must skip reps who are away. This single detail causes more silent leakage than any other implementation gap.
Escalation chain
Reminder to owner at the standard; alert to manager at the breach; daily digest of anything still untouched.
Duplicate protection
Match on email and phone at creation. Route the duplicate to the existing owner rather than creating a second record and a second conversation.
Phase 4 — Test properly (half a day)
- Submit a test lead in-hours and confirm assignment, task and acknowledgement within the standard.
- Submit out-of-hours and confirm the queue behaviour and the honest acknowledgement.
- Submit a duplicate and confirm it routes to the existing owner.
- Mark a rep unavailable and confirm the rotation skips them.
- Let one test lead breach deliberately and confirm the escalation actually reaches the manager.
- Break the integration on purpose and confirm somebody is alerted rather than silence.
Phase 5 — Run it (ongoing)
- Weekly: breach list by owner, reviewed in the existing sales meeting. Five minutes, no new meeting.
- Monthly: the same four numbers from Phase 1, trended. This is the proof the change held.
- Quarterly: revisit the rules. Territories, staffing and sources move; routing rules that are never revisited become a hidden constraint.
Failure modes to watch
| Symptom | Likely cause | Fix |
|---|---|---|
| Response times good, conversion flat | Contact happens but the attempt sequence is one call | Define a multi-channel attempt sequence with a stop rule |
| Breaches concentrated on one rep | Capacity, not discipline | Rebalance the rotation before coaching |
| Leads assigned but never worked | Task not created, or reps work from a private list | Fix task creation; make the CRM view genuinely better than the private list |
| Volume dropped after launch | Duplicate protection merging distinct people | Tighten the match rule to email plus phone rather than name |
Related work
The problem statement is leads go cold after form submission. If record quality is also poor, run the CRM cleanup playbook first.
Muhammad Sameed Abid
Muhammad Sameed Abid is a business operations, automation and growth systems professional with 9+ years across operations management, workflow and CRM automation, marketing operations and customer success. He is currently Head of Customer Success at GHA Marketing and writes here about the operating layer underneath growth.