Article

How should an MSP triage and route tickets?

Triage every new ticket the same way: a clear title, the right company and contact, a category and a priority based on impact. Then route it in two layers. Write rules for the cases that must always go one way (a VIP client, an escalation contact, a specialist queue), and let a routing engine assign everything else from how your team has assigned similar tickets before, taking skills, schedules, time off and workload into account. Run the engine in test mode first, next to your dispatcher’s own picks, and switch it on when it agrees. Good triage and routing saves minutes on every ticket and keeps the right tech on the right work.

Why does triage and routing matter?

A ticket waiting in a queue costs the client time and costs you response-time goodwill. A ticket that lands on the wrong tech costs twice: once for the tech who reads it and hands it on, once for the tech who starts again. At most MSPs, a dispatcher or a senior tech spends part of every day sorting tickets, and the tickets that come in after hours wait until morning.

Step 1: Triage every ticket the same way

Decide what every ticket must have before it is worked:

  • A clear title. “Help” and “Re: FW: issue” tell nobody anything. Rewrite unclear titles into what is actually wrong.
  • Company and contact. Match the requester to the right client so contracts and history apply.
  • A category or ticket type. It drives reporting, routing and the right workflow.
  • A priority based on impact. “The whole office can’t print” and “one user’s second monitor flickers” are not the same priority, whatever the email says.
  • A short summary. What the user wants, what they’ve tried, and anything the tech needs first.

The MSPs that do this well write the rules down, then automate them, so every ticket gets the same treatment at 3 a.m. as it does at 10 a.m.

Step 2: Write rules for what must always go one way

Rules are deterministic and easy to trust. Use them for:

  • A client with a named primary tech.
  • An escalation contact or a VIP who always goes to a senior tech.
  • Ticket types that belong to a team (projects, security, procurement).
  • Mentions of a specialist system only one or two techs support.

Keep the list short. Every rule is something you maintain, and too many rules recreate the dispatcher’s job in a settings page.

Step 3: Let a routing engine handle the rest

For everything the rules don’t cover, a learned engine can pick the owner the way your best dispatcher would. A good one weighs:

  • Who on your team has solved tickets like this one before.
  • Who has history with this client and this user.
  • Skills, so specialist work goes to the people who can do it.
  • Schedules and time off, so a ticket doesn’t wait for someone who’s out.
  • Current workload, so one tech isn’t buried while others are free.

It should also learn from corrections. When a dispatcher reassigns a ticket in the PSA, the engine should take that as a signal.

Step 4: Test it before it assigns for real

Don’t switch automatic routing on cold. Run it in test mode for a week or two: it makes its pick for every new ticket and shows it next to the owner your team chose, without assigning anything. Look at where it disagrees. Usually it is a missing rule, a skill you didn’t record, or a tech’s schedule that isn’t set. Fix those, then switch it to live.

What does it save?

Take a 10-tech MSP that opens 1,000 tickets a month. If a dispatcher spends two minutes triaging and assigning each one, that is about 33 hours a month, and every misrouted ticket adds a second read. Automating triage and routing gives the dispatcher those hours back and gets tickets to the right tech faster, around the clock. Together with one-screen context and workflows, Toolqit gives back 10 to 15 hours back per tech per week, worth $6,000 to $8,000 or more of billing capacity per tech per month.

How does Toolqit triage and route tickets?

  • Toolqit Triage can rewrite only the unclear titles, fill a blank HaloPSA category from your own category tree, and set priority by impact. Each action is an opt-in (on HaloPSA, scoped to the ticket types and teams you choose), and every change is written as one internal note on the ticket, so techs can see what changed and why. Your own title rules win over the built-in ones.
  • Toolqit Routing learns from how your team has assigned tickets, including corrections made in the PSA, and weighs skills, schedules, time off and workload. Your routing rules always come first, and a rule can send a ticket to a HaloPSA team, with routing picking the owner inside it.
  • Three modes: Off, Test mode (picks shown next to your team’s own assignment) and Live (assigns in Toolqit and in the PSA).
  • Every ticket opens on its Triage tab, with a briefing of what the ticket needs and the actions that fit it.

FAQ

Should I use rules or AI to route tickets?

Both. Rules for the cases that must always go one way, and a learned engine for everything else. In Toolqit, rules always win over the engine.

How do I know automatic routing will get it right?

Run it in test mode first. In Toolqit, test mode shows the engine’s pick next to your team’s own assignment for every new ticket, so you can compare before it assigns anything.

Does AI triage change my tickets?

Only what you turn on. In Toolqit, each Triage action is a separate opt-in, and every change is recorded as an internal note on the ticket.

Which PSAs does Toolqit route tickets for?

Toolqit syncs two ways with ConnectWise PSA, HaloPSA, Autotask and SyncroMSP, and assignments made by Toolqit Routing in live mode are written to the PSA.

Will routing respect who is on call or on holiday?

Yes. Toolqit Routing takes schedules and time off into account, and you can switch a tech out of routing entirely.

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.