CRM · ScoutRV → your CRM

ADF/XML lead delivery

Most CRMs in this industry 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 expects.

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 — a database outage rather than a CRM one — the submission is held in a separate system and replayed once the primary recovers, so the lead is not lost in the gap.
  • Routing is per location and per department. The address that receives service enquiries does not have to be the address that receives sales enquiries, and a group can route each store independently.
  • The address field takes a list, not a single value, so a store mid-migration between CRMs can send to both without picking a cutover date.
  • The ADF carries the unit the shopper was looking at — year, make, model, floorplan, stock number and VIN where we have them — plus trade-in details when the form collected them. Where a shopper did not type their location and it was derived from their connection, the notes say so rather than presenting it as something they told you.
  • A failed delivery raises an alert rather than disappearing into a log.

Questions

ADF/XML lead delivery questions

Which CRMs does this cover?+

Any that accepts ADF 1.0, which is most of them in this industry. If you are not sure, your CRM vendor can confirm whether they take ADF by email — that is the whole requirement.

Can different departments go to different places?+

Yes — per department and per location, and a department can be explicitly set to receive nothing if you handle it elsewhere.

We are switching CRMs. Can we send to both for a while?+

Yes. The destination is a list, so you can run the old and the new in parallel and cut over when you are ready.

Ask us about your stack.

Request a Demo