Salesforce for Automotive OEMs and Dealers
Automotive relationships revolve around the vehicle as much as the person. Here is how Salesforce links buyers, owners and vehicles across OEM and dealer.
In automotive, the customer relationship is shaped by three parties: the manufacturer or importer, the dealer, and often a finance provider. The vehicle sits at the centre. It is sold, serviced, financed, recalled and eventually resold, sometimes to a buyer the original dealer never meets. Most of the data needed to communicate well exists, but it is spread across OEM systems, dealer management systems (DMS), finance platforms and connected-vehicle services.
Engagement and data challenges
- Lead hand-offs between OEM and dealer. Leads from the brand website reach dealers slowly or without context, and the OEM rarely learns the outcome.
- The person-vehicle relationship changes. Owners sell cars, households share them, company fleets assign drivers. A model that links a vehicle to one Contact forever goes stale.
- Service retention. After the warranty period, many owners move to independent workshops. Timely, relevant service reminders help keep them.
- Recalls and safety notices. These must reach the current owner reliably and are not marketing.
- Dealer data quality varies. Each dealer captures customer data differently, so OEM-level reporting is inconsistent.
Use cases mapped to Salesforce
Lead distribution to dealers
Flow routes brand-site leads to the right dealer by location and model, tracks acceptance and reports outcomes back to the OEM.
→Owner and driver identity
Data Cloud (now branded Data 360) links people across OEM, dealer and finance records and keeps current ownership visible.
→DMS and OEM system integration
Sales, service history and vehicle data synchronised from dealer systems through an integration layer.
→Service reminder programmes
Scheduled segments based on last service date, mileage estimates and warranty status drive reminder journeys.
→Test drive and handover journeys
Booking confirmations, reminders and post-handover onboarding for new owners.
→Modelling vehicles and ownership
A reliable data model is the foundation. Treat the vehicle as its own record keyed by VIN, and model ownership as a relationship with start and end dates rather than a field on the vehicle. That lets you message the current owner, keep history for the previous owner and represent fleets where a company owns the vehicle and a driver uses it. Salesforce offers Automotive Cloud with vehicle and ownership-oriented data models; whether it fits depends on your scope and licensing, and the same principles apply if you build on standard or custom objects. The guide to designing a data model that scales covers the trade-offs.
Example: selecting vehicles due for service
The query below is a sample for a Marketing Cloud Query Activity. It assumes a Vehicles_DE data extension with one row per vehicle, including the current owner's key in OwnerSubscriberKey, LastServiceDate and an OwnershipEndDate that is empty for current ownership, and an Owners_DE keyed on SubscriberKey with a ServiceRemindersOptIn flag. It selects vehicles whose last service was between 11 and 12 months ago. Your actual intervals, field names and consent logic will differ, and you would test it before use.
SELECT
v.VIN,
v.OwnerSubscriberKey AS SubscriberKey,
o.EmailAddress,
v.Model,
v.LastServiceDate,
v.PreferredDealerCode
FROM Vehicles_DE v
INNER JOIN Owners_DE o
ON o.SubscriberKey = v.OwnerSubscriberKey
WHERE v.LastServiceDate >= DATEADD(MONTH, -12, GETDATE())
AND v.LastServiceDate < DATEADD(MONTH, -11, GETDATE())
AND v.OwnershipEndDate IS NULL
AND o.ServiceRemindersOptIn = 1Data, consent and compliance considerations
Recall and safety notices are operational communications with their own legal basis and should not depend on marketing consent; keep them separate from promotional sends and make sure they reach the current registered owner. Service reminders sit in between, so agree with your legal team how they are classified. Connected-vehicle data (location, driving behaviour) is particularly sensitive; collect only what a clear purpose requires and be transparent about it. India's DPDP Act and, for UK or EU customers, GDPR apply to owner and prospect data, and data shared between OEM and dealers needs a clear agreement on who controls it. This is general guidance, not legal advice.
Integration landscape
Dealer management systems (often several different ones across a network), OEM vehicle and warranty systems, finance and leasing platforms, connected-vehicle platforms, website configurators, test drive booking tools and call centre systems. Dealer data often arrives in nightly batches and needs standardising before it is trusted; leads and bookings benefit from near real-time integration.
How GeekMidst would start
- 01
Agree the operating model
Who owns the customer relationship at each stage between OEM, importer and dealer, and what data each may see.
- 02
Design the vehicle and ownership model
VIN-keyed vehicles, dated ownership and fleet relationships, tested with real sample data.
- 03
Integrate one data source well
Typically the main DMS or the OEM lead source, with standardisation and reconciliation.
- 04
Launch lead distribution or service reminders
Whichever offers the clearest value, with a control group for measurement.
- 05
Extend across the network
Onboard further dealers and data sources once the pattern is proven.
Questions we hear
Should the OEM or the dealer own the customer record?
How do we keep ownership current when cars are resold privately?
Do we need Automotive Cloud?
Connect vehicles, owners and dealers
Tell us about your dealer network, systems and the customer moments you want to improve. We will suggest a practical first phase.
