Ask Dealer Marketing Vendors to Prove How They Recover

Recovery Is a Customer Journey Question

A dealer vendor may host a website, feed inventory, route leads, schedule service, send email, or report campaign performance. If one system fails, the important question is not only whether the vendor has backups. It is whether a customer can still find accurate hours, submit a request, reach a person, and receive a response while the service is restored. Recovery evidence shows what the vendor protects, what returns first, which data may be delayed, and how the dealership will operate in the meantime.

Map Critical Workflows and Recovery Priorities

List customer-facing workflows and rank them by harm and dependency. A broken sales form, service scheduler, phone route, or incorrect hours may need a faster workaround than a delayed monthly report. For each workflow, document the system owner, data involved, upstream dependencies, manual fallback, expected recovery time, and acceptable data loss or delay. Do not assume that restoring a database restores a third-party integration or a vendor’s configuration. Recovery priorities should be agreed with sales, fixed ops, BDC, marketing, and leadership.

• Ask what is backed up, how often, where it is stored, and who can restore it.
• Separate configuration, customer records, creative assets, reports, and credentials.
• Define how the vendor identifies the last complete record and handles duplicates after restore.
• Document the dealer contact, vendor incident lead, update cadence, and escalation route.
• Keep a temporary customer-facing message and manual intake process for critical failures.

Request Evidence, Not a Brochure

A recovery plan should include the date and scope of the last test, the scenario exercised, the measured restore time, unresolved issues, and the owner of the next action. The dealership does not need every confidential infrastructure detail, but it does need enough evidence to understand the service it is buying. Ask how the vendor protects data access, verifies restored records, and communicates a partial recovery. If a vendor cannot share a meaningful summary, record the limitation and decide whether the workflow needs a local fallback.

Run a Tabletop With Real Dealer Decisions

A tabletop exercise can test coordination without taking a live system down. Give the team a scenario such as a form outage during a weekend promotion, a stale inventory feed, or a scheduling failure before a busy service day. Ask who detects it, who pauses media, where new requests go, how staff answer customers, what the vendor restores first, and when leadership receives an update. Capture decisions and missing contacts. A realistic exercise reveals more than a generic statement that the vendor is prepared.

Close the Loop After an Incident or Test

After recovery, reconcile records, check duplicate or lost requests, restore paused campaigns deliberately, and communicate the current customer path to staff. Review the timeline, workaround, data impact, vendor response, and prevention action. Add the result to the vendor record and contract review. Recovery is not a once-a-year document. A platform migration, new integration, acquisition, or staffing change can alter the dependency map and make an old test irrelevant.

Recovery evidence gives the dealership a practical answer to a difficult question: how will we continue serving customers while a vendor fixes the system? That answer is part of vendor quality, not an optional technical appendix.