Two days a week, just to keep tickets in sync

One of our investors, Ryan Spillane, spent years running and advising IT service businesses before he put money into Support Fusion. He knows what a healthy co-managed relationship looks like, and he also knows what an unhealthy one looks like. The one he flagged to us early on wasn't a special case. It was a common case.

An engineer on site two days a week, just to keep tickets in sync.

Two days a week. Copying work between one ticketing system and another. It sounds like it can't be real, and then you count the hours.

What it looks like on the ground

The industry term is swivel chair work, or the swivel tax. It's the hours your team spends turning the chair from one screen to another and rekeying the same ticket twice.

Week one of a new enterprise contract, one of your engineers starts doing it quietly. Customer logs a ticket in ServiceNow. Engineer reads the ServiceNow ticket, opens ConnectWise, creates the same ticket there. Adds the right priority. Copies the description. Finds the customer record. Sets the agreement. Saves. Back to ServiceNow. Marks it in progress on the customer's side.

On a good ticket, that's four minutes. On a ticket with a form, ten fields, and an attachment, it's more.

Multiply by the ticket volume on a mid-sized co-managed relationship and the numbers get uncomfortable fast.

A week on paper

Here's a conservative picture. Mid-sized enterprise client, in-house IT team, MSP covering level two and after-hours. Volume that lands in the MSP's PSA: around 40 tickets a day, or roughly 200 a week.

At four minutes per ticket for the base case, that's 13 hours a week. At eight minutes a ticket, because half of them need comment updates later, it's closer to 20.

Twenty hours is half an FTE. On a loaded cost of sixty US dollars an hour, that's about twelve hundred a week in pure rekeying, or a bit over sixty thousand a year. The contract is probably worth 10 to 30 times that, which is why the pain gets absorbed. But the absorption is real.

This is before we talk about SLA risk.

The quieter cost

The hours are the obvious bit. The quieter cost is the part that bites later.

One of the MSPs we speak to has a story most of you will recognise. Their custom workaround sits in a generic automation tool and routes tickets via email to stitch two systems together. It mostly works. It's held together by one person, who built it and knows how to fix it when an API changes.

When that person is on leave, the service delivery manager has a bad week. When that person moves on, the organisation has a bad quarter.

Every MSP at some scale has a flow like this somewhere. The risk isn't that the tool breaks. It's that the knowledge lives in one head.

What it looks like when tickets flow

The alternative isn't a dashboard or a single pane of glass. It's the ticket just landing.

A customer logs a P1 in ServiceNow at 2:14am. Seconds later it lands in ConnectWise with priority intact, the customer agreement linked, the description and attachments in place, and the on-call engineer's queue set. The engineer picks it up, starts the clock, works it, closes it with a resolution note. The customer sees the corresponding resolution back in their ServiceNow at 3:31am - all before they're up.

No one rekeyed anything. No one's asleep in the wrong time zone. No one forgets to update the other side.

That's what keeping tickets flowing both ways is actually meant to look like.

The test that shows up the cost

A practical test, if you want to see whether you're paying the tax.

Ask your service delivery manager how many of your contracts have an engineer on them who could tell you, without checking, how many tickets went through to the customer system yesterday. Then ask how many of them would bet their bonus on the number being right.

If the answer is few, the tax is real and it isn't being reported. That's usually the bigger concern than the hours themselves.

What to do about it

If you've got one co-managed contract where this is already the story, the fix is smaller than most teams expect. A standard sync between a PSA and an ITSM stands up in about twelve minutes once both sides are ready to connect. It runs in the background, we monitor it, and it doesn't need an engineer to keep it alive.

If you want to see what it looks like on your specific stack, check your platform pairing first, then book a demo and we'll walk through it with you.