Automate Candidate Rejection Emails
Recruiters either send a generic templated rejection to everyone — which candidates notice and which damages employer brand — or skip sending one at all because personalizing hundreds of rejections isn't a good use of time, leaving candidates in silence for weeks. Neither option is good: silence generates complaints and poor employer reviews, and a copy-paste template with no reference to the specific role or stage reads as dismissive. The riskiest failure mode is sending an automated rejection to a candidate who is actually still active in a different open pipeline, which happens more often than teams expect when candidates apply to multiple roles.
STARTING PRICE
From €299
Standard tier · Multi-step workflow with AI extraction/decisioning and 2-3 integrations.
Get a quote →Saves roughly 3-4 hrs/week for a recruiter managing high applicant volume.
How the automation works
We generate rejection emails that reference the actual role and stage the candidate reached, drawing on interview notes when available to add one genuine, specific line rather than pure boilerplate, so the message reads as considered rather than mass-produced. Before any email sends, the candidate's status is cross-checked across every open requisition they're part of — if they're active in another pipeline, the rejection is held and routed to a recruiter rather than sent automatically. Tone and content adjust by stage, and every sent email is logged against the candidate record for compliance and candidate-experience tracking.
Process flow
- 01
Candidate marked not-advancing trigger
A recruiter or the screening step marks a candidate as not proceeding, which queues the rejection for drafting rather than firing an email immediately.
- 02
Check cross-pipeline status ai
The candidate's status is checked against every other open requisition they're active in before anything sends — an active candidate elsewhere is routed to a human, not auto-rejected.
- 03
Draft stage-appropriate email ai
A rejection is drafted referencing the specific role and stage reached, pulling a genuine detail from interview notes where available rather than generic boilerplate.
- 04
Queue for recruiter review output
Drafts route to the recruiter for a quick review-and-send rather than firing unsupervised, keeping a human in the loop on tone and accuracy.
- 05
Send and log integration
Once approved, the email sends and is logged against the candidate record in the ATS for compliance and future employer-brand tracking.
Inputs
- Candidate ATS record and pipeline status across all requisitions
- Role and stage reached
- Interview notes (where available)
- Company tone/template guidelines
Outputs
- Stage-appropriate rejection email drafts
- Cross-pipeline status check log
- Sent-email compliance record
- Candidate-experience response time metric
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- Automated rejection emails sent to a candidate who is still active in a different open pipeline is the single most damaging failure mode here — it reads as the company not knowing who it's talking to, and it requires an explicit cross-requisition status check before any send, not an assumption that one pipeline's rejection means the candidate is fully out.
- Generic templated rejections that reference the wrong role name (a common copy-paste error when handling volume) are worse for employer brand than no automation at all — the role and stage need to be pulled live from the ATS record at send time, not hardcoded into a static template.
- Sending rejections in a batch immediately after a hiring decision, with no delay, occasionally rejects a candidate the hiring manager was still reconsidering — a short hold window with an override option protects against decisions that get revisited within a day or two.
- Feedback language that sounds specific but is actually generated without real interview notes behind it can create legal exposure if a candidate challenges the stated reason — feedback content should only reference notes that actually exist, defaulting to generic-but-honest phrasing when they don't.
Frequently asked questions
Will this ever send a rejection automatically without a human reviewing it?
No — drafts queue for recruiter review and approval before sending; the automation removes the drafting burden, not the final send decision.
How does it prevent rejecting someone who's still being considered for another role?
Every draft runs a cross-requisition status check against the candidate's full ATS record first; if they're active anywhere else, the rejection is held and flagged to a recruiter instead of sent.
Can the tone be adjusted for candidates who made it further in the process?
Yes — post-interview rejections are drafted with more specific, considered framing than application-stage passes, reflecting the greater investment the candidate made.
Does this help with compliance record-keeping?
Every sent rejection is logged against the candidate record with the role, stage and content, which supports audit trails for hiring compliance reviews.