CRM adoption at a dealership means every salesperson, BDC rep, and manager logs every customer contact in the CRM, and managers check those records every week. It turns into accountability when each role knows what to log and who reviews it.
Last updated: October 26, 2026
Your CRM can only tell you what somebody typed into it.
That sounds obvious, but it isn’t how plenty of stores actually run. Picture a Saturday: a customer walks the lot, talks numbers with one of your salespeople, and heads home with a business card. The notes from that conversation live on a scrap of paper in a desk drawer, or in a text thread on the salesperson’s personal cell phone. On Monday the CRM shows a lead with no activity. As far as the system knows, nobody ever talked to that customer.
I’ve spent more than 10 years in the automotive industry. I started in the detail and service departments where my dad was the service manager, and later spent about four years on Tekion’s Learning & Development team building training for dealership staff. Now I work with stores at Helion Technologies through our Tekion enablement services, mostly in the stretch beyond go-live. The pattern I see with the dealership CRM is the one I saw in training rooms. The software works. The habit is what’s missing.
What I want to talk about here isn’t which CRM your store should buy, because the one you have is probably fine. I want to talk about making it accountable, meaning what each person logs, what a manager looks at on Tuesday morning, and the handful of reports that tell you whether any of it is happening.
What CRM Adoption Actually Means at a Dealership
CRM adoption is the share of real customer activity at a dealership that actually gets recorded in the CRM, by the person who did it, close to when it happened. Logins don’t measure it. Complete records do: every lead, call, text, visit, appointment, and follow-up, logged where the next person can find it.
Logins tell you who opened the system. Only complete records tell you who did the work. Big difference.
Where the Customer Record Goes Missing
Walk into almost any store and you’ll find at least a few of the same leaks. There’s the paper desk log at the sales tower that everyone keeps “just in case,” and over a few months it quietly becomes the real record while the CRM turns into the backup. There are the texts and calls that happen on personal cell phones, so the whole relationship lives in one salesperson’s pocket and walks out the door with them if they ever leave. Walk-ins and phone-ups get typed in at closing from memory, if they get typed in at all, and internet leads get answered by email outside the system because somebody decided it was faster.
The service drive has its own version. An advisor is writing up a customer whose lease is almost up, the customer says they’ve been eyeing the new model, and the advisor fully means to tell sales. Sales never hears about it. Meanwhile, somewhere in the CRM, there’s a note that says “follow up” and nothing else.
Nobody’s being lazy here. Each habit got built for a reason, usually because the old way really was quicker on a packed Saturday, and when the showroom is full people are going to take care of the customer standing in front of them before they take care of the software. I get it. Time is money on a sales floor.
Where it costs you is later, and quietly. Back in 2011 Harvard Business Review published research by James Oldroyd, Kristina McElheran, and David Elkington, “The Short Life of Online Sales Leads”, and the authors’ finding was that most companies weren’t responding to online leads nearly fast enough. Now think about a lead your CRM has never heard of. It can’t be routed to anyone, it won’t trigger a reminder, and nobody can pick it up on the day its owner is off. If you’re thinking about putting AI on those leads, the same gap applies, which is why we wrote up the questions to ask before an AI BDC works your leads.
Incomplete records don’t break anything. That’s exactly why they stick around for years.
Why Software Training Doesn’t Stick
During my time at Tekion I built more than 100 training storyboards, and if all that work taught me one thing, it’s that people don’t keep what they only watch.
A salesperson sits through a CRM session during go-live week and nods along. Then they head back to the floor, a customer walks in, and they do what they’ve always done, because that’s what their hands remember. It’s not stubbornness. It’s memory. Researchers Jaap Murre and Joeri Dros replicated Hermann Ebbinghaus’s forgetting curve in PLOS ONE in 2015, the old finding that we lose newly learned material quickly unless we come back to it, and their results looked a lot like his original data from the 1880s.
What changes it is hands-on experience and repetition. Not a longer slide deck. Not a quiz.
I think about the Cleveland Auto Show, the last year it was held at the I-X Center. A couple of brands kept their vehicles locked or marked “display only.” People go to an auto show to sit in the driver’s seat and try things, so locking the doors missed the whole point. CRM training works the same way. Same mistake. If your team only watches somebody else click through a lead, the doors are locked.
Here’s what hands-on looks like in a store:
- Practice on real leads from this week, in the live system, with a manager sitting next to the salesperson.
- Ten minutes before the Saturday sales meeting to log a walk-in from greeting to next step. Then do it again the next Saturday.
- New hires learn from a trainer or a manager, not from whoever sits at the next desk, workarounds included.
- Retraining whenever something changes. A new lead source counts. So does a new rule in the CRM or a new person in the BDC.
Training is a habit you schedule. Not an event you attend.
What Each Role Has to Log
Accountability starts with a short list nobody can argue about. Each role knows what it owns, when it’s due, and who checks it.
| Role | What they log in the CRM | When | Who checks it |
|---|---|---|---|
| Salesperson | Every walk-in, phone-up, and test drive, with a real note and a next step | Before the customer leaves, or right after the call | Sales manager, daily |
| BDC rep | Every lead response, call, text, and appointment, sent from the CRM rather than a personal phone | As it happens | BDC manager, daily |
| Sales manager | Desking notes, turnovers, and the reason a deal didn’t close | Same day | General manager, weekly |
| Service advisor | A sales opportunity flag for a customer with equity or a lease ending soon | During the write-up | BDC or sales manager, weekly |
| General manager | Nothing new. The GM reviews the records and runs the weekly meeting | Weekly | Dealer principal |
Keep it that short. Really. A list with 30 rules is ignored by the second week, and then you’re back to the desk log.
If it isn’t written down, it isn’t a rule.
The Weekly Review That Makes It Stick
On one CDK to Tekion move I worked on, a multi-rooftop dealer group with more than 30 stores, the work after each go-live included deal spot checks, CRM check-ins, and a standing weekly meeting with dealership leadership and the Tekion implementation team. Same day. Same people. Same questions. Those check-ins are the model I’d hand any store, whatever CRM it runs.
No war room required. You need 30 minutes, the same day every week, and a few reports pulled before anyone sits down.
- Leads with no activity: every new lead from the past seven days with no logged call, text, or email.
- Pull 10 sold deals and read each one’s CRM history from first contact to delivery. A deal that shows up in the DMS with no trail in the CRM was worked outside the system. Ask how, without blame, and fix whatever step pushed it out.
- Appointments set against appointments shown, by person.
- Empty notes. “Follow up” isn’t one.
- Service-to-sales flags: how many came in and how many got a call back.
The point of the meeting isn’t to catch anybody. It’s to find the step in the process that makes logging harder than skipping it, and change that step. When a salesperson keeps texting customers from a personal phone, ask why. Sometimes the answer is that the store never turned on texting from the CRM, and that’s a setup fix, not a people problem. Easy fix, too. CRM user adoption climbs when the easy way and the right way turn out to be the same way.
What gets reviewed gets logged.
After a DMS Move, the Process Has to Move Too
OEMs keep updating their vehicles to match the times. Dealership processes don’t always keep pace, and a DMS move is where that gap shows up first.
Tekion built its CRM on the same Automotive Retail Cloud as its DMS. When the company launched the CRM in March 2022, it described a 360-degree view that unifies customer data across departments, along with a configurable rules engine for lead flow. That’s a real strength. I mean it. A service advisor and a salesperson can look at the same customer, with the same history, in one place.
It pays off when the store’s process changes with it. Carry the paper desk log, the personal-phone texting, and the data entry at closing over from the old system, and all you’ve done is move your workarounds onto a better platform. Workarounds need to be left in the past. All of them. Tekion’s own team gets the store trained and live, and what continues after that program is the daily habit, which every store has to own for itself.
So I’d plan CRM habits as part of the move, not after it. Our Tekion implementation timeline puts the IT work on the calendar week by week, and the DMS conversion checklist covers cutover. Add one line to both: who owns CRM adoption the week after go-live, by name. Then read where dealerships leave money on the table after Tekion go-live, because how people use the system is the first thing a post-go-live review looks at.
A new system doesn’t change habits. A new process does.
How We Help With CRM Adoption at Helion
Helion stays on after go-live, extending the momentum Tekion’s own team builds. For the CRM, that means time with the people on the floor, not only the managers. We look at how each role actually uses the system, retrain on real leads, help the store set up its weekly review, and come back to see what stuck.
Across the 2,000-plus dealerships we support, the workarounds repeat. The paper log. The personal phone. The note that says “follow up.” Every time. Seeing the same ones over and over is what lets us spot them quickly, and it’s how we help a store get to peak efficiency on the system it already paid for.
The team doing the logging does the hard part. Our job is to set them up for success.
Questions I Get From Sales Managers
Our salespeople say the CRM slows them down. Are they wrong?
How do you get a 20-year veteran to log everything?
Should CRM activity be part of the pay plan?
What should a general manager look at in the CRM each week?
We just went live on Tekion. Is it too soon to hold people to this?
Start With What Gets Logged
I learned standards on the service drive, working in the department where my dad was the service manager. Ex-Navy. No shortcuts. He held me to a higher standard than anyone else on his team, and at the time it felt relentless. A CRM needs that kind of standard: one for everybody, checked every week.
Pick the handful of things each role has to log, put one review on the calendar, and give the people on the floor enough practice to make it routine. That’s the real work, and your team is the one doing it. If you’d like a second set of eyes on how your systems and processes are set up after a DMS move, start with our complimentary IT and cybersecurity assessment.