The Question Most Dealerships Never Think to Ask
When an AI chat vendor pitches your store, the demo is usually polished. The bot answers inventory questions, handles trade-in inquiries, routes leads to the right salesperson. It looks like the future of your BDC.
Then you ask whether the platform is eligible for your OEM's digital co-op program — and the room goes quiet.
That silence is expensive. OEM digital programs exist to help dealers fund exactly this kind of technology investment, but the reimbursement only flows when the vendor meets program-specific technical and compliance requirements. Most AI vendors selling into automotive have never been inside one of those requirement documents. They don't know what ADF/XML means in a practical pipeline context. They haven't mapped their data outputs to a DMS record structure. And they certainly haven't navigated the certification experience that OEM approval workflows demand.
This post is a buyer's guide. Use it before you sign anything.
Why OEM Digital Programs Complicate the Vendor Decision
OEM digital programs aren't just marketing co-op with a technology label slapped on. They are structured reimbursement frameworks with defined vendor tiers, technical benchmarks, approved platform lists, and audit requirements. The OEM wants assurance that dealer technology investments are consistent, measurable, and data-compliant across the network.
That means your AI vendor has to demonstrate more than a good conversion rate on demo traffic. They need to show:
- How their platform outputs lead data and whether that output conforms to industry-standard formats
- Whether their integration points map cleanly to the systems your store already runs
- How their reporting satisfies OEM audit or co-op substantiation requirements
- That their data-handling practices meet the compliance thresholds the program demands
Dealers who skip this evaluation phase often discover the problem at the worst possible moment — mid-reimbursement cycle, after the contract is signed and the platform is live.
The ADF/XML Question: Don't Let a Vendor Wave It Away
ADF/XML — Auto-lead Data Format — is the lingua franca of automotive lead delivery. It is the standard format that connects a lead source to a CRM, and it is the format most OEM programs expect when they require verified lead attribution data.
When you evaluate an AI chat vendor, the ADF/XML conversation should be specific:
Does your platform generate ADF/XML-compliant lead records natively, or does it depend on a third-party middleware layer? Middleware adds latency, adds a failure point, and adds a vendor relationship you'll have to manage. Native ADF/XML output is the cleaner answer.
What fields do you populate, and are they complete? An ADF/XML record that's missing vehicle interest data, source attribution, or contact qualification fields is not a complete lead record. Some platforms generate technically valid XML that is functionally incomplete for OEM reporting purposes.
Can you provide a sample record for review? Any serious automotive AI vendor should be able to hand you a sanitized ADF/XML output file within 24 hours of the request. If they can't, that tells you something about how production-ready their pipeline actually is.
The right vendor won't treat this as a gotcha question. They'll treat it as a baseline expectation — because in automotive, it is.
DMS Integration: Depth Matters More Than Brand Name
Nearly every AI vendor will tell you they integrate with your DMS. The meaningful follow-up is: at what depth?
Surface-level integration often means the platform can pull vehicle inventory for display purposes. That's useful for a chat widget, but it's not what OEM digital programs — or your operations team — actually need.
Deep DMS integration means bi-directional data flow: the AI platform can write qualified lead records directly into your CRM layer, can read real-time inventory status including in-transit units, can access service appointment availability, and can pass structured data downstream without requiring manual re-entry by your BDC staff.
Ask these questions directly:
- Do you write lead records to the DMS, or only to a separate CRM that then syncs?
- How do you handle DMS credential management and security?
- What is your documented integration process with the specific DMS our store runs?
- What happens to our data pipeline during a DMS version update or migration?
Vendors who have genuine DMS integration experience will answer these fluently. Vendors who have bolted on a generic API connector will hedge, defer to their integration team, or describe a process that clearly involves significant manual configuration on your store's side.
Co-op Eligibility: Get It in Writing Before You Commit
Co-op reimbursement documentation requirements vary by OEM program, but the pattern is consistent: the OEM will want proof that the vendor is approved, that the spend falls within eligible categories, and often that the platform meets defined performance or compliance benchmarks.
Ask your prospective AI vendor for their co-op substantiation package. This should include documentation of their approved vendor status within the relevant OEM program, a breakdown of which platform features are co-op-eligible versus which are not, and guidance on how to submit claims correctly.
If the vendor responds with confusion about what co-op substantiation means, or if they tell you they'll "figure it out with you" after the contract is signed, that is a meaningful red flag. An automotive-experienced vendor has been through this process before. They know the documentation trail. They can accelerate your reimbursement cycle rather than complicate it.
TCPA Compliance Is Not Optional and Not Negotiable
AI-powered chat and messaging platforms touch consumer contact in ways that carry TCPA exposure. The Telephone Consumer Protection Act governs how automated systems can contact consumers — and the regulatory environment around AI-assisted outreach has tightened.
Your vendor evaluation should include a direct conversation about consent capture. How does the platform document consumer opt-in at the moment of lead capture? How is that consent record stored, timestamped, and retrievable in the event of a dispute? What is the vendor's documented policy on contacting consumers via SMS through the platform?
Consent architecture is not a legal formality. It is operational infrastructure. A dealership that deploys an AI chat platform without verified consent documentation is absorbing TCPA liability that the vendor may not share.
Why Most AI Vendors Can't Answer These Questions
The AI vendor market is large, well-funded, and moving fast. Most vendors entering automotive from adjacent verticals — insurance, real estate, general retail — carry strong general-purpose conversational AI capabilities and genuinely weak automotive program experience.
OEM digital program requirements, ADF/XML pipeline architecture, DMS integration depth, and co-op substantiation processes are not things you learn from a product roadmap. They come from years of operating inside the automotive retail ecosystem, building integrations under real program constraints, and carrying live certifications through renewal cycles.
InWork Global brings 10+ active OEM certification experience to every dealership engagement. That experience reflects engineering work done inside the frameworks that matter — not described from the outside, but built within them. Combined with US CTO oversight on every engagement and a 20-year engineering legacy, it is the difference between a vendor who can demo well and a vendor who can deploy correctly.
What a Rigorous Evaluation Looks Like
Before your next vendor conversation, prepare a short technical brief that covers the specific OEM program your store participates in, your current DMS and CRM stack, and your TCPA consent management process. Send it to prospective vendors ahead of the call and ask them to come prepared to address each point specifically.
The vendors who come back with specific, documented answers — not general assurances — are the ones worth your time.
OEM digital programs represent real capital for dealership technology investment. The vendors who earn a place in those programs earn it through technical discipline, compliance depth, and operational experience. That bar is worth holding.