Neglected tickets at MSPs: the causes, the cost, and thresholds that catch them

Every MSP has to make sure service and project tickets get started, worked and finished in a reasonable time. Some do it well. Many carry a pile of neglected tickets: tickets with no recent activity even though nothing is blocking them.

This post covers the three problems behind neglected work, what it costs, and how to set thresholds so you can see it and deal with it.

What causes neglected tickets

1. Nobody can see which tickets are neglected

You can’t move a ticket forward if you don’t know it has stalled. PSAs such as ConnectWise and Autotask make it hard to tell which tickets have recent activity and which don’t, so neglected ones sit among the rest.

2. There is no process for dealing with them

Even with visibility, neglected work stays put unless someone owns it. An MSP needs two habits:

1. Technicians check their own neglected work first. For example, first thing every morning, before starting anything new.
2. The service manager reviews the rest on a schedule. That covers tickets nobody owns and tickets the assigned tech missed. The manager can assign the ticket, reassign it, or agree a plan with the tech.

3. The team has too much work in progress

Too much work in progress is the root cause, and it defeats teams that have the visibility and the process. Picture a team where each tech has one or two tickets in progress and finishes a ticket before starting the next. Tickets don’t go stale there, because the load is always manageable. Now picture a team where each tech has fifteen in progress. Nobody can juggle fifteen tickets, so some go untouched for days.

Two practices keep work in progress down:

• Let techs pull work instead of pushing it at them. Rather than a dispatcher booking work into time blocks, techs pull the next ticket from a prioritized queue when they are ready. Pull vs. push covers why.
• Finish before starting. Set a maximum number of tickets in progress per tech and make each tech’s current count visible. WIP limits explains how to choose the number.

What neglected tickets cost

Wasted time. With many tickets open, techs spend time choosing what to work on and rereading tickets to remember where they left off. The longer a ticket sat, the longer that takes. Service managers spend longer reviewing, dispatchers redo calendars, and team meetings run long.

Slower billing. Time logged on a ticket that then stalls waits a long time to be billed, like a growing accounts receivable balance. Bill it before the work is finished and the client is more likely to question the charge. A ticket started, finished and billed quickly brings in the revenue and gets paid without argument.

Stressed techs. A long queue means more decisions all day about which ticket to resume, and a constant worry that a client will ask for an update and turn an old ticket into an emergency.

A less responsive team. The more work in progress, the longer new work waits to start, and the more often techs are interrupted by old tickets that suddenly turn urgent.

Unhappy clients. This is the worst cost. When tickets take a long time, clients wonder whether asking for help is worth it. When they have to chase for status, they start thinking about other providers.

Thresholds: when does a ticket count as neglected

Start by deciding how long a ticket can sit without activity before it counts as neglected. One number won’t work, because some statuses are expected to wait longer than others. TopLeft recommends these thresholds for service tickets:

Status	Neglected after
New	2 hours
Ready	2 days
In Progress	2 days
Waiting on Customer	7 days
Waiting on Vendor	7 days
Scheduled	14 days
Completed and Closed	not applicable

A ticket can wait a week for a client to reply, but a ticket In Progress should see activity every two days, and nothing should sit in New for more than two hours without being triaged.

If you are just starting, use longer thresholds at first so the team works on the oldest tickets without being swamped, then tighten them over a few weeks.

Making neglected work visible

Once the thresholds are set, the team needs a list of tickets that break them, checked every day. The free No More Neglect guide shows step by step how to build that report in ConnectWise and Autotask, how to track the count over time, and who should check it and how often.

A Kanban board makes the same tickets hard to miss. TopLeft boards sit on top of ConnectWise, Autotask and HaloPSA and flag neglected tickets on the card. When KaufmanIT first saw their tickets that way, the team closed almost 300 old or finished tickets out of 450 in a week. Their CEO, Matthew Kaufman, put it this way: “It’s weird that this is the exact same data in a new visual form, but suddenly everybody knows which tickets should have been closed when they didn’t just with ConnectWise Manage.”

To see a board like that running on your PSA, book a demo.