When a flight encounters turbulence, passengers expect the pilot to know what to do. They do not expect to hear, “Give me a few minutes while I figure this out.”
Pilots prepare for situations they hope will never happen. Responsibilities, procedures, and priorities are established before anyone is under pressure.
A dealership technology emergency should work the same way.
When the dealer management system becomes unavailable, the internet fails, employees lose access to email, or an important server stops working, the dealership should be following a plan—not creating one while sales, service, finance, and accounting are waiting.
One Technology Problem Can Affect the Entire Dealership
A disruption may begin with one system, but the effects can spread quickly.
An internet outage can interrupt phones, Wi-Fi, payment processing, cloud applications, customer communication, and access to vendor systems. An account problem may prevent an employee from reaching email, the CRM, lender platforms, or shared documents. A server failure may affect accounting, files, printing, or other local applications.
The problem is not limited to technology.
Salespeople may be unable to follow up with customers. Finance employees may have trouble reaching lender platforms or documents. Service advisors may lose access to the information they need to communicate with customers. Accounting may be facing payroll, reporting, or month-end deadlines.
At the same time, the General Manager or Dealer Principal wants to know what happened, which departments are affected, and when the dealership will be operating normally again.
Without a plan, no one can answer those questions confidently.
The Real Cost Is Often the Time Lost Deciding What to Do
When a dealership does not have a documented response process, every step becomes a new decision.
Who contacts the DMS provider? Should someone call the internet company first? Is the phone problem related to the network? Who updates employees? Which department should receive help first? What should the dealership tell customers?
Each question consumes time. More importantly, the answer may depend on another vendor or employee who is also trying to understand the situation.
Employees begin opening separate support cases. Vendors receive different descriptions of the problem. Leadership gets partial updates from several people, and no one has a complete view of the response.
The delay is not always caused by a difficult technical repair. Sometimes the dealership loses valuable time deciding what should have been settled in advance.
That is why preparation matters.
A Recovery Plan Sets Priorities Before Pressure Starts
A useful dealership recovery plan does not need to predict every possible emergency. It needs to provide enough structure so that employees and vendors know how to begin.
The first step is deciding which systems the dealership needs most.
Internet connectivity and employee accounts may need to be returned before staff can reach other applications. Finance may need lender portals and current documents. Service may need customer and repair-order information. Accounting may have payroll or reporting obligations that cannot wait.
The easiest system to restore is not always the one employees need first.
Dealership leadership should set business priorities. The IT provider should then document and support the technical steps needed to meet them.
That keeps the recovery order focused on dealership operations instead of whichever vendor responds first.
Someone Must Own the Vendor Coordination
Dealerships depend on many technology companies, and their responsibilities often overlap.
The DMS provider may say the network is causing the problem. The network provider may say the internet connection is working. The phone company may say its equipment is online. A software vendor may insist the problem belongs to IT.
Meanwhile, employees are still waiting.
A recovery plan should identify which vendor supports each important system, how to open an urgent case, who is authorized to speak with the vendor, and how the issue will be escalated.
It should also identify who is responsible for coordinating the response.
That does not mean one IT provider can directly repair every vendor-hosted platform. It means someone gathers the information, keeps the vendors communicating, tracks progress, and stays involved until the dealership understands what happened and what comes next.
The Dealer Principal, General Manager, or Controller should not have to spend the day passing messages between the DMS company, internet provider, phone vendor, and IT company.
A dealership needs one accountable technology partner managing the process.
Employees Need Direction While Systems Are Down
Restoring technology is only one part of the response.
Employees also need to know what is happening, what they should do, and when they can expect another update.
Without direction, people begin creating their own workarounds. Customer information may be written down in several places. Employees may use personal email accounts or unapproved storage. Different departments may give customers conflicting explanations.
A practical communication plan should establish who updates leadership, who communicates with employees, and how those messages will be delivered if email or the phone system is unavailable.
Departments may also need temporary procedures.
Sales may need a safe way to record customer information until the CRM returns. Service may need a temporary process for appointments and customer calls. Finance and accounting may need to know which activities can continue and which should wait.
The goal is not to create a complicated emergency manual that no one will read. It is to give employees enough direction to keep the dealership organized while the technical work continues.
Multi-Location Dealerships Need to Account for Shared Systems
A dealer group may assume another location can take over if one store experiences an outage.
That may be possible, but it should be confirmed before the emergency.
Locations often share employee accounts, cloud platforms, phone services, internet providers, vendor systems, security tools, or centralized servers. A disruption involving one shared service may affect several stores at once.
A multi-location recovery plan should identify which systems are shared, which stores can operate independently, and what employees need to work securely from another location.
It should also establish who coordinates communication across the group.
Without that planning, moving employees or work to another store can create more confusion instead of reducing the disruption.
Test the Plan Before the Dealership Needs It
A recovery plan that has never been reviewed or tested is still largely an assumption.
The dealership does not need to shut down every system or simulate a major disaster. A practical review can begin by walking through a realistic situation and discussing what would happen next.
For example, suppose the dealership loses internet access on a busy weekday morning. Phones, Wi-Fi, cloud applications, and several vendor platforms are unavailable.
Who notices first? Who contacts the provider? Who determines whether the problem is limited to the dealership or affects a wider area? Who updates employees? Which departments can continue working? When should the issue be escalated?
Walking through those questions may uncover outdated contact information, inaccessible documentation, overlapping vendor responsibilities, or temporary procedures that no longer fit the dealership.
Those problems are much easier to fix during a planned conversation than during an actual outage.
Preparation Matters More Than Having the Most Expensive Tools
After more than 30 years of working with business technology, we have found that the businesses that handle disruptions best are not always the ones with the most expensive systems.
They are usually the ones that know who is responsible, what should happen first, and how employees will be kept informed.
Reliable backups, monitoring, cybersecurity protection, and redundant systems all matter. They can reduce the likelihood and impact of an interruption.
But technology alone does not decide who calls the vendors, which department receives priority, or what employees should tell customers.
That comes from preparation and ownership.
Five Questions Every Dealership Should Be Able to Answer
A useful emergency plan should answer five basic questions:
- Which systems and departments have the highest recovery priority?
- Who is responsible for the technical response?
- Who coordinates the DMS, internet, phone, software, and other vendors?
- How will employees and leadership receive updates?
- What temporary procedures will departments use while systems are unavailable?
Uncertainty in one of these areas does not mean the dealership has failed. It may simply mean the business has grown beyond the process that worked when it had fewer employees, fewer systems, or one location.
Your response plan should match the dealership you are operating today.
Make the Decisions Before the Emergency
The worst time to decide who owns the response is after systems are already down.
A practical recovery plan reduces delays, keeps employees organized, gives leadership better information, and prevents vendors from working in separate directions.
Most importantly, it allows the dealership to focus on restoring operations instead of trying to manage confusion.
Tech Marvel helps Morris County and Northern New Jersey auto dealerships review their critical systems, recovery priorities, backup processes, vendor responsibilities, and employee communication plans.
During a free 20-minute dealership IT review, we can talk through your locations, important systems, current vendors, recurring concerns, and what would happen if a major service became unavailable.
The goal is to identify which parts of your response are already working—and which decisions should be made before the dealership is under pressure.
Call 862-201-5710 or schedule your Free 20-Minute Dealership IT Review.
