A recruiter closes one application and sends a rejection email. The candidate is still interviewing for another role at the same company. An AI draft that says the company will not move forward can now contradict an active conversation. The wording may read well while communicating the wrong decision.
A useful Greenhouse rejection workflow starts with the selected job, the recruiter decision and the intended communication. AI can help prepare that communication. It should not infer a hiring decision from interview notes, pick a rejection reason or silently expand a rejection across jobs. The controls below are a recommended custom workflow around Greenhouse, not a claim that Greenhouse provides this AI approval system natively.
Separate the decision, record change and message
Greenhouse describes rejection as removing a candidate from consideration and from the pipeline for a particular job. Its individual flow also includes a separate option to reject the candidate from all jobs. Treat that option as a different action with a different approval scope.
Use three checks in the review screen. First, has the recruiter decided the outcome for this application? Second, which record changes should follow? Third, should the candidate receive an email now, later or through another agreed channel? A draft should never collapse these choices into one generated instruction.
| Decision | What to review | Suggested owner |
|---|---|---|
| Reject the selected application | Candidate, job and confirmed outcome | Authorized recruiter |
| Reject from all jobs | Every affected application and intended scope | Recruiter responsible for the wider decision |
| Send a rejection email | Recipient, sender, subject, wording and timing | Communication reviewer |
| Do not send an email | Reason and any separate communication owner | Recruiter handling the candidate |
Build a small communication brief for AI
Pass only the information needed to write the email. A practical brief contains the approved candidate name, the selected role, an approved template version, the permitted level of personalization and the recruiter responsible for review. Include whether the person remains under consideration elsewhere.
Keep the internal rejection reason separate from the outward message. An internal reason can be useful for reporting without belonging in a candidate email. Do not ask a model to translate every internal note into a candidate-facing explanation. Where no explanation is approved, use the approved general wording.
The workflow should stop when the brief conflicts with the selected application. A missing role name, an unresolved recipient or a newer recruiter decision should return the item for review. Generating a plausible substitute creates a communication error rather than resolving the missing input. Our approach to AI recruiting agents starts with these bounded tasks.
Use Greenhouse templates without changing them accidentally
Greenhouse provides a default rejection email and supports additional organization-wide versions. It also allows an ad hoc email during an individual rejection. Edits in the individual rejection dialog do not update the saved template. That distinction matters when recruiters ask AI to improve wording.
Decide whether the request is to adjust one email or change the shared template. For one email, preserve the approved template identifier in the review record and store the proposed variation separately. For a shared change, route the new wording through whoever manages company templates.
Greenhouse documents template management permissions for Site Admins and Job Admins with the additional permission to manage company email and social media templates. Do not assume permission to reject a candidate also grants authority to change the organization's reusable wording.
Review the individual rejection before committing
- Open the candidate and select the correct job in Greenhouse.
- Confirm the hiring decision with the responsible recruiter.
- Review the rejection reason separately from the email draft.
- Check whether rejection should affect only this job or all jobs.
- Choose whether an email should be sent and review any selected delay.
- Inspect the resolved recipient, sender, subject and complete message.
- Confirm the accepted outcome before closing the work item.
Greenhouse offers both a rejection without an email and a rejection with an email. Its documentation specifically notes situations where a candidate remains under consideration for another role or receives a single separate communication. Make the no-email choice visible in the review record instead of treating it as a forgotten send.
Give bulk rejection its own validation
Do not reuse the individual email checks unchanged for bulk rejection. Greenhouse's bulk flow has different token restrictions. JOB_NAME, SOURCE, APPLIED_DATE, OFFICE and interview scheduling tokens are among the application-specific tokens that cannot be used there. Custom application, job and offer field tokens are also unavailable. Greenhouse says invalid tokens prevent sending.
Test the intended template in the actual bulk flow before a live batch. If the message needs role-specific wording, separate the group by reviewed context and use wording confirmed for that group. Do not rely on an unsupported token to fill the role name later.
Also inspect the selected records and their job or prospect-pool associations. The bulk action affects the selected candidates and prospects in their associated jobs or pools. A list that looks right by name can still represent the wrong set of application contexts. Save the reviewed selection and verify it again before acting.
Treat delayed and uncertain sends as operational states
A selected email delay changes timing. It does not replace review. Record the intended send choice and schedule in the custom work item so the next operator can tell whether communication was requested, deliberately omitted or still awaiting confirmation.
If an integration or browser action times out, do not immediately repeat the rejection and email action. Mark the attempt as uncertain. Check the candidate's current application state and the available communication record before deciding whether another action is needed. The rejection outcome and email outcome can require separate investigation.
This is recommended integration design, not a claim of a universal Greenhouse retry guarantee. Keep a manual reconciliation path for cases the connector cannot verify. An operator should be able to see what was intended, what was attempted and what remains unknown.
Common mistakes to prevent
- Letting a draft imply rejection from the whole company when only one application ended.
- Copying raw interviewer comments into a candidate-facing explanation.
- Assuming a one-off email edit updates the shared template.
- Sending a bulk template that depends on unavailable application tokens.
- Repeating a timed-out action without checking whether communication already occurred.
How Remqa can help
Remqa builds custom recruiting workflows around your team's decision ownership, ATS records and communication process. A rejection-email project can start with a draft-only queue, a reviewed template library and a clear record of each approved action. Broader recruiting workflow work can connect that queue to the surrounding handoffs.
Bring the templates your recruiters use and a few anonymized edge cases. We can help define what AI should prepare, what a recruiter must confirm and how the team resolves an uncertain outcome before anything is repeated.