Placeholders are substitute text used in emails and email templates that will be replaced by information based on context.
They come in handy when sending bulk or automated emails, as candidate, event, or job information will automatically be inserted into your template.
You can also use them when sending a regular email; for example, instead of looking up who is the recruiter or hiring manager for the job, you can insert a placeholder and have the information populated automatically.
In this article:
Inserting placeholders
You can use placeholders wherever you create or send emails or email templates in Recruitee. You can insert them into the subject line and body of your emails in two ways:
1) By selecting them in the placeholder bar.
2) By typing a square bracket and a few characters. We will suggest possible placeholders based on that.
⚠️ To ensure placeholders interpolating data, always insert an email template via the drop-down menu and select placeholders in the placeholder bar or from the drop-down after typing a square bracket and a few characters. Do not copy-paste email templates into the editor, and do not manually write out placeholders, as they may not interpolate data. Candidates may receive emails with placeholders instead of their data as a result.
Placeholders available in Recruitee
Here’s a list of all placeholders you can use, what information they interpolate, and their limitations.
Category | Placeholder | Description | Limitations |
Candidate | candidate.first | The candidate’s first name |
|
| candidate.last
| The candidate’s last name |
|
| candidate.full | The candidate’s full name |
|
| candidate.full_email | The candidate’s full name, followed by their email address in brackets |
|
Email sender | email_sender.first | The first name of the team member who is sending the email | Available only in Event invitation and General email templates |
| email_sender.last | The last name of the team member who is sending the email | Available only in Event invitation and General email templates |
| email_sender.full
| The full name of the team member who is sending the email | Available only in Event invitation and General email templates |
| email_sender.full_email | The first name of the team member who is sending the email, followed by their email address in brackets | Available only in Event invitation and General email templates |
Event | event.full | The type of the event, date, time, and the full names of all interviewers (in the email notification to the candidate) or name of the candidate (in the email notification to interviewers) | Available only in Event invitation email templates |
| event.link | The link to the view box with event details | Available only in Event invitation email templates |
| event.location | The event location | Available only in Event invitation email templates |
| event.date | The date of the event | Available only in Event invitation email templates |
| event.type | The event type | Available only in Event invitation email templates |
| event.interviewers | The full names of all interviewers participating in the event | Available only in Event invitation email templates |
Hiring manager | hiring_manager.first | The first name of the team member who is assigned to the job as the hiring manager | Not available in GDPR/EEO |
| hiring_manager.last | The last name of the team member who is assigned to the job as the hiring manager | Not available in GDPR/EEO |
| hiring_manager.full | The full name of the team member who is assigned to the job as the hiring manager | Not available in GDPR/EEO |
| hiring_manager.full_email | The full name of the team member who is assigned to the job as the hiring manager, followed by their email address in brackets | Not available in GDPR/EEO |
Recruiter | recruiter_per_job.first | The first name of the team member who is assigned to the job as the recruiter | Not available in GDPR/EEO |
| recruiter_per_job.last | The last name of the team member who is assigned to the job as the recruiter | Not available in GDPR/EEO |
| recruiter_per_job.full | The full name of the team member who is assigned to the job as the recruiter | Not available in GDPR/EEO |
| recruiter_per_job.full_email | The full name of the team member who is assigned to the job as the recruiter, followed by their email address in brackets | Not available in GDPR/EEO |
General | company | The company name |
|
| department | The name of the department to which the job is assigned to | Not available in GDPR/EEO |
| job_offer | The job title | Not available in GDPR/EEO |
| job_offer.all | Inserted in email body: titles of all jobs to which EEO questions relate to; jobs are separated with a comma, e.g., “Software tester, Tech support agent, Junior QA”
Inserted in email subject: title of the first of jobs which EEO questions relate to; followed by “and X other jobs,” e.g., “Software tester and 2 other jobs”
| Available only in EEO emails |
Interpolating job-related placeholders
When a candidate is assigned to multiple jobs, we fill the job-related placeholders (such as [job.offer], [department], and placeholders from the Recruiter and Hiring manager categories) with information from the job first assigned to the candidate by default. You can adjust the job when sending the email:
You can pick the correct job in the drop-down if you send the email to one candidate assigned to multiple jobs.
If you send an email to multiple candidates assigned to various jobs, a pop-up will appear so you can ensure the placeholders populate with the correct information.
📌 If you send an email to multiple candidates directly from within a job, the placeholders will automatically interpolate information from that job.
⚠️ Job-related placeholders do not work with talent pools, archived jobs, jobs you don’t have access to, candidates not assigned to any jobs, and non-candidates!
Related articles |