CRM · ScoutX → your CRM
ADF/XML lead delivery
Most dealership CRMs accept ADF, the standard lead format. If yours does, it is already supported — you give us the address and leads arrive in the shape your CRM parses.
How it works
- Leads are written on the Scout side before any delivery is attempted. Delivery is a second step, which is why a CRM outage delays a lead rather than losing it.
- If the write itself fails — an infrastructure outage rather than a CRM one — the submission is held separately and replayed once things recover, so the lead is not lost in the gap.
- Routing is per location and per department, which in a multi-franchise store is what puts a Polaris enquiry in front of whoever sells Polaris rather than in a shared queue nobody owns.
- The destination field takes a list, so a store mid-migration between CRMs can send to both without picking a cutover date.
- The ADF carries the unit of interest — year, make, model, stock number and VIN where we have them — plus the trade-in when the form collected one.
- A failed delivery raises an alert rather than disappearing into a log.
Other integrations
Lightspeed → ScoutX
Lightspeed DMS
Automatic unit sync from Lightspeed across every franchise you carry.
Motility → ScoutX
Motility
Unit sync from Motility, in either its XML or CSV export.
Your DMS → ScoutX
SFTP inventory feed
Any DMS that can drop a scheduled file — XML, CSV or pipe-delimited.
Questions
ADF/XML lead delivery questions
Which CRMs does this cover?+
Any that accepts ADF 1.0, which is most of them. Your CRM vendor can confirm they take ADF by email — that is the whole requirement.
Can leads route by franchise?+
Yes — by franchise, by location, by department, or a combination.
We are switching CRMs. Can we send to both?+
Yes. The destination is a list, so you can run both in parallel and cut over when ready.