Bulk candidate rejection emails
Skill Society Bulk Candidate Rejection lets an authorised Administrator select non-hired applicants after a role closes, review one shared branded message and queue an email for each eligible recipient. Your hiring team chooses who receives it.
Example closed-role workflow
Warehouse Team Member
Candidate-experience context
“Talking to Alex, the AI, was such a unique experience. It felt seamless and surprisingly engaging.”
How bulk candidate rejection works
The current workflow starts only after a role is actually closed. It moves an authorised administrator from a filtered audience to an editable preview and one email workflow per selected candidate.
Candidate rejection stays locked while a role is open or only scheduled to close. Once it is actually closed, Skill Society builds a role-specific list from the latest prequalification record for each application and leaves applications currently marked Hired out.
Final communication begins only when the hiring team has finished the role.
Closed-role checkpoint
Step 01
The rejection workflow becomes available after the role has actually closed.
Search by candidate, email, status, or rejection-workflow state. Filter by the candidate's current stage, select individual rows, or select all visible eligible applicants. Completed and in-progress rows remain visible but cannot be selected again; failed workflows can be retried.
Your team sees exactly who is selected before opening the email review.
Review the role-aware starting draft, then edit its subject, title, message, and footer. The preview uses a selected candidate's name when available plus the account's saved logo, colours, typography, and surfaces. The edited copy is shared by the whole selection.
See the final branded format before any email workflow is queued.
After confirmation, Skill Society queues a durable email workflow for each selected applicant and reports how many workflow triggers were queued, skipped, or failed. Completed and in-progress rejection workflows stay unavailable for re-queueing, while failed workflows remain retryable.
Scale the communication while keeping a separate rejection-workflow state for every selected applicant.
A bulk action, still owned by a person.
Skill Society communicates the decision your hiring team has made. It does not choose who to reject or change the candidate's pipeline status for you.
Outcomes from the wider Skill Society journey
William Buck used Skill Society in its wider graduate and intern screening workflow. This story provides candidate-experience context rather than a measured result for bulk rejection.
Read the William Buck story
Pet Circle let candidates complete interviews around their own schedules in its wider high-volume workflow. This result is not attributed to bulk rejection alone.
Read the Pet Circle story
Wilbur brought greater consistency to technical screening through its wider Skill Society workflow. This result is not attributed to bulk rejection alone.
Read the Wilbur storyClose the loop
These customer outcomes come from broader Skill Society screening and interview workflows. Candidate Rejection gives selected non-hired applicants a clear, branded final communication once a role closes.
Questions, answered
These answers reflect the candidate-rejection workflow currently shipped in Skill Society.
Bulk Candidate Rejection is an Administrator-controlled email workflow for a closed hiring role. Your team selects eligible non-hired applicants, edits a shared branded message and confirms the batch before emails are queued.
Yes. After the role has actually closed, an authorised administrator can filter the non-hired audience, select one or more eligible applicants, review the shared email, and queue one rejection-email workflow per selected candidate.
No. Your hiring team chooses the recipients. Skill Society excludes candidates currently marked Hired and keeps completed or in-progress rows in this rejection workflow from being selected again, but it does not make the rejection decision.
The current workflow adds the selected candidate's name to the greeting when a name is available and uses your saved account branding. You can edit the subject, title, message, and footer for the batch, but you cannot give individual candidates different body copy inside the same bulk send.
Not in the current bulk-rejection page. It starts with a role-aware default draft that an administrator can edit before each send, but it does not yet provide a saved or approval-based template library.
No. Candidate stage and final communication are separate in the current product. This workflow queues the rejection email and tracks whether its workflow is pending, running, completed, or failed; your team manages the candidate's pipeline status separately.
Each prequalification in this feature has its own rejection-workflow identity. Rows with a completed, pending, or running workflow remain visible but cannot be selected again, and eligibility is checked again on the server before new workflows are queued. Failed workflows can be selected for a retry.
The workflow is restricted to authorised account administrators and is treated as a destructive role action. It is available only for a role that has actually closed.
The current workflow sends from Skill Society's no-reply notification address, so it should be treated as a final outbound communication rather than a managed reply inbox.
