Article

How do I automate employee onboarding for my MSP’s clients?

Give each client a request form, so every new-hire ticket arrives with the same details. Then turn your onboarding checklist into one workflow: check the address, create the Microsoft 365 account, assign the license, add the groups and shared mailboxes, create a Temporary Access Pass, note it on the ticket and reply to the requester. A tech reviews the run and approves it from the ticket. In Toolqit, setting up a new employee goes from about 25 minutes to about 90 seconds of tech time. Start with onboarding and offboarding, because they are the requests every client sends and every tech does slightly differently.

Why start with onboarding?

New-hire and leaver requests are repetitive, predictable and full of small steps that are easy to miss. One forgotten distribution group means a second ticket next week. A license assigned to the wrong plan shows up on the next invoice. Because the steps are the same for every user at a client, onboarding is the safest first workflow and the easiest to measure: count the tickets, multiply by the minutes.

Step 1: Get the request right

Most onboarding time is lost before the work starts. The email says “Sarah starts Monday,” and a tech spends ten minutes asking for the title, department, manager, license and start date.

Fix that with a request form per client. Ask for:

  • Name, preferred display name and start date.
  • Job title, department and manager.
  • License or plan (offer only the plans this client buys).
  • Groups, Teams and shared mailboxes, picked from the client’s own list.
  • Anything this client always needs, like a phone number or a desk location.

In Toolqit, each form-first workflow gets its own link. The client’s staff sign in with their Microsoft account, so Toolqit knows which company the request is for, and submitting the form opens a ticket with the workflow ready to run.

Step 2: Write the checklist as a workflow

Take the checklist your best tech follows and write it as ordered steps. A typical Microsoft 365 onboarding looks like this:

  1. Check that the new email address is free.
  2. Make sure the client has a spare license, and add a seat in Pax8 if it doesn’t.
  3. Create the Microsoft 365 account with the new hire’s name and address.
  4. Assign the license.
  5. Add the standard groups and Teams for the department.
  6. Grant access to the shared mailboxes.
  7. Create a Temporary Access Pass for the first sign-in.
  8. Write an internal note with what was done and how to hand over the pass.
  9. Reply to the requester and resolve the ticket.

Add a condition where clients differ (“if the department is Finance, add the Finance group”), and an approval step for anything you want a person to confirm first. In Toolqit, building it is magic made by your voice: describe the job in your own words and Toolqit Build lays out the steps in the Workflow Studio, or start from a Suggested Workflow built from tickets your team already solved.

Step 3: Test it before it touches a client

Run the workflow in a test run first. In Toolqit, a test run executes the Microsoft 365 steps against a made-up sandbox tenant and simulates the other writes, so you can see every step’s result without creating a real account. Fix what looks wrong, then run it on one real ticket with the tech watching.

Step 4: Do offboarding the same way

Offboarding is the mirror image, and it carries more risk, so it is worth the same care:

  1. Confirm the request is signed off by someone at the client who can approve it.
  2. Sign the user out everywhere and disable the account.
  3. Convert the mailbox to shared and give the manager access.
  4. Forward new mail and set an automatic reply.
  5. Remove the user from every group and free the license, reducing the Pax8 seat if you use Pax8.
  6. Note what was done and confirm to the requester.

What does it save?

Take a 10-tech MSP that handles 60 onboarding and offboarding tickets a month at about 25 minutes each. That is 25 hours of tech time. At 90 seconds of review per run, it falls to about 1.5 hours. The bigger win is the second ticket that never gets opened because a group or mailbox was missed.

Onboarding is one workflow. The same approach covers password and MFA resets, mailbox access, license changes and lockouts. Together, they are a big part of the 10 to 15 hours per tech per week that Toolqit gives back, worth $6,000 to $8,000 or more of billing capacity per tech per month.

FAQ

Can I automate onboarding without a separate automation platform?

Yes. In Toolqit, onboarding and offboarding run as workflows from the ticket, so you don’t need a separate tool or an automation engineer.

Do clients need a portal?

No. Each client gets a link to the form. Their staff sign in with Microsoft, and the submission opens a ticket.

Does a tech still review the onboarding?

Yes. A form submission opens a ticket with the workflow ready, and a tech approves the run from the ticket. You can add approval steps inside the workflow too.

Does it work for clients with different setups?

Yes. Use conditions for differences between departments or clients, or keep one workflow per client where their setups differ a lot.

Which PSAs does it work with?

Toolqit syncs two ways with ConnectWise PSA, HaloPSA, Autotask and SyncroMSP, so the ticket, notes and time entry land in your PSA.

About Toolqit

Toolqit is the AI-native platform where managed service provider (MSP) technicians can do all their work. It sits on top of an MSP’s PSA, RMM and Microsoft 365, syncs two ways with ConnectWise PSA, HaloPSA, Autotask and SyncroMSP, and gives technicians and operators one screen for triage, workflows, documentation, remote sessions and profitability. Toolqit, Inc. is based in San Francisco.

Give your technicians their day back.

In a friendly 30-min call, we will transform what you thought a productive MSP looked like.

Book a demo

See Toolqit on tickets like yours.