Getting dealers to accept your car sales leads
Give the dealer network a clear standard for the enquiries it receives. LeadScale applies agreed contact checks and repeat controls before delivery, helping you identify which rejection reasons need attention in the data or the hand-over.
Dealer rejection can reflect a faulty contact detail, a repeated enquiry, the wrong destination or a buyer who is not ready. LeadScale applies the record checks agreed for the programme before delivery. Separate those checks from dealer routing and follow-up, so each problem gets the appropriate response.
Agree what an acceptable enquiry contains
Ask dealers to define the information they need and the reasons they reject an enquiry. A contact fault, a repeat submission and an unsuitable destination call for different actions. Those definitions need to be useful both to the network and to the team designing the processing.
- Set the criteria. Agree the contact fields and programme conditions that matter to the receiving dealers.
- Configure the checks. The Engine can check names, email addresses, phone numbers and postal addresses. The checks, their order and failed-result handling are agreed for the programme.
- Define repeats. Set deduplication and frequency rules, including which further enquiries should continue.
- Confirm the route. Identify the receiving systems and the onward hand-over to dealers. Assess each connection needed.
Use the rejection reason to choose the next change
Imagine two dealers returning the same number of enquiries. One reports phone-number faults. The other reports that people are still comparing models. The totals look alike, but the first raises a contact-data question and the second raises a question about the agreed buying stage.
Review reasons alongside the source and destination. Contact faults appearing across several dealers may warrant a review of capture and checking. Enquiries reaching an unsuitable location call for attention to the hand-over. Different expectations of buying readiness call for a review of acceptance criteria.
The Engine's checks, repeat controls and processing history give you evidence about the record. Combine that with dealer feedback to decide which part of the programme needs changing.
A correction opportunity at capture
Everest checked phone numbers on its enquiry form, prompting visitors to correct an entry before it reached the contact centre. Everest allowed people to submit if they ignored the warning.
For a dealer programme, agree the checks and the action required when a record fails one.
Make the dealer hand-over explicit
Agree where each enquiry needs to go and what information must accompany it. Records created through the Engine carry source, timestamp, lineage and consent audit information to support review of that route.
The brand and dealer still need to assess their intended use.
Questions from automotive teams
Can you deliver into our dealer systems?
Delivery can use configured integrations, the receiving system's API or files. Identify the brand system and any onward dealer destinations so the required connections can be assessed.
How do we handle someone enquiring again?
Define what makes the repeat useful or unwanted. A further request about another vehicle may need different treatment from a repeated copy of the same enquiry. The programme's rules determine the handling.
What should we ask dealers to return?
An identifiable enquiry and a specific reason for rejection are useful starting points. Agree the feedback your programme needs and how it can return, then review it alongside the processing and source history.
What are dealers rejecting, and why?
Bring recent feedback, your acceptance criteria and the systems receiving the enquiries. We'll identify the checks and delivery requirements that address the problem.