A candidate applies to your role at 7pm on a Tuesday. They applied to four others in the same sitting, because that is what the apply button on a job board is for.
Whoever calls them first gets the conversation. Everyone else gets a voicemail, a polite reply three days later, or nothing. The role has not been lost on fee, service, or the quality of your shortlist. It has been lost on the fact that your consultants were asleep.
This is the least glamorous problem in recruitment and one of the most expensive, and it is worth being precise about why it resists the usual fixes.
Why the response gap is structural, not a discipline problem
Every agency owner has run the "we must call applications faster" meeting. It works for about three weeks.
It fails afterwards because the maths does not care about resolve. A consultant billing properly is on the phone with clients during the day, running interviews, chasing references, and managing the candidates already in process. Applications arrive on their own schedule, heavily weighted to evenings and weekends. The gap is not the consultant being slow. It is the overlap between when candidates apply and when anyone is available to answer.
Widely cited lead response research consistently finds that the odds of qualifying a lead fall away sharply within the first hour, and that most of the advantage sits in the first few minutes. Recruitment has the same curve with an added twist: the candidate is not only comparing you against other agencies, they are also deciding whether they are still interested in moving at all. Enthusiasm decays faster than intent.
7:04 PM
Application lands
Candidate is engaged, at their laptop, and has applied to several roles in one sitting.
7:06 PM
A rival calls
First real conversation. Salary, notice period, and location get qualified before anyone else speaks.
9:30 AM
You call
Fourteen hours later. The candidate has an interview booked elsewhere and is now comparing, not exploring.
What the out of hours hour is worth
Take a ten consultant agency working a mix of permanent and contract roles. Agencies in that shape typically see a meaningful share of applications arrive outside working hours, and a further share arrive during the day while every consultant is already on a call.
The candidates in that overflow are not worse candidates. They are the same population, sorted by the accident of when they happened to hit apply. Which means the placements lost there are not marginal ones. They are a random sample of your pipeline, quietly removed.
Once you see it that way, the fix stops looking like a productivity project and starts looking like a coverage one. You do not need consultants to work harder or later. You need something to answer at 7:06pm that can qualify well enough to hold the candidate's attention and book the consultant's diary.
What answering requires
The instinct is to reach for an autoresponder, and it does not work, for a reason worth naming. An email saying "thanks for applying, we will be in touch" does not compete with a rival human asking about notice period. It is an acknowledgement, not a conversation.
What competes is a conversation. Which in practice means something that can call within a couple of minutes of the application, hold a natural exchange in the candidate's language, ask the four or five things that determine whether the role is even viable, and put time in a consultant's calendar while the candidate is still interested.
That list is the useful specification, and it is worth checking any tool against it rather than against a demo:
- Calls in minutes, day or night, including weekends
- Qualifies against the role, not a generic script: notice, salary expectation, location and right to work
- Handles the candidate ringing back, not only outbound
- Writes what it learned into the CRM against the right record
- Books into the consultant's real availability
The first two are what most platforms demonstrate. The last three are where deployments quietly fail, because they depend on your systems rather than on the voice.
An acknowledgement is not a conversation, and candidates can tell the difference in about four seconds.
the Kaigen team
The UK specifics that change the design
Two things make this different from running the same play in the United States.
First, the rules. Calling candidates in the UK sits under PECR and UK GDPR, which means a lawful basis for the call, the Telephone Preference Service where relevant, and a clear route to opt out. A candidate who applied to your advertised role is a very different consent position from a name bought on a list, and the two should not share a dialling strategy. Our compliance guide covers the UK position alongside the other markets.
Second, the market shape. UK recruitment runs heavily on contract and temp desks where speed is not a nice to have but the entire product. A temp booking that needs filling by Monday morning is decided on Friday evening by whoever can reach available workers fastest. That is a broadcast and response problem more than a qualification one, and it rewards the ability to call fifty people in ten minutes and hand the consultant the three who said yes.
Where the consultant fits afterwards
The objection worth taking seriously is that recruitment is a relationship business and candidates do not want to talk to a machine.
Both halves of that are true, and neither leads where it seems to. The relationship is built in the consultant conversation, the interview prep, the salary negotiation, the call where somebody talks a nervous candidate into accepting. None of that is what happens at 7:06pm on a Tuesday. What happens then is qualification, and candidates in our experience mind a fast competent qualification call far less than they mind silence.
The honest framing is that this handles the part of the job consultants like least and defer most, and hands them a diary of qualified conversations instead of a list of applications to work through. The relationship gets more consultant time, not less.
Q1
What share of your applications arrive after 6pm?
Most agencies have never measured it. The number is usually higher than the guess, and it is the size of the problem.
Q2
How long until a new applicant hears a voice?
Measure from application timestamp to first connected call, not to first attempt. Attempts are not conversations.
Q3
Who owns the follow up when nobody picks up?
If the answer is the consultant's memory, the second and third attempts are not happening.
We wrote a longer teardown of this pattern using a public staffing business as the worked example, in the response gap deep dive, and the recruitment page shows how the desk is put together. If you are weighing whether to build this yourself or have it run for you, how we work lays out the split.
KEY TAKEAWAYS
- The response gap is a coverage problem, not a discipline problem. Applications arrive when consultants are unavailable, by definition.
- Candidates lost to slow response are a random sample of your pipeline, not the weak end of it.
- An autoresponder does not compete with a rival human asking about notice period. Only a conversation does.
- Judge any tool on CRM write back, inbound handling, and diary booking. The voice is the part that already works everywhere.
- UK calling sits under PECR and UK GDPR, and an applicant to your advertised role is a different consent position from a purchased list.
MAP YOUR DESK
Want to see where your applications are leaking?
Twenty minutes on your application flow, out of hours volume, and what a first response inside two minutes would need to touch.
Book a 20 minute audit →FAQ
Will candidates be put off by an AI call?
Far less than by silence. The call that matters here is a fast qualification conversation at a moment when the alternative is nobody ringing at all until the next working day. The relationship building parts of recruitment, interview preparation, negotiation, and closing, stay with the consultant, who now receives qualified candidates rather than a queue of applications.
How fast is fast enough for a first response?
Minutes rather than hours. Widely cited lead response research finds qualification odds fall sharply within the first hour, with most of the advantage concentrated in the first few minutes. In recruitment there is a second clock running too, because candidates apply to several roles in one sitting and the first real conversation frames all the others.
Does this work for temp and contract desks?
It suits them particularly well. Filling a Monday booking on a Friday evening is a reach and response problem: contacting a large pool quickly and handing the consultant the people who said yes and are available. That is closer to broadcast with qualification than to a long consultative call.
What do we need in place before starting?
A CRM the agent can write to, clarity on which roles it should qualify against, and a defensible basis for calling applicants under PECR and UK GDPR. Most pilots are live in two to three weeks, which is dominated by integration and script work rather than by the voice itself.
