Candidates applied at half past eight in the evening. Nobody answered until Tuesday.
A UK recruitment agency was losing candidates to response time rather than to competitors' propositions. An out-of-hours desk under its own brand closed the window.
Sector: Recruitment agency. Market: United Kingdom. Services used: Out-of-hours desk, Recruitment research UK.
A UK recruitment agency was losing candidates to response time rather than to competitors' propositions. An out-of-hours desk under its own brand closed the window.
The situation
A UK recruitment agency noticed that a substantial share of candidate applications and replies arrived outside working hours — evenings, weekends and across bank holiday weekends. Those candidates were being answered on the next working day, by which point many had engaged with other agencies. The agency did not have the volume to justify a permanent evening team.
What we did
We established an out-of-hours desk operating entirely under the agency's brand: calls answered in its company name, emails sent from its domain, its templates, its tone and its escalation rules. Cover ran weekday evenings, agreed weekend hours and all UK bank holidays, including the Scottish dates that differ from England and Wales. A written handover was delivered before the agency's team started each working day.
What the research found
Four findings that changed the decision.
The out-of-hours window was larger than assumed
Once measured rather than estimated, a meaningful share of all candidate-initiated contact was arriving outside the working week.
Response speed mattered more than response quality at first contact
A short, prompt, human reply outperformed a considered one sent eighteen hours later, by a wide margin.
Bank holiday weekends were disproportionately costly
A four-day gap in responsiveness around a bank holiday accounted for a share of loss out of proportion to its length.
Escalation volume was very low
Almost everything the desk handled was routine. Genuine emergencies requiring a duty manager were rare, which made the escalation path cheap to maintain.
The outcome
Candidate response times outside working hours fell from next working day to within the same evening. The agency retained every relationship — to candidates and clients, the desk was simply the agency, answering. Monthly reporting on volume, response times and outcomes let the agency size the cover to demand rather than guessing at it.
The point of it
In competitive UK markets the response window is frequently the whole competitive advantage, and it is one of the few advantages that can be bought outright rather than built over years.
A note on confidentiality. Clients are never named without written consent, and we do not publish project values, candidate records or commercially sensitive figures. These accounts describe real engagement patterns with identifying detail removed. Where a specific number is not stated here, it is not a number we have published — please do not infer one.
How this engagement was structured
The commercial and methodological shape of the project, for readers assessing whether a similar approach would suit their own situation.
| Service | Out-of-hours desk |
|---|---|
| Scope | An overnight and weekend desk run in the client agency’s name, with a written handover each morning. |
| Commercial model | Fixed project fee in pounds, agreed against a written scope before work began. No commission and no percentage of salary. |
| Data ownership | Every record produced transferred to the client permanently at the close of the project. |
| Lawful basis | Legitimate interest under UK GDPR and the Data Protection Act 2018, documented for the project with an agreed retention period. |
Method
What we actually did
The decisions that determined whether this project produced something usable.
Scripts written jointly and approved
Greeting, qualification, booking confirmation and escalation wording in the client’s voice, signed off before a single call was taken.
Working inside the client’s systems
Every call and booking recorded where the day team expects to find it, so handover is a summary rather than a data-entry exercise.
Escalation thresholds defined precisely
What the desk resolves, what triggers a call, to which named person, within what time. Outside those rules nobody was woken.
Shadowed before going live
Running alongside the existing arrangement so calls were handled correctly from the first night rather than learned on the client’s clients.
What this engagement demonstrates
The expensive consequence of a missed evening call is not the lost booking. It is that the client re-orders the list of who they ring first, and nobody finds out for a quarter.
A note on how we present client work
Client identities and commercially sensitive details are withheld unless we hold explicit written permission to name them. Where figures are quoted they come from the engagement itself. Where an example is constructed to illustrate a method rather than describe a specific client, we label it as illustrative rather than presenting it as a case study. We would rather publish a less impressive page than an unverifiable one.
Questions we are asked about this work
Can we speak to a reference client?
In many cases yes, subject to the client’s agreement. Some engagements are confidential and will stay that way — which is itself a reasonable indication of how we would treat yours.
Would this approach work for our situation?
That is exactly what a scoping call establishes. Thirty minutes is usually enough to tell you whether the method transfers to your market and what the right scope and fee would be — including telling you if it does not transfer.
How much would a comparable project cost?
It is quoted as a fixed fee against a written scope, driven by market breadth, seniority and the depth of validation required. Because scope drives the fee, a meaningful figure needs a short conversation about what you actually need.
Recognise the problem?
Most of these engagements began with a client describing a symptom. Thirty minutes on a call is usually enough to work out what is actually causing it.