When you send an email in Recruiterflow, the platform needs context to auto-fill merge fields correctly. A generic candidate email can't auto-populate interview times — the system doesn't know which interview you mean. That's where template types come in. They tell Recruiterflow exactly which data to pull, so merge fields fill in accurately instead of returning blank values.

Each template type is tied to a specific moment in your recruiting workflow. When you pick a template in that context, Recruiterflow matches it to the right data — the right candidate, interview, job, or offer — and populates the relevant merge fields automatically.

You assign a template type when creating or editing a template in Settings → Templates. Once set, the template only appears in the contexts where it's relevant.

The default type for general candidate correspondence. Pulls in candidate details and job information.

Visible: Everywhere across the platform — except when emailing an contact after scheduling an interview.

For outreach to contacts (clients, hiring managers, vendors). Includes fields from the contact's profile.

Visible: Everywhere where the contact is involved. Think emailing a contact from their profile, MPC, etc.

Used when submitting candidates to clients. Includes a candidate list field that lets you bundle multiple candidates with their relevant details into a single email.

Visible only in the candidate submission flow.

For follow-up emails to candidates after an interview is completed. Gives you access to interview-related merge fields in a post-interview context.

Visible in:

For sending follow-up communications directly to the interviewer after a session. Only surfaces in the specific flow where it makes sense.

Visible: After scheduling an interview, when sending an email to the interviewer.