Automotive CRM: What Dealership Software Should Cover
A customer submits a lead on Cars.com at 7:40pm. By 7:41 the lead should exist in your automotive CRM with a source, a vehicle of interest, an assigned salesperson, an auto response text and a task that fires in fifteen minutes if nobody has touched it. By the next morning it should be matched against the DMS so the desk knows this person bought a Tacoma from you in 2021, still owes on it, and is four months from equity. Every piece of that chain runs through an integration. None of it runs through the part of the software you look at when you watch a demo.
That is the whole problem with how dealership CRM gets bought. The demo is a tour of screens, and screens are the least differentiated thing in the category. What actually separates one auto dealer CRM from another is whether it reads and writes to your DMS cleanly, whether it can receive every lead source your store already pays for, whether the desk can structure a deal without retyping numbers, and what happens to your customer data on the day you leave. Evaluate those four things first. Interface preference is a tiebreaker, not a criterion.
What an automotive CRM must cover before you compare interfaces
A general purpose sales CRM handles contacts, deals, stages and tasks. A car dealership CRM has to do all of that plus a set of jobs that exist nowhere else in software:
- Ingest ADF/XML leads from every marketplace and OEM feed. Auto-lead Data Format is the industry standard, and the reason your CRM can accept a lead from Autotrader, CarGurus, Edmunds, KBB Instant Cash Offer and the manufacturer's own lead program without custom work. The question is not whether a vendor supports ADF. It is how they parse the non standard fields each provider stuffs into it, and whether duplicate detection across sources works.
- Match a lead to a DMS customer record and a vehicle in inventory. Without that match you have a name, not a customer. With it, you have service history, prior deals, payoff estimates and an equity position.
- Manage the up. Walk-in traffic, phone ups, internet ups and text ups all need to land in the same log with an owner and a timestamp, because the up log is the raw material for every accountability conversation a general sales manager will ever have.
- Desk the deal. Trade, payoff, rebates, lender programs, payment grids, lease versus finance, F&I menu. If this happens in a separate system with separate data entry, you will pay for it in gross and in errors.
- Run structured follow up over years, not weeks. Unsold follow up, sold customer touchpoints, service to sales, lease maturity, equity mining. Automotive is one of the few sales motions where a two year old dead lead is still a live opportunity.
- Stay inside the compliance envelope. Consent capture for texting, adverse action handling, credit application routing, and the access controls and vendor oversight the FTC Safeguards Rule expects of dealers. Ask how the CRM logs consent and who at the vendor can see customer PII.
If a product cannot demonstrate all six with your data, it is a sales CRM being sold into automotive, not an automotive CRM. That distinction matters the same way it matters in other regulated verticals: the general purpose tools look cheaper right up until you discover the vertical workflow lives in a spreadsheet next to them. We walked through the same trap in CRM for Financial Advisors: Redtail and the Alternatives, where the compliance and household modelling requirements do the same job of narrowing the field.
DMS integration decides your automotive CRM more than features do
Your DMS is the system of record for deals, parts, service, accounting and customer master data. Your CRM is the system of engagement. The seam between them is where dealership software projects succeed or fail, and it is almost never discussed honestly in a sales cycle.
Three things to establish before anything else:
Which direction does data flow, and how fast? Read only integration means the CRM can show you DMS data. Bidirectional means the CRM can push a customer, a deal structure or an appointment back. Nightly batch means your desk is working on yesterday's inventory and yesterday's payoffs. Near real time means a sold unit disappears from the CRM's available list before the next customer asks about it. Get the answer in specifics: which objects, which direction, what refresh interval.
What does the integration cost, and who charges it? Major DMS vendors run certified integration programs, CDK's Third Party Access program and the Reynolds Certified Interface among them, and those programs bill for data access. Depending on the vendor and the data set, that can be a monthly fee per interface, a per record charge, or both, and it is typically invoiced by the DMS, not the CRM. A CRM quote of a given price per rooftop can become materially more expensive once the DMS integration fee is added. Ask both vendors, in writing, what your integration line item will be.
Is the integration certified or scraped? Some smaller CRMs get DMS data through screen scraping, a nightly file drop, or a service that logs in as a user. These work until the DMS changes something. Certified interfaces are slower to build and more expensive, and they do not break on a Tuesday.
Here is the practical shape of the market. Cox Automotive owns VinSolutions and Dealertrack DMS, so that pairing is tight by construction. Tekion built its CRM inside its own cloud DMS, which is why its integration story is the cleanest of the group and also why it is the least useful answer if you are not moving your DMS. The product most buyers mean by CDK CRM traces back to Elead, and its relationship to the CDK DMS has been reshaped by ownership changes in recent years. DealerSocket CRM sits inside the Solera portfolio alongside the DMS formerly known as Auto/Mate. Ownership in this category changes hands often enough that you should verify who owns the product and the roadmap on the day you sign, not on the day you shortlisted.
The takeaway is simple and slightly uncomfortable: for most stores, the DMS you already run narrows the automotive CRM shortlist to two or three viable options before you have opened a single demo.
Lead source coverage: the ups you already paid for
Every dealer pays for lead sources. Very few can say, on demand, which sources produced sold units last month at what cost per sale. The CRM is the only place that question can be answered, and it can only be answered if every source lands in the system with an accurate, unedited source tag.
Work through this list with a vendor and ask how each one arrives:
- Third party marketplace ADF leads, including the ones that arrive with the referring source obscured
- OEM lead programs, which frequently carry response time requirements tied to co-op money
- Your own website forms, chat and trade appraisal tools
- Inbound phone, ideally with call tracking that attaches a recording to the customer record
- SMS, including consent state, because a text opt-in captured on the website has to survive the trip into the CRM
- Walk-in ups entered on a tablet at the door
- Service lane opportunities, which is where the highest intent traffic in your building already is
Two failure modes to probe. First, source collapsing: some systems normalise a dozen distinct feeds into "Internet" and destroy your ability to measure. Second, duplicate handling: the same shopper submits on three marketplaces in one evening, and you need one customer record with three source touches, not three customers assigned to three salespeople who each call within the hour.
Response time is the metric that pays. The mechanics of that are not automotive specific, and the general treatment in Sales CRM Software: Pipeline, Lead Routing and Follow-Up covers routing rules, escalation and ownership in a way that transfers directly to a store floor.
Desking is the workflow that pays for the software
Desking is where the CRM either earns its cost or becomes a logging tool. The question is whether a manager can take a customer record, pull the vehicle, apply the trade and payoff, load current lender programs and incentives, produce a payment grid across terms and down payments, print or send it, and have the whole structure carry into F&I and the DMS without anyone retyping a number.
Some CRMs include native desking. Some integrate with a dedicated desking tool. Some pretend a payment calculator is desking. Get a real deal desked in the demo, using your own inventory file, your own lender programs and a trade with negative equity. Watch for:
- Whether rate and residual data is current and maintained by the vendor or maintained by you
- Whether the F&I menu and product pricing lives here or somewhere else
- Whether credit application routing to RouteOne or Dealertrack is native
- How many times a number gets keyed by a human between the desk and the deal jacket
Every retype is a chance to lose gross and a chance to create a compliance error. This is the single highest value thing you can test in a demo, and almost nobody tests it.
Automotive CRM software compared on integration, export and cost
Prices in this category are quoted, not published, and they move with rooftop count, DMS relationship, contract length and whatever the vendor needs to close in the quarter. Treat the cost column below as a shape rather than a number, and get every quote in writing with the DMS integration fee itemised separately.
| Platform | Typical fit | Integration posture | Desking | Export and exit posture to verify |
|---|---|---|---|---|
| VinSolutions Connect | Franchise stores already in the Cox Automotive stack | Tight with Dealertrack DMS and Cox inventory and marketing products | Integrates with Dealertrack desking | Ask for the format and cadence of a full customer and activity export |
| DealerSocket CRM | Franchise and larger independent groups | Broad DMS certified interfaces, plus in-house DMS in the same portfolio | Native desking with inventory and equity tooling | Confirm whether equity and appraisal history exports with the customer file |
| CDK CRM (Elead lineage) | Franchise stores, heavy BDC operations | Long history of certified DMS interfaces across vendors | Native desking, strong BDC and call workflows | Verify ownership and roadmap before a multi year term |
| Tekion | Stores willing to move CRM and DMS together | Single platform, no integration seam by design | Native, inside the same data model | Cleanest data model, so ask specifically what leaves with you |
| DriveCentric | Stores prioritising engagement, video and messaging | Certified DMS interfaces, lighter back office footprint | Integrates rather than owning desking | Confirm message and consent history is exportable, not just contacts |
| ProMax, AutoRaptor and similar | Independents and small groups | Varies by DMS, ask whether certified or file based | ProMax has native desking and compliance tooling | Smaller vendors are often more flexible on export terms, get it in writing |
| Reynolds CRM | Reynolds DMS stores | Native to the Reynolds stack | Native | Reynolds interface policies are strict, model exit cost early |
Two honest notes about reading that table. First, no row is a recommendation, because the right answer is determined by your DMS, your OEM requirements and your group structure, not by a feature grid. Second, the exit column is the one people skip and later regret.
Data export rights: read the contract, not the marketing page
Your customer list, deal history, appraisal history, call recordings, text threads and consent records are among the most valuable assets in the store. The contract decides whether they are yours in practice.
Ask for these in writing before signing:
- Scope. Which objects can you export? Contacts and deals is the easy answer. Activity history, notes, call recordings, SMS threads with timestamps and consent state, appraisal and trade history, and email logs are the hard ones.
- Format and cadence. Self service export on demand, or a support ticket and a fee? CSV, or a documented API? Can you run it monthly as a standing backup?
- Termination window. How many days after termination can you still retrieve data, and does the vendor charge a "data extraction fee"? That fee is a real line item at some vendors and it is negotiable at signing, not at exit.
- Vendor access to your PII. Under the FTC Safeguards Rule you are responsible for overseeing service providers who handle customer information. Ask who at the CRM vendor can query your data, and what their access logging looks like.
A useful rule: if you cannot pull a complete export yourself, on a Tuesday, without asking anyone's permission, you do not fully control your data. The broader version of this argument, including what portability means when the vendor hosts everything, is in Cloud Based CRM Software: How to Choose and What Comes Next.
Cost per rooftop: building the number the quote does not show
The per rooftop price is a fraction of the real number. Build the total yourself, per store, per month:
| Cost line | Where it comes from | How it gets missed |
|---|---|---|
| CRM license | The CRM vendor quote | This is the only line most buyers compare |
| DMS integration fee | Your DMS vendor's certified interface program | Billed separately, often discovered after signature |
| Implementation and data migration | CRM vendor or a partner | Quoted as one time, frequently runs long |
| Texting and calling | Bundled or a separate vendor | Per message and per minute charges scale with volume |
| Equity mining and appraisal tools | Add-on modules or separate vendors | Sold as included in the demo, priced as an add-on in the order form |
| Training and ongoing admin | Your payroll | The BDC manager who becomes the accidental CRM admin |
| Contract length and escalators | The order form | Three year terms with annual uplifts are common |
Multiply by rooftops and you get a number that is often two to three times the headline license cost. That is not a scandal, it is just how the category prices, and it is why a group with eight stores should model the total before falling in love with a product.
The other half of the cost equation is adoption. Software nobody uses is the most expensive line on the list. Automotive has a specific version of this problem, because salespeople log activity to satisfy a manager rather than to serve a process, and the data goes soft within a quarter. CRM Strategy: Making the System Stick After You Roll Out covers the operating habits that keep a system honest after launch, and they apply on a showroom floor as well as anywhere else.
A demo script that exposes the differences
Run every vendor through the identical sequence, with your data, in this order:
- Send a real ADF lead from two different marketplaces for the same shopper. Show me one customer, two sources, one owner.
- Pull that customer's DMS history live. Not a slide, a live pull, with the refresh interval stated out loud.
- Desk a deal with a trade carrying negative equity and a manufacturer rebate. Count the retypes.
- Show the up log for a Saturday, by salesperson, with phone, walk-in and internet separated.
- Show me every sold customer in the last 36 months who is now in a positive equity position on a unit you have in stock.
- Export everything from step 1 through 5 to a file, in the demo, without a support ticket.
Step 6 is the one that ends sales cycles. If a vendor cannot do it live, you have learned the most important thing about the relationship.
Where Skopx fits around the store, and where it does not
Plainly: Skopx is not an automotive CRM, and this is not a pitch to replace one. Skopx does not desk deals, does not ingest ADF leads, does not manage an up log, and does not integrate with every DMS. If you are shopping for dealership CRM software, buy dealership CRM software from the list above.
What Skopx is, is an AI workspace that connects nearly 1,000 tools a company already uses, including Gmail, Slack, Google Sheets, QuickBooks, Stripe, HubSpot and Google Analytics. In a dealership, that maps to the ops layer around the store rather than the retail floor: the email threads with lead vendors and lenders, the spreadsheets the controller and the marketing manager actually work in, the accounting system, and the marketing spend questions that never fit neatly into a CRM report.
Concretely, the questions Skopx is built for sound like this. What did we spend with each lead provider last quarter according to the invoices in the accounting system, and how does that compare to the budget in the sheet? Which vendor invoices arrived this month that we have not seen before? What did our website traffic do after the radio buy started? Where are the open threads in the general manager's inbox that nobody has replied to in five days? Skopx answers with cited data from the connected tools, so you can click through to the invoice or the message rather than trusting a number on a screen.
It also produces a morning brief, runs an insights engine that surfaces anomalies such as a spend line moving sharply against its own history, and lets you build automations by describing them in chat rather than configuring a builder. One example that fits a dealer group's back office:
Monthly lead vendor spend reconciliation
First business day
Runs monthly
Pull vendor invoices
Lead providers and marketing vendors from accounting
Read budget sheet
Planned spend per vendor per rooftop
Compare to plan
Flag any vendor over or under plan
Scan inbox for new vendors
Invoices with no prior history
Send variance summary
To the GM and controller with links to each invoice
That is the honest boundary. Sold units, gross per copy, closing ratio by source and desk performance belong to the CRM and the DMS, and you should get those answers there. The finance, email and spreadsheet questions around them are where a general workspace helps. If you want to see the automation side, workflows shows how they get built from a description, and pricing is Solo at $5 per month and Team at $16 per seat per month, with BYOK so you bring your own AI key for any major model at zero markup. Two adjacent pieces are worth reading if that is the layer you care about: Sales Analytics CRM: Get Answers Without Building Reports for the reporting habit, and Accounting Automation Software: What to Automate First for the back office sequence.
Frequently asked questions
Do I need an automotive CRM, or can I use a general sales CRM?
If you sell vehicles at retail, you need an automotive CRM. The deciding factors are ADF lead ingestion, DMS customer and deal matching, desking, and long horizon follow up built around ownership cycles. A general tool can be bent into shape for a very small independent lot, but the moment you are paying for marketplace leads and running an equity mining program, the vertical product costs less in total than the workarounds.
How much does automotive CRM software cost per rooftop?
Vendors quote rather than publish, and the license is only part of it. Build the number from the license, the DMS certified interface fee, implementation and migration, texting and calling usage, any equity mining or appraisal add-on, and the internal admin time. Model it over the full contract term including annual escalators, because three year terms are the norm in this category.
Should I let my DMS vendor pick my CRM?
Not automatically, but do not pretend the DMS is irrelevant either. The DMS determines integration quality and integration cost, which are the two variables that matter most. A same vendor pairing is usually the smoothest and rarely the cheapest. An independent CRM on a certified interface is a perfectly good answer as long as you have the integration fee in writing before you sign.
What should I check about data export before signing?
Check scope, format, cadence, termination window and fees. You want the ability to export contacts, deals, activity history, notes, call and text records with consent state, and appraisal history, in a documented format, on demand, without a support ticket. Negotiate any data extraction fee at signing. After termination you have no leverage.
How do I compare DealerSocket CRM, VinSolutions and CDK CRM fairly?
Run all three through the same demo script with your own data: duplicate lead handling from two marketplaces, a live DMS pull with the refresh interval stated, a desked deal with negative equity and a rebate, a Saturday up log by salesperson and source, an equity list matched to current inventory, and a full self service export at the end. Score the six steps, not the interface. Then add the DMS integration fee to each quote before you compare price.
What does Skopx do for a dealer group?
It connects the tools around the store, email, spreadsheets, accounting, marketing and analytics, and answers questions across them with cited data, plus a morning brief, an insights engine and chat built automations. It is not a CRM, it does not desk deals, and it does not connect to every DMS. Use it for the back office and marketing spend layer, and keep the retail workflow in your automotive CRM.
Skopx Team
The Skopx engineering and product team