Most of this job is not a fire. It is Tuesday.

The difference is whether anyone intends to fix it

Here is a story we have heard versions of many times, this one secondhand from a large medical employer. A staff member's laptop kept shutting down at random and she could not see patients. She called the help desk, who said somebody would come out the following week, then gave her a loaner in the meantime, which was fair enough. They took the machine, did almost nothing to it, and gave it back. The same fault carried on.

Nobody was rude. Nobody broke a service level agreement. The ticket was opened, worked and closed. It is just that at no point did anyone actually intend to fix the problem, and the problem was physical, so it came straight back.

That is the failure mode that costs businesses the most, and it never shows up in a report. A ticket closed is not a problem solved.

We would rather find the gremlin

When somebody here takes a ticket, they are trying to work out what is actually wrong, not what will make the symptom go away this afternoon. A band-aid that holds until Friday is not a fix, it is a deferral with your name on it.

So a technician who fixes the thing you reported and notices something underneath it will escalate the second part rather than close and move on. The message we want, and the one we get, reads roughly like this: here is what we saw, we got it fixed, but we also noticed this other thing and we need help coordinating some downtime to deal with it properly.

That second half is the whole difference. It is somebody choosing more work, on purpose, because the alternative is you having the same conversation again in three weeks.

We run at the speed you hand it to us

When you give us a ticket with urgency attached, we carry that urgency. Sometimes harder than you do, because occasionally the person reporting it cannot see how bad it is going to get and we can.

What owners tell us they hate, and they tell us this often, is the call where they explain that something is seriously wrong and the voice on the other end is unhurried and procedural about it. Now they are stressed about the original problem and stressed about whether anyone is actually working on it. We would rather you only had the first problem.

Our average response to a new ticket is 20 to 25 minutes, against a two-hour commitment written into every plan. But the number is the floor, not the point. The point is that somebody who already knows your setup picks it up and treats it the way you handed it over.

There is always a next action

Every open ticket here has a next step written on it. Not a status, a step. If a technician does not know what the next action is, they ask somebody, because a ticket without one is a ticket that has quietly stopped moving.

When we are waiting on one of your vendors, the commitment is specific: we are calling them at nine on Monday morning, and if there is no answer then we do this, and then this. A lot of shops are forty tickets deep with no plan attached to any of them, and the client becomes the follow-up system.