China → Africa

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 talk

Give each vehicle enquiry an accountable destination

Vehicles displayed in a spacious automotive showroom.
Illustrative photography · rawkkim / Unsplash

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?
Agree the minimum needed to understand and act on the request, such as model, location, enquiry type and relevant consent context. Check the receiving record against the submitted form during testing. The dealer should be able to see what the buyer asked for without asking them to repeat those initial details. An empty field in the destination system is not, by itself, a reason to collect more data.
Who decides which dealer owns an area?
The network’s authorised business owner supplies and approves the rules. We can implement those rules and show where coverage is missing or overlaps, but the network must resolve exclusive territories and commercial disputes. Also agree who updates the coverage map when a dealer joins, leaves or changes its area, so the website and receiving logic stay aligned.
What if a customer chooses a dealer directly?
Decide whether that preference overrides automatic rules and how unsupported combinations are handled. The explanation should be clear to the buyer. A preference field should not be shown if the system will silently ignore it, while a chosen location should not imply model availability that the network has not confirmed.
How are fleet requests kept separate?
Give fleet enquiries a recognisable request type and an agreed recipient, carrying the context that team needs. Retail and fleet buyers may read the same model page, so the enquiry form needs a clear way to express the different request. Preserve that choice through assignment and reporting so the receiving team can prepare the appropriate follow-up.
Can retries create duplicate dealer tasks?
They can, so include retries in the test enquiries. Sending the same record again after a failed delivery differs from a buyer submitting a new model choice. Agree how the receiving team recognises each case: the first should not create repeated work, while the second must preserve the changed request. Give operations a way to inspect uncertain matches before combining or dismissing them.
What happens when a destination is unavailable?
Use the agreed retry or exception path and give an operational owner visibility. The customer must not receive an unsupported success message. Ongoing monitoring and escalation coverage need an explicit responsibility; a routing specification alone does not provide continuous management of every receiving system or mailbox.
Will the programme tell us how many vehicles sold?
Only where the dealer network supplies reliable authorised sales-stage evidence. A received lead or test-drive request is not a sale. Reports should make missing feedback visible and distinguish the stages that can be substantiated from those beyond the system’s current reporting capability.
How is readiness for a wider model launch assessed?
Test representative territories, enquiry types and failures, then review dealer acceptance and qualification feedback in the pilot. Broader traffic requires actual receiving capacity. A technically correct integration does not establish stock, finance approval, servicing capability or the commercial case for promoting additional models.
Let’s move things forward

Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

Let’s talk