AI First
Start the day with a list, not a keypad
The AI listens to what you agreed and queues the callback itself. Recruitly also sweeps for people in your CRM who rang, got no answer and were never called back — so the calls worth making find you, rather than the other way round.
One queued by the AI from today's call, one swept up from a missed call nobody returned.
The problem
Nobody plans tomorrow at 6pm on a Friday
You said you'd ring her back Thursday. It's Tuesday. She's accepted somewhere else.
It was never a decision to drop it. You made the commitment on a call, meant to write it down, and the next call came in. The candidate who rang while you were in an interview got a missed-call notification nobody looked at again. The client who asked for a shortlist by Friday is now three days into wondering whether you are on it. None of these are in a task list, because the moment they happened you were talking to someone else.
What slips
- The callback you promised at the end of a good call
- Inbound calls that came in while you were on another
- The candidate who went quiet and nobody chased
Why lists don't fix it
- Creating a task mid-call means stopping the call
- Whatever you type at 6pm is what you can still remember
- A shared to-do list nobody trusts gets ignored by everyone
What it costs
- Placements lost to a competitor who rang back first
- Clients who conclude you are not on top of the role
- Candidates who assume the process ended
The most valuable call in most agencies is the second one. It is also the one nobody is scheduled to make.
How we solve it
1
Your own promises come back to you
When a call is analysed, the AI judges which of its action items actually need a phone call — not by keyword matching, but by reading what was agreed — and queues those against the person you agreed them with.
- "You promised the prep pack and the salary band on today's call"
- The reason is attached in your own words, so it makes sense a day later
- Only commitments that need a call are queued, not every stray remark
- Queued against the person, so opening it opens their record
- Nothing to remember, and nothing to type while you are still talking
2
Missed calls that nobody returned, swept up
Every hour, Recruitly looks for inbound calls from people in your CRM that went unanswered and never got a call back — and puts them in the queue with the reason attached.
- Inbound, from a candidate or contact you already know
- Between one and twenty-four hours old, so it is still worth ringing
- Only if nobody on the team has called them since
- Labelled "Missed their call — not returned yet"
- Dismiss one and it stays dismissed — the sweep never nags twice
3
And the ones you add yourself
The queue is not only automatic. Anyone on the team can add a person to their own call queue straight from the record's menu, so a plan made in a meeting survives contact with a busy afternoon.
- "Add to Call Queue" in the more-actions menu on any record
- Dial straight from the queue row, or open the person first
- Every row carries why it is there and when it arrived
- Yours, not the team's — nobody is filling your list for you
- Clear as you go; what you dismiss does not come back
What lands in your queue
Included with the phone system.
The rest of the phone system
Call Queue is one part of it. They only work like this because they are all the same product as your CRM.
Questions recruiters ask
How does it know a commitment needs a call?
The AI that analyses the call judges each action item on what was actually agreed, rather than scanning for keywords. "I'll send the pack tonight" is an email; "I'll call you Thursday once I've spoken to the client" is a call. Only the second one is queued.
Will it flood my queue?
No. Only items that genuinely need a call are queued, the missed-call sweep is limited per run, and anything you dismiss never comes back. The queue is meant to be short enough to clear.
Is the queue shared with my team?
Your queue is yours. Managers see the team's calling through the call logs and manager view, but nobody is dropping work into your list — the only things in it are your commitments, your missed calls, and what you added yourself.
What counts as a missed call worth returning?
An inbound call from someone who exists in your CRM, that went unanswered, is between one and twenty-four hours old, and that nobody on the team has called back since. Anything older than a day is a different conversation, so it is left alone.
Can I add someone without calling them first?
Yes — "Add to Call Queue" is in the more-actions menu on candidates, contacts and the rest, so you can plan a morning of calls from a shortlist or a search.
Does the queue work with the AI briefing?
Yes, and that is the point. Open a queue row, stage the person, and the briefing arrives knowing why they are queued — including the promise that put them there.
The second call is where the money is. Stop losing it.