How Thinc Forward Transformed Help Desk Operations with MSPbots AI Triage and NextTicket

The Challenge: Growing Lean Without Losing Control

Thinc Forward runs a tight help desk. For a team built on efficiency, that's a point of pride — but it comes with a real operational risk. The leaner the team, the more each technician works independently, and the harder it becomes for leadership to maintain visibility into how tickets are being handled.

‍

As the team grew, that tension grew with it. Managers couldn't easily tell whether high-priority work was being picked up first, or whether medium-severity tickets were quietly aging into crises. ConnectWise offered data, but surfacing the right insight at the right moment required too much manual effort.

‍

Jim Slayton, who leads the implementation effort at Thinc Forward, put it plainly:

"There's a lot more reliance on individual techs to do things without oversight. As we grow, that becomes harder and harder to keep a handle on."

The team could see what tickets someone had taken. What they couldn't easily see was whether a higher-priority ticket had been sitting there, waiting, while something less urgent got attention first.

‍

‍

The Turning Point: Triage Unlocks the Queue

The decision to adopt MSPbots wasn't just about dashboards. Thinc Forward had previously used BrightGauge for reporting, but found it limiting — inflexible filtering, rigid widget structures, and no ability to act on the data it surfaced.

‍

What drew Jim deeper into MSPbots was something different entirely: the platform's ability to not just show data, but do something about it.

"There are a lot of reporting tools. There are definitely not as many that you can set up to take action on your behalf. Getting more into the automation side of MSPbots has been really great."

‍

But before automation could work, the data feeding it had to be reliable. That's where AI Triage became the foundation.

‍

Then, NextTicket — MSPbots' intelligent ticket dispatch system — assigns tickets to technicians based on priority scoring. But that scoring only works if tickets are correctly categorized. AI Triage handles that automatically, reading incoming tickets and applying the right classifications before they ever reach the queue.

"The AI triage is what really enables NextTicket to work."

‍

With triage in place, NextTicket could do its job: surface the right ticket to the right technician at the right moment, every time.

‍

‍

What Changed on the Floor

The impact showed up in two ways: what technicians stopped doing, and what the data started showing.

‍

For technicians, the change was a single addition to their workflow — opening a Teams chat and typing a letter to request their next ticket. That's it. No scanning the queue. No second-guessing whether a colleague was already working a ticket. No cognitive overhead.

"All I've had to ask of the techs that we weren't asking them to do before is go to a Teams chat and type in NT. And that's it."

What they gained in return was time — and focus. Instead of spending minutes per ticket deciding what to work on, they could direct that energy toward solving problems. The bot handled the queue logic so they didn't have to.

‍

‍

For escalations, Jim took it further. Client-escalated tickets automatically receive a massive priority score, vaulting them to the top of every queue instantly.

"We have a Teams chat for client escalations. But if somebody isn't paying attention to that chat, they're going to get the escalation anyway. If there is an escalation, NextTicket is giving that to the next person who uses it. There's no opportunity for a client escalation to sit untouched."

‍

‍

For managers, the change freed them from being the enforcement mechanism. When a technician isn't following process, the bot sends the reminder — not a person.

"It's okay for a tech to get frustrated at the bot. The bot can be the bad cop. The manager becomes the good cop."

This matters more than it might seem. Repeatedly flagging the same behavior to the same person is draining and creates friction. Delegating that to automation keeps the manager relationship constructive while the process still gets enforced.

‍

‍

Early Results

Thinc Forward is still in the measurement phase, but one metric already stands out: ticket response time dropped meaningfully between March and April — during a period when ticket volume held relatively steady.

‍

Jim attributes this directly to NextTicket's effect on queue behavior:

"Most of the time what happens is the high urgency stuff gets closed out pretty quickly and the medium stuff sits forever. With NextTicket, those tickets don't get as old. You don't have as many two-week-old tickets killing the average."

‍

Beyond response time, the maintenance burden on managers dropped. Thinc Forward's help desk manager used to manually maintain custom ConnectWise views for each technician — and update every single one whenever a new client was added. With NextTicket, rules are centralized. Adding a client, or assigning a tech to prioritize a specific client, takes a few clicks rather than a cascade of updates.

‍

‍

Looking Ahead

Jim sees MSPbots less as a tool and more as an operating system for the business:

"The better your data, the better you can act on it. The more consistent your actions, the better the data is going to be. It's a flywheel."

‍

And on whether he'd recommend it to another MSP?

"I would absolutely recommend it. It saves everyone time. The only thing I've had to ask techs to do differently is type one letter. And in exchange, it removes a lot of clicking around, a lot of looking at things — and there's no excuse for a client escalation to sit untouched."

‍