L1 automation
November 12, 2026

Getting technicians to adopt automation: A plan that sticks

Kelly Benton's headshot for the Fixify blog
Kelly Benton
MSP technician adopting automation

MSPs roll out an automation, announce it at the Monday meeting, and a month later technicians are still resetting passwords by hand. The workflow passes every test. In the live queue, people go around it, the way office staff wear a dirt path across the lawn when the paved walkway takes the long way to the door.

That dirt path shows up in your margin. An automation nobody runs never pays back the hours that went into building it. The savings in the plan never reach cost per ticket, and the help desk margin you promised the board stays flat.

When adoption stalls, the usual next move is to decide the team resisted change. More often, technicians route around automation because the old way is still faster or the new way is unclear.

An MSP gets its team to adopt automation by treating it as a change-management job that leadership owns, not a tool it installs: involve technicians early, remove the friction that keeps the old way faster, and show a win the whole team can see. Plenty has been written on why MSP automation rollouts stall after the build. Whether your team uses the workflows that do run is a leadership problem.

Step 1: Let technicians choose what gets automated first

Technicians should nominate the first candidates, because they know which requests eat their day and which ones they’d happily never touch again. Give them protected time to do it: a slot in the team meeting, or a short form where each person lists three requests they resolve the same way every time.

Leadership then applies the filter. Rank the nominations by ticket volume and cost per ticket, so the first win is one you can measure and report. Favor requests that are high frequency, repetitive, low risk, and easy to verify once done. Password and MFA resets, account lockouts, and Level 1 onboarding steps usually top the list.

You’ll also hear about the one printer at the dental office that has defeated three technicians. Thank them, write it down, and pick something with volume.

Your first workflow should be the request with the highest volume and the most predictable steps. For most MSPs, that means password resets or lockouts.

Step 2: Build technician trust in automation

Technicians trust automation when leadership explains plainly how their work changes and when they can see who controls the risky actions. Visible sponsorship takes more than a kickoff memo. Prosci’s 2026 research found manager behavior tracks closely with adoption, yet only 35% of organizations adequately prepare managers for their role in change. If the COO never mentions the rollout after kickoff, the team will reasonably conclude it’s optional.

What automation changes about technicians’ work

Leadership should give the talk track directly, in plain words, and repeat it at each phase. Something like this:

  • What leaves your plate: Password and MFA resets, lockouts, routine access requests, and standard onboarding steps for known roles.
  • What stays with you: Judgment calls, harder tickets, anything a client describes in a way that does not fit a pattern, and approval on sensitive changes.
  • How you work with it: You nominate what gets automated, you review what it proposes, and you flag anything it gets wrong.

Then say what is not automated, by name, so nobody discovers the boundary in front of a client. Being vague about scope does more damage than any broken workflow.

What stays under human control

Human control over automation rests on concrete checks, which earn more trust than any slide about responsible AI. Each of these should be in place before a write action runs:

  • Named approver: A named person approves high-impact actions before they run. The OWASP AI Agent Security Cheat Sheet recommends explicit approval for high-impact or irreversible actions and a preview of the action before execution.
  • Read first, write second: Automation starts by reading and proposing, and gets write access later. Microsoft’s agent-ready app checklist states that read-only tools ship first.
  • Graduated approval: Approval levels follow risk. The same OWASP guidance recommends setting autonomy boundaries by action risk level, so a routine reset that has held up for weeks can need less sign-off than a group membership change.
  • Rollback: Every workflow has a documented undo, and technicians can interrupt it, which OWASP also recommends.

When a check is unclear, the action stops and goes to a person. Most PSAs already carry workflow rules and approval steps, so technicians can supervise inside the system of record they already open every morning.

Step 3: Pilot one workflow with technician champions

A pilot works when it has a named group, one or two champions, one workflow, and one visible win before anything expands. Champions should be technicians the team already asks for help, and they should have the technical depth to spot a bad proposal and the standing to say so.

If you run more than one PSA or have acquired companies that never fully merged, pilot inside one client segment or one entity first. Keep the pilot measures identical across entities, so the second rollout compares cleanly with the first.

Training happens in your PSA and RMM, with no tool swap. Automation output should show up as ticket notes, status changes, and approval requests where technicians already work. Teams often spend more time adapting to a new tool than working in it, and a pilot that adds another console earns exactly that complaint.

Technicians nominate, review, and supervise automations. They should not each build and maintain them, because that turns every champion into a part-time developer with a full queue.

The 30, 60 and 90-day plan below is a suggested framework, not a benchmark:

  • Days 1 to 30: Automation runs read-only on the chosen workflow, and champions compare each proposal against what they would have done.
  • Days 31 to 60: Write actions go live with named approval in one segment, and champions show the first resolved tickets at the team meeting.
  • Days 61 to 90: Approval steps that held up move to a lighter level, the team nominates a second workflow, and a second segment or entity joins.

Leadership owns the protected pilot time and the success measures. If the pilot only happens when the queue is quiet, it won’t happen.

Step 4: Measure adoption and cost per ticket, not just output

Cost per completed ticket, resolution time, and automation rate are the three measures to lead with. Automation rate counts activity, not improvement; pair it with cost and service measures. An automation rate can climb all quarter while cost per ticket sits still, which makes for an awkward board meeting.

Resolution time is the place to look for change. In Fixify’s 2026 benchmark report, covering 50,000+ tickets across 30+ organizations from January 2025 through February 2026, Fixify reported a median resolution time of 4.4 hours for automated tickets against 71 hours without automation. Treat that comparison as context when measuring your queue’s results.

Track these alongside the lead three:

  • Escalation volume from Level 1 to Level 2
  • Level 1 hours per end client
  • Automation runs per technician, which shows who is using the workflows

Use the same definitions across every entity. Cost per ticket should be total monthly help desk operating expense divided by completed tickets, and resolution time should be measured in business hours everywhere. Report the set to whoever you answer to, a board or PE sponsor where there is one, and hold a formal review at 90 days.

Name the technicians who nominated and supervised the automations that moved the numbers, in that same review.

Should your team build and maintain every automation itself?

Building and maintaining every automation yourself costs more than the build suggests: building is a one-time cost, but maintenance repeats, and you pay for it in the hours of your most experienced technicians. Every PSA release, Microsoft 365 change, or new client with its own approval rules lands on whoever built the workflow. Those hours carry the fully burdened Level 1 technician cost (or more, since the builder is usually senior), and they come out of the capacity the automation was supposed to free up. What matters is weighing that recurring cost against the cost per ticket, margin, and reclaimed capacity a managed service delivers instead.

If you have someone whose job is owning automations, building in-house can work. If maintenance would fall to whoever has a free afternoon, price the alternative.

Fixify is a managed automation solution for MSPs. Level 1 requests that land in your PSA get worked end to end by Fixify’s automation within the agreed scope, under your brand. When the automation gets stuck or a request requires human judgment, Fixify’s human IT analysts step in 24/7. Fixify writes the result back to your PSA as a technician would record it. L2 and L3 stay with your team. Live PSA integrations are ConnectWise PSA, HaloPSA, Kaseya Autotask, and NinjaOne PSA, and the list is expanding. Pricing is tied to completed tickets.

Start with the tickets that cost your techs the most time

Your next move is to find the repetitive requests that consume the most technician hours, then put those in front of the team as the first nominations. That list gives Step 1 real data instead of a hunch.

Start with the free IT Help Desk Ticket Snapshot: upload 90 days of CSV ticket data and receive a customized benchmarking report in 48 hours, showing where your help desk spends time and where automation opportunities sit.

FAQ

Related articles

Stay in the loop

Sign up to get notified about our latest news and blogs