# How Lead Generation and Dealer Routing Work in African Automotive Markets > Design an automotive enquiry workflow with qualification rules, dealer ownership, exception handling and useful sales-stage reporting. Canonical page: https://webvelopment.co.za/insights/africa-market-entry/automotive-lead-generation-dealer-routing/ Language: en Africa market-entry insights When someone asks about a vehicle, who receives the request—and who helps if the usual dealer cannot? We explain how to plan the enquiry fields, dealer assignment and sales feedback so your team can follow each request beyond the form submission. Webvelopment · 25 October 2026 ## Treat a lead as a handover A buyer has asked about a vehicle, a viewing or a quotation. They need to know what happens next. Your brand team needs to know where the request went, and the receiving dealer needs enough context to start a useful conversation. Before choosing software, draw the route together: buyer → enquiry record → assigned dealer → sales feedback. Put a person’s role beside each handover. If nobody can say who handles an unmatched location or a failed delivery, the process still has a gap. We would start with your actual network, including the people who receive and reassign enquiries. Countries and dealer arrangements differ; check the workflow for each operation before reusing its rules elsewhere. ## Capture enough information to act For an initial consumer enquiry, consider model interest, customer location, contact details and requested action. Ask the receiving sales team what they need to make the first contact. Then separate the fields needed to send the request to the right person from questions that can wait. For example, if location determines the dealer, explain which location you mean: where the buyer lives, where the vehicle will be used or their preferred dealership. An ambiguous field can leave both the buyer and the receiving team guessing. A commercial or fleet conversation may also need business type, intended use and approximate vehicle requirements. You can collect enough to identify that request and let the responsible person ask the detailed procurement questions afterwards. For each proposed field, ask: what will we do differently with this answer? Explain why you need it and what the buyer should expect after submitting. ## Write routing rules in plain language Write a rule that your sales team can explain without opening the code. An illustrative rule might be: send a supported model enquiry to the dealer responsible for the buyer’s chosen area; send a location without coverage to a central queue. Your network must approve its own version. Give the rule a few awkward requests. What if two dealers cover the area? What if the location is missing, or the nominated dealer cannot respond? Agree who may reassign the enquiry, how the previous recipient learns about the change and where both can see the current assignment. If someone moves a request through a private message, update the shared record too. ## Design the exception path Most demonstrations show the ideal enquiry. Test the awkward cases too: - A customer selects an area outside the supported territory. - A dealer email address is invalid or a CRM connection fails. - The same person submits more than once. - A model is temporarily unavailable in the requested location. - A customer asks to correct or withdraw their details. For each case, name the person or team who takes over and show what they need to do. A label such as “needs dealer assignment” is useful only if someone knows to look for it. Keep the enquiry securely available for recovery; the operator should see the delivery problem without customer details appearing in public logs or dashboards. ## Measure the whole journey Choose a small set of stages your dealers can use consistently: received, assigned, acknowledged, contacted, appointment proposed and closed, for example. Define what evidence moves a request into each stage. Does “acknowledged” mean a system received it or a dealer accepted responsibility? Does “contacted” mean an attempted call or a conversation? Agree the meanings before comparing results. When a record closes, distinguish an unsuitable enquiry from a buyer who purchased or decided against proceeding. Review how long requests sit between stages using only the information covered by your reporting agreement. Many enquiries with little contact may point to a handover problem. Prompt contact with poor suitability may call for a review of the targeting or offer. Check the underlying records with sales before deciding which change to make. ## Pilot the process before scaling Run made-up test enquiries through every intended route, including the fallback. Have the receiving person open the final record and explain what they would do next. Check the context they received, the buyer’s acknowledgement message and the status information that returns to the campaign team. Agree how test records will be labelled or removed so they do not enter ordinary sales reporting. Keep the result specific: the tested enquiry reached the intended person and its status came back correctly. Sales volume still depends on what happens beyond that test. Our [automotive workstream](https://webvelopment.co.za/industries/automotive/) can connect [marketing](https://webvelopment.co.za/services/marketing/) with [API integrations](https://webvelopment.co.za/services/development/api-integrations/). [Discuss your dealer workflow](https://webvelopment.co.za/contact/) with a sample enquiry, your current assignment rules and the gaps your team wants to resolve. ## Work through a routing exception before launch Imagine a campaign for a defined dealer network. A buyer near a territory boundary asks about a model. Dealer A is closer, but the network has not confirmed that it handles that range. This is a planning example, not a delivered client system. Walk the request through these decisions with sales: - **Check coverage.** Use the approved model and territory information. If it does not establish a valid dealer, leave the request with the central team responsible for finding an answer. A map alone cannot decide the network’s commercial policy. - **Resolve the gap.** Suppose the network confirms that Dealer B handles this model in the buyer’s area. The authorised person updates the assignment and makes that change visible to anyone who previously received the request. Also identify who maintains the dealer information for the next enquiry. - **Check a changed request.** Resubmit the synthetic enquiry with the same details, then with a different model interest. Agree which is a repeat delivery and which needs the sales team to review the buyer’s updated request. Inspect the receiving record and sales tasks in both cases. - **Practise recovery.** Interrupt delivery in a safe test environment. Ask the operator to find the incomplete handover and follow the agreed recovery steps. Check that retrying does not create unexplained duplicate tasks. Read the buyer’s message alongside that exercise. Receipt of an enquiry can be acknowledged accurately; a dealer appointment should only be described as accepted once that has happened. At review, count submitted, assigned and dealer-accepted records separately. Report later outcomes where the network can substantiate them. You now have a concrete set of questions for the brief: who approves coverage, who resolves an unmatched request, what counts as an update and how a failed handover is recovered. Settle these with the people running the network before expanding the campaign. ## Test the routing rule and its exceptions The following is an illustrative planning check, not a reported client result. | Decision | Evidence to prepare | | --- | --- | | Known destination | Use an approved location or dealer choice and verify the receiving record and owner. | | Missing match | Exercise the fallback queue and identify who handles an enquiry without a valid dealer match. | | Duplicate submission | Retry the same synthetic enquiry and check that the process does not create another sales task. | For each check, keep the synthetic input, expected recipient and observed outcome together. Ask the receiving team to confirm the result, including the exception path. Use that material to [discuss the relevant delivery scope](https://webvelopment.co.za/industries/automotive/) or [bring a specific question to Webvelopment](https://webvelopment.co.za/contact/). ## Practical questions A few useful answers before you decide. ### Who should approve the dealer-routing rule? The business owner responsible for network operations should approve it, with the relevant dealer input. Technical staff can explain implementation and exception handling. A geographical formula should not silently establish commercial coverage or responsibility for a model. ### What makes a duplicate rule useful? It distinguishes repeated delivery from a legitimate change in the buyer’s request. Agree identifiers and behaviour with sales, then test both cases. Automatic suppression should not discard a real update, while retries should not create multiple unexplained tasks. ### How should a lead with no suitable dealer be handled? Send it to a defined exception owner with accurate expectations. Do not assign it arbitrarily to keep every record looking complete. The business needs a decision about the request and any supported alternative, rather than a technically populated dealer field. ### Does an email or API response prove dealer acceptance? Not necessarily. It can show delivery to a system or mailbox, depending on the evidence available. Define a separate acceptance stage where required. Reporting should not merge those stages simply because one is easier to automate. ### Can the same routing model be reused across countries? Only after reviewing the actual network, buying journey and operating responsibilities. A reusable technical pattern may help, but country and partner arrangements can differ. Validate the business rules instead of assuming a previously used assignment model is automatically applicable. ### What should operations know at handover? Give them the current assignment rule, where to find failed handovers, the recovery steps and the people responsible for dealer-network updates. Walk through a normal request and an exception with the operator who will use those notes. Keep access to customer details appropriately controlled and make clear who they can ask when the documented rule does not resolve a request. ## Implementation reference Consult [W3C’s accessible forms tutorial](https://www.w3.org/WAI/tutorials/forms/) for the relevant platform or accessibility detail. The planning example above is Webvelopment’s general guidance; it is not a client case study. Planning guidance from Webvelopment Editorial. Confirm platform requirements and project assumptions before committing budget. Keep exploring ## Keep the right things connected. [Industry perspective ### Dealership Websites & Automotive Systems Connect vehicle discovery, campaign landing pages and dealer enquiries with practical website, marketing and integration work for automotive businesses.](https://webvelopment.co.za/industries/automotive/)[Development ### API Integrations Connect websites, CRM and operational tools through scoped API integrations with field ownership, permissions, duplicate handling and visible delivery failures.](https://webvelopment.co.za/services/development/api-integrations/)[China → Africa ### Africa Market Entry for Chinese Businesses Connect market-entry strategy, localised websites, customer acquisition and sales follow-up, starting with South Africa.](https://webvelopment.co.za/cn/) Let’s move things forward ## Start a conversation Tell us what you are working towards. We’ll help you find a practical next step. [Discuss this planning question](https://webvelopment.co.za/contact/)