CloudHire's Email Template and Candidate Communication Workflow
There’s a version of candidate communication that most recruiters know too well: A copied-and-pasted email that went out without being updated, a generic rejection message that didn’t match the candidate’s stage, or a follow-up that took three days because no one had a template ready. The friction isn’t always visible, but it adds up across every role.
CloudHire’s email template and candidate communication workflow are built around the hiring pipeline itself. Templates aren’t stored in a separate section that recruiters have to go find; they surface at the moment a candidate is being moved between stages, which is when the communication decision actually matters.
CloudHire Email Templates Across Hiring Stages:
Where Templates Appear in the Workflow
Candidates move through CloudHire’s pipeline in stages: Sourced, shortlisted, evaluated, offered, rejected, and others in between. Whenever a recruiter selects a candidate and chooses to advance them to the next stage, the platform automatically suggests a corresponding email template. The recruiter doesn’t have to remember which template applies; the system matches the stage and surfaces the right one.
This happens across multiple starting points. Whether a candidate is in the sourced section, the Cloud ID verified pool, or the applied section, the template logic applies. Moving someone from applied to evaluation, for example, triggers a different template than moving them from shortlisted to offered.
What Recruiters Can Do With a Template Before Sending
The suggested template opens in an editable view. Recruiters can read it, adjust the language to reflect the specific candidate or role, add any details relevant to that hire, and then send it. Nothing goes out automatically; there’s always a review step before the email is dispatched.
The ‘send and move’ action handles both things at once: The email goes to the candidate, and the candidate’s pipeline stage updates simultaneously. This keeps the communication and the tracking in sync without requiring two separate actions.
Editing and Saving Your Own Templates
Recruiters aren’t locked into the predefined templates. Any template can be edited and saved with a ‘save and overwrite’ option, which updates the default for that stage going forward. This is useful for teams that have a specific tone they prefer, or for roles where the standard language doesn’t quite fit technical positions, senior hires, contract roles, and so on.
Over time, a recruiter can build a set of templates that reflect how their team actually communicates, rather than relying on defaults. The predefined options serve as a starting point, not a constraint.
Why Stage-Aware Templates Matter
A rejection email at the sourcing stage reads differently from one sent after a final interview. An evaluation invite for a senior candidate probably needs a different context than one for an entry-level applicant. Stage-aware templates reduce the chance that a recruiter sends the wrong message at the wrong time, not because recruiters are careless, but because managing a pipeline with dozens of candidates in different stages is a lot to track manually.
The system also keeps candidate experience more consistent. Candidates moving through a structured process receive communications that match where they actually are, which tends to reflect well on the company doing the hiring.
How This Connects to the Rest of the Platform
Email templates work alongside the other communication features in CloudHire, just like Gmail integration for routing candidate emails through a recruiter’s connected account, automated follow-up sequences for interview invitations, and the full hiring pipeline that tracks where every candidate stands. The other posts in this series cover each of those in more detail.
Read More:
- CloudHire’s Gmail Integration and Email Sequences Everything in One Dashboard
- CloudHire AI Inbound Calling for Candidate Outreach
- CloudHire Google Calendar Integration for Interview Scheduling