Trace an inquiry from the source
Begin the evaluation with the sources your dealership actually uses. A broad claim about lead handling is less useful than watching a representative inquiry arrive with the expected fields and source information.
Ask the vendor: which sources are supported today? What happens when a required field is missing? How are duplicates identified, and can a team member see the original inquiry?
Look for: a clear explanation of native functionality versus a third-party connection. Ask who investigates delivery problems and which dependencies or fees apply. Use a test record with no customer data during an initial demonstration.
Review the record, not just the list
A list can look organized while hiding the context needed for a useful response. Open an individual record and consider what the next person handling it would need to know.
Ask the vendor: where can the team see the vehicle of interest, the original question, prior interactions, and ownership? Which information is visible to each role? Can corrections be made without losing the history that matters?
Look for: a coherent sequence rather than scattered panels. Distinguish a saved note, a message draft, a sent communication, and a delivery confirmation. They represent different facts.
Walk through the next action
Follow-up should match how your team works. A reminder, a scheduled task, an automated message, and a confirmed appointment are not interchangeable. Ask for the exact behavior of the actions that matter to you.
Ask the vendor: how is ownership assigned? Can the team identify overdue work? What happens when someone is absent? If automation is proposed, what triggers it, how can it be stopped, and how are consent and opt-outs managed?
Look for: a practical workflow you can explain to a new team member. Do not assume texting, calling, sequences, calendar booking, or AI are included because an interface uses those labels.
Check the manager and handoff views
A manager may need a different perspective from the person responding to an inquiry. Useful visibility should help the team find outstanding work without exposing more information than a role needs.
Ask the vendor: how do permissions work? Can responsibilities be reassigned? What history remains after a handoff? Which reports describe activity and which genuinely connect to a verified outcome?
Look for: a demonstration using multiple test roles. Ask the vendor to explain the meaning and limitations of a metric before using it to assess people or revenue.
Separate the product from its connections
Write down the inventory, website, phone, email, and other tools you already use. For each proposed connection, record the direction of information and which system owns it.
Ask the vendor: is this native, already supported for our provider, or a request that needs assessment? Who configures it, monitors it, and resolves failures? Are there separate contracts, credentials, permissions, or charges?
Look for: written boundaries and a realistic test plan. A provider name on a slide is not proof that your required workflow works. Bring the required connection questions to your product discussion.
Ask about access, export, and departure
Data ownership is easy to overlook during a product demonstration. It becomes important when records need correction, staff access changes, or a dealership changes systems.
Ask the vendor: what can be exported, in which format, and by whom? Does the export include the information and history your team needs? What fees, notice periods, retention rules, and deletion processes apply?
Look for: a test export with no customer data and clear written terms. Keep credentials and customer information out of informal demos. Legal and privacy obligations need review in the context of your actual dealership.
Make the setup work visible
Moving to a CRM is an operational change as well as a software decision. The migration, account setup, role configuration, training, and review process should have named responsibilities.
Ask the vendor: which data will move, how it will be checked, and who signs off? What training is included? Can the team practice before a cutover, and how are exceptions handled?
Look for: an agreed checklist, not an assumed launch date. Identify dependencies on your current providers and choose a review point before live work relies on the new setup.
Test the support conversation
Support needs are more specific than a general promise of availability. A dealership should know where to ask, what information to provide, and how an operational problem is escalated.
Ask the vendor: which contact paths are real and monitored? What service hours or response commitments are contractual? Who handles third-party connection issues, and how are product changes communicated?
Look for: clear account guidance and a way to track a genuine request. Compare proposals against your must-have workflows and unresolved questions. An impressive demo should narrow those questions, not replace them with assumptions.
Make the demo work for your team.
Bring your current lead sources, a representative workflow, and a short list of non-negotiable requirements. Ask to see the current product and have any unverified requirement documented for follow-up.
No vendor-specific capability, integration, commercial term, or response commitment is implied by this guide.