Automotive Customer 360: From Lead to Vehicle Ownership

OEM marketing generates a lead — through digital advertising, a configurator session, or a test drive request — and hands it to a dealer for follow-up. From the OEM's perspective, this handoff is often the end of its visibility into that customer. What the dealer does with the lead, how quickly they respond, whether the customer ever converts, and on what terms, frequently never makes it back into an OEM-level system in a structured, timely way.

This creates two problems. The OEM cannot accurately measure marketing effectiveness, because conversion data is either missing or arrives too late and too aggregated to attribute to a specific campaign or lead source. And the customer experience itself degrades, because a customer who engaged with OEM marketing and then walks into a dealership is often treated as a completely new, unknown prospect, with no continuity between the digital engagement and the showroom conversation.

Fixing this requires a lead and customer identity model shared between OEM and dealer systems, with a clear, timely feedback loop on lead status and outcome. This does not require the OEM to control the dealer's sales process. It requires visibility into outcomes, structured well enough to inform both marketing decisions and the next customer interaction.

A single vehicle can be sold by one dealer, serviced at another, sold again as a used vehicle through a third, and serviced by an independent shop that reports nothing back to the manufacturer at all. Each of these events generates data that is relevant to understanding that vehicle's condition, warranty status and service needs, but the data rarely follows the vehicle across these transitions.

This matters most at points of ownership transfer and warranty claims. A dealer evaluating a trade-in, or a service advisor assessing a warranty claim, benefits enormously from a complete vehicle history — not just what happened at their own location, but the full record across every dealer and every owner. Without it, decisions are made on partial information, warranty claims are harder to validate, and the customer is asked to repeat information the manufacturer should already have.

Building a genuine vehicle 360 means anchoring vehicle history to the vehicle identification number as the durable identifier, with service, warranty, ownership transfer and, where available, telematics data all linked to that identifier regardless of which dealer or system originated the record.

Warranty programmes are designed and funded by the OEM but executed almost entirely by dealers and independent service networks. This creates a structural tension: the OEM needs accurate, timely warranty claim data to manage cost and detect quality issues, while dealers need fast, low-friction claim approval to keep service operations moving and customers satisfied.

When claim data flows slowly or inconsistently from dealer service systems to the OEM, two things suffer. Warranty cost management becomes reactive rather than predictive, because the OEM only sees a clear pattern of a component failure well after it has already affected a large number of vehicles. And dealers experience friction and delay in claim approval, which they pass on to customers as a slower, less satisfying service experience.

A shared service and warranty data model addresses both sides. Faster, more structured claim data gives the OEM earlier visibility into emerging quality issues, which is directly useful for supplier management and proactive campaigns. And a claims process built on shared, validated vehicle and customer data reduces the manual back-and-forth that currently slows approval down.

Captive finance arms typically operate on separate systems from sales and service, for understandable regulatory and risk-management reasons, but this separation often goes further than it needs to. A dealer working with a customer approaching lease-end has no visibility into that customer's finance status unless the customer volunteers it, and marketing has no ability to time a renewal or trade-in offer against actual lease maturity dates.

This is a missed commercial opportunity as much as a customer experience gap. Lease-end is one of the most predictable and valuable moments in the automotive customer lifecycle, and it is entirely knowable in advance from finance data. Where that data is not connected to sales, service and marketing systems, appropriately and with the right compliance controls, the business loses the ability to act on the single most reliable trigger it has for a repeat purchase conversation.

This does not require merging finance systems into the customer platform wholesale. It requires exposing the relevant, compliant signals — lease maturity date, payment status where permitted, finance product held — to the systems where sales and marketing can act on them, with governance appropriate to financial data.

Dealers are independent businesses, and the customer relationship at the point of sale and service is, commercially, theirs. OEMs cannot simply mandate access to dealer customer data without addressing the legitimate concern that this could be used to disintermediate the dealer, redirect service business, or shift commercial leverage in the OEM's favour.

A workable customer 360 model has to be built around this reality rather than against it. That typically means defining clearly what data flows from dealer to OEM, what flows from OEM to dealer, and what stays local to the dealer, with governance and commercial agreements that make the exchange sustainable rather than adversarial. The OEM's interest is aggregate visibility, quality signals and marketing effectiveness; the dealer's interest is not losing control of the relationship it worked to build. Both can be served by the same data model if the boundaries are set deliberately.

Where this tension is ignored, the usual outcome is a data-sharing agreement that exists on paper but is not honoured in practice, because the underlying incentives were never actually reconciled. Where it is addressed directly, both OEM and dealer end up better equipped to serve the customer, because neither is operating on a partial view of the relationship.

AX3 approaches automotive customer 360 as a shared data and governance problem that spans OEM, dealer and captive finance systems, rather than as a single CRM rollout to one party. That starts with a common customer and vehicle identity model, defined data-sharing boundaries that respect dealer commercial interests, and integration across Automotive Cloud, Experience Cloud, Field Service and Data 360 to connect lead, vehicle, service, warranty and finance data without requiring any party to give up ownership of the relationship they are entitled to.

Done well, this produces a customer experience where a person's history with the brand — the lead, the purchase, the service visits, the finance agreement — is recognisable regardless of which dealer or channel they engage through next, without requiring the OEM to take over the dealer relationship to achieve it.