Loading
Because an unassigned lead in a shared list has no age anybody can see. It is not urgent to any individual, so it waits until it is either claimed by chance or too old to matter.
A queue holds leads that have not yet been claimed, each with the time it has been waiting, an escalation threshold and a visible owner once claimed.
Every queued lead shows its age. Passing a threshold escalates it to a named person rather than to the queue at large, and the queue's oldest item is the first thing the view shows.
A queue averaging 9 hours to claim had one lead at 61 hours. It was a £40,000 enquiry from an existing Kanaka Foods contact, sitting behind forty smaller ones because the list was ordered by arrival.
It does not create capacity. A queue that is permanently long is telling you about staffing, and making the ageing visible is the beginning of that conversation rather than the end of it.
Routing rules fill it, lead scoring can order it, deal scoring inherits the response time, and activity reports measure time-to-first-contact from the moment the lead arrived rather than from claim.
Yes, by score, age or value. Age is the default because it is the one that gets ignored.
It is assigned to a named person, not returned to the queue.
Yes. Queues are per motion, not per person.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.