Customizing Rejection Reasons

Created by Sai Prashanth, Modified on Tue, 17 Sep at 8:51 AM by Erin Estabaya

As your organization's talent acquisition strategy evolves, so will the reasons for rejecting candidates. Tracking and analyzing why candidates are rejected is critical for assessing your recruiting process and identifying potential bottlenecks. Kula enables you to fully customize your rejection reasons, offering insight into patterns that may affect your hiring decisions.

Adding Rejection Reasons

  1. Click the Settings icon at the bottom of the left-side menu.

  2. Under the Jobs & Applications section, select Rejection Reasons.

  3. You will see three default categories:

    • We rejected them
    • They rejected us
    • Others


(Note: These categories cannot be deleted, but you can add, edit, enable/disable, or delete custom reasons within them.)


  1. To add a rejection reason, click Add Rejection Reason under the relevant category.
  2. Enter the reason in the Reason field based on your organization's criteria.

  3. Click Add to save the new rejection reason. It will be enabled by default on the Rejection Reasons homepage.


Editing Rejection Reasons
  1. Hover over the rejection reason on the Rejection Reasons homepage and click the Edit icon.
  2. Update the name as needed.
  3. Click Save to apply the changes.

Moving Rejection Reasons
  1. Hover over the rejection reason and click the Move icon.

  1. Select the new category to which you want to reassign the reason.


(Note: The rejection reason will retain its enabled or disabled status in the new category.)


Deleting Rejection Reasons
  1. Hover over the rejection reason and click the Delete icon.
  2. Type DELETE when prompted.
  3. Click Delete to confirm and remove the rejection reason.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article