ATZ CRM connects candidate rejection prompts to respectful status updates, careful feedback boundaries, email templates, and talent-pool routing.
Copy-ready prompts
Use these rejection prompts when a candidate needs closure without damaging the relationship. They help recruiters be respectful, concise, and careful about feedback boundaries.
Use for candidates not advancing.
Write a respectful rejection email for [candidate] after [stage] for [job title]. Include thanks, clear decision, brief job-related reason if appropriate, and future-fit language only if relevant.
Use when a candidate asks why.
Draft a careful response to [candidate] requesting feedback after rejection. Keep feedback job-related, concise, kind, and avoid subjective or protected-category language.
Use for strong future-fit candidates.
Write an invitation for [candidate] to stay in our talent community after being declined for [job title]. Explain why future roles may fit and ask permission to stay in touch.
Prompt framework
Rejection prompts should include the hiring stage, approved decision reason, tone, future-fit status, and follow-up boundary. That keeps the message humane without adding risky or unsupported explanations.
Candidate rejection context: Stage
Candidate rejection context: Decision reason
Candidate rejection context: Tone
Candidate rejection context: Feedback boundaries
Candidate rejection context: Future-fit action
Use cases
Common mistakes
Workflow
Related resources
FAQ
It should keep the reason job-related, avoid over-explaining, use respectful language, remove protected-category references, and clarify whether future contact is appropriate.
Only include feedback that is accurate, role-related, approved by the hiring team, and useful to the candidate. When in doubt, keep the response brief and careful.
They can close the loop respectfully, preserve trust, ask permission to stay in touch, and route strong future-fit candidates into a relevant talent pool.
