A customer searches for a new SUV on a manufacturer’s website, asks a nearby dealer about stock, books a test drive, and later returns for service. The customer sees one brand. Behind the scenes, the manufacturer, dealer, lender, and repair operation may use separate records. A missing vehicle status or delayed lead handoff can break the experience even when each team is doing its own job.
Salesforce Automotive Cloud is designed to connect those relationships. It adds vehicle records and automotive workflows to Salesforce’s sales and service platform. Its value depends on the data moving between systems, especially the dealer management system (DMS), OEM platforms, and service applications. A familiar CRM dashboard doesn’t solve those dependencies on its own.
This guide explains Salesforce Automotive Cloud for both dealers and original equipment manufacturers (OEMs). It covers what the platform does, how specific vehicle records work, where dealer portals and automotive finance fit, and what the current licensing options mean. It also explains which operational systems still need to stay in place.
TL;DR
Salesforce Automotive Cloud, now also called Agentforce Automotive, connects customer and vehicle records with sales, service, dealer-network, and selected finance processes. Dealers can use it to manage inquiries, find vehicles, book test drives, and follow customer service needs. OEMs can coordinate lead distribution, dealer performance, warranty claims, and ownership information across a wider network. The industry data model separates vehicle specifications from an individual VIN-linked vehicle and its related Asset record. Automotive Cloud is generally a connected CRM layer rather than an automatic replacement for a DMS, ERP, loan servicing platform, or workshop system. Public US pricing starts at $300 per user per month for Sales & Service Core on annual billing. Final fit depends on license entitlements, integration quality, dealer access rights, and the exact workflows required.
What Is Salesforce Automotive Cloud and How Does It Work?
Salesforce Automotive Cloud is an industry-focused CRM product that combines customer relationships with vehicle and asset information. Rather than showing only a lead, contact, and sales opportunity, it can relate the interested buyer to a vehicle model, dealership, test drive, and later service activity. Manufacturers can also use automotive records to work with business partners and manage selected stages of the vehicle lifecycle.
The product’s public name changed in 2026. Salesforce’s automotive release notes call the offering Agentforce Automotive, formerly Automotive Cloud, and describe industry agent features introduced in recent releases. Existing Salesforce documentation still uses Automotive Cloud extensively. Buyers should check the exact SKU rather than assuming the renamed product gives every customer the same AI tools.
The system’s foundation is an automotive data model. Salesforce records can represent a vehicle model and an individual vehicle with a VIN. They can also hold people linked to an asset and events such as a warranty case or service milestone. Apps and dashboards use those records to present a useful view of the vehicle relationship. The Vehicle Console shows vehicle history, milestones, and linked assets. The Asset Console shows work orders, warranties, claims, and other service details. Integrations supply the information that lives elsewhere.
Follow the Vehicle, Not Just the Opportunity
A normal lead may close when the salesperson records a sale. An automotive relationship carries on after the purchase. A customer might return for maintenance, buy a service package, change a lease, or sell the vehicle to another owner. If the CRM remembers only the original opportunity, later staff may need to rebuild the story from several systems.
Automotive Cloud features help users connect those events where the organization has enabled and supplied the required data. For a dealership, the useful outcome might be seeing whether the customer has a service appointment. For an OEM, it could be seeing the dealer involved in a warranty claim. Neither result is automatic without the relevant record relationships and access rights.
The platform therefore sits alongside other applications. A DMS may remain responsible for final inventory status and repair orders. A captive lender may hold the official loan balance. Telematics data may come from an approved provider. Automotive Cloud can organize selected information for staff and customers, but the business still must decide which system is the source of truth.
How Dealers and OEMs Use Automotive Cloud Differently
A dealership’s day is shaped by local demand. Staff handle web inquiries, available cars, trade-ins, scheduled visits, and service appointments. Their questions are immediate: which model does this buyer want, which VIN is available, and who should call next? Salesforce Automotive Cloud for dealers is most useful when it answers those questions using current information from the dealership’s existing systems.
An OEM operates across a wider network. It may own the brand website, distribute leads to independent dealers, manage warranty policies, and review how programs work across regions. Salesforce Automotive Cloud for OEMs needs to represent the manufacturer-dealer relationship as well as the driver-vehicle relationship. Access rules become more demanding because independent dealers may be permitted to view only their own work.
| Business Need | Dealer View | OEM View |
| Vehicle inquiry | Respond and arrange a visit | Route and track the inquiry |
| Inventory | Confirm local stock | Review availability across locations |
| Sales progress | Manage a buyer and sale | Compare dealer and regional results |
| Service | Schedule and track customer visits | Review service programs and trends |
| Warranty | Submit supported claims | Apply coverage and adjudication rules |
| Customer relationship | Serve local owners | Maintain brand-level lifecycle context |
Dealer programs have their own data and approval flows. Salesforce’s dealer performance guidance describes support for sales targets, visits, and related dealer performance work. Those functions are more relevant to a manufacturer or distributor than to a single store that wants to answer website leads.
One Customer, Different Authorized Views
Imagine a customer who sends an OEM inquiry and chooses Dealer A. Dealer A should receive the information needed to respond and record the outcome. Dealer B shouldn’t necessarily see the lead or its notes. The OEM may need a network-level response-time report without exposing unrelated customer details to every dealer. This is an access-design question before it becomes a dashboard question.
Salesforce Automotive Cloud for dealers can be a focused CRM application for an individual dealer group with approved integrations. Salesforce Automotive Cloud for OEMs often includes a portal or other partner arrangement because users from separate companies need controlled access. Licensing a dealer’s internal staff isn’t the same as licensing dozens of dealer organizations to use OEM-owned records.
Neither group should judge the system by feature count alone. The dealer needs enough functions to complete actual sales and service tasks. The OEM needs rules that apply consistently across its network while allowing each dealer to maintain the records it owns.
The Automotive Data Model: Products, Vehicles, and Assets
The data model is the clearest technical difference between a general sales CRM and the automotive product. A vehicle model and a physical car are different things. So are the customer who first purchased a car and the person who currently owns it. Salesforce represents those concepts through related objects instead of assuming that a single product name or account record can hold every detail.
Salesforce’s automotive data model identifies Product, Vehicle Definition, Vehicle, Asset, and related lifecycle objects. Vehicle Definition holds information about a type of vehicle, while Vehicle records describe particular instances. Each Vehicle is associated with an Asset record. That relationship is important when the vehicle has related components or milestones.
| Record | What It Represents | Illustrative Example |
| Product | An item in the commercial catalog | Compact SUV offering |
| Vehicle Definition | Standard model characteristics | Engine and trim specification |
| Vehicle | An individual vehicle instance | A car with a particular VIN |
| Asset | The physical item and its lifecycle | The delivered vehicle |
| Asset Milestone | A dated lifecycle event | Delivery or service event |
| Asset Account Participant | An account linked to an asset | Selling dealer, owner account, or financier |
| Asset Contact Participant | A contact linked to an asset | Driver or service technician |
Why a VIN Needs Its Own Record
An OEM may manufacture thousands of cars with the same model definition. Their model specifications can be shared, but each physical car has its own VIN and history. Salesforce’s Vehicle field reference includes VIN, linked Asset, Vehicle Definition, owner, status, and external identifiers. That makes a vehicle’s current owner or location separate from its general model specification.
In a practical setup, the business should create or map the Asset and Vehicle records as Salesforce documentation requires. It should also preserve the external identifiers used by the DMS or OEM system. Otherwise, imports may create 2 Salesforce vehicles for the same car when its location changes or a dealer uploads a new feed.
Ownership Changes Must Not Erase History
Vehicle information has a longer life than a lead. A vehicle may be sold, serviced, transferred, and resold. The firm needs rules for which owner relationship is current and how older relationships are retained where lawful and necessary. A historical customer association doesn’t automatically give an employee a reason to see that person’s current personal information.
Automotive Cloud features built around a lifecycle work only when these basic records are trustworthy. The data model should be approved before pages, automation, or reports are built. A vehicle dashboard can’t repair a VIN that points to the wrong Asset.
Automotive Leads, Dealer Assignment, and Sales Follow-Up
A manufacturer may capture an inquiry from a model page and route it to a dealer chosen by the customer. The inquiry can include the vehicle of interest and a preferred location. The assigned dealer then needs to confirm availability, contact the buyer, and record whether an appointment or sale results. The two companies need an agreed handoff process rather than separate lead counts that never reconcile.
Salesforce’s lead management documentation covers automotive-specific interests and preferred seller information on leads and opportunities. These records can retain the buyer’s stated preferences as staff move through the sales process. A preference for a model should not be mistaken for proof that an individual vehicle is reserved.
The lead distribution guide describes how dealer groups can receive assigned leads or opportunities through the supported network setup. Each implementation must define how a dealer accepts a lead and what happens if the chosen location cannot fulfill the request. Lead routing is useful only if the owner can act on the record.
Test the Exceptions Before Launch
Consider a customer requesting an electric SUV at Dealer A. The OEM routes the inquiry and expects a response. Dealer A has no suitable stock, but Dealer B has a matching vehicle. Should Dealer A ask for a transfer, refer the customer, or return the inquiry to the OEM? This is a business rule. The CRM should record the agreed outcome and prevent 2 dealers from contacting the person without a clear reason.
For Salesforce Automotive Cloud for dealers, test lead assignment, contact permissions, appointment updates, and disposition codes from an ordinary salesperson’s login. For Salesforce Automotive Cloud for OEMs, also test network reports and reassignment approvals. Report inquiry counts separately from test drives and completed sales so teams can identify where a handoff stopped working.
Do not use a lead conversion percentage as proof of improved revenue unless the firm has a valid baseline and consistent counting method. Leads may be duplicated across brand websites or paid advertising channels. Customer identity matching and consent handling must be designed before those records are shared among businesses.
Inventory Search and the Dealer Management System Boundary
Inventory is often the point where a useful CRM demonstration meets a difficult operating reality. A salesperson can search for an SUV in a preferred color, but an accurate result depends on vehicles being recorded at the right location and marked with the right sale status. The dealer may update stock in its DMS while the manufacturer receives a later inventory feed. Both systems can report different availability if the timing isn’t controlled.
Salesforce’s inventory search explanation says the automotive search framework draws information from Vehicle, Vehicle Definition, Product, Product Item, Location, and related records. It supports criteria such as model, location, fuel type, and color. That feature can make a dealer’s stock easier to search, but it doesn’t guarantee that inventory values match the live DMS at every moment.
Decide Which System Owns Availability
An implementation should map each inventory event to the system responsible for it. A sale can remove a vehicle from available stock. A transfer can change its location. A reservation may temporarily prevent another sale, depending on the dealer’s policies. Define which event changes Salesforce status and how quickly the update should arrive. Don’t label a search result “available now” if the integration supports only a nightly refresh.
| Data Element | Control to Establish |
| VIN or external vehicle ID | One stable match between systems |
| Stock location | Authoritative dealer or site record |
| Availability status | Agreed meaning of sold, held, and in transit |
| Displayed price | Source and approval for the quoted price |
| Transfer record | Event ownership and update timing |
| Refresh timestamp | Last confirmed feed update |
A DMS commonly holds dealership accounting and repair-order transactions along with core operational records. Automotive Cloud features can connect with that information, but a DMS replacement must be justified through a separate review of the actual functions. The CRM should not be described as having replaced payroll, vehicle accounting, parts purchasing, or repair orders simply because related data appears on a page.
For a large OEM, network visibility introduces another level. A dealer may show a vehicle as held for a local customer while the manufacturer still sees it in regional stock. The platform needs a policy for when a dealer’s operational status takes priority. Clear ownership keeps reports useful and avoids sales staff making promises on stale inventory.
Test Drives and Vehicle Service Appointments
Automotive Cloud features include supported appointment workflows, but test drives and repairs need different rules. A test drive may reserve a salesperson, location, and suitable model. A service booking requires a service site and resources that can perform the requested work. Both cases need reliable availability and a way to handle cancellations or changes.
Salesforce’s automotive appointment guide describes scheduling test drives and service appointments for supported users. The configuration draws on appointment and resource capabilities, with license and setup prerequisites. A company should confirm the specific appointment allowances in its contract before estimating how many bookings the process can support.
A Dealer Test Drive Scenario
A customer asks for a test drive of an electric SUV on Saturday. The dealer checks a matching vehicle or model, selects an available appointment slot, and confirms the visit. Staff should know whether that appointment reserves a specific VIN or only a model class. When the requested car is unavailable, the user needs a clear alternative rather than a calendar entry that can’t be fulfilled.
Salesforce Automotive Cloud for dealers can make those activities visible to the sales team. The store should test what happens when a customer reschedules through a website or phones a second employee. Duplicate appointments can create unnecessary customer messages and waste staff time. Where a DMS or scheduling application remains the appointment authority, Salesforce must respect its final status.
A Service Booking Scenario
A vehicle owner requests scheduled maintenance. The dealership needs the correct vehicle and location, and it may need to confirm required parts or workshop capacity outside the CRM. If a repair order is created in the DMS, the CRM should show an approved reference and status instead of independently inventing one. Staff should be able to explain whether a booking is requested, confirmed, or canceled.
An OEM may look at service demand across its dealers, but a local workshop controls daily capacity. Salesforce Automotive Cloud for OEMs should use appropriate aggregate reporting without exposing other dealers’ unnecessary customer records. This difference matters when a manufacturer wants visibility into customer care but doesn’t run the workshop itself.
Warranty Claims, Dealer Performance, and OEM Decisions
Warranty management is a different process from sales lead handling. A dealer identifies a possible covered failure and may submit a claim with repair details. The manufacturer assesses coverage and policy conditions, then records its decision. The system must preserve supporting evidence and explain what happens when a claim is rejected or sent back for more information.
Salesforce’s warranty claim guidance describes manual and rules-based claim adjudication. The available claim model includes related items, coverage, and payment details. Configuring automated decisions still requires a manufacturer to approve eligibility rules for mileage, terms, excluded failures, and relevant service actions.
OEM recall campaigns cover groups of affected vehicles, unlike a single warranty claim. Where licensed, Product Service Campaign records can identify affected models and VIN ranges, coordinate dealer outreach and repairs, and track completion. The OEM should reconcile completion status with dealer service records so unresolved recalls aren’t marked as finished.
Dealer Submission and Manufacturer Review
Imagine a dealer replacing a component on a vehicle that might be under warranty. The service team records the vehicle and defective part, then submits the associated labor and parts information. The OEM claim reviewer checks coverage and supporting records. The result might be approved, denied, or returned for correction. Each decision should remain traceable to the claim and the rule or person responsible.
For Salesforce Automotive Cloud for dealers, the critical requirements are claim creation, visibility into status, and a way to correct rejected information. Salesforce Automotive Cloud for OEMs needs review queues and consistent policy rules across the network. It may also need reports about repeat failures by model or part, subject to the accuracy of incoming dealer records.
The design must account for warranty history after a vehicle changes owner. Some coverage is linked to the asset or terms rather than the current customer. The service advisor should not have to recreate a claim from scratch because the CRM associated the car with the wrong original purchaser.
A manufacturer can also use dealer performance records for programs and visits, but those are distinct from warranty adjudication. Sales targets should not be used as a substitute for claim compliance. The relevant process owners should agree on measures before the OEM compares dealer performance across regions. Otherwise, differences in dealer operating practices may produce misleading rankings.
Captive Finance, Loans, and Lease Relationships
A captive finance organization serves customers who borrow or lease through a vehicle maker’s financing business. The customer may contact a dealer about a car, apply for finance, and later ask about a payment, due date, or end-of-lease options. Those requests span sales and a regulated financial relationship. The CRM can connect some of the context, but access rights and the source of financial figures need separate treatment.
Salesforce’s automotive finance records cover financial account information for vehicle loans and leases. These records can connect the financed asset to the financial account and relevant parties. The data shown to a support representative depends on how the finance system exchanges information with Salesforce.
A Lease Customer Example
Suppose a customer asks whether an existing lease is close to its end date. A service or sales employee may need a verified maturity date and the authorized next step. The loan servicing platform can remain responsible for balances, payment processing, and official statements. Salesforce may display selected values or link the employee to the appropriate process without taking over the lender’s accounting function.
Automotive Cloud features shouldn’t be described as automatically underwriting loans or collecting payments. Those processes need their own licensed capabilities, approved workflows, and applicable controls. If an AI-assisted finance function is proposed, evaluate what action it performs, which records it can read, and when a human must approve the outcome.
The dealership may only need a limited view of the customer’s finance status for a permitted business purpose. The captive lender may need broader information but have stricter obligations for protecting it. Share only the fields needed for the task and retain evidence of access where required. A dealer’s normal CRM permissions shouldn’t grant staff direct access to sensitive credit or payment information merely because the vehicle appears in the same customer record.
For Salesforce Automotive Cloud for OEMs, captive finance creates an added organizational boundary. Manufacturers and lenders may be related companies, yet records can still be subject to different permissions and policies. Design the transfer of information as a controlled integration rather than an assumption that every business unit is one user group.
Connected Vehicles and the Role of AI Agents
Connected vehicles can report permitted technical events from onboard systems or a telematics provider. A manufacturer might receive information relevant to maintenance, while an authorized service team may need a related customer case. The raw event stream isn’t a normal contact record and can arrive in large volumes. Decisions about retention and useful events should come before enabling customer-facing automation.
Salesforce’s connected services setup documents integration with external IoT or telematics providers and relevant automotive service processes. Specific features can require additional entitlements or consumption allowances. The mere presence of a Vehicle record doesn’t mean live telemetry is available for that car.
Turn a Qualified Event Into a Service Action
Consider a hypothetical battery-system warning that a provider sends with a permitted vehicle identifier. The system should verify the event type and whether the customer and vehicle are eligible for the intended workflow. A dealer may then receive a service case or the customer may be notified through an approved channel. The message shouldn’t claim a confirmed fault when the signal only indicates a possible issue.
Salesforce Automotive Cloud for OEMs may use connected data to coordinate selected campaigns or service programs. A dealer that doesn’t receive the event or doesn’t have capacity to act on it needs an exception process. Follow-up should be recorded against the correct asset, with the event’s source and time preserved. Later troubleshooting is difficult if a brief AI-generated summary replaces the original technical context.
Agentforce Automotive also offers AI-supported actions in relevant sales, service, and finance workflows. These depend on licensing, configured data, user access, and tested instructions. Automotive Cloud features don’t become reliable merely because an agent can create a message or suggest a next step. Test the output against approved data and define when a person must review it.
Vehicle location and driver behavior information can be sensitive. Companies must assess permissions, relevant privacy obligations, customer notices, and data sharing across parties. Avoid gathering telemetry unrelated to a defined business purpose. The technology should support a legitimate service task, with a clear way to investigate errors and customer concerns.
Salesforce Automotive Cloud Pricing and License Choices
Salesforce Automotive Cloud pricing is based on the selected edition and licensed users, with additional charges possible for other services. The current US automotive price list names Sales & Service Core at $300 and Advanced at $500 per user per month, billed annually. Sales Max and Service Max each list at $700, while the combined Sales & Service Max is listed at $725. Contract terms and feature rights must be checked in a quote.
| Edition | Published USD/User/Month |
| Sales & Service Core | $300 |
| Sales & Service Advanced | $500 |
| Sales Max | $700 |
| Service Max | $700 |
| Sales & Service Max | $725 |
For 25 users, Core costs $90,000 a year at list price and Advanced costs $150,000, excluding tax and other products. Salesforce Automotive Cloud pricing for partner access may differ from internal staff licensing. The calculation also leaves out DMS integration, migration, training, and support.
Salesforce Automotive Cloud pricing comparisons should evaluate exactly which sales, service, AI, and security functions the buyer will use. Published features and allowances vary by tier. An OEM rollout with external dealers has a different budget from one dealership with 25 internal staff. Quote the actual user populations before comparing annual totals.
Dealer Portals, Access Rules, and Customer Privacy
Partner sites can give authorized dealers access to selected OEM-owned work. Salesforce’s portal licensing guide distinguishes customer and partner Experience Cloud rights, including access to leads and opportunities. An OEM should test dealer-specific visibility before giving partners production logins.
A related product named Automotive Cloud for Dealer has documented ISV partner restrictions. It shouldn’t be assumed to be a standard dealership subscription available to every buyer. Salesforce Automotive Cloud pricing needs to separate internal licenses from external portal arrangements and any qualified dealer-focused offerings.
US dealers that finance or lease vehicles may have duties under the FTC Safeguards Rule. The FTC’s dealer safeguards FAQs explain that covered dealers need a written information security program and address how the rule applies to dealer and OEM relationships. Automotive Cloud features can help apply controls, but software installation alone doesn’t establish compliance.
For Salesforce Automotive Cloud for dealers, check that finance details aren’t visible to unrelated employees. For OEM portals, test that Dealer A cannot open Dealer B’s customer records. Salesforce Automotive Cloud pricing may cover a user’s application access without covering the security work needed to configure those boundaries.
How to Plan an Automotive Cloud Implementation
Begin with one business journey: a lead handoff, an inventory search, a service booking, or a warranty claim. Choose its record owner and source systems. Then configure the required automotive data and permissions in a test environment. Avoid rolling out every automotive process before the first data exchange has been verified.
A practical acceptance test follows a VIN from source import into Salesforce, checks the correct dealer and customer relationship, and verifies a sale or service status change. Test missing updates and duplicate identifiers as well as ordinary transactions. The launch team should record who resolves a failed integration and how staff recognize stale information.
Salesforce Automotive Cloud for OEMs often requires agreement from several dealers on handoff and reporting rules. Salesforce Automotive Cloud for dealers may have a smaller scope but still needs its DMS provider involved. Budget for implementation separately from Salesforce Automotive Cloud pricing and reserve time for ordinary users to test realistic scenarios.
Conclusion: Choose the Scope That Fits the Automotive Business
Salesforce Automotive Cloud is strongest when customer and vehicle records connect to trusted operational systems. Dealers need current leads and service information; OEMs need controlled network coordination. The right implementation keeps the DMS and finance boundaries clear, tests permissions, and buys only the functions needed for approved workflows.
Frequently Asked Questions
What Is Salesforce Automotive Cloud?
It is Salesforce’s automotive CRM offering for connecting customer, vehicle, dealer, sales, and service information. Availability of specific workflows depends on licensing and connected data.
Is Automotive Cloud Now Called Agentforce Automotive?
Yes. Salesforce uses Agentforce Automotive as the newer product name. Automotive Cloud still appears in product pages and technical documentation.
How Is Automotive Cloud Different From Sales Cloud?
It adds industry-specific records and workflows for vehicles, dealers, service, warranty, and related processes. Ordinary Sales Cloud doesn’t by itself provide the full automotive data model.
How Does Automotive Cloud Help Dealerships?
It can connect incoming inquiries, vehicle interests, test drive bookings, and service relationships. Dealers must maintain accurate inventory and customer information through suitable systems.
How Do OEMs Use Automotive Cloud?
OEMs can coordinate dealer leads, monitor program results, and support warranty workflows. Data sharing across independent dealers requires carefully configured access.
Can Automotive Cloud Replace a DMS?
Don’t assume so. A DMS may remain responsible for inventory transactions, repair orders, and accounting. Evaluate those functions separately before considering replacement.
Does Automotive Cloud Support Inventory Search?
Yes. Supported inventory search uses automotive records, vehicle attributes, and locations. Its results depend on current feeds and correctly mapped vehicle identifiers.
Can Salesforce Distribute Leads to Dealers?
Yes. Supported lead distribution connects manufacturer inquiries with dealer groups. Routing conditions and response ownership need to be configured.
Does Automotive Cloud Support Test Drive Appointments?
Yes, with appropriate scheduling setup and entitlements. Dealers must confirm availability of staff, time slots, and the vehicle or model requested.
How Are Automotive Warranty Claims Managed?
Dealers can submit claim details and OEM reviewers can apply approved coverage rules. Decisions require suitable evidence and correct links to vehicle records.
Can Automotive Cloud Use Vehicle Telematics?
Yes, through supported connected-service integrations. Available data depends on providers, entitlements, and privacy permissions. A standard vehicle record alone isn’t live telemetry.
Does Automotive Cloud Support Loans and Leases?
It supports financial account relationships for automotive finance. An external loan servicing platform may remain responsible for payments, statements, and official balances.
What Does Salesforce Automotive Cloud Cost?
Salesforce Automotive Cloud pricing starts at $300 per user per month for Sales & Service Core on public US annual billing. Other editions and external access cost more.
Can Independent Dealers Use an OEM Partner Portal?
Yes, subject to the relevant Experience Cloud licenses and sharing settings. Partner access differs from customer access and should be tested for each dealer.
What Should Dealers and OEMs Check Before Launch?
Verify VIN matching, inventory freshness, authorized record access, and business process outcomes. Test integration failures and establish who maintains each connection.
