CRM · ScoutX → DP360
ScoutX and DP360
Leads land in DP360 routed to the right store and the right franchise team, in the format DP360 expects.
How it works
- Leads are written on the Scout side before delivery, so nothing depends on DP360 being reachable at that instant.
- Failed deliveries retry, and the retry re-posts only the failed leg rather than duplicating a lead that already arrived elsewhere.
- Routing supports franchise as well as location, so a Polaris enquiry reaches whoever sells Polaris.
- Scout also serves an inventory feed DP360 can pull for the merchandising side, on its own schedule rather than a push window.
Other integrations
Lightspeed → ScoutX
Lightspeed DMS
Automatic unit sync from Lightspeed across every franchise you carry.
Read more
Motility → ScoutX
Motility
Unit sync from Motility, in either its XML or CSV export.
Read more
Your DMS → ScoutX
SFTP inventory feed
Any DMS that can drop a scheduled file — XML, CSV or pipe-delimited.
Read more
Questions
DP360 CRM questions
Can leads route by franchise rather than just by store?+
Yes — by franchise, by location, or both.
What happens during a CRM outage?+
The lead is stored on our side and retried, and is visible in the Scout admin either way.
Do we reconfigure DP360?+
No. Scout delivers into your existing setup.