Bad IT support at a dealership usually looks busy, not absent: tickets close quickly, but the same problems come back, nobody owns the whole system, and nobody can show you what was fixed or why.
Last updated: October 22, 2026
Pull up the last few closed tickets from your store and read the closing notes. Not the subject lines. The notes. If most of them say some version of “resolved, user able to work,” you’ve learned something about your IT support, though maybe not what you expected.
That note isn’t wrong. The person on the phone got back to work, and that matters. But it tells you the call ended. It doesn’t tell you whether the problem did.
I’ve spent more than 25 years leading managed services teams, and what I’ve learned over time is that a help desk can be very busy and not very effective at the same time, and for the first few months you can’t tell the two apart from the outside. The difference shows up later, when the same issues keep coming back and everybody at the store has quietly decided that’s just how IT works.
This post is for dealers who already have a provider and aren’t sure it’s working. It isn’t an argument for switching. It’s a list of signs worth checking, whoever handles your dealership IT support, our own team included.
Closing a Ticket and Fixing a Problem Aren’t the Same Job
Closing a ticket means the person who called can work again. Fixing a problem means the cause is found and removed, so the same call doesn’t come in next week. Bad IT support is support that does the first job well and the second one rarely, or never.
ITIL, the service management framework I’m certified in, keeps these as two separate practices, incident management and problem management, because they need different things. One needs speed. The other needs time, history, and somebody willing to ask why.
Microsoft runs its own cloud the same way. Its guide on how to check Microsoft 365 service health lists a status called “Post-incident report published,” a report that “includes root cause information and next steps to ensure a similar issue doesn’t reoccur.” If Microsoft writes down why Exchange Online broke, your provider can write down why the parts counter printer keeps failing.
Speed closes tickets. Attention fixes problems.
Six Signs Your Provider Is Closing Tickets Instead of Fixing Problems
None of these proves anything on its own. Two or three together usually do.
| The sign | What you’d notice at the store | What to ask |
|---|---|---|
| The same issue comes back under a new ticket number | The parts printer, the Wi-Fi in one F&I office, or one salesperson’s DMS lockout, every few weeks | Which of our tickets this quarter were repeats, and what changed because of them? |
| Tickets close before anyone at the store says it’s fixed | A “resolved” email arrives while the problem is still happening | Who confirms a fix with the user before a ticket closes? |
| Nobody owns the whole system | The network contractor points at the phones and the phone company points at the internet circuit | When two vendors disagree, who owns the answer? |
| Ticket notes say “resolved” and nothing else | Every new technician starts from scratch on an old problem | Can I read the full notes on our last 5 closed tickets? |
| Reports count tickets, not results | A monthly email with a big closed-ticket total and no trend | Which of these numbers should be going down? |
| Your people stopped calling | Workarounds everywhere, and ticket counts that look better than the store feels | When did someone from IT last ask the people doing the work what’s still broken? |
The repeat ticket is the easiest one to check and the one most often missed. Three calls about the same lockout may land with three different technicians, and each of them fixes it properly in the moment. Each call, on its own, went fine. You only see the pattern from above. Somebody has to be up there looking, and on a lot of help desks nobody is. We wrote about what that job looks like in our post on root cause analysis for dealership IT problems.
The early close is sneakier. CompTIA, the IT trade association behind the A+ certification, teaches a seven-step troubleshooting methodology whose sixth step is to “verify full system functionality,” and the article suggests you “have the users that rely on the system test functionality for you when possible.” At a dealership, that user is the service advisor or the title clerk. If nobody asked them, the ticket closed early. Too early.
Ownership is the one I’d put first if I had to rank them. Count the vendors in your building. The DMS provider. The phone company. Whoever owns the internet circuit, the OEM’s systems in the shop, a network contractor, maybe a separate security company. Now the service drive Wi-Fi drops and the diagnostic stations in the shop can’t connect. Each vendor checks its own piece and finds it working. They’re all right, and the problem sits there for a week anyway. What problem are we actually trying to solve? A car that can’t get written up. Somebody has to own that from end to end, and the agreement should say who.
The quietest sign is the one your staff gives you without saying a word. When people stop calling IT, it’s rarely because things got better. They found a workaround. Everyone prints in parts because the service printer can’t be trusted, or two people share one login at the desk because resets take too long. The tickets go down, the report looks great, and the problem is still there, now with a security gap attached.
A falling ticket count isn’t always good news.
Why Good Technicians End Up Just Closing Tickets
I want to be fair here. I’ve sat on the provider’s side of this for a long time, starting with the MSP I built that served banks and credit unions. Most of the time, a help desk that only closes tickets isn’t lazy or careless. It’s measured on the wrong things.
If the scorecard rewards tickets closed per hour, technicians close tickets per hour. People do what they’re measured on. I would too.
The other cause is not knowing the building. Anybody can reset a Windows password, but knowing that the shop’s OEM diagnostic stations need their own path through the network, or that a DMS lockout at 8 a.m. on a Saturday hurts the service drive far more than the same lockout on a Tuesday afternoon, takes years of working with dealerships specifically. A provider that mostly supports law offices and clinics hasn’t had those years, and that isn’t a character flaw. It’s a fit problem.
Fit problems are fixable. Fix the scorecard first.
What to Ask Your Current Provider Before You Change Anything
“We already have an MSP, and switching sounds like a lot of work.” I hear that a lot, and I agree with the second half. Switching is work. So start with one meeting and a short list of questions instead.
- Which issues came up more than twice at our stores in the last 90 days, and what did you change because of them?
- Show me the full notes on 5 tickets you closed last week.
- When Microsoft 365 acts up, do you check Microsoft’s service health first? Microsoft’s own guidance is to see whether “this is a known issue with a resolution in progress before you call support or spend time troubleshooting.” A provider that looks there first can save your people an hour of rebooting.
- Who owns a problem that crosses two vendors, and where is that written down?
- Which numbers in your monthly report should be going down, and are they?
We laid out the numbers worth asking for in our post on help desk metrics a dealer principal should ask for, and if the talk turns to what the contract actually promises, our guide to IT support SLAs for dealerships is the place to go next.
Pay attention to how the answers come back, because that tells you as much as the answers do. Over the years I’ve been the one across the table getting these questions more times than I can count, and more than once my honest answer was that we hadn’t been tracking it yet, which was uncomfortable to say and was also the start of fixing it. A provider who says that and then follows up is doing fine. The one I’d worry about gets defensive, or promises the report and never sends it.
Have the meeting before you shop.
How We Try to Hold Ourselves to It
On our side, the first job looks like this: a live technician picks up in 82 seconds on average, and the help desk is open whenever dealers are open, 7 days a week. I care about that number, and I also know it only measures half of what a dealer is paying for.
The rest of it isn’t mine to take credit for. It’s the service desk, the field techs, and the systems engineers. When the same F&I office calls a third time in a month, somebody on the desk reopens the old ticket instead of starting over, and somebody in the field drives out and stays until the fix holds (field support is included at no extra charge, so there’s no bill to weigh against that half hour). After that a systems engineer makes the fix the standard at every rooftop in the group. They find the causes. I just try to keep out of their way.
We don’t get it right every time. When one of our fixes doesn’t hold, the right move is to reopen the original ticket and say so, not to open a new one that makes the numbers look cleaner. I’d rather see an honest reopen rate than a pretty one. We keep 98% of our clients, and I think that has more to do with the second job than the first.
If your own IT staff handles part of this alongside a provider, co-managed IT only works when it’s written down who owns the repeat problems. Otherwise each side assumes the other one is looking into it. Nobody is.
What Dealers Ask When They Already Have a Provider
We already have an MSP. Why would we look at anyone else?
Realistically, how many repeat tickets is too many?
Our provider says everything is in the monthly report. Is that enough?
Is it fair to judge a provider on a few bad weeks?
Who at the dealership should be asking these questions?
Read the Closing Notes
I don’t think most dealerships have bad IT support. Some do. I think a lot of them have support that’s good at the first job and was never asked to do the second. You can see that gap from the outside if you know where to look. Start with the ticket notes.
Here’s my suggestion. Pick 10 tickets your store closed in the last 30 days, ask for the full notes on each, and read them with one question in mind: do we know what caused this, or only that it stopped? If you’d like a second set of eyes, our complimentary IT and cybersecurity assessment looks at how your stores are set up and where the repeat problems are likely coming from.
Closed is a status. Fixed is a result.