The Questions That Expose Whether a Vendor Understands Your DMS and CRM

Every vendor walking a showroom floor at NADA or Digital Dealer will tell you they integrate with your DMS and CRM. The claim is nearly universal. What is not universal is an understanding of what that actually requires inside a live dealership environment, where CDK Global's DRIVE, Reynolds ERA-IGNITE, Dealertrack DMS, and Tekion each expose data differently, restrict write-back differently, and fail in different ways under load.

The questions below are not gotcha tests. They are the same diagnostic prompts a competent internal IT director or a seasoned fixed ops manager would ask. If a vendor struggles to answer them concretely, that is useful information before you sign a 24-month agreement.

Why does this matter more than it did five years ago?

The stakes for bad integration have risen because more revenue-affecting tools, from AI-driven lead scoring to automated service follow-up, now depend on real-time or near-real-time data accuracy. A vendor who pulls a stale RO feed or writes duplicate customer records into your CRM does not just create cleanup work. They corrupt the data layer that downstream decisions depend on.

CDK Global's third-party access program, the 3PA, and Reynolds and Reynolds' Reynolds Certified Interface program both impose specific data governance requirements that vendors must adhere to. A vendor who cannot name the certification tier they hold under either program has not done the baseline work.

What specific data objects do you read and write, and in which direction?

A vendor who understands your DMS will answer this question by object name, not by category. Reading a customer record is different from reading a repair order, which is different from reading a vehicle inventory unit. Writing an appointment back to the DMS is a different permission level than writing a sold deal. The directionality and the object specificity matter.

For CRM integrations, the same logic applies. Ask which CRM objects the vendor touches: leads, contacts, accounts, opportunities, activity logs, custom fields. Ask whether they create new records or update existing ones, and how they handle duplicate detection. A vendor who has actually built against VinSolutions, DealerSocket, or Elead will know that each handles duplicate logic differently and will say so.

How do you handle integration failures and data drift?

Every integration breaks at some point. CDK performs maintenance windows. Reynolds has known connectivity restrictions on certain legacy store configurations. Tekion's API versioning moves faster than most vendors update their connectors. The revealing question is not whether a vendor has experienced failures but how they detect them and what the dealership sees when they happen.

A vendor with genuine field experience will describe a specific alerting mechanism, a fallback behavior, and a documented recovery process. They will also acknowledge that data drift, where the vendor's database and the DMS slowly diverge because of missed updates, is a real operational problem that requires periodic reconciliation, not just a healthy connection status light.

What should a qualified vendor be able to answer without hesitation?

The following is a practical checklist. A vendor with real integration depth answers these in the first conversation. A vendor who is inflating their capability will deflect, generalize, or promise to follow up.

• Which version of the CDK 3PA or Reynolds RCI program are you certified under, and can you provide documentation?
• Do you use a direct API connection, a middleware layer like Authenticom or InDesign Technologies, or a flat-file extract?
• What is your polling frequency for read operations, and what triggers a write operation?
• How do you handle a customer record that exists in both the DMS and the CRM with conflicting data?
• What happens to queued transactions if the DMS connection drops for more than four hours?
• Have you integrated with our specific DMS version, and can you name a reference store running that configuration?
• Who owns the data governance agreement with the DMS provider, you or the dealer?

That last question is particularly important. Some vendors route dealer data through their own DMS data access agreements, which creates a dependency and a liability exposure that many dealers do not realize until a contract dispute.

How do you validate that the integration is working correctly over time?

Integration validation is an ongoing operational requirement, not a one-time setup confirmation. A vendor who treats the go-live handshake as the end of their integration responsibility will create problems at the worst moments, typically during a high-volume sales event or a fixed ops push when data accuracy has direct revenue implications.

Ask specifically about reconciliation reporting. Ask whether the vendor provides a periodic audit comparing their record counts and field values against what is in the DMS. Ask whether the dealership receives visibility into that reconciliation or whether it is entirely managed on the vendor side. Opacity in this area is a warning sign.

For CRM integrations specifically, ask how the vendor handles activity attribution when a lead touches both CRM-native workflows and the vendor's own system. Duplicate attribution inflates reported performance and makes it nearly impossible to evaluate the vendor's actual contribution to a conversion.

Where do most integration claims fall apart in practice?

In diagnostic conversations with operators across the industry, the breakdown points cluster in three areas: write-back permissions that were never actually established, polling intervals that are far slower than the vendor implied, and a lack of any monitoring that would surface a silent failure. A connection that authenticated successfully six months ago and has been delivering partial data ever since is not an integration. It is a liability.

The Reynolds and Reynolds and CDK environments in particular have historically been restrictive about third-party data access, a dynamic that has been the subject of litigation and regulatory attention. Dealers operating on these DMS platforms should expect vendors to demonstrate specific, documented access rather than asserting general compatibility.

For a structured way to evaluate where your current vendor stack actually stands, the diagnostic process we use with operators starts exactly here, with the data layer, before examining anything else. If you want to understand what your DMS and CRM data is actually making possible for AI-driven applications specifically, the AI reality check covers the preconditions that most vendors skip entirely.

For dealers evaluating lead intelligence tools in particular, the lead intelligence page outlines the specific data dependencies that determine whether a tool can function at all. And if you are assessing a broader vendor stack, the services overview describes how we structure that evaluation.

The National Automobile Dealers Association publishes guidance on data access agreements and dealer rights in DMS contracts that is worth reviewing as a baseline before any integration negotiation. The work done by dealers on the NADA data standards working groups reflects real-world operating experience that vendor sales materials rarely acknowledge.