You can add additional conditions to your workflow to send separate decline notifications based on the decline reason. Recruiters manually select a decline reason when they decline a candidate in Recruiting > Job Requisitions, in the Candidates tab.
Before You Begin: Adding condition nodes for decline reason is optional. If you choose not to include them, the workflow sends a notification for all decline reasons by default.
A decline reason can also be assigned to candidates who are auto-declined based on their job application. You can define the decline reason for job applications in the Recruiting Setup > Job Application Configuration > Question Configuration, in the Answer Configuration section.
For example, if an organization requires a separate notification to go out to candidates who are unable to work in the United States without sponsorship (based on the candidate’s response to a custom question in the online job application template) the workflow would look as shown in the following example. Here, the condition node checks for candidates who were declined for the reason "Unable to Work in US." If it finds that this decline reason occurred, the true response leads to nodes that result in a notification for that decline reason. If the candidate was declined for any other reason, the false response leads to nodes that result in generic decline notification:
Note:
- You should always add this condition node after the condition node that checks for candidate status (which was described earlier in the document). After the condition node that checks for candidate status determines that the “Declined” status occurred, the node for decline reason can be used to create separate notifications.
- While you should always add this condition node after the condition node that checks for candidate status, you can use it before or after other condition nodes, such as the one that checks for automatic and manual status updates.
- You can use more than one condition node for decline reason in your workflow.