10 Recruiter Email Templates for Candidates and Clients
Recruiters send the same kinds of messages over and over: a first reply to an applicant, a cold approach to a passive candidate, a rejection, a progress update, a client introduction, a follow-up, a shortlist.
Each one has a different job, and using the wrong one wastes the reader's time. The ten templates below cover those moments. Each is short enough to adapt in a minute and specific enough to sound like a person wrote it. Fill the bracketed fields, delete what does not apply, and send.
Choose the template by the moment, not by the recipient
The most common mistake is sending a progress update when the reader expects a decision, or a rejection when the candidate is still in play. Use this decision table before you open your email client. The right-hand column names the one field that most affects whether the message feels personal.
Templates for reaching candidates
These four templates cover the candidate side of the desk: an applicant who looks strong, a passive candidate you want to approach, a candidate you are not taking forward, and a candidate who is still in the process and needs an update. Each template below shows the subject line and body exactly as you would send it, with a Copy button so you can paste it straight into your email client and fill the bracketed fields.
Templates for reaching clients and prospects
The client side has its own rhythm: introduce the agency, ask for a response, answer an inbound enquiry, open a cold conversation, follow up, and submit a shortlist. The six templates below follow that sequence, each with its subject line, body and a Copy button.
Field map: what to fill in before sending
Every template uses a small set of placeholders. Keep the names consistent so you can merge them from your applicant tracking system or CRM later. The list below covers every placeholder that appears in the ten templates.
Worked example: filling the cold-email template
Suppose you are approaching a candidate who currently works at a company in the same sector as your client. The template asks for the current company, the role, and the new company name. A filled version reads: the candidate's experience at their current employer makes them a strong fit for the open role at the client. The template then invites a reply with a phone number and a preferred call time. Nothing in the message promises an outcome, a salary, or a start date; those details belong in the conversation that follows.
Rejection or progress update? A quick distinction
A rejection closes the application. A progress update moves it forward. The rejection template states that the process will not continue and gives a reason. The progress-update template names the stage the application has reached and says the recruiter will be in touch again. If a candidate is still being considered, send the update. If the decision is final, send the rejection. Sending both in the wrong order is the fastest way to lose a candidate's trust.
Practical checks before you hit send
A short checklist keeps the templates from sounding automated. Personalize the first line with something specific to the reader. Keep the subject line short and concrete. Make the ask obvious: a reply, a call, or a decision. Send follow-ups on a schedule you can keep. Use a signature that identifies you and your agency. Keep the tone friendly but professional. Automate the sending only after the content has been reviewed.
Why a plain, text-heavy email can outperform a designed one
Najam Ahmed of Cloudways makes a practical point: a mostly plain-text email can read as though someone actually sat down and wrote it, and recipients tend to engage more with a message that feels individually addressed. The takeaway for recruiters is not to abandon formatting entirely, but to avoid hiding a generic message behind a polished template. Write the first two sentences for this specific reader, then let the rest of the template carry the structure.
Turning a reviewed template into a reusable one
Once a template has been sent a few times and reads well, save it as a reusable template in your email tool or CRM so the structure stays consistent across the team. Keep the personalization fields populated from accurate records, and review the saved version periodically so it does not drift into stale phrasing. The templates below are starting points; the reusable version should be the one your team has actually tested. Saving them as templates in your email tool also saves time and keeps your team's email communication consistent.
| Hiring moment | Template | Recipient | Field that matters most |
|---|---|---|---|
| Strong applicant applies | 1. Perfect candidate applies | Candidate | Job title and company name |
| Approaching a passive candidate | 2. Cold email to a potential candidate | Candidate | Current company and new company name |
| Application will not proceed | 3. Reject an applicant | Candidate | Reason for the decision |
| Application is moving forward | 4. Update candidates on progress | Candidate | Hiring stage |
| First contact with a client | 5. Recruitment agency introduction | Client | Industry or niche |
| Client has not replied | 6. RTR email sample | Client | Job title or service |
| Inbound enquiry about services | 7. Email to a recruitment agency | Agency | Job placement or recruitment services |
| Cold approach to a prospect | 8. Cold email to prospective clients | Prospect | Recruitment specialisation |
| Following up with a client | 9. Follow up with clients | Prospect | Similar company and roles |
| Sending a shortlist | 10. Submit shortlisted candidates | Client | Job title and attachments |
Template numbering follows the order used in this guide. Field names are placeholders, not system fields.
| Placeholder | Used in | What to enter |
|---|---|---|
| [Job_Title] | Templates 1, 2, 3, 4, 10 | The role the candidate applied for or is being approached about |
| [Company_Name] | Templates 1, 9 | The hiring company or the client company |
| [Candidate_Name] | Templates 1, 2, 3, 4 | The candidate's name as it appears in your records |
| [Date/Time] | Template 1 | Proposed interview slot |
| [Your_Name] | All templates | Your name and, if useful, your agency |
| [Current_Company] | Template 2 | The candidate's current employer |
| [New_Company_Name] | Template 2 | The client company with the open role |
| [Reason] | Template 3 | A short, factual reason for the rejection |
| [Agency_Name] | Template 4 | Your agency's name |
| [Hiring_Stage] | Template 4 | The stage the application has reached |
| [Your Agency Name] | Template 5 | Your agency's name |
| [Client Name] | Template 5 | The client contact's name |
| [industry/niche] | Template 5 | The sector you recruit for |
| [similar companies] | Template 5 | Client names you are willing to reference |
| [Job Title/Service] | Template 6 | The role or service the client asked about |
| [Recipient Name] | Template 6 | The client contact's name |
| [Recruitment Agency Name] | Template 7 | The agency you are writing to |
| [job placement/recruitment services] | Template 7 | What you are asking the agency to help with |
| [Industry/Field] | Template 7 | Your background |
| [Prospect_Name] | Templates 8, 9 | The prospect's name |
| [Agency_Name] | Template 8 | Your agency's name |
| [Your Recruitment Specialisation For Target Type Of Client] | Template 8 | The niche you serve |
| [Insert 2-3 Clients Here Relative To The Vertical] | Template 8 | Relevant client names |
| [What You have done for that client] | Template 8 | A factual description of the work |
| [Similar_Company] | Template 9 | A comparable client |
| [Technical/Executive] | Template 9 | The type of roles you placed |
| [Company_Name] | Template 9 | The prospect's company |
| [Client_Name] | Template 10 | The client contact's name |
Placeholder names are reproduced from the templates. They are not API fields or system variables.
Frequently asked questions
Can I use these templates for both candidates and clients?
Yes, but not interchangeably. Templates 1 to 4 are written for candidates; templates 5 to 10 are written for clients and prospects. The recipient, the ask, and the tone differ, so pick the template that matches the relationship.
What is an RTR email?
RTR stands for Request to Respond. It is a short follow-up that asks the recipient to confirm whether they are still interested and how they would like to proceed. Template 6 is an RTR sample.
Should I send a rejection email or a progress update?
Send a rejection when the decision is final and the application will not continue. Send a progress update when the candidate is still being considered and has moved to a new stage. The two templates are not substitutes for each other.
Do I need to personalize every template?
Yes. Each template contains placeholders for names, companies, roles, and reasons. Filling them in is the minimum; adding one specific detail about the reader makes the message read as a real approach rather than a mass mailing.
Can I automate these emails?
You can turn the templates into reusable templates in your email tool or CRM so the structure stays consistent. Review the content before automating, and keep the personalization fields populated from accurate records.