The daily decision that costs you conversions
Every morning, a counsellor with 140 open leads and a task list makes the same decision about fifty times: whom do I call next?
The honest answer is usually "whoever looks easiest", because the list shows a name, a date and a note, and the brain picks the friendly-sounding one. The prospect who was promised a call on Tuesday and is now two days overdue sits in the overdue section, visually the same as everything else, and gets called on Friday, if at all.
This is not a discipline problem. It is what a task list is designed to do: hold reminders. It was never designed to decide.
A call queue is a different object. It is built by the system, it has a fixed order, and the agent works it from the top. Nobody sorts it. The only way to change what is on top is to make the call and log what happened.
What a queue orders, and why the order is fixed
Crosvia's queue has four bands, always in this order.
1. Calls awaiting disposition
Calls already made, through the dialler or logged by hand, where the outcome has not been recorded. These come first because an undispositioned call is an unfinished unit of work: no follow-up has been created, the score has not moved, the manager's dashboard is wrong. Clearing them takes ten seconds each and fixes the rest of the queue.
2. Overdue follow-ups
Calls the agent promised a prospect and did not make on time. They come second because a broken promise to a prospect is the single most expensive thing in a lead pipeline: the person remembers. Putting them above today's work means the morning starts by repairing yesterday.
3. Follow-ups due today
Promised calls that are still on time, ordered by due time and then by score.
4. Hot leads nobody has called
The highest-scoring leads in the workspace with no call logged at all. This band is what makes the queue more than a to-do list. An agent who clears the first three bands does not stop dialling; the system hands them the most promising untouched lead, with the reasons for its score beside the name.
The order is fixed because a queue the agent can re-sort becomes a task list again within a week. The fixed order is the feature.
A worked example: one counsellor, one morning
Anju arrives at 9:30 am. Her queue shows 23 items.
- 4 calls awaiting disposition from yesterday evening. She logs them: two interested with follow-ups set for Thursday, one no-answer with a retry at 2 pm today, one not interested with a reason. Three minutes.
- 3 overdue follow-ups, two days and one day late. She calls all three before anything else. One books a counselling session, one asks to be called next week, one does not answer and gets a WhatsApp message from the thread and a retry tomorrow.
- 9 follow-ups due today, ordered by the time she promised. She works them between 10 and 12:30, logging each disposition as she goes.
- 7 hot uncalled leads. The top one is a referral from last week that nobody has called, score 76, reason "strong source, appointment booked, no activity since." She calls it first. The second is a Meta lead from last night, score 63, reason "replied once, never called."
By 1 pm the queue shows 2 items, both scheduled for the afternoon. At 2 pm three new Meta leads arrive, get scored, and appear in band four. Nothing was assigned by a manager all morning, and nothing promised to a prospect was missed.
Compare the same morning with a task list: 23 reminders, sorted by date created. The referral from last week would have been item 19.
What changes for the manager
- Overdue is visible per agent, every morning, before it becomes a lost month.
- Awaiting-disposition counts show who is dialling but not logging, which is where pipeline data quietly rots.
- The hot-uncalled band shows whether the team is keeping up with lead flow. If it grows every day, you need people or a tighter ad budget; the number tells you which.
- Coaching is concrete: "you called 14 band-four leads before the 3 in band two" is a sentence, not an impression.
When a task list is still the right tool
Tasks did not go away. A queue answers one question, who do I ring next, and nothing else.
Preparing a document checklist, chasing an institution for an offer letter, or sending a revised quotation are tasks, with due dates and owners, and they live in the task list. The mistake is using the task list to hold calls, because calls have a natural ordering that tasks do not.
How this fits with scoring and automation
The fourth band runs on the lead score, so the reasons behind the score decide who gets called first among the untouched.
Automations feed the queue too. A rule that creates a follow-up when a lead replies puts that lead in band three automatically; a rule that escalates an SLA breach moves it into band two.
The three features were built to work as one loop: capture creates the lead, scoring ranks it, automation commits a time, and the queue holds the agent to it.
What to do next
- See the queue and the manager view: Call queue.
- How the score that orders band four is built: How lead scoring reasons work.
- Create follow-ups and escalations automatically: Automations.
- Related terms: call queue, call disposition, follow-up, SLA.
- Plans and the 14-day trial: Pricing.