Questions to Ask an Automotive CRM Vendor

A demo is designed to show you what the software does well. These questions find out what happens in year two.

A CRM demo is a performance, and a good one. It is run on a clean database by a person who uses that software every day, following a path rehearsed hundreds of times, showing the modules that photograph well. Nothing about that is dishonest. It is just not the same activity as evaluating software.

What the demo cannot show you is the part you will live with. What the invoice looks like in month thirteen. Whether the thing you were shown is in your tier or the tier above. How long a support ticket sits on a Saturday. What your data looks like coming out if you leave in two years. Those answers exist, but only if somebody asks for them out loud and writes down the reply.

The approach that works is simple and slightly unpopular. Send your questions in writing before the demo, ask the vendor to answer them in writing afterward, and treat reluctance as information. Vendors who are comfortable being pinned down on paper tend to be the ones still worth having in year three. Vendors who want to answer everything verbally, warmly, in the room, are telling you something too.

Take the list below into every demo you sit through, including ours. A structured version is on our CRM demo checklist, and a fuller procurement document sits on the CRM RFP template.

Start here because the answer shapes everything else, and because the quoted price and the real price are frequently different numbers.

What is the total monthly cost with every module I need to do the job I described? Not the base platform, the working configuration. Which of the things you just showed me are included at that price, and which are add ons? Is this per user or flat rate, and what happens when I hire three people in April? Is there a minimum seat count?

Then the ones people forget. What is the one time implementation, setup, data migration or training fee? Are text messages, phone minutes, recording storage or email volume metered, and at what rate? What happens if I exceed an allowance? Is there a charge for API access or for a third party to connect to you?

And the question that matters most and gets asked least: what is the price at renewal, and is there a cap on increases written into the agreement? A store that negotiates hard on year one and leaves renewal open has negotiated a discount, not a deal. Our pages on total cost of ownership and per user versus flat rate pricing break the arithmetic down.

Ask about the exit before you sign, because that is the only moment your leverage is high. Once you are inside a three year term the conversation is a different one.

How long is the initial term? Does it auto renew, and how much notice do I have to give to stop that? What is the cancellation process, in writing, including who I have to notify and how? Is there an early termination fee, and how is it calculated? If you raise the price mid term, do I get a right to leave?

Then the data questions, which are the ones that actually trap stores. What exactly can I export if I leave? In what format? Does the export include communication history, meaning the text threads, the emails, the call recordings and the notes, or only the contact fields? Is there a fee for the export? How long do I have access after cancellation before the account is closed? Who owns the customer data while I am a customer, and what rights do you claim over it?

Get those in writing. A vendor that will confirm export scope on paper is telling you something useful. Our data export checklist lists the specific fields to name, and CRM contract negotiation covers what is genuinely negotiable in the paperwork.

Every store underestimates this, and the underestimate is what turns a two week cutover into a three month mess.

What can you import from my current system, specifically? Contacts and vehicles, presumably, but what about notes, appointment history, text threads, email history, call recordings, deal records and salesperson assignment? Who does the mapping work, you or me? What does it cost? How long does it take from the day I hand over a file?

Ask what happens to the records that do not map cleanly, because there will be thousands of them. Duplicates, dead phone numbers, contacts with no owner, customers who belong to a salesperson who left in 2019. Does the vendor clean them, flag them, or import them as they are and leave you to find them later?

Ask whether you can run both systems at once during the transition, and for how long, and at what cost. Cutting over with no overlap is the most common way a store loses leads during a change. And ask what happens to leads arriving from third party sources on the day of the switch, because that is where the gap usually opens. The CRM migration checklist sequences all of this.

This is where automotive CRM products separate the most, because the communication layer is expensive to build and easy to describe vaguely.

Is texting native or is it a third party bolted on with a separate invoice? Are inbound and outbound messages in one thread on the customer record? Can I send MMS with photos, which matters for trades and for damage? Do you support RCS with SMS fallback so branded messages land on handsets that support it without excluding everyone else? Who handles 10DLC registration and messaging compliance, and what does it cost?

On voice: is there a dialer inside the record or does the salesperson use their cell phone? Is there call recording, and is there transcription, or only recording? Because recording without transcription is a compliance archive that nobody reads. Is there voicemail drop? IVR and routing for inbound calls? Call forwarding?

On email: a real inbox and composer, or a send only tool? Bulk email with recipient management? Domain authentication so your mail lands? Ask specifically whether the platform has an email validator and a phone validator, because most do not, and a dealership database goes stale faster than anyone expects. Compare against CRM with texting and calling.

Make the list of everything currently connected to your CRM before you take a single demo. Website forms, third party lead providers, chat, phone system, inventory feed, the back office, digital retailing, reputation tools. Every one of them is a task on a cutover plan.

Ask each vendor: which of these do you support today, in production, at a store like mine? Is the integration built by you or by the other party? What does it cost, on both sides, and who maintains it when one end changes? Do you accept standard ADF or XML lead posting, which covers most third party sources without a custom build? Is there an open API, and is access included or priced?

On the back office, ask precisely what the integration does rather than accepting a yes. Reading inventory is not the same as writing a deal. Pushing a sold record is not the same as bidirectional customer sync. Vague integration answers become expensive surprises in week six.

Then ask the reverse question, which almost nobody asks: what happens if I do not integrate anything? On our platform the answer is that it still works, because no access to the dealer management system you run and no inventory feed is required to operate. That is why solo salespeople and brokers can run on it. See CRM with DMS integration for where the line sits.

Most CRM failures are not software failures. The store buys a capable product, the salespeople quietly go back to their personal phones and a notebook, and eighteen months later somebody says the CRM does not work.

Ask how long implementation takes and what the store has to supply. Ask what training is included, whether it is live or recorded, and whether new hires six months from now get the same training or a link to a library. Ask what the mobile experience is, because if it is a stripped down afterthought your salespeople will not use it on the drive, and that is where they live.

On support: what are the hours, in my time zone? What happens at 6pm on a Saturday, which is peak retail and dead vendor time? Do I get a named contact or a queue? What is a realistic first response time, and is it in the agreement or just a promise? How do you communicate outages and releases?

Then ask for a reference from a store like yours that has been live for over a year, and call them without the vendor on the line. Ask that store one question: what do you wish you had asked before you signed? Our CRM adoption guide covers the management side of this, which is the half no vendor can sell you.

Some vendors sell software. Some sell leads. A few sell both, and that combination needs its own questions, because bundling can hide a weak half.

Are the leads exclusive to my store, or shared with other dealerships? How is my territory defined, and can I change it? How many leads should I expect, and what happens if volume is lower than we discussed? What is the process when a lead is bad, and is it a credit, a replacement or nothing? Where do the leads come from, in plain language?

Be suspicious of any answer involving guaranteed volume, guaranteed quality or a promised close rate. Nobody controls what a consumer does after they submit a form. On our side, nothing is filtered or scored. We ask prescreening questions at capture and deliver every submitted lead inside your zone, exclusively, and problems are handled by post delivery replacement review rather than by a quality claim made up front. Leads are a mix of VIN specific shoppers and open shoppers, and we will not promise you a ratio.

Read what to expect from car sales leads before you judge any lead program by its first two weeks. It explains normal consumer behavior rather than apologizing for it.

Total cost: CRM Only is from $199 a month, Lead Data Only from $599, Inbound buyer leads from $799, Marketplace Acquisitions from $999, and the Buyers and Sellers Hybrid Plan from $1,599. Skip A Month is $199 for stores with seasonal swings. United States only, and the number is 844-376-2274.

Contract: month to month, no long term commitment, no auto renewing multi year term to escape from. That removes most of the negotiation above, which is the point. Cancel and you stop paying.

Data: it is your customer data. You can export it, including communication history. Ask us to put the scope in writing and we will.

Integrations: not required. No back office access and no inventory feed is needed to operate, and standard lead posting is supported. Integration depth is more limited than an enterprise product built around one back office system, and if certified depth is central to how you run, that is a real reason to choose someone else.

What we are not: we are not an OEM certified CRM, and we do not sell a dealer management system. No general ledger, no repair orders, no title work. If those are on your list, we are the wrong vendor for that part and you should shop it separately. Watch the demo or contact us and ask the hard ones directly.

What is the single most important question to ask?

What exactly can I export if I leave, in what format, and does it include communication history. It is the question with the largest consequence and the one vendors are least prepared to answer in writing. Ask it before signature, when your leverage is highest.

Should we send questions before the demo or after?

Before, so the demo addresses your situation instead of the standard path, and again after in writing so the answers are recorded. Reluctance to answer on paper is useful information in itself.

How many vendors should we shortlist?

Three is usually right. Two gives you no reference point and five turns evaluation into a full time job for a manager who already has one. Score them against the same written questions rather than against how well each demo went.

Is a long contract ever worth it for a discount?

Sometimes, if the discount is real and the exit terms are fair. But price the risk honestly. A multi year term on a product your team ends up not using costs far more than the discount saved, and you have no leverage left when support quality slips.

What questions should we ask about lead programs specifically?

Whether leads are exclusive, how territory is defined, what happens when a lead is bad, and where they come from in plain language. Treat guaranteed volume or guaranteed quality claims with suspicion, because nobody controls what a consumer does after submitting a form.

Do you answer these questions about your own product?

Yes, and the last section on this page does it. Month to month terms, your data is exportable including communication history, no back office integration or inventory feed required, and we are neither an OEM certified CRM nor a dealer management system.

We will answer cost, contract, export rights and integration limits in writing, including the places we are not the right fit. Month to month, no long term contract.