Email templates and merge fields

Build reusable email templates with placeholders for candidate, job, and signature data.

Where to manage

Settings β†’ Email Templates.

The templates list

The page shows a table with these columns:

  • Visibility β€” public, private, or shared (icons: for private, for shared).
  • Template Name.
  • Subject.
  • Type β€” the template's context (see below).
  • Actions β€” Edit, View, Delete.

Top-right button: + New Template.

Template types (contexts)

Each template belongs to a specific context that controls where it surfaces. The available contexts:

  • Share Resumes (resumeshare) β€” sending resumes to a colleague.
  • Discover Share (discovershare) β€” sharing from the Discover view.
  • Share with Vendor (sharewithvendor) β€” vendor-collaboration messages.
  • Job Offer (joboffer) β€” used by the Send Job Offer action.
  • Job Requisition (requisition) β€” job-related messages.
  • Email (emailstab) β€” generic candidate emails.
  • Consent Request (consent) β€” GDPR consent request emails.
  • Interview Schedule β€” interview invites.
  • GitHub Profile (githubProfile) β€” outreach to GitHub-sourced candidates.
  • Customer (customer) β€” customer/client-facing messages.
  • Contact (contact) β€” contact-management emails.
  • Resume Pool (resumepool) β€” candidate-database emails.

The right context surfaces the template in the right place β€” e.g. Send Job Offer only shows templates with the Job Offer context.

Visibility

  • Public β€” usable by anyone in your workspace.
  • Private β€” only the creator can use it.
  • Shared β€” explicitly shared with specific users.

Available merge placeholders

Use these in the subject or body β€” they get substituted at send time:

  • Candidate: {{NAME}}, {{CANDIDATE_NAME}}, {{CANDIDATE_FIRST_NAME}}, {{CANDIDATE_LAST_NAME}}, {{CANDIDATE_EMAIL}}.
  • Job: {{JOB_PROFILE}}, {{JOB_LOCATION}}, {{JOB_LINK}}, {{POSITION_SALARY_RANGE}}, {{EXPERIENCE_REQUIRED}}.
  • Company / sender: {{COMPANY_NAME}}, {{EMAIL_SIGNATURE}}.
  • Scheduling: {{MEETING_SCHEDULING_LINK}}.
  • Context-specific: {{LATEST_EVENT_DETAILS}}, {{LANGUAGE_SKILLS}}, {{GITHUB_PROJECTS}}.

Creating a template

  1. Click + New Template.
  2. Pick the type (context) β€” this controls where it'll appear in the product.
  3. Set visibility (public / private / shared).
  4. Write the subject and body using the rich-text editor.
  5. Insert merge placeholders where needed.
  6. Save.
  • Application received (Email).
  • Phone screen invite (Interview Schedule).
  • Take-home assignment (Email).
  • Onsite invite (Interview Schedule).
  • Job offer cover (Job Offer).
  • Rejection β€” early stage (Email).
  • Rejection β€” late stage (Email).
  • Talent pool re-engagement (Resume Pool).
  • GDPR consent request (Consent Request).

Tips

  • Always include {{EMAIL_SIGNATURE}} at the end so the user's signature renders.
  • Test merge fields with a real candidate before launching a new template β€” empty placeholders look terrible in the wild.
  • Keep template names short and descriptive β€” they appear in dropdown pickers.