Zendesk’s ticket management system is flexible enough to be quite useful when taking care of the many tasks associated with onboarding new hires. Whether new equipment needs to be ordered, network permissions created, workspace arranged, or compliance documents signed, Zendesk helps get it done with minimum effort.
However, there are many redundant tasks that must be done to get each new employee started, and these tasks quickly become burdensome even for Zendesk during group hires.
----------------------------------------
For our take on onboarding best practices, check out our article …
----------------------------------------
That’s where Myndbend Process Manager can make the process much more efficient. It can:
- make approvals and multiple sign-offs easy
- handle repetitive tasks in bulk
- note progress through the onboarding process
- track compliance
- manage forms and whether they’re signed
To see an example of how Myndbend Process Manager can be used to simplify and automate the onboarding process, read on to see our checklist / comparison grid.
Onboarding Checklist and Myndbend Process Manager Comparison Grid
The onboarding checklist in the left column below was originally published as a downloadable Word document available on the MIT New Employee Orientation & Onboarding website. Some changes have been made to make the checklist applicable to a broader audience.
NOTE: Although the list is designed to be used for the onboarding of one employee, it is just as useful (if not more) when bringing on many employees at once.
Before Employee Start Date Outcomes: This is a welcoming work environment with informed colleagues and a fully-equipped work space; new employees feel “settled in” on their first day. |
How Myndbend Process Manager can help with onboarding tasks and approvals* |
|
A Zendesk form would collect “New Hire” requests with custom fields including “New Hire Name, New Hire Email, and New Hire Phone.” The tickets would automatically be assigned to the HR group and necessary approvers added using a Myndbend trigger. For illustration purposes, we’ll call this ticket #1. |
|
Once approvals of the hiring request are received, the HR manager in charge of making the offer can contact the candidate and update a field called “Offer Status” to “Extended” on Ticket #1. |
|
Once the offer is accepted, the HR manager will update the “Offer Status” field to “Accepted.” This field will place a tag on the ticket “offer_accepted” which can be used to trigger a Child Ticket (ticket #1 is the parent, let's call this #1A), which will include the offer request text and be assigned to a designated HR agent, who can mark the child ticket as solved. Myndbend app will can automatically copy the patent tickets custom fields to children tickets. This will allow child tickets to use field data, such as New Hire’s name, in the ticket description. This step may also require the addition of approvers for the written offer. The assignee and approvers can be preselected in the Myndbend child ticket template. |
|
Child Ticket #1B can be automatically generated, once the offer ticket (#1A) is solved, to task HR agent with sending an email to the employee with the necessary start information, including assignment of an onboarding buddy. Myndbend calls this “sequencing,” where one child ticket is solved or approved first, then additional tickets are spawned. |
|
Child Ticket #1C can be automatically generated once ticket #1B is solved. This ticket will be assigned to the HR agent, who will send an email updating all necessary parties, including the new employee as appropriate. Once complete, this ticket can be solved. |
|
A batch of child tickets (using a template set) can be automatically generated once the offer ticket (#1A) is solved to request standard equipment based on department and role, with bulk child tickets for each individual requirement such as network permissions, and automatically require approvals from the manager of the department and IT manager. It should also require the department manager to close relevant child tickets once the employee actually receives the equipment or access. |
|
A new facilities child ticket can be automatically generated once the department notification ticket (#1C) is approved to request an allotment of workspace, including approvals from the manager of the department and Facilities manager. |
|
Child Ticket #1D can be automatically generated once the offer ticket (#1B) is solved to send an email to the department manager to remind them to create the calendar, and they can solve the ticket when complete. A new ticket (#1E) can be generated by HR for orientation and required trainings, with child tickets for each individual training requirement. Ticket can be assigned to approvers and employee. |
|
Child Ticket #1F can be automatically generated once the offer ticket (#1A) is solved to remind the HR assignee to create the welcome packet and assign an onboarding buddy if relevant. An electronic welcome packet can be created within Zendesk Help Center. |
|
A new ticket (#1G) can be automatically generated once Child Ticket #1B is solved to send a reminder email the day before, assigned to the employee's point of contact, onboarding buddy, and the HR representative who will be processing the employee's arrival. The ticket text can include a checklist similar to the following section for First Day. |
|
Child Ticket #1H can be automatically generated once the offer ticket is solved to send an email to the senior executive's assistant requesting an appointment or reminder be added to their calendar. The ticket can contain the text from the offer ticket, providing essential info about the new employee. Once all child tickets have been approved and solved, the main on-boarding request (parent ticket) can be solved. |
First Day Outcomes: The employee feels welcomed and prepared to start working; begins to understand the position and performance expectations |
|
|
Ticket #2 can be created and assigned to the designated HR representative as a reminder to create the welcome message or send out welcome announcement to the company via email. Child tickets can be created for each of the first day tasks. |
|
Child Ticket #2a can be closed by the employee's point of contact. |
|
Child Ticket #2b can be created and assigned to the direct supervisor. This ticket can be solved once the direct supervisor completes the first day tasks. |
|
Direct supervisor can open new requests as needed if any assistance from IT in getting connected to and using office technologies. |
|
Child Ticket #2c can be assigned to supervisor and solved once this has been done. |
|
Child Ticket #2d can be assigned to HR representative and solved once the employee receives this information. |
|
Child Ticket #2e can be assigned to Supervisor, HR representative or onboarding buddy and solved once the employee receives the tour. |
|
Child Ticket #2f can be assigned to Supervisor and solved once the employee is taken to lunch with team. |
|
Child Ticket #2g can be assigned to the Supervisor and solved once the employee completes HR forms. A Zendesk form can be used to capture the employee's acknowledgement of receipt of this information, as well as a checklist for the employee's HR contact to make sure everything is gone over. An electronic version of the employee handbook could be available through Zendesk Help Center. |
|
Child Ticket #2h can be assigned to supervisor to review schedule and solved by the supervisor when complete. |
First Week Outcomes: New employee builds knowledge of internal processes and performance expectations; feels settled into the new work environment. |
|
|
Ticket #3 (and its child tickets) can be used to track employees progress / as a checklist. Assignees can close these tickets once it has been confirmed that each training is complete. |
|
A Zendesk form can be used to capture the employee's acknowledgement of receipt of this information, as well as a checklist for the employee's supervisor to make sure everything is gone over. Zendesk Help Center can be used to present this information. |
First Month Outcomes: Employee is cognizant of his/her performance relative to the position and expectations; continues to develop, learn about the organization, and build relationships. |
|
|
|
|
|
|
Child Ticket #3a will be assigned to supervisor, and reminder automatically sent (see Myndbend Ticket Reminder app) to the direct supervisor a week before the employee's one month anniversary to remind them to schedule the check in. The supervisor can close this ticket once complete. |
|
Child Ticket #3b will be assigned to the HR representative and reminder automatically sent (see Myndbend Ticket Reminder app) to the HR representative, onboarding buddy and employee a week before the employee's one month anniversary to remind them to schedule the meeting. The HR representative can close this ticket once complete. |
90 Days Outcomes: Employee is becoming fully aware of his/her role and responsibilities, beginning to work independently and produce meaningful work. He/she continues to feel acclimated to the environment, both functionally and socially. |
|
|
Ticket #4 (and its child tickets) can be used to track employees progress / as a checklist. Assignees can close these tickets once it has been confirmed that each training is complete. Child Ticket #4a will be assigned to supervisor, and reminder automatically sent (see Myndbend Ticket Reminder app) to the direct supervisor a week before the employee's three month anniversary to remind them to schedule the check in. The supervisor can close this ticket once complete. |
|
Child Ticket #4b will be assigned to the HR representative and reminder automatically sent (see Myndbend Ticket Reminder app) to the HR representative and direct supervisor a week before the employee's 90-day anniversary to remind them to schedule and prepare for the benefits meeting. |
Six Months Outcomes: Employee has gained momentum in producing deliverables, has begun to take the lead on some initiatives, and has built some relationships with peers as go-to partners. Employee feels confident and is engaged in new role while continuing to learn. |
|
|
Ticket #5 (and its child tickets) can be used to track employees progress / as a checklist. Assignees can close these tickets once it has been confirmed that each training is complete. Child Ticket #5a will be assigned to supervisor, and reminder automatically sent (see Myndbend Ticket Reminder app) to the direct supervisor a week before the employee's six month anniversary to remind them to schedule the check in. The supervisor can close this ticket once complete. |
End of First Year Outcomes: Employee is fully engaged in new role – applies skills and knowledge, makes sound decisions, contributes to team goals, understands how his/her assignments affect others in the organization, and develops effective working relationships. He/she has a strong understanding of the organization's mission and culture. Employee continues to be engaged in his/her role and has gained greater confidence in position; begins to take on additional assignments and works with some level of autonomy. |
|
Supervisor conducts annual review process, and checks in with them about:
|
Ticket #5 will be created by HR and assigned to the supervisor. A reminder will be automatically sent (see Myndbend Ticket Reminder app) to the direct supervisor a week before the employee's one year anniversary to remind them to schedule and prepare for the annual review. The HR representative can be added as an approver. The supervisor can close this ticket once the review is complete and HR approves. |
* Please note that the following functions are only available in the premium version of Myndbend Process Manager: automatic creation of tickets via trigger, automatically add approvers, templates for HR onboarding common tasks, sequencing child tickets.
----------------------------------------
For our take on onboarding best practices, check out our article …
----------------------------------------
Did we think of it all? If you include other steps in your onboarding process that you think should be included, let us know! Leave a comment below...