An IT support SLA is the part of a managed IT contract that says how fast a provider must respond to, and resolve, each kind of problem. At a dealership, the definitions behind those times matter more than the times themselves.
Last updated: October 21, 2026
Picture a Saturday morning at the end of the month. The card terminals at the service cashier stop connecting at 9:40, and there’s a line of customers holding keys and waiting to pay. Somebody calls the IT provider, and the contract says priority 1 gets a 1-hour response. At 10:25 an email arrives saying the ticket has been received and assigned. The clock stops. The terminals are still down at noon. The customers are still waiting.
Every word of that contract was honored. Nobody at the store would call it good service, and they’d be right. That gap, between what an SLA measures and what a dealership actually needs, is what this post is about.
In a lot of IT agreements, the service level section is a single table near the back. A few priority levels, a response time beside each one, maybe a resolution target. It looks precise. It rarely says what counts as a response, when the clock is running, or what “priority 1” means in a building that sells and services cars. Those definitions decide whether the table protects you. Whoever runs your managed IT support for dealerships, us or anybody else, should be able to explain every line of it in plain English.
What an IT Support SLA Actually Promises
An IT support SLA, or service level agreement, is the section of an IT contract that sets measurable targets for how quickly a provider responds to and resolves problems, sorted by priority, plus what happens when it misses them. A help desk SLA works the same way, limited to calls and tickets.
Strip the table down and an SLA makes 4 kinds of promise. Here’s what each one usually means in the contract, and the question I’d ask before signing.
| SLA term | What it often means in the contract | What a dealer should ask |
|---|---|---|
| Response time | The first contact after a ticket is opened, which can be an automatic email | Does a response mean a person working the problem? |
| Resolution time | A target for closing the ticket, often written as a goal rather than a commitment | Is it a promise or an aim, and does a workaround count as resolved? |
| Coverage hours | The hours the clock runs, frequently business hours on weekdays | Does the clock run on Saturday, and do evenings cost extra? |
| Priority levels | Generic definitions such as “all users affected” for the top level | Which dealership systems are named as priority 1, and who decides? |
| Remedy | A service credit, a small share of the monthly fee, usually claimed in writing | What happens after repeated misses, beyond a credit? |
A Fast Answer Isn’t a Fixed Problem
Microsoft is about as large a support operation as exists, and its own published terms are a good lesson in reading the clock. Its Azure support plans list an initial response of under 1 hour for the most serious tier, called Severity A, on the standard paid plan. Microsoft defines that response as the time from when you submit the request to when a support engineer contacts you. The page lists no resolution time at all.
That’s honest, and I respect it. It also tells you exactly what a response-time promise is worth on its own. Somebody gets in touch. The work starts there. That’s all.
Years ago I took a 2-year detour through culinary school, and my internship was at the Ritz-Carlton in Washington, DC. The whole program was built around the customer’s experience, and it shaped how we run support to this day: actual people, polite, not the stereotypical computer guy. A warm greeting at the door is part of that experience. Nobody walks out of a hotel happy because the front desk said hello quickly, though, if the room still isn’t ready.
Our own number is an 82-second average to reach a live support agent. I’m proud of it, and it still isn’t a fix. It’s the moment a technician starts on your problem, which is why I’d want any SLA to track 3 clocks, not one: the time to a person, the time until the store is working again, even on a workaround, and the time until the cause is actually gone.
Ask for all 3 clocks.
What Priority 1 Should Mean at a Dealership
Generic SLAs define the top priority as a complete outage affecting all users. At a dealership that definition is wrong in both directions. A whole store can be losing money while most people can still log in, and a problem that hits everyone, like a slow shared drive, might not cost you a single deal.
Priority should follow the money. The NADA Data 2025 report counts more than 276 million repair orders written at 16,990 franchised light-vehicle dealerships in 2025, which works out to over 16,000 per store if you do the division. Each of those needed the DMS and the network to be up. When a service drive can’t open repair orders, that store is down, even if the sales floor is fine.
| Priority | Dealership examples | What it should trigger |
|---|---|---|
| Priority 1 | DMS unreachable at a store, main or service phone lines down, card terminals or cashiering down, internet circuit out at a rooftop, a security incident in progress | A technician on it right away and working it without a break, a workaround first, a call to a named person at the store, updates on a set schedule |
| Priority 2 | One department stopped: F&I can’t print contracts, the parts counter can’t scan, the BDC can’t reach the CRM | Worked the same day, with a workaround offered while the cause is found |
| Priority 3 | One person or one device: a slow laptop, a single locked account, one printer in the office | Handled in normal order, most of it on the first call |
| Priority 4 | Requests: a new hire’s logins next week, a new email signature, a software install | Scheduled, with a date the store agrees to |
The day matters too. A department-level problem at 9 a.m. on the last Saturday of the month deserves more urgency than the same problem at 4 p.m. on a Tuesday, and a good SLA says the store can raise the priority when that’s true. Ask who assigns priority and how you change it. If the answer is that the provider decides alone, you’ve just found the line in the contract that matters most. Push on it.
To be fair to providers, the opposite problem is real. When every call is priority 1, nothing is. The general manager’s laptop isn’t a store outage, no matter who’s calling about it.
Priority is a business decision, and it belongs to the business.
The Fine Print Worth Reading Before You Sign
Start with when the clock runs. The same Microsoft support page says its lowest severity is handled during business hours only, and defines business hours in North America as 6 a.m. to 6 p.m. Pacific, Monday through Friday. Saturday isn’t in there, and plenty of IT contracts use a weekday window just like it. For a dealership, Saturday is often the busiest selling day of the week. A 4-hour, business-hours response on a call placed late Friday afternoon can legally come due on Monday. Think about that.
Then look for the pause button. Many SLAs stop the clock while a ticket is “waiting on customer” or “pending third party.” Some of that is fair, since nobody can fix a laptop the user has taken home. But a DMS problem nearly always involves the DMS vendor, and if your provider’s clock stops every time it opens a ticket with that vendor, the hardest problems are the ones the SLA quietly stops measuring. Ask who chases the vendor, and whether the clock keeps running while they do. It should.
The 2024 CDK outage made one more limit plain. No IT provider’s SLA covers a software vendor’s outage, and none should pretend to. What the contract can say is what your provider does while it lasts: keeping the store’s network, phones, and printers working, helping set up the manual workarounds, and checking that systems are clean when the vendor comes back. Our DMS outage plan lays out what a store needs ready before that day.
Read the exclusions list, too. “Factors outside the provider’s reasonable control” and “third-party hardware or software” can cover a surprising share of a dealership, from the OEM’s own diagnostic equipment in the service bays to the phone carrier that runs your main line. Read it slowly.
Service credits deserve a sentence. Usually a small percentage of one month’s fee, often available only if you file a claim within a set number of days, a credit won’t come close to covering a lost Saturday of deals. Uptime promises have the same issue; 99.9% monthly uptime still allows about 43 minutes of downtime in a 30-day month, and those minutes can land at 10 a.m. on a Saturday. A credit is an apology with a number on it.
Last, the bill. Some contracts meet every response time and then charge separately for evenings, weekends, or a technician in the building. That part belongs in the SLA conversation, not the invoice, because a fast response you’re afraid to call for isn’t worth much. Nobody calls. We don’t charge extra for after hours. We don’t charge extra for weekends. When you pay the number, the number’s the number.
And whatever the SLA says, ask how it’s measured and reported. A provider that won’t send you its SLA results every month, broken out by store and by priority with the misses explained, is asking you to take the table on faith. Don’t. The numbers worth seeing are the ones in our guide to help desk metrics for dealerships.
How We Approach It at Helion
We’ve already seen this exact problem across 2,000-plus dealerships: a contract with a neat response table, a store that’s down on a Saturday, and 2 vendors explaining why it belongs to the other one. So we keep our own promises to things we can measure and publish. Here they are.
Our dealership IT help desk is live from 6 a.m. to midnight Eastern, Monday through Saturday, and your staff reach a live support agent in 82 seconds on average. After-hours, weekend, and field support are included at no extra charge, and we close only on Christmas Day and Thanksgiving Day. We don’t call that 24/7, because the live desk isn’t, and I’d rather you know exactly when a person picks up.
What I won’t do is write a fixed resolution time for every kind of problem into a proposal. A failed circuit depends on the carrier, and a DMS outage depends on the DMS vendor, so anyone who promises you a 4-hour fix for both is promising something they don’t control. What we own is the work: one integrated team on the problem from the first call, a workaround while the cause is found, and no finger-pointing about whose ticket it is. That’s on us to get it all done, and make sure it’s right.
If your dealership keeps its own IT person, the same thinking applies inside the building. Under co-managed IT, the split of who answers which priority should be written down just like any other SLA.
What Dealers Ask About IT Support SLAs
Is a 15-minute response time better than a 1-hour one?
Help desk SLA vs IT support SLA: does the gap actually matter?
Should our SLA say 24/7?
Who should decide that a ticket is priority 1, us or the provider?
Are service credits worth negotiating hard?
Our IT is all in-house. Do we still need an SLA?
Read the Definitions First
The response times are the part of an SLA everyone reads, and they’re the least useful part on their own. The definitions underneath them decide what you’ve actually bought. That means what counts as a response and when the clock runs. It means who sets the priority, too, and what’s excluded. A dealer would never sign a floor plan agreement without reading how interest is calculated. An IT contract deserves the same read. It’s worth an hour.
If you’d like a second set of eyes on yours, start with a complimentary IT and cybersecurity assessment. Send us your current agreement, and we’ll show you what it promises on a Saturday morning when the card terminals go down. Then you’ll know what you’re paying for.