Who Owns the Customer Record When Three Dealership Systems Disagree?

Many dealerships never formally decide this. They inherit it, one integration at a time, until the DMS, the CRM, the OEM portal, and sometimes a separate service scheduling tool are all quietly keeping their own copy of who a customer is. Nobody notices until two systems send conflicting messages to the same household in the same week.

What does "owns the record" actually mean at a dealership?

Ownership means which system's value wins when two fields disagree, not which system touched the customer first or which one a manager happens to trust more.

A lead can enter through an OEM portal, get worked by a BDC rep in the CRM, close in the DMS under a slightly different name spelling, and then show up in the service system under a third variation tied to the VIN. Four systems, four partial pictures, zero single owner. "Who owns the record" is really asking: when the phone number in the CRM doesn't match the phone number in the DMS, which one does staff act on, and who decided that in advance.

Why do DMS, CRM, and OEM portals disagree in the first place?

They disagree because each system was built to serve a different department's workflow, not a shared customer identity.

• The DMS exists for F&I and accounting. It cares about transaction history, contracts, and legal accuracy.
• The CRM exists for sales and marketing. It cares about touch history, follow-up cadence, and lead scoring.
• The OEM portal exists for manufacturer reporting. It cares about lead source and attribution, often on its own schema.
• The service system exists for warranty and recall compliance. It cares about VIN-linked history above all else.

Most of these systems were not designed to ask "is this the same person as the one in that other system." They were designed to be correct within their own department, which is a very different thing from being correct across the dealership.

Which system should be the source of truth?

None of them, by default, which is exactly why dealerships need to assign authority by field rather than by platform.

| Field | Best source of truth | Why | |---|---|---| | Contact info (phone, email) | CRM | Updated most frequently by sales and BDC staff | | Deal and transaction history | DMS | Legal and financial record of record | | Service and VIN history | Service system | Required for warranty and recall accuracy | | Lead source and attribution | OEM portal, synced to CRM | Needed for marketing spend accountability |

Treating one platform as the master of everything usually fails, because no single vendor's schema was built to hold legal, financial, marketing, and service data with equal fidelity. The workable model assigns a primary system per field type, documents it, and builds a reconciliation habit around it. This is the kind of mapping exercise we walk dealers through on a diagnostic call, because it's almost never visible from inside the day-to-day workflow.

What happens when sales and service don't talk?

The customer gets contacted based on stale or conflicting data, and the dealership quietly burns trust and marketing spend on a list that was never accurate to begin with.

A customer who already bought a car keeps getting a "we want your trade" email because the CRM record never synced with the DMS close. A customer with an open recall doesn't get the service reminder because the VIN record lives in a system the marketing platform never queried. These aren't edge cases, they're the predictable output of three systems each doing their job correctly in isolation.

The fragility of this setup isn't theoretical. The June 2024 CDK Global cyberattack took core DMS functions offline at thousands of dealerships for about two weeks, and the incident made visible just how centralized and interdependent these systems actually are when something breaks. Separately, the FTC's Safeguards Rule now requires most dealers that finance or lease vehicles, as financial institutions under Gramm-Leach-Bliley, to inventory where customer financial data lives and who can access it (FTC Safeguards Rule guidance). Both point to the same underlying fact: not knowing which system owns a record isn't just inefficient, it's a compliance and continuity risk.

How do you fix this without ripping out your DMS?

You fix it by building an arbitration map, not by replacing the systems that already work for their own department.

1. Audit which system actually holds each core field today, including the ones nobody officially assigned.
2. Assign one primary system per field type, using the logic in the table above as a starting point.
3. Build or buy a reconciliation layer that flags conflicts instead of silently picking the most recent write.
4. Review the map quarterly, because new integrations and new vendors will quietly introduce new conflicts.

This isn't a project you solve with one more integration. It's closer to an honest audit of what your tools can and can't reconcile on their own, which is the exact gap we cover in our AI reality check.

Who should make the final call when records conflict?

A named person or role should own the arbitration map, not a vendor and not a default system setting.

Many dealerships assume their CRM vendor or DMS provider has already solved this because the systems are "integrated." Integration usually means data moves between systems, not that conflicts get resolved correctly. Someone on staff, usually an ops or BDC director, needs explicit authority to say which value wins and to update that rule as the dealership adds tools. Without that person, the informal rule becomes "whoever complains loudest gets their version fixed," which is not a data strategy.

If this sounds like a conversation your dealership has never actually had out loud, that's the first sign it's overdue. A 30-minute diagnostic call is where we start mapping the conflict points.

The three systems will keep disagreeing. That part is structural, not a bug to be patched. What's fixable is whether the dealership has decided, in writing, who wins the argument.