Client Communication Is Where Agencies Lose Deals
Agencies lose mandates to silence, not to weak shortlists. Why response time decides who keeps the client, and which client updates are worth automating.
Agencies lose far more mandates to silence than to weak shortlists. A client who has heard nothing for 8 days does not conclude that the search is difficult; they conclude that nothing is happening, and they call a second agency. Response time — how fast a candidate hears back, how fast a client sees a submission, how fast a hiring manager gets chased for feedback — is the competitive variable most agencies never measure. The shortlist is what you are judged on at the end. The cadence decides whether you are still on the mandate when the end arrives.
I ran a recruitment agency for four years before I built Pickr. Every mandate I lost that I could reconstruct afterwards had the same shape, and none of them looked like a quality problem at the time.
Why clients really stop working with a recruitment agency
When a client ends a search, you get a clean, unarguable reason. Budget froze. They decided to hire internally. The role changed. Sometimes that is true. More often it is the polite version of a decision made 2 weeks earlier, in a gap you did not know was open.
The sequence repeats with small variations. Three candidates go over on a Tuesday. No acknowledgement, no feedback. The recruiter waits, because chasing feels pushy and there is nothing new to report anyway. Around day 8 the hiring manager mentions to a colleague that the search is not moving. By day 14 a second agency has the brief. Your candidates are still sitting in that inbox, and when feedback finally arrives you are no longer the only supplier — you are the slow one.
Nothing in that story is about candidate quality. Typical agency time to hire runs somewhere in the 30-45 day range, and a large share of it is waiting states that nobody owns; in the searches I could reconstruct afterwards it was routinely a third or more. Those waiting states are where the relationship is actually decided.
The three response times that decide who keeps the mandate
Only three matter, and none of them is hard to measure.
Candidate to recruiter. How long a candidate waits to hear something after applying or replying. Target under 24 hours, even when the answer is no. This is the candidate side of the same discipline, and it feeds the client side directly: a pipeline full of people who have gone cold cannot produce a fast submission.
Brief to first submission. For a live role, under 5 working days. Longer than about 2 weeks and the client has already had the conversation that ends with a second agency being briefed — not because your shortlist would have been worse, but because they had no evidence that one was coming.
Submission to client decision. The one agencies treat as out of their hands. It is not. If a submission has been sitting for 72 hours, chasing is your job. At 5 days it becomes a phone call, not another email. Recruiters hesitate here because chasing feels like weakness, and it reads as the opposite: the agency that chases is the one behaving as though its candidates have other options, which they do.
Retained and exclusive work buys you a little patience on all three, which is one of several reasons to pursue exclusivity rather than compete on speed alone. It does not buy much. I have seen retained mandates go quiet and never recover.
The trade-off is real, and I would rather name it than sell around it. Holding these numbers across a dozen live searches is work, and a second nudge in the same week irritates a certain kind of hiring manager — you spend a little goodwill to get a decision. None of it rescues a weak shortlist either. A punctual agency with the wrong candidates still loses the mandate, just more slowly and with better documentation.
What a client update should contain in a week with no good news
The instinct every recruiter has is to go quiet in a bad week. Nothing has moved, so there is nothing to say, so you say nothing and hope next week is better. That is precisely the week the client's confidence drops, because from where they sit a silent week and an abandoned search look identical.
"No news" is information, provided it arrives with what you actually did. 42 profiles reviewed, 11 approached, 3 in conversation, 2 declined because the salary band is roughly 10% under what the market is paying. That last clause is worth more to the client than a shortlist, and it only exists because someone sent an update in a week that had no good news in it.
| Reads like a mail merge | Reads like a partner | |
|---|---|---|
| Subject | Weekly update, Senior Backend Engineer | Two salary declines this week — we should revisit the band |
| Content | Pipeline counts and stage names | The same counts, plus what they say about the role |
| Timing | Same slot weekly, regardless of what happened | Weekly floor, plus anything material the day it happens |
| The ask | None, or "let me know your thoughts" | One decision, named, with a date attached |
| Bad news | Absent until it cannot be avoided | First item, before the client hears it elsewhere |
The difference is not tone or length. It is whether the message contains an interpretation only you could make. Automation is very good at the first column and cannot produce the second on its own.
What to automate in client communication, and what has to stay human
The factual half of client communication should never be typed by a person. Submission notifications, stage moves, interview confirmations, a nudge to a hiring manager at 48 and 72 hours, a weekly summary of what moved — these are messages whose entire value is that they are never late and never forgotten, which is exactly what people are worst at. That is the job of client and candidate communication in Pickr, and the counts come out of the live pipeline behind each mandate rather than a recruiter's recollection on a Friday afternoon.
What stays human is anything that changes the client's model of the market or the role. Salary pushback. A finalist declining. Telling a hiring manager that the brief describes a person who does not exist at that level in that city. The rule I would give a new consultant: if the message asks the client to change their mind about something, a human sends it, and preferably says it out loud first.
There is a third category worth naming, because it is where most agency tooling fails. A client hiring manager who has to be given a paid seat is a hiring manager who never logs in, so their verdict arrives as half a sentence in an email reply and lands nowhere the search can use. Pickr is the AI-native recruiting platform for recruitment agencies and in-house teams, and interviewer and hiring-manager seats on it are free, so that loop can close inside the system instead of in someone's inbox. Multi-client pipelines, client portals and placement tracking are native rather than permission workarounds, which matters when you are running 11 searches for 6 clients and every update has to be right for its own client. Free seats remove the excuse, not the habit: a hiring manager who would rather reply by email will keep replying by email, and someone still has to put that reply where the search can see it.
Interviews are transcribed and scorecards arrive pre-filled with evidence mapped to each criterion, so an interviewer edits a draft instead of facing an empty form 4 days later. The client-facing consequence is small and useful: the submission note can quote what the candidate actually said, rather than a CV and a paragraph written from memory.
A client communication cadence you can actually hold
| Event | Target | Owner |
|---|---|---|
| Candidate applies or replies | Acknowledged immediately, human reply within 24 hours | Automated, then recruiter |
| Brief to first shortlist | 5 working days | Recruiter |
| Submission reaches client | Same day, with evidence attached | Automated |
| Client feedback on a submission | Chase at 72 hours, call at 5 days | Recruiter |
| Interview to candidate feedback | 48 hours | Recruiter |
| Weekly client update | Same slot, including silent weeks | Automated draft, human sends |
Pick numbers you can hold with your current headcount, then hold them. A promised 24 hours that slips to 4 days does more damage than never having named a target, because now the client has a benchmark to measure you against and you supplied it.
What to change this week
Shortlist quality wins you the placement. Communication cadence decides whether you are still on the mandate long enough to make one. The three response times — candidate reply, brief to submission, submission to decision — are measurable this week without buying anything, and most agencies have never looked at them. Automate the messages whose value is punctuality, write the ones whose value is judgement, and never let a bad week be a silent one. The client who has not heard from you is not waiting patiently. They are drafting a brief for somebody else.
Frequently Asked Questions
Why do clients stop working with a recruitment agency?
More often than a weak shortlist, the cause is silence. A client who has heard nothing for a week or more assumes the search has stalled and briefs a second agency, and by the time your next candidate lands the role is contested. The reason given for ending a mandate is usually budget or a decision to hire internally, but the decision itself is normally made in a communication gap that nobody on either side owned.
How often should a recruitment agency update a client during a search?
Set a weekly floor and send event-driven updates on top of it. The weekly update goes out in the same slot even in a week with no progress, because a silent week is exactly when a client's confidence drops. Anything that changes what the client believes about the market, the salary band or the role goes out the day it happens rather than waiting for the weekly slot.
How fast should an agency chase client feedback after submitting candidates?
Acknowledge the submission the same day, then treat 72 hours as the point where chasing feedback becomes your job rather than the client's. At 5 days it should be a phone call rather than another email. Waiting politely for a hiring manager is how strong candidates get lost, because they are usually in 2 or 3 other processes moving faster than yours.
Can client updates be automated without sounding like a mail merge?
Partly. Automation is reliable for facts: stage moves, submission notifications, interview confirmations and reminders are better sent by a system, because they are never late and never forgotten. Anything that interprets the market, delivers bad news or asks a client to change the brief should be written and sent by the recruiter who owns the relationship, since that judgement is the part clients are paying for.
What should a weekly client update to a hiring manager contain?
Three things: what moved since the last update in specific numbers, what those numbers say about the role or the salary band, and one decision you need from the client with a date attached. An update that lists activity without interpreting it reads like a status bar, and status bars stop being opened after 2 or 3 of them.
Free recruiting audit · 2 minutes
Find out what your hiring process is actually costing you.
Answer eight questions, or connect your current system read-only, and get a report on where your funnel loses candidates and which changes are worth making. No signup, no API key stored, data stays in the EU.
Written by Andreas Amann
Founder of Pickr. Former operator at startups in Berlin and Silicon Valley, where he helped scale companies from 40 to 200+ people. Built Pickr after years of using every major ATS as a recruitment agency owner at ScalingPPL.