Onboarding365 Step Best Practices & FAQ

Maximize the efficiency of your onboarding workflows with these best practices for the Onboarding365 Automation Step. This guide provides actionable tips to ensure smooth automation, along with answers to common questions about functionality, supported automation types, and troubleshooting. Whether you’re configuring the step for the first time or refining existing processes, this resource will help you achieve seamless onboarding for your candidates.

Best Practices

• Use branching logic to validate candidate records before they enter the Onboarding365 step. Ensure all required candidate fields are populated in the ATS, as these determine which onboarding package is sent.
• For clients wanting to notify a distribution list in case of failures, create an internal user with the desired email address and assign it to the notification.
• Schedule onboarding automations to avoid overlapping with other critical workflows.

FAQ

Can we make changes to the Bullhorn Automation Error Notification?

No, this is hard-coded, and the error message displayed is the error message supplied by Onboarding365.

Can I set the Error Notification to send to a Distribution List?

The only way to achieve this is to create an internal Bullhorn user with the distribution list email address you wish to notify. You can then select that User under Notify Specific User.

I have different onboarding packages, how can I make sure Candidates receive the right one?

We recommend using branching logic within your automations to appropriately filter your candidates using Bullhorn ATS data to ensure they are sent the correct notification package.

Can I make changes to my onboarding packages via Bullhorn Automation?

Bullhorn Automation can only be used to initiate and cancel onboarding requests.