dealership IT support Pacific Northwest
Dealership IT fails differently than regular business IT, and most general-purpose IT providers do not find out until something stops a deal. If you are running a franchised store in the Pacific Northwest and your IT story starts with "we handle tickets fast," that is not enough. The DMS, the service drive, and the F&I office each carry operational weight that a standard managed services contract was never designed to protect.
I keep seeing shops where the outage that matters most is invisible to every standard monitoring tool. The whole DMS looks fine. The sales floor is running. But parts lookups are dark because a middleware server that a previous IT vendor installed and never documented has a certificate that expired. The current vendor does not know the server exists. It only handles catalog sync, so most operations keep running. But parts lookups route through that sync, and when it fails, your parts counter goes dark while everything else looks normal.
What that means in practice: techs are standing around, 14 open ROs need parts posted, and four cars in the service drive cannot move forward because nobody can confirm availability or lead time. No system technically broke. But the service lane cannot function. That is real cost, and it does not show up in your ticketing dashboard until someone calls the GSM.
This is what IT in automotive looks like. Not whether you have good backups or reliable internet in the abstract. Whether your IT provider understands the operational weight of each system at each point in the day.
Start with DMS expertise. Reynolds and CDK are not normal enterprise applications. They require specific network configurations, specific firewall rules, and specific on-prem hardware even when the vendor calls it a cloud solution. CDK is going to make certain migrations painful and they know it. The desking software the GSM opens at 7am to set the day's pricing and allocations is fragile, poorly documented, and essential. If your IT provider's first suggestion is to move everything to the cloud, they have not spent enough time on the service drive to understand what the sales floor actually runs on.
F&I has changed. The FTC Safeguards Rule hit automotive retail harder than most dealers expected. Your F&I managers are now handling customer financial data under compliance requirements that did not exist three years ago. That means documented encryption, access logging, and incident response procedures. If your IT provider cannot walk you through what Safeguards requires and map it to what you currently have, you are carrying exposure you probably do not know about. It shows up in audits and in your ability to maintain lender relationships. The deal jacket has become a posture question.
Parts department uptime has to mean something specific. Not a monthly average. Actual uptime Tuesday at 10am when you have six techs waiting on parts lookups and a line in the service drive. The UPS in the parts department is not just protecting a server. It is protecting the entire service lane's ability to open and close ROs. When that UPS fails, or the switch it powers starts flapping, you can lose an hour of service productivity before anyone realizes what happened.
Internet here fails differently. Windstorms take out power and connectivity for entire neighborhoods. A store in Tacoma or Portland can lose internet for six hours in January and it is not an outage, it is weather. Your infrastructure has to account for that. Local internet failover, local on-prem DMS capability, and actual redundancy that does not assume the cloud will handle it. The cloud does not handle it when the fiber line to your building is down and your advisors cannot open ROs. I have been doing this work since the late 1990s, and that pattern has not changed.
Vendor access also matters here. CDK and Reynolds both require regular access for updates, patches, and support, happening on your network, touching your servers, often during business hours. If your IT provider is remote-only or cannot put a human on-site within an hour when vendor access goes sideways, a 30-minute support call turns into a half-day event.
Here is what I ask on behalf of dealership clients when evaluating their current setup or a prospective vendor:
At TCG, our dealership IT support work is built for automotive retail in the Pacific Northwest because dealership infrastructure is specific enough that general service contracts leave real gaps. IT success at a dealership is measured in whether the service drive stays open during peak hours and whether the sales floor can desk deals when a customer is ready to buy. Those are the only numbers that matter to the GM on a Tuesday morning.
What you have to weigh is whether your current provider has actually been inside a service drive when it went dark, or whether they are learning that lesson on your dime.
If you want someone to walk your current setup and tell you plainly what is working and what is not, reach out through our contact page and we will start there.