Lead Routing Rules for Dealerships: Right Lead, Right Desk, Every Time

Ask a dealership where leads die and the honest answer is usually the same place: the shared inbox. Not because the team is lazy - because a lead that belongs to everyone belongs to no one. Routing rules fix the ownership problem: every lead gets an owner, automatically, the moment it arrives.

Three dimensions cover most routing

• By intent: finance requests to the finance desk, trade-ins to appraisal, vehicle inquiries to sales - the reply that starts the conversation is different for each.
• By store: multi-location groups and lead providers must match each lead to its dealership before anything else makes sense.
• By source: paid leads, organic form fills, and partner feeds can carry different SLAs and different follow-up scripts.

Start with the one dimension causing the most pain. In the routing system I built for a lead provider serving multiple dealerships - documented on the builds page - store matching was the whole game: every inbound SMS reply had to land in the right dealership's tab without a human deciding.

The unmatched queue is not optional

Rules will meet leads they cannot classify - a reply from an unknown number, a form with a typo'd store selection, a partner feed with a new field. The wrong move is guessing; misrouted leads erode the team's trust in the whole system. The right move is a review queue: unmatched leads drop into a visible holding area, flagged for a human, and each resolution teaches you a rule worth adding. In the build above, that exact "no match → drops to review" path is in the workflow diagram because it ran that way in production.

Kill duplicates at the door

The same buyer submits twice, replies twice, or arrives from two sources. Without deduplication, two salespeople call the same person - which looks exactly as disorganized as it is. Match on phone or email within a time window, keep the richer record, and log the duplicate against it rather than creating a second lead.

Keep the rules visible and boring

Routing logic buried in a vendor's settings screen becomes folklore - nobody remembers why leads go where they go. Write the rules down somewhere the team can read: intent X goes to desk Y, store matching works like Z, unmatched goes to review, duplicates merge. Boring, legible rules survive staff turnover; clever invisible ones do not. What happens after routing - statuses, reminders, dashboards - is covered in the follow-up system post.