Index
Why a generic CRM doesn't work well for a used car dealer
Generic CRM vs automotive-specialised CRM
What an automotive CRM needs to be able to do
When it makes sense to implement a CRM and when it doesn't
How to evaluate a CRM before purchasing it
How many fields are enough: the rule of seven
The right pipeline for a used car dealership
How to prioritise leads without relying on gut feeling: basic lead scoring
How to merge the same buyer arriving through several channels
How to log calls without turning it into bureaucracy
Why loss reasons are the most valuable data in the CRM
How to migrate from Excel without importing the chaos
The CRM on mobile: why it's the key to adoption
How to get the team to use it every day
The metrics that actually help you make decisions
More than 750 dealerships already use Dealcar for their daily operations
Frequently asked questions
Why a generic CRM doesn't work well for a used car dealer
A generic CRM (Salesforce, HubSpot, Zoho in their standard configuration) is designed for sales processes with long cycles, multiple contacts within the same company and complex qualification stages. The sales process for a used car doesn't work like that.
At a used car dealer, the sales cycle is short (days or weeks, not months), the buyer is always an individual, the product is unique and one-of-a-kind (each car is its own file), and the inbound channels are multiple and simultaneous: car portals, WhatsApp, phone calls, the dealer's own website and walk-ins. A CRM that doesn't automatically link the lead to the vehicle of interest, doesn't know which cars the dealership has in stock or doesn't centralise WhatsApp alongside the other channels creates more manual work than it saves.
Without a CRM, the information lives in the portal's inbox, in the salesperson's WhatsApp, in an Excel sheet or in the memory of whoever handled the call. When that salesperson isn't around, the information disappears with them. The real difference isn't having the data: it's having it accessible, structured and connected to the actions that need to be taken.
Generic CRM vs automotive-specialised CRM
Generic CRMs are powerful and flexible, but they need configuring to fit the way a used car dealer operates. That configuration takes time and can turn into a project that's never quite ready.
An automotive-specific CRM comes preconfigured for the industry's logic: opportunity stages match the actual phases of a car sale (enquiry, visit, test drive, negotiation, finance, delivery), records fields include vehicle details, and reports are geared towards the metrics that matter in a dealership.
The advantages of a specialised one are a shorter implementation time, a gentler learning curve for the team (the language and processes match day-to-day work) and more specific support from people who understand how the business operates.
The advantages of a generic one are greater flexibility if there are very specific processes that don't fit the predefined structure, a broader ecosystem of integrations and, in some cases, a lower price on entry-level plans.
For a dealership selling fewer than 50 cars a month with no existing tech setup, an automotive-specialised CRM makes more sense. For one with very particular processes or already integrated into a specific tech ecosystem, it may be worth evaluating the generic ones.
Read also what a DMS is in the automotive sector and how it differs from a CRM.
What an automotive CRM needs to be able to do
An automotive CRM has to solve five specific operational problems.
The first is centralising all inbound channels. A lead from Coches.net, a WhatsApp message about the same car and a call from the same buyer need to create a single file, not three separate records.
The second is automatically linking the lead to the vehicle of interest. Knowing that "Pablo García is interested in an SUV" is less useful than knowing that "Pablo García asked about the Kia Sportage registration 1234-XYZ, price 18,500 euros, 67,000 km".
The third is managing tasks and reminders. The next step in every conversation needs a date and an owner. A CRM that doesn't generate automatic reminders depends on the salesperson remembering when to call, which consistently fails at busy times.
The fourth is genuine mobile access. If the CRM only works well on the office computer, the salesperson puts off updates and the context gets lost.
The fifth is tracking where each sale came from: which portal, campaign or channel generated each closed sale.
When it makes sense to implement a CRM and when it doesn't
A CRM makes sense when there's enough lead volume for manual management to be a real problem. For a dealership receiving between 5 and 10 leads a week, Excel may be enough if the process is clear. From 15 or 20 leads a week, managing without a system starts to cause visible losses.
It also makes sense when there is more than one person managing leads. If the same salesperson handles all communications, the loss of information is lower. When there are two or more people, without a shared system, leads get duplicated, overlap, or are lost in conversations.
It doesn't make sense if the business has no defined follow-up process and nobody is going to review the data. An empty or poorly updated CRM is worse than having none: it gives a false sense of control without any real benefit.
How to evaluate a CRM before purchasing it
Before committing to any tool, there are five questions that need answering during the demo or trial period.
How long does it take to log a new lead? If it's more than two or three minutes, there's too much friction. The CRM has to make the work easier, not add steps.
How do leads from the portals come in? If they have to be copied manually from the portal's email into the CRM, the system isn't integrated and the manual work causes errors and delays.
Can I see on one screen how many active leads I have and what stage each one is at? The main dashboard should give you that view without having to go into several menus.
How does it work on mobile? A big part of the work happens outside the office: while showing a car, during a test drive, while waiting for the customer.
What kind of support do they offer and in what language? For a tool the team uses every day, response speed and support being in Spanish are relevant practical factors.
How many fields are enough: the rule of seven
The more mandatory fields the CRM has, the less likely the team is to fill them in. A CRM full of outdated information gives you less control than a simple, well-maintained one.
The seven fields that make a record useful are: the buyer's name and phone number, the vehicle or vehicle profile of interest, source channel, current owner, outcome of the last interaction, next action with a date, and status and closing reason.
The rest can be optional. But these seven are the minimum for anyone on the team to pick up a lead without having to call the previous salesperson to ask what happened.
The right pipeline for a used car dealership
Pipeline stages need to represent real decisions in the sales process, not administrative categories. A useful pipeline for a used car dealer has six stages: new and unhandled, in contact, appointment confirmed, negotiating, reserved, and closed with reason.
Creating more stages than these six usually causes confusion about when to move from one to the next. If the team isn't clear whether a lead is "in contact" or "following up", the pipeline doesn't reflect reality and the conversion metrics per stage are useless.
See also how to structure a dealership's sales funnel.
How to prioritise leads without relying on gut feeling: basic lead scoring
Not all leads have the same urgency or the same likelihood of turning into a sale. A basic lead scoring system doesn't need complex algorithms: you just assign points to the signals that predict conversion.
The signals that add points are: appointment confirmed (+30), asked about financing terms (+20), asked about a specific car with a specific reference (+15), replied to two or more messages from the team (+10), lead coming from a phone call or direct visit (+20).
The signals that subtract points: no reply after three attempts on different days (-20), lead who said they're not ready to buy yet (-15), financing declined with no alternative (-10).
With that score, the CRM can sort the daily work list by priority. The salesperson still makes the decisions: the scoring just sorts the list.
See also how to manage leads in a dealership to increase sales.
How to merge the same buyer arriving through several channels
The same buyer might enquire through AutoScout24 in the morning, message on WhatsApp in the afternoon and call the next day. If each channel creates a separate file, the team may contact them three times from three different people, or not at all because each one thinks someone else is already handling it.
The phone number is the most reliable identifier: it's the same regardless of the inbound channel. When a new contact comes in, the CRM must first check whether a record with that number already exists before creating a new one.
What you shouldn't delete when merging is the source channel of each interaction. If the buyer came first through AutoScout24 and then through WhatsApp, that tells you they're actively searching on portals and also use WhatsApp for follow-up. Keeping it lets you measure which combination of channels generates the most sales.
Read also how to automate WhatsApp Business at a dealership.
How to log calls without turning it into bureaucracy
A call that leaves no trace in the CRM forces the next salesperson to rely on memory. Logging it must be possible in under a minute from a mobile, right after the conversation ends.
There are three things to log: the outcome of the call (contacted, no answer, voicemail, asked to be called back later), the next action agreed with a date, and whether any relevant new information came up that changes the lead's status.
"4-minute call" says very little. "Contacted. Wants to trade in his León. Send valuation today. Call tomorrow at 12:00" lets anyone on the team carry on with the sale without asking what happened.
Why loss reasons are the most valuable data in the CRM
Marking all lost leads as "not interested" hides what's really happening in the business. Loss reasons need to be few (between six and ten), mutually exclusive and actionable.
A useful list includes: price of the car, vehicle not available, financing not approved, bought from another dealership, no reply, postponed the decision, and profile didn't fit.
Analysing these reasons by period, by salesperson and by vehicle reveals patterns that lead to concrete decisions. If "vehicle not available" comes up often, the problem may be that stock isn't being updated quickly enough on the portals. If "no reply" dominates, the problem is the speed and cadence of follow-up.
How to migrate from Excel without importing the chaos
Importing all the Excel columns and rows as they are usually just replicates inside the CRM the same duplicates and inconsistent statuses that made the original Excel unmanageable.
The right process has six steps: make a copy of the original Excel and always work on the copy, delete all columns that don't correspond to the seven minimum fields, normalise phone numbers and emails before importing, deduplicate by phone number before the import, separate active contacts from archived ones and import only the active ones first, and validate a sample of 20 or 30 records before importing the whole lot.
A clean migration with 200 well-structured contacts is more useful than a full migration with 2,000 records, half of which are duplicates or out of date.
The CRM on mobile: why it's the key to adoption
If the CRM only works well on the office computer, the salesperson puts off updates until they get to the computer. By then, part of the conversation's context has been lost.
The mobile CRM must be able to do five things without opening the computer: open a customer's file by name or phone number, see the full history and the linked vehicle, log the outcome of an interaction with predefined options, create a task with a date and owner, and reply to the buyer on WhatsApp from within the file itself.
The practical test: after showing a car, the salesperson should be able to log the visit and agree the next step before seeing the next customer, not reconstruct it at the end of the day.
How to get the team to use it every day
Sales team resistance to the CRM has three common causes.
The first is that the CRM doesn't give the salesperson immediate value. If logging a call only feeds a monthly report for the manager, the salesperson sees no benefit. If logging a call automatically creates the reminder for the next action, the salesperson does get immediate value.
The second is that the CRM adds steps to the process without removing any. If the salesperson has to handle WhatsApp on their personal phone, answer emails in another system and also update the CRM separately, the CRM is extra work, not a simplification.
Read also how to organise a dealership's sales team.
The third is that the team sees the CRM as a surveillance tool. If the only visible use the manager makes of the data is checking how many calls each salesperson made, the team sees it as control. If the manager uses the data to spot which leads need more support, the team sees the CRM as a tool that helps them sell more.
The metrics that actually help you make decisions
CRM metrics are only useful when they lead to a concrete action. The six that matter most are: first response time, effective contact rate, leads with a defined next action, conversion by pipeline stage, sales by source channel, and losses by reason.
See also how to measure the real performance of portals in your dealership.
It's not a good idea to use these metrics to judge an individual salesperson without context. The combination of response speed, follow-up activity, progress through stages and final outcome lets you tell whether the problem is workload, lead quality, process or sales execution.
More than 750 dealerships already use Dealcar for their daily operations
Dealcar's CRM is designed specifically for used car dealers and dealerships: it centralises leads from portals, WhatsApp and the web in a single inbox, automatically links each lead to the vehicle of interest, generates follow-up reminders and records the full history of every conversation. Mobile access lets you log visits, calls and tasks from the lot without going to the computer.
You can see how it works at dealcar.io/crm-leads-automocion or request a demo at dealcar.io.
Frequently asked questions
Do you need a CRM from day one, or can you start with a spreadsheet?
With fewer than 5 leads a day and a single salesperson, a shared sheet may be enough. The system becomes fragile when more channels come in or several people get involved. The time to bring in a CRM isn't when the chaos is already unmanageable: it's before the volume makes the migration more complex.
How many fields should a salesperson be required to fill in?
Only the ones that change a decision: outcome of the last interaction, lead status, linked vehicle, owner and next action with a date. The rest should be captured automatically wherever possible.
What is the difference between a CRM and a DMS?
A DMS (Dealer Management System) covers the dealership's entire operational cycle: stock, invoicing, paperwork, tax and, in many cases, customer and lead management too. A CRM is specifically the customer relationship management part. Some DMSs include a CRM; others need to be integrated with a dedicated tool.
Can the CRM replace the salespeople's personal WhatsApp?
The goal is not to replace it but to centralise WhatsApp conversations inside the CRM, so the history stays in the system and not on the salesperson's personal phone. When a salesperson leaves the dealership, the conversations don't leave with them.
How long does it take to implement a CRM at a small used car dealer?
With a CRM designed for the sector, the basic setup can be ready in one or two days. Migrating data from Excel adds time depending on the quality of the original spreadsheet. Team adoption usually stabilises after 4 to 6 weeks of real use.
