Ask a sales leader how fast inbound gets contacted and you will hear a number. Measure it and you will get a different one.
One lead contacted in four minutes and one in four days averages to a reassuring two days. The median tells you what normally happens, and the ninetieth percentile tells you how bad the tail is. Both matter more than the mean.
A routing rule that depends on an overnight job. Assignment to a round robin without an out of office check. Notification going to an inbox rather than the place the rep actually works. A lead that lands in a queue nobody owns over a weekend.
A buyer filling in a form is usually filling in several. The first credible response frames the evaluation. A day of delay does not cost you a day, it costs you the position of incumbent in a comparison you never saw.
Routing that fires on record creation rather than on a schedule. Assignment that checks availability. Notification in the tool the rep already has open. And a visible queue with a named owner, so nothing sits without somebody accountable for it.
| Cause | What happens | Fix |
|---|---|---|
| Scheduled routing jobs | A nightly job sets a floor no coaching can beat | Route on record creation |
| No availability check | Leads go to people who are out | Check calendars or status first |
| Notification goes nowhere useful | An inbox checked twice a day | Push to the tool the rep has open |
| Weekend and holiday gaps | Usually the largest single bucket | A rota, not software |
| Two ownership models | Scheduler and CRM disagree on the owner | One ruleset for both |
| No fallback owner | A lead matching no rule belongs to nobody | Always name one |
In one engagement, moving from an overnight job to event driven assignment on record creation took first contact from five days to twelve hours without anyone working harder.
Want your own number? The free speed to lead checker reads a lead export in your browser and gives you the median, the ninetieth percentile and the weekend gap.
Faster is better and the useful target is hours rather than days. The number that matters is your own median over time, and whether the tail is getting shorter.
Compare record creation timestamp to the first logged activity on that record, then report the median and the ninetieth percentile rather than the average.
Yes, though for a different reason. In a long cycle the first credible conversation sets the frame for the evaluation, even if the decision is months away.
Scheduled rather than event driven routing, assignment without availability checks, and notifications landing somewhere the rep does not work.
Usually mechanical: routing on a scheduled job, round robins that ignore availability, and notifications arriving somewhere nobody checks often.
Not always. Native assignment rules handle most straightforward cases. Tools earn their place on complex matching or instant scheduling.
Usually mechanical: routing that runs on a scheduled job, round robins that ignore availability, and notifications arriving somewhere nobody checks often.
Compare record creation to the first logged activity, and report the median and ninetieth percentile. Averages hide the tail, which is where the problem lives.
Not always. Native assignment rules handle most straightforward cases. Tools earn their place on complex matching or instant scheduling.
All of it free.
Leave an email and I will reply myself, usually the same day. No sequence, and no calendar link unless you ask for one.
Would rather just book time? Here is the calendar.
We use browser storage to run the site and to understand how it is used. You can accept all or necessary only. See our privacy notice.