What a dealership CRM cannot see, and how to fill the gap

Ask a general sales manager how many opportunities the store had last month and they will read a number off the CRM. That number is the count of records somebody created. It is not the count of people who tried to buy a car from you, and the difference between those two figures is where most of the recoverable business in a dealership sits.

A CRM is a record of entries, not of conversations

This is not a criticism of any particular system. VinSolutions, DealerSocket, Tekion, eLead and the rest are built to hold structured records of customers and deals, and they do that. What they hold is what somebody put in them. A conversation that nobody typed up did not happen, as far as the database is concerned, and a conversation typed up inaccurately happened the way it was typed.

Managers forget this because the CRM is the only complete-looking picture they have. It has every field filled in, it produces reports, it sorts and counts. Completeness of format gets mistaken for completeness of fact.

Six things it cannot see

What was actually said

The note is a summary, written by a person with an interest in how it reads, minutes or hours after the call. The customer's exact words are gone, and the customer's exact words are where the buying signals are. Wants a third row, needs to be out of the current payment, has to talk to a spouse, is going to another store on Saturday: all of it lives in the conversation and only some of it survives into the record.

The call nobody answered

This is usually the biggest invisible category. A customer calls at 5:50 on a Friday, it rings through, nobody picks up, no record is ever created. There is no rep to blame in the CRM because there is no entry. The opportunity existed, it just never became data. Stores routinely improve their close rate faster by finding these than by working the records they already have.

The thread on a personal phone

A customer texts a rep directly because that is the number they have. The whole negotiation happens there: photos, a payment question, a change of plan on Saturday. None of it reaches the record. When the rep is off, or leaves, the customer's history leaves with them, and whoever picks up the record starts from a note written two weeks ago.

The email with no owner

Messages arrive at sales@ and internet@ and a handful of forwarding addresses. Some get assigned, some get answered by whoever saw them first, some sit. An email that was never assigned has no owner in the CRM, which means nobody is late on it, which means nobody notices.

Whether the promise was kept

A CRM can record that a rep said they would send photos. It cannot tell you whether the photos went. Unless somebody logged the sending, the record looks identical whether the customer got what they were promised or has been waiting since Tuesday. From the customer's side those are opposite experiences.

The customer who came back after the record was closed

A record is closed as unreachable. Four days later the customer replies to the last text. The record is out of every queue, so the reply goes nowhere. This one is particularly expensive, because that customer had just told you they were still in the market.

Why the gap is wider than it used to be

When almost every opportunity arrived as a phone call to a switchboard or a walk-in, a CRM entry captured most of what happened. That is no longer the shape of the business. A single customer now touches a store across a form, a text thread, two calls, an email and a chat, often before anyone at the store has said a word to them.

Each channel that gets added is another place where something can happen without producing an entry. The record has not got worse. The share of the customer's experience that it covers has shrunk.

Three ways stores try to close it, and how each one fails

Ask reps to log more. The standard response, announced in a Monday meeting, effective for about ten days. It fails because the gap is not caused by laziness, it is caused by a rep taking nine calls in a morning. Asking a busy person to type more produces shorter notes, not fuller ones.

Add required fields. Make the trade field mandatory and it will be filled in. With what, is the question. Required fields produce entries, not accuracy, and n/a will appear in your trade column by the end of the first week.

Listen to calls yourself. This works and it does not scale. A manager can review a handful of calls a day and a store takes hundreds. Hand sampling also finds the calls somebody answered, which by definition excludes the largest invisible category.

What actually closes it: connect the conversation to the record

The fix is structural, not motivational. The conversations have to arrive attached to the customer record without a person retyping them, and somebody has to compare the two on a regular schedule.

• Calls attached to the record, including the unanswered ones. A missed call needs to create or attach to a record, or it stays invisible forever.
• Texting through a store number, not a personal one. This is the single highest value change most stores can make, and it is mostly a policy decision. It also protects the store when a rep leaves.
• Shared inboxes with assignment rules. Every inbound email gets an owner and a clock, even if the owner is a queue.
• Promises captured as tasks. A promise with a time on it should become something dated that somebody owns, not a sentence inside a paragraph.
• A weekly comparison. Twenty records read next to the conversations behind them. Nothing keeps a record honest like the knowledge that somebody checks.

Put it in place in this order

1. Missed calls first. Find out how many inbound calls went unanswered last week and where they landed. This is almost always the largest and fastest recovery.
2. Move texting onto store numbers. Set the policy, give the team a workable tool, and say plainly that customer conversations belong to the store.
3. Give every inbound email an owner. Assignment rules, a clock, and a manager who looks at what went unassigned.
4. Turn promises into dated tasks. Start with the two that cost you most: sending information and calling back at a named time.
5. Start the weekly comparison. Small, regular, rep by rep, not a quarterly audit.

Do them in that order. Each one is useful on its own, and the first three make the fifth worth doing, because there is something to compare against.

What none of this will tell you

Be clear about the limits, or you will replace one false picture with another. Attaching conversations to records tells you what was said and what was not done. It does not tell you whether a customer would have bought, whether a returned call would have produced a visit, or why somebody went quiet. A customer who stops answering may have bought elsewhere, or been pulled into something at work, or decided to wait a year. The conversation shows you the gap. It does not show you the outcome, and a manager who treats a missed callback as a lost sale is guessing with extra steps.

What you get is narrower and more useful: an accurate view of which customers tried to reach your store, what they asked for, and which of those requests nobody answered.

What to do this week

1. Pull the inbound call log for one week and count the calls nobody answered, then check how many of those exist anywhere in the CRM.
2. Ask three reps to show you their last five customer text threads and see how many are on a personal phone.
3. Open the shared sales inbox and count the messages with no owner and no reply.
4. Pick the two promises your store makes most often and turn them into dated tasks.
5. Put forty minutes on the calendar for a weekly comparison of twenty records against the conversations behind them.