The eight messages a recruiting desk keeps sending

The job of a first approach is to make one person believe this message was written for them and to make replying cheap. It fails when it opens with the recruiter's firm, when the relevance is generic, and when the ask is a call rather than an answer. A message that requires the recipient to schedule thirty minutes before knowing whether the role is interesting is asking for a large commitment in exchange for very little.

The sequence that works is: the specific thing about this person that caused the message, the role in one line including the thing they would actually want to know, why it might fit them specifically, then a small ask. The salary band or rate belongs in the first message. Withholding it to force a conversation is the most reliable way to be ignored by exactly the people who have options.

Follow-up is a different message, not a repeat with more punctuation. Its job is to add one new piece of information and to make it easy to say no. Adding something new gives a legitimate reason to write again; explicitly permitting a no removes the social cost of replying and produces answers instead of silence. One follow-up on most channels, two at the outside on email, and then stop.

This is the message that most affects a desk's long-term database and the one most often skipped. Its job is to close the loop cleanly, quickly, and in a way that leaves the person willing to hear from you again. Its usual failure is not being sent at all, followed closely by being sent so late that the candidate had already concluded you were rude.

Speed matters more than eloquence. A short message within a day of the decision is better received than a considered one a fortnight later. Be clear that it is a no, because softened language that reads as ambiguous produces a follow-up asking what it meant, which is worse for both parties.

Give a reason only if it is true and specific enough to be useful. Vague feedback is worse than none, and detailed feedback about a client's decision is not always yours to pass on. Where you would genuinely welcome them for other roles, say so and mean it, because saying it as a formula and never contacting them again is how a database of silver-medal candidates becomes worthless.

A confirmation is an operational document, not a courtesy. Its job is to eliminate every question the candidate might otherwise have to ask, and its failure mode is a missing detail that produces an anxious email the day before, or worse, a candidate at the wrong entrance.

It should carry the date and time with the time zone stated explicitly, the format and the joining method, the names and roles of everyone in the room, how long it will run, what the candidate should prepare or bring, and a direct way to reach a human if something goes wrong on the day. Travel detail for an in-person interview belongs here too: which entrance, which floor, whose name at reception.

The reminder is a separate short message timed to be useful rather than to satisfy a rule. Repeat only the essentials and the contact route. On messaging channels it is the single highest-return message a desk sends, because a forgotten interview costs the same as one that was never arranged.

An offer message has to be unambiguous and complete, because it is the document the candidate will re-read, forward to a partner and compare against a counter-offer. Its job is to remove every reason for hesitation that is merely informational.

It should state the salary or rate exactly, the start date, the working pattern and location expectation, the notice or acceptance deadline, and what happens next procedurally. Vagueness about any of those is where a candidate's enthusiasm goes to cool, because they cannot make a decision on an incomplete picture and the delay is what a counter-offer needs.

Deliver the detail in writing even if you called first, and call first. The conversation is where you hear the hesitation; the written version is what gets shown to the person whose opinion actually decides it. Then have the resignation conversation before the acceptance rather than after, because the counter-offer is the most predictable event in recruiting and it is far easier to discuss in the abstract.

A reference request has to make a busy stranger do unpaid work for someone else's benefit. Its job is to make that as small as possible: say who is asking, who they are being asked about, what specific role that person is being considered for, exactly what you need, how long it will take and by when. Open-ended requests for general impressions produce either nothing or a paragraph that says the person was reliable, which is not information.

Ask a small number of specific questions tied to the requirements of the role. Structured answers are comparable across referees, and comparable answers are the only kind that can affect a decision defensibly.

A client update is a different discipline. Its job is to keep an account confident between events, and it fails by only appearing when there is good news. A short regular update covering what happened, what is happening next and what you need from them is worth more than a long one triggered by a submittal. When there is a problem, lead with it: clients forgive a difficult search far more readily than they forgive discovering it late.

This is the message that turns a database into an asset, and it is the hardest of the eight. Its job is to restart a relationship that has gone cold without pretending it never went cold. It fails when it is transparently a mail-merge to everyone who has not been contacted in six months, which candidates identify instantly.

The structure that works acknowledges the gap plainly, references something specific and verifiable from the previous conversation, states what has changed that makes contact worthwhile now, and asks a low-cost question. If you cannot name something specific from the last conversation, that is a data problem rather than a writing problem, and the honest response is to send fewer, better-researched messages.

Re-engagement is also where consent and suppression matter most, because these are people who have not heard from you in a long time. Check that the record still carries a basis for contact and that no opt-out has been recorded since. A re-engagement campaign that messages people who asked to be removed is the fastest way to damage a database you spent years building.

Templates go stale in three ways. They circulate until recipients recognise them. They accumulate qualifiers as different people edit them until nothing is said clearly. And they persist after the thing they describe has changed, so a template still mentions a process step that was removed a year ago.

The practical defence is ownership and review. One person owns each template. Every template carries a review date. Variables are limited to values you reliably hold, because an unpopulated merge field is more damaging than a plain sentence would have been.

Personalise the first two sentences and leave the rest structural. That is where the reader decides whether to continue, and it is the only part where individual effort measurably pays. Beyond that, effort is better spent on sending fewer messages to better-chosen people.