Put Validation Gates at the Dealer CRM Lead Intake

Validation Should Protect the Conversation

A dealership wants a lead record that an employee can work, but a form that rejects every unusual answer can punish the customer for not fitting a template. Validation should catch clear problems—an impossible email shape, a missing contact route, or a vehicle identifier in the wrong format—while providing a human path for questions that do not fit the fields. The goal is a usable record, not a perfect-looking database.

Separate required fields by journey. A vehicle inquiry may need a preferred contact method and either a model reference or a free-text question. A service appointment request may need a vehicle detail, requested concern, and preferred time. A parts question may need a description that cannot be reduced to a dropdown. Write the minimum needed for the next employee to act, then let the team request more information during follow-up.

Validate Format Without Inventing Meaning

A field can be structurally valid and still be wrong. A ten-digit phone number may belong to someone else; a valid email may contain a typo; a stock number may have expired. Use format checks to prevent obvious transmission errors, but label business verification separately. Never replace a customer’s entered value with a guessed correction without showing the employee what needs confirmation. A failed verification should create an actionable exception, not a silent discard.

Define behavior for duplicates, retries, attachments, and partial submissions. A customer may submit a form twice after waiting for a confirmation page. The intake process should preserve the original request, show the relationship between attempts, and prevent the employee from treating every retry as a new conversation. If an attachment fails, tell the customer what to do next and keep the text that was successfully received.

Make Exceptions Visible in the Queue

An exception queue should show the missing or conflicting field, the time received, the department, and the action needed. Do not put every uncertain record into a generic “bad lead” bucket. A missing VIN, an unreadable phone number, and a service question sent to sales need different responses. Assign an owner and a review time, then let the employee correct the record with an audit note rather than editing history invisibly.

Test validation with real examples from each rooftop and department. Include a multilingual name, a shared household phone, a customer with no specific vehicle, a parts question, and a submission made outside business hours. Ask frontline employees whether the resulting record tells them what to do next. Review rejected and abandoned submissions for evidence that the gate is blocking legitimate demand. Adjust the rule only after understanding the failure.

Give the intake owner a daily exception summary that distinguishes technical failures from customer follow-up needs. A broken destination, rejected payload, and missing vehicle detail should not sit in one queue. The owner can repair the integration, ask an employee to clarify a request, or improve the form based on the category. Small distinctions at intake keep a technical alert from becoming an unworked customer record.

Intake-Validation Checklist

• Define minimum required context for each sales, service, parts, and general journey.
• Use format validation without silently changing or discarding customer values.
• Handle duplicate submissions, retries, attachments, and partial records explicitly.
• Show the missing or conflicting field in an owned exception queue.
• Test rejected and unusual requests with frontline employees before tightening rules.

FAQ: Should Invalid Leads Be Deleted?

Usually no. Preserve the received record according to the dealership’s retention and privacy rules, label the validation issue, and route it for an appropriate review or suppression decision. Deleting it can hide a broken form or a recurring customer problem. The employee should be able to see why the record was not ready and what, if anything, can make it workable.

Good intake validation creates a safer starting point for human follow-up. It catches transmission errors without teaching the CRM to mistake unusual customers for unusable ones.