On this page9 sections
Why unassigned leads need their own review
Most pipeline reviews look at deals that already have an owner. That leaves an awkward gap for inbound leads that arrived but never reached a person. The lead may sit in the CRM with a blank owner field, or it may be assigned to a queue nobody checks daily. Either way, no one is accountable for the first reply. A short review before the standup closes that gap without turning the meeting into a data cleanup session. It should take a few minutes and produce a named owner for every lead that arrived since the last review.
Set the assignment clock at form submission
Use the form submission timestamp as the start of the assignment clock, not the time the record was created or last edited. Creation time can differ when a form writes to a staging table, and edit time changes whenever anyone touches the record. The submission timestamp is the moment the customer asked for contact. If the form and the CRM disagree, record both and treat the earlier time as the honest start. This keeps the review focused on customer wait time rather than internal tooling delays.
Separate unassigned from unworked
An unassigned lead has no owner. An unworked lead has an owner but no recorded attempt. The two problems need different fixes, so the review should count them separately. A blank owner points to a routing rule, a queue, or a permissions problem. An owner with no activity points to capacity or follow-through. Mixing the two into one "stale leads" number hides which part of the process failed. Report the counts side by side and investigate the larger bucket first.
Check the routing rule before the person
When a lead is unassigned, inspect the rule that should have assigned it before messaging an individual. Routing can fail because a territory value is missing, a round-robin list is empty, or a new form field no longer matches the rule condition. These are system problems, and asking a salesperson to watch the queue more closely will not fix them. Reproduce the routing decision with the record's actual field values. If the rule behaves correctly, move on to ownership and capacity; if it does not, fix the rule and recheck the affected records.
Record the first owner and the first touch
For each lead in the review, capture who received it and when the first attempt happened. The owner should be a person, not a team inbox that several people monitor informally. The first touch should be a real contact attempt, not an internal note or a task created for later. Recording both fields makes the handoff auditable and gives the next review a clean baseline. It also prevents a lead from looking handled because someone opened the record and changed a status.
Escalate by age, not by volume
Sort the exception list by age, with the oldest unassigned lead first. A long list sorted by arrival time is easy to scan and hard to ignore. Set one escalation threshold that reflects the team's normal response window, then keep it stable long enough to judge whether it works. Escalating every lead at once creates noise and encourages people to clear the list without fixing the cause. Age-based escalation keeps attention on the small number of leads where the customer has already waited too long.
Keep a short daily exception list
The review should end with a list short enough to finish before the standup. Include the lead, the arrival time, the failed condition, the named owner, and the next action. Anything that cannot be resolved in the review becomes a dated task with an owner. Do not carry the same unresolved items for days without changing the response; if an item keeps reappearing, the routing or capacity problem is bigger than the daily list. A short list that closes is more useful than a comprehensive report nobody acts on.
Review the pattern weekly
Once a week, step back from the individual leads and look at the pattern. Count how many unassigned leads came from each form, campaign, or region, and compare that with the routing rules that cover those sources. Look for rules that fire late, queues with no backup, and forms that collect fields the routing logic does not expect. Use the daily list as evidence, not as the whole analysis. The weekly view is where a recurring exception becomes a repair that removes the exception from tomorrow's list.
Make the handoff visible to the customer
Finally, remember that the internal clock is only a proxy for the customer's experience. A lead can be assigned quickly and still wait hours for a reply, and the review should make that visible rather than implying the job is done. If the team promises a response window, measure the time from submission to first attempt against that promise. Publish the result where the people doing the work can see it. The point of the review is not a cleaner board; it is a shorter wait for the person who filled out the form.
