We want to ensure that any lead we capture on your website gets sent in to the CRM appropriately by Safety Net, but there are is a key scenario in where it may seem that we aren't routing them appropriately.
Example: Your store's website, Store A, shares used vehicle inventory with group stores B and C. Your store is a dealer for OEM X and you work leads for their used vehicles out of your CRM. Most of them are on your lot, and the same goes for stores B and C who deal for OEM's Y and Z and work leads out of their own CRM, usually a sublevel instance of yours or the group CRM as a whole.
As you share inventory on your site, leads for vehicles that are at other stores may come in on your site, but you likely have directed your website provider to send those directly to that store's CRM rather than yours, as it may make more sense for that store to work that lead rather than you, even though it came in on through a visit to your website.
Every account that we set up, while we can track multiple domains for you, can only integrate with a single CRM instance and ADF address. When we are tracking a domain that shares inventory with a "sister store", we do not inherently know if the lead we just tracked exists at your location or at a separate rooftop. When we track a lead on a domain, whichever CRM you've directed us to integrate with is the one that we will check to see if the lead is being worked.
When the piece of inventory that lead is based around happens to be one that lives at a different store and as such may already be getting worked in a different CRM, our systems can only check the CRM that is connected your store. This means we cannot check other CRM's in your group if your website has already routed that lead to the sister store's CRM, and as such we will push it through in order to help you choose what to do with it. As mentioned in the example, this most often happens for stores in automotive groups where multiple OEM's are represented and used inventory is shared across the group.
We recognize that this can disrupt your process and confuse your sales team unnecessarily. Thankfully, we have a resolution for dealers on common website providers that instructs our system to restrict sending a lead in on a vehicle unless it is known to be at your location. This is not a default setting as we want you to know exactly what leads are happening on your site. If you would like this solution implemented, please reach out to [email protected] and we will work with our developers to put that solution in place.
Why did Foureyes send me a lead that is being worked at my sister store?
Shared inventory leads across OEM's can get sent to the "wrong" CRM
Written by Seth Morrigan
Updated over 2 weeks ago