Skip to main content

Send disqualification email to candidates automatically

Set up a Recipe that emails candidates when they're disqualified from a job, so you never miss closing the loop.

Written by Amritanshu Anand

When you disqualify a candidate, sending them a quick "thanks but no" email is good practice, but easy to forget when you're juggling 50 candidates across 10 jobs. A Recipe automates it. Set it up once, and every candidate who gets disqualified from a stage you care about receives the email automatically.

Set up the Recipe

  1. Go to the Recipes page from the main navigation.

  2. Create a new Recipe and give it a name (e.g., "Auto disqualification email").

  3. Set the trigger to Candidate is disqualified.

  4. Scope the Recipe β€” apply it to all jobs, or pick specific jobs you want it to run on.

  5. Optionally pick the Source Stage (the stage from which the candidate is disqualified). Leave open if you want the Recipe to fire from any stage.

  6. Optionally pick the Disqualification Reasons the Recipe should trigger on. Leave open to fire on any reason.

  7. Add the action: choose Send an Email and set the recipient to the candidate.

  8. Compose the email β€” write it from scratch using fields, or pick a saved email template.

  9. Save the Recipe and turn it on.

The Recipe runs the next time anyone disqualifies a candidate that matches the scope.

Practical example

Your team disqualifies a lot of candidates from the Application Review stage based on resume fit. You set up a Recipe scoped to all jobs, source stage = Application Review, no specific reason filter. The action is a friendly rejection email using a saved template. Every candidate disqualified from Application Review now gets the email automatically, no more manual sends.

Things to know

  • The Recipe applies going forward only. Candidates already disqualified before you turned the Recipe on won't receive the email.

  • Use email templates so the wording stays consistent across recruiters and over time. Templates also make it easy to update the message later without editing the Recipe.

  • Confirm the scope before going live. A Recipe scoped to "all jobs" runs across every job in the workspace. If you only want it for specific roles, pick those jobs explicitly.

  • The candidate's email on file is the recipient. If a candidate doesn't have an email address, the Recipe can't deliver β€” make sure your candidate intake captures it.

Did this answer your question?