Find out who is still looking, before a recruiter calls.
A candidate database goes stale faster than any other list a business keeps. Most of the names in it took a job three months ago and nobody has asked.
Recruitment · 9 steps
Recruiters spend a large share of their week re-qualifying a list rather than placing from it. The question is always the same and the answer is usually no.
Meanwhile the candidates who are actively looking are the ones who move fastest, and the delay in reaching them is measured in placements lost.
Step by step, with the node each one uses.
- 01
Match to the candidate record
If Existing LeadSo the call can reference the role they registered for rather than starting from nothing.
- 02
Say why you are calling
Playback AudioNamed, specific and short. A vague recruitment call gets hung up on inside four seconds.
- 03
Ask the only question that matters
Route to IVRStill looking, not right now, or take me off the list. All three are useful answers and the third one is the one most systems never capture properly.
- 04
Take an availability date
Capture DigitsFour digits, day and month, on the still-looking branch. A recruiter opening that record sees a date rather than a note saying to chase.
- 05
Tag by the answer given
Manage TagsActively looking, passive, or opted out. The tag is what every later search runs against.
- 06
Move them between lists
Manage ListOff the calling list if they asked, onto the active list if they are looking. The list is corrected by the call that discovered it.
- 07
Send the right follow-up
Add to Email SequencesRoles for the active ones, a check-in months later for the passive ones. Chosen by branch, not by memory.
- 08
Put the hot ones straight through
Route to UserAnyone actively looking reaches their own recruiter while they are still on the phone, which is the only moment that reliably converts.
- 09
Honour a removal request immediately
Add to Caller FilterSomebody who asks to come off the list comes off it during the call, not when a note gets actioned.
The variables.
Captured mid-call and readable by every later node, including inside a spoken prompt and inside a webhook body.
${AVAILABLE_FROM}Four digits the candidate keys in${CANDIDATE_STATUS}Which branch they took, used for tagging and sequencingThe recruiter's day starts with a list of people who said yes this week, rather than a list of people who said yes in March.
The opt-out branch is the part worth keeping honest. Handling it in the flow rather than in a note is both the decent thing and the defensible one.
- Keep the opening under ten seconds and name the role. Recruitment calls have the least patient audience of anything in this list.
- Do not put the hot branch through to a queue. The value is in reaching a specific recruiter while the candidate is still on the line, so route to the owner.
Book a demo
We will build this one on your numbers.
Half an hour. Bring the awkward case rather than the easy one, and we will tell you if it does not fit.
14-day trial · no card · migration included