Why Your Current "System" Is Probably Failing

Back in the 1970s, when a dealer's "IT department" was a guy named Gary who knew how to thread a tape drive and could coax the mainframe into printing payroll checks by Friday, the concept of ticket triage didn't exist. If something broke, Gary fixed it. If Gary wasn't around, you waited. Simple.

Fast forward fifty years, and you're running a dealership with integrated DMS, CRM, service lane cameras, parts management software, customer portals, SMS platforms, and a mobile app your sales team uses to pull market comps in the parking lot. When one of those systems goes down, it cascades. Your front desk can't check customers in. Service advisors can't write repair orders. Parts managers can't pull inventory. And your phone starts ringing.

The difference between a dealership that hemorrhages productivity during an outage and one that manages through it comes down to one thing: a real triage system. Not a vague "we'll handle it" approach, but an actual playbook that tells every person on your team exactly what to do, in what order, and why.

This is the playbook most dealer principals and GMs don't have—and honestly, most small IT vendors won't teach you because they'd rather keep you dependent on their emergency response calls.

Why Your Current "System" Is Probably Failing

Let's be honest. Most dealerships handle IT issues reactively.

Something breaks. Someone notices. That person calls the IT guy (or your MSP, or you, or all three). Everyone waits. The IT person handles it based on gut feel, or whatever they were working on before, or whoever yelled loudest. There's no priority matrix. There's no escalation path. There's no clear communication to affected departments about what's being done and when service will be restored.

The result? Your service director is losing $500 a minute in stalled technicians. Your parts manager has no idea if the issue is being worked on. Your receptionist is manually writing down customer check-ins on a notepad like it's 1987. And your GM is fielding complaints from every department head.

This doesn't have to be your reality.

The dealerships that run smoothly during tech disruptions have one thing in common: they treat IT tickets like they treat service ROs. There's a queue. There's a priority level. There's accountability. Someone owns the outcome.

The Three-Tier Triage Model

Start here. This is the framework that separates managed chaos from actual disaster.

Tier 1: Revenue-Stopping Issues

These are the ones that turn your dealership into a parking lot.

Your DMS is down. Your service lane can't write ROs. Your payment processing is broken. Your parts ordering system is offline. Your customer portal crashed and you're bleeding sales leads. When any of these go down, you're not losing productivity—you're losing money. Fast.

Tier 1 tickets get immediate escalation. We're talking drop-everything urgent. Your IT person or MSP is notified directly (not via email,via phone call or emergency channel). Your GM and the affected department head are looped in within 5 minutes. You've got a target restore time of 15-30 minutes, depending on the system.

Here's the key part people miss: you also need a manual workaround ready. Say your parts ordering system goes down. Instead of just sitting there waiting for IT to resurrect it, you've got a process,maybe it's calling your distributor directly and getting a parts order number on a physical form, or it's using a backup vendor portal. You're not perfect, but you're moving. The technicians aren't sitting idle. Your delivery promise to customers doesn't blow up.

A typical Tier 1 ticket might look like this: Service DMS outage at 10:47 AM. Twelve technicians on the clock. You've got maybe 90 minutes of manual workaround capacity (hand-written ROs, verbal job descriptions, old-fashioned labor time tracking) before the whole operation grinds to a halt.

Tier 2: Department-Level Disruptions

Now you're in the territory where one team is impacted, but the dealership still functions.

Your service scheduling system is slow or partially down. Your CRM is glitchy and sales can't pull customer history. Your email is running at 50% speed. Your loaner vehicle tracking system is offline. These suck, but they're not an all-hands emergency.

Tier 2 tickets get logged, prioritized, and assigned within 30 minutes. You're targeting a 2-4 hour resolution window. The affected department gets a status update every 30 minutes. Your IT person or vendor is working on it, but it's not dropping everything else.

This is where a lot of dealerships mess up. They treat every ticket like it's Tier 1, which means nothing gets fixed efficiently. Your IT person is constantly context-switching. The service director is panicking about a scheduling system that's mildly slow, which is fair, but it's not a revenue stopper.

Tier 2 also needs a process. If the CRM is glitchy, sales can still take deals,they just call your BDC to pull customer history. If scheduling is slow, the service advisor writes down appointments on a paper sheet and enters them into the system later. Not ideal. Manageable.

Tier 3: Non-Urgent Issues

A user's printer doesn't work. Someone's laptop is running slow. A software license renewal notice came through. The staff bathroom sink has a leak (okay, that's facilities, not IT, but you get the idea).

Tier 3 gets logged and queued. You're targeting resolution within 1-2 weeks. It's on the backlog. Your IT person gets to it when Tier 1 and Tier 2 are handled, or it's a routine maintenance item.

The reason this matters is that it's a pressure release valve. If every single issue goes into a bucket labeled "fix immediately," everything takes longer. By clearly marking Tier 3, you're giving your IT person (or MSP) permission to defer low-impact stuff and focus on what actually moves the needle.

Who Decides the Tier? And How Do You Avoid Arguments?

This is where the playbook gets real.

You need one person who owns triage decisions. Not by committee. Not by whoever calls first. One person. Usually it's your IT director, your MSP account manager, or in smaller shops, your GM delegating to the IT person. Whoever it is, they've got a decision tree and clear criteria.

Here's the criteria matrix. Post this somewhere your team can see it (and honestly, put it in your staff handbook):

• Tier 1: Does this issue prevent work from happening in a core dealership function (sales, service, parts, accounting) right now? Can technicians not write ROs? Can customers not complete purchases? Can you not process payroll? If yes, it's Tier 1.
• Tier 2: Does this affect a department or a specific workflow, but the dealership can still operate? Can sales still take deals, even if the CRM is slow? Can service still write ROs manually? If yes, it's Tier 2.
• Tier 3: Does this not affect revenue or core operations? Can it wait a few days or a week? If yes, it's Tier 3.

Once you've got those criteria written down, your triage person doesn't get to argue. They ask the questions. The answers dictate the tier.

But here's the part that prevents chaos: whoever reports the ticket needs to know the tier immediately. Not three hours later. Within 5 minutes of submission, they get a response: "Tier 2. You'll get a status update at 11:30 AM." They know what to expect. They can tell their boss what's happening. The dealership doesn't spiral into rumor-mongering about "the system being down."

The Escalation Path: When Triage Isn't Enough

Tier 1 tickets can escalate beyond your internal IT person fast.

Say your DMS goes down and your IT person has been working on it for 20 minutes with no progress. At the 20-minute mark, they're escalating to the vendor's support line. At the 30-minute mark, if it's still not resolved, the GM is involved and making a decision: do we call the vendor's emergency support line (usually more expensive)? Do we call a backup MSP? Do we activate the manual workaround and tell everyone this is going to take a few hours?

This is the conversation you want to have in a planned way, not while your service director is standing in front of your desk yelling about idle technicians.

Build the escalation path before you need it. It should look something like this:

1. Ticket submitted → Triage person assigns tier and notifies affected department within 5 minutes.
2. Tier 1: IT person starts work immediately. Department head is notified. 15-minute check-in with triage person.
3. If unresolved at 20 minutes: Escalate to vendor support (or backup MSP if it's infrastructure). Notify GM.
4. If unresolved at 30 minutes: Activate manual workaround. Update all affected staff. Notify dealer principal if it's extended outage.
5. Tier 2: Standard triage workflow. 30-minute status updates. No additional escalation unless it drops to Tier 1.
6. Tier 3: Queued for standard work cycles. No escalation needed.

This takes the emotion out of it. Everyone knows the playbook. When something goes wrong, you're executing a plan, not panicking.

Staffing and Pay Plan Implications

Here's where a lot of dealer principals get quiet: you can't run this system with a part-time IT person or someone who's got a dozen other jobs.

If your IT person is also your facilities guy, your compliance officer, and the guy who fixes the WiFi, they're not triaging anything. They're surviving.

A real IT triage system needs accountability, and accountability requires someone whose primary job is managing the tech stack and the ticket queue. For a single rooftop with 30-40 employees and a standard software suite, that's usually one dedicated person, or a contract with an MSP that includes defined SLAs and a triage agreement.

And yes, that costs money. A solid MSP runs $1,500 to $3,500 a month depending on your complexity. An internal IT hire runs $45,000 to $65,000 a year plus benefits. But think about the math the other way: a single hour of downtime in your service department at a typical dealership costs you $300 to $500 in lost productivity. You don't need many outages before that contract with an MSP pays for itself.

If you're running multiple rooftops, the calculus changes. You might have one IT director overseeing a team of support people, with clear responsibilities carved out by dealership location or by function. Your pay plan for IT staff should include metrics around ticket resolution time, first-contact resolution rate (meaning how often an issue is solved without escalation), and customer satisfaction scores from your internal departments. Tie bonuses to those metrics, and you'll see your ticket queue improve fast.

(And honestly, this is one of those areas where a lot of dealers underpay because they don't understand that IT is now core to dealership operations. You wouldn't hire a service director on the cheap. Your IT director should get similar respect.)

Tools and Systems That Actually Help

You don't need fancy software to run a triage system. A spreadsheet with columns for date, ticket description, tier, assigned person, status, and resolution time will work. Seriously.

But spreadsheets get messy. They don't send automatic notifications. They don't show patterns in what's failing and why. If you're running a multi-location operation or you've got 50+ staff members, you need something with a little more structure.

Dedicated ticketing systems like Jira, Zendesk, or Freshdesk are overkill for most dealerships. They're built for massive tech companies. But there's a middle ground: tools that integrate your dealership operations platform with a simple queue management system. This is exactly the kind of workflow Dealer1 Solutions was built to handle. When something breaks in your inventory system or your reconditioning workflow, the ticket gets logged automatically, triaged based on which system failed and how many vehicles or technicians are affected, and your team gets a clear status update without anyone having to manually email status reports back and forth.

The point is: whatever you use, it needs to be visible and updated in real-time. Everyone on your team should know the status of every active ticket. No surprises. No "I didn't know that was being fixed."

Training: The Part Everyone Skips

You can have the best triage playbook in the world, and it falls apart if your team doesn't know how to use it.

Every single person on your staff needs to know three things: how to submit a ticket (or who to tell), what the tier system means, and what to expect for resolution time. That's it. Not complicated.

For your IT person or MSP, the training is deeper. They need to understand the decision tree. They need to know the escalation path. They need to practice the manual workarounds so they're not improvising during an actual outage.

And your GM, service director, and parts manager need to understand the playbook from a leadership perspective. They need to know they'll get updates every 30 minutes during a Tier 2, and they'll get immediate action on Tier 1. They need to know that if they're not getting updates, something is wrong and they should escalate.

Run a training session once a year. Make it 30 minutes. Walk through a hypothetical scenario: "DMS is down. Here's what happens in the first 5 minutes. Here's what your job is." Let people ask questions. Then you're done. It sticks.

The Real Benefit: Hiring and Retention

Here's the thing nobody talks about: a clear triage system makes your IT person's job way less miserable.

When everything is an emergency, burnout is guaranteed. Your IT person is constantly being pulled in a dozen directions. They can't focus. They can't actually fix root causes because they're always fighting fires. They leave.

A good triage system gives IT a framework. They know what's truly urgent and what can wait. They've got breathing room to actually improve the system instead of just patching it. They can plan their day instead of just reacting.

Good IT people are hard to find and harder to keep. A dealership that respects their time and gives them clear priorities will retain talent. One that treats every ticket like a five-alarm fire will lose them.

And from a hiring perspective, when you're recruiting an IT director or support person, you can tell them: "Here's our triage system. Here's what Tier 1 looks like. You'll own the queue. You'll have authority to prioritize." That's attractive to good candidates.

Start Monday

You don't need to overhaul your entire operation to get this working. Pick a Monday. Sit down with your IT person (or MSP account manager) and your GM. Spend 90 minutes building your triage matrix.

Write down your critical systems: DMS, CRM, payment processing, parts ordering, service scheduling, email, customer portal. For each one, ask: what happens if this goes down? How fast do we need to fix it? What's the manual workaround?

That's your framework. Build your tier criteria from that. Write down your escalation path. Print it out. Post it. Train your team.

By the end of the week, you've got a system. It won't be perfect. You'll refine it. But the next time something breaks, you won't be panicking. You'll be executing.

That's the whole point of a playbook.

The Ongoing Piece: Regular Review

A triage system that you set once and ignore will atrophy. Once a quarter, sit with your IT person and review the ticket log. What got triaged wrong? What took longer