Automotive Lead Routing for African Dealer Teams
Plan how model, test-drive and fleet enquiries reach the right African dealer, with clear rules for territories, duplicates and failed handovers.
Let’s talkGive each vehicle enquiry an accountable destination

A buyer has chosen a model and asked about a purchase or test drive. Your team now needs to know which dealer should respond, whether that dealer received the request and who steps in if the handover fails. We help turn those questions into routing rules your China-to-Africa sales team and participating dealers can use.
The less obvious requests matter too: a buyer outside the network’s coverage, a fleet enquiry sent through a retail form or a second submission with a different model choice. Each needs a destination without losing what the buyer asked for.
Agree the routing rules with the network
Start with your approved models and offers, participating dealerships, coverage rules and the person responsible for sales operations. We work through how buyer location, model choice and enquiry type affect assignment. A fleet request may need a different recipient from a test-drive request, while a dealer-partnership enquiry may belong outside the retail sales queue altogether.
We can use those decisions to scope landing-page requirements, qualification fields, routing logic and lead statuses. Before adding a field, ask what the receiving team will do with the answer: location may determine territory, while enquiry type may determine the team. CRM or sales-system implementation depends on the interfaces and access actually available. Channel planning and media spend are separately agreed.
Test awkward handovers as well as normal ones
Use controlled enquiries to test both covered territories and the gaps between them. A buyer outside a supported area needs someone responsible for the exception; assigning any available dealer can conceal the gap. Test repeated submissions as well. If the buyer changes their model choice, the receiving team needs to see that change, even when the contact details match an earlier request.
For each test, follow the request from the form to the receiving team. Check that model, location and consent context arrive together, that the dealer can record acceptance and that a failed delivery is visible to the person expected to resolve it. A website confirmation shows what the buyer saw; you also need evidence of what reached the dealership.
Report the sales stages honestly
Your campaign report should separate form submissions, assigned records, dealer-accepted enquiries and later sales stages supported by dealer feedback. This helps you see where follow-up stops. If an enquiry is assigned but no dealer response is recorded, the report should leave that gap visible. It cannot establish whether the buyer was contacted.
A test-drive request, a confirmed booking and a vehicle sale also mean different things. Keep them separate wherever the network can supply the evidence.
Dealership availability, stock, finance approval and service promises remain business responsibilities. The programme does not guarantee sales or substitute for a functioning local network. Review the automotive industry approach or discuss a model campaign and its dealer handover.
Agree the state model before adding volume
An illustrative automotive pathway could use received, assigned, accepted by dealer, contacted and closed. Agree what moves an enquiry into each state and who can make that update. For example, “assigned” could mean that a destination has been selected; “accepted by dealer” would require confirmation from the receiving team. Delivery to a system or mailbox alone should not imply that a salesperson has taken responsibility.
The handover pack can include a territory matrix showing who receives each request, a field map showing where the submitted answers go, an exception list and evidence from controlled test enquiries. Your operations team should be able to trace a record and correct a routing issue while retaining the original request. We would confirm network coverage, account access and dealer participation before agreeing which parts to implement.
Use a dealer exception to accept the whole handover
For example, test a model enquiry where the buyer has selected a preferred dealer but that destination is unavailable. The agreed rule might send it to an exception owner for review. Check who sees the request, what the buyer is told and which status remains on the record. If no alternative dealer has accepted it, the record should still make that clear.
Resolve this example before increasing campaign activity. Automotive sector planning supplies product context, while CRM integration defines delivery and status ownership. Bring a routing rule and one difficult exception so we can discuss the handover your programme needs.
Automotive handover FAQs
A few useful answers before you decide.
Which fields need to survive dealer assignment?
Who decides which dealer owns an area?
What if a customer chooses a dealer directly?
How are fleet requests kept separate?
Can retries create duplicate dealer tasks?
Will the programme tell us how many vehicles sold?
How is readiness for a wider model launch assessed?
Keep the right things connected.
Africa Market-entry Services for Chinese Teams
Identify what your team needs to learn or approve before committing to an African market launch.
CRM Integration for China–Africa Sales Handover
Give each website enquiry a clear route into your CRM, with agreed fields, sales ownership and a way to resolve failed deliveries.
Start a conversation
Tell us what you are working towards. We’ll help you find a practical next step.