L1 automation
November 17, 2026

Where to start automating Level 1 tickets in your PSA

Kelly Benton's headshot for the Fixify blog
Kelly Benton
MSP operator turning gears to automate l1 tickets in their PSA

MSP technicians open the queue each morning and find the tickets they closed yesterday: a locked account, an MFA prompt on a replacement phone, a new starter who needs Microsoft 365 by Monday. The fix is routine. Someone still clicks through it by hand, one ticket and one client at a time.

Your PSA routes and triages, but stops before the reset, so the ticket still lands on a technician. Often it’s a senior one, who remembers which client wants a callback before any MFA change. A well-routed password reset is still a password reset; it arrives with better posture.

An MSP automates its PSA by configuring each job as a trigger, condition and action: a new ticket mentioning a lockout moves to the identity board with an owner; an SLA timer past its threshold raises priority and notifies the on-call tech; a failed monitor opens a ticket for that client; time entries post to recurring agreement invoices that sync to QuickBooks or Xero; client reports send on schedule.

What does it mean to automate PSA software?

Automating PSA software covers two different layers of ticket work, and most MSPs have built only the first.

Routing rules: A trigger, a condition and an action, all native to your PSA. A ticket arrives, matches a client and keyword, and moves to a board with a status and an owner.

Resolution automation: Work that finishes the ticket. It reads the request, checks the account, makes the change, writes the note and closes the ticket, or hands it off with context.

Beyond ticket work, PSA automation also includes scheduled and cross-system work: RMM alerts that open tickets, billing and QuickBooks or Xero sync, and scheduled client reports. These run on a timer or a system event rather than a ticket rule, and they move data between systems rather than resolve a request.

Think of routing rules as the mailroom sorter. Mail reaches the right desk quickly, but the envelope stays sealed. Resolution automation is the person at that desk who opens the envelope and does what the letter asks. Most PSA rule engines are very good sorters.

Which ticket types should MSPs automate first?

Start with the repetitive Level 1 tickets your team resolves the same way every time. Password and MFA resets, account lockouts, app access requests, onboarding and offboarding usually lead the list.

Your PSA export shows where they sit: sort by summary keywords and category, then count how often each pattern appears per client. That count usually starts with the password reset tickets that clog the MSP queue.

Rank ticket types by volume, repeatability and risk

Score each candidate ticket type on three questions:

  • How often does it arrive across all clients?
  • Are the steps written down, or do they live in one person’s head?
  • What breaks, and for whom, if the automation gets it wrong?

Risk, the third question, carries the most weight. A misfiled printer ticket costs a few minutes, while a bad MFA reset can hand someone an account. The CISA and FBI advisory on Scattered Spider describes attackers calling help desks to convince staff to reset passwords and transfer MFA to devices the attackers control. Rank high-volume, low-risk tickets first, and keep identity changes behind a verification step, no matter who performs them.

Start with read actions before write actions

Read actions look things up without changing anything: whether the account is locked, which licenses the user holds, when the password last changed, which groups they belong to. They speed up every ticket and can’t damage a tenant. Add write actions such as unlocks, resets and group changes per ticket type once the read results have matched what your technicians would have found, ticket after ticket. Promotion should be earned one ticket type at a time.

How automation reads and writes tickets in your PSA

Categorizing, dispatching and updating status can run as routing rules in your PSA. Writing notes and resolving the ticket need resolution automation.

Step 1: Categorize the ticket on intake

Automation reads the summary and description, then sets the type, subtype and client. A ticket titled “can’t get into Outlook, says account locked” becomes Identity and Access, Account Lockout, for the correct client. The categories have to stay consistent, because every later rule matches on them. When half the lockouts are filed under “Email” and half under “Login,” dispatch rules fire unevenly and your reports describe a help desk that doesn’t exist.

Step 2: Dispatch to the right board and technician

Dispatch is where trigger, condition and action earn their keep. A typical rule in your PSA looks like this: the trigger is a new ticket, the condition is category equals Account Lockout and the client has an approved unlock playbook, and the action is to assign the ticket to the automation queue and set status to In Progress. Tickets that fail the condition go to the Level 1 board with the category already set, so the L1 tech doesn’t re-read the ticket from scratch.

Step 3: Update status and SLA timers

Status changes should follow what is happening on the ticket. When automation is waiting on the end user, the status says so and the SLA clock pauses where your contract allows. Escalation rules then watch time against severity. One rule configures this directly: the trigger is an SLA timer crossing a threshold, the condition is the ticket still open at a given severity, and the action is to raise the priority, move it to the escalation board and notify the on-call tech.

A ticket where the whole business is down escalates within minutes, a ticket where one user is blocked with no workaround escalates sooner than a routine request, and an aging routine request triggers a reminder before it breaches.

Step 4: Write notes and time entries

A good automated note matches what your best technician would write, covering three things:

  • What was checked, such as the lockout state, last sign-in and MFA methods on file
  • What was done, such as an account unlock or session revocation
  • What the end user was told, and through which channel

Diagnostic detail goes in the internal note, and the client-facing note stays short and readable. Every automated action also needs a time entry against the correct client, plus an audit history that shows who or what made each change. Across forty tenants, that history is how you answer “who touched this account?” in one search.

Step 5: Resolve, close or escalate with full context

When the playbook completes, automation writes the resolution note and closes the ticket, or sets it to resolved and waits for the end user to confirm. When it cannot finish, it hands the ticket to Level 2 with the steps already tried, the results of each check and the exact point of failure. With that context, L2 can pick up where the automation stopped rather than start the investigation over.

Where do PSA workflow rules stop?

PSA workflow rules route, triage, notify and escalate well, but they don’t reach into Microsoft Entra ID to unlock an account or provision a user. Closing that gap means building resolution yourself with scripts, API calls or a workflow platform. You can build it, and many MSPs have. The upkeep is the part that rarely makes the project plan: each client has its own approval quirks, a Microsoft or PSA update moves a field, and someone has to fix the workflow that broke last Tuesday. A workflow tool at this level can need someone close to full time writing and maintaining the automations. Whether to build, buy or hand off that work is its own operating decision, so weigh it before you commit an engineer to it.

Fixify is the automation-native option in this space. It delivers managed automation that resolves Level 1 tickets inside your PSA, with Fixify-employed IT analysts reviewing and approving automation plans before they execute and handling the judgment calls. Fixify works live with ConnectWise PSA, HaloPSA and NinjaOne PSA, and the list of integrations is expanding.

How do you know PSA automation is saving technician time?

PSA automation saves technician time when your baseline numbers improve, not just because the automation is busy. Pull a baseline before rollout, then track these measures per client and per ticket type:

  • Time from ticket creation to dispatch
  • SLA breaches by severity
  • Reopen rate on automated closes
  • Escalations from Level 1 to Level 2
  • Cost per completed ticket
  • Reclaimed technician capacity, in Level 1 hours per client per month

Cost per ticket carries the economic case. MetricNet’s 2026 white paper puts a fully loaded Level 1 ticket in North America at about $20, against roughly $70 at desktop support. When your team escalates a reset because nobody had time for it, you pay for resolution in the more expensive column.

Automation rate belongs on the operating dashboard, and it proves nothing about improvement by itself. A CIO column describes a vendor whose resolution rate looked strong until the author checked reopen numbers: “Auto-closed tickets had been counted as wins.” Measure reopens, escalations and cost next to automation rate, or you are measuring activity.

Fixify’s 2026 IT Help Desk Benchmark Report, covering 50,000+ tickets across 30+ organizations from January 2025 through February 2026, found a median resolution time of 4.4 hours for AI-automated tickets against 71 hours without automation.

That result comes from one vendor’s dataset and doesn’t predict your own outcome; it does show resolution time as the measure to watch.

When the numbers go the wrong way, look at the process first. When you configure conflicting rules on the same ticket, they can overwrite each other’s status changes. RMM alerts with no deduplication flood a board with copies of one outage. Automated notes in three different formats make ticket history unreadable.

Each of these is a design fault in the rules, and your technicians are usually the first to spot them.

Where to start with your own ticket data

Pick two or three ticket types, such as password and MFA resets, lockouts, or onboarding and offboarding, and write one rule for them. Run it in read-only mode against live tickets for a few weeks, compare its results with your technicians’ work, and only then let it make changes.

To find which ticket types repeat most in your own queue, use the IT Help Desk Ticket Snapshot: upload 90 days of CSV ticket data and receive a customized benchmarking report in 48 hours that shows the repetitive ticket types in your PSA export.

FAQ

Related articles

Stay in the loop

Sign up to get notified about our latest news and blogs