ADF/XML is the container, not the process
ADF/XML is a structured automotive lead format used in email-based CRM workflows. It can carry shopper information, vehicle details, provider information, comments, and a timestamp. It does not guarantee that the record lands in the right CRM bucket, reaches the right person, or receives a fast response. Those are dealership workflow decisions.
What a usable lead should include
At a minimum, preserve the shopper name, phone, email, preferred contact method when collected, vehicle year/make/model, VIN or stock number when available, campaign name, lead source, comments, and submission time. A lead without vehicle or source context makes the first call harder than it needs to be.
Test the entire handoff
Before launch, send a controlled test lead. Confirm the email arrives, the CRM creates a record, the source is readable, the vehicle is attached correctly, and the record enters the expected ownership or BDC workflow. Keep a simple record of the test and the people who confirmed it.
Plan for the exception
An email can arrive late, be filtered, map to the wrong source, or create a duplicate. Decide who receives a failed-delivery alert and what the fallback is. A simple notification path is better than discovering a problem after a customer has waited.
What to review after launch
Look at delivery status, source consistency, duplicate patterns, first-response time, appointment setting, and outcome data when it is available. The purpose is not to admire the XML. It is to make sure a shopper can get a useful response.
Further reading
Need to look at your own setup?
Start with the current system, the inventory, and the people who work the lead. That makes the next decision much easier.
Start the Conversation