Lead Assignment: Round Robin vs Skill-Based Routing

Round robin feels fair. Every rep gets the next internet lead. Nobody can accuse the manager of feeding the closer. Then you watch a first-year associate get a $48,000 diesel that needs a commercial conversation, and your truck specialist get a $9,500 commuter that a junior could have handled. Fair distribution produced a mismatch, a slow first call, and a customer who already messaged two other stores.

Skill-based routing feels efficient until it becomes a caste system. The same two reps get every "good" lead. Everyone else gets crumbs, stops working the crumbs, and the desk invents a black market of lead stealing. The internet manager spends Thursday afternoons in ownership fights instead of coaching.

Lead assignment is not a personality contest. It is an operating design choice: round robin vs skill-based routing, or a hybrid with written exceptions. This guide is for general managers and internet directors who need a rule they can explain on a whiteboard and audit in the CRM. It is not a claim that one model "converts better" in every store. It is a way to pick a model and stop improvising.

What Lead Assignment Has to Solve Before You Pick a Model

If you skip this section, you will argue about fairness while the real leaks stay open.

Ownership in minutes, not in theory

A lead is unassigned until a named human is responsible for the first contact. "The internet department" is not a name. "Whoever is on the floor" is not a name. Assignment must produce:

• One owner.
• A timestamp.
• A first-attempt expectation (call, text, or in-app reply) that matches speed-to-lead standards by lead type.

Coverage when the owner is on a test drive

The model has to say who covers overflow. Round robin without overflow becomes a queue of aging new leads. Skill-based without overflow becomes a specialist who is also the bottleneck.

Source and unit context

A Marketplace "is this still available" on a specific VIN is not the same object as a third-party credit app with no vehicle. If your CRM dumps both into one bucket labeled Internet, no routing model can be smart. Fix source naming first; lead source conventions are a prerequisite.

Pay plan alignment

If the pay plan only pays the closer, round robin is a gift of unpaid work. If it only pays the first appointment, specialists will dodge hard units. Routing and spiffs for online lead handling have to be designed together or the floor will route around you.

Round Robin: When Even Distribution Is the Right Default

Round robin assigns the next lead to the next eligible rep, then the next, in a loop.

Where round robin earns its keep

• Small used lots where every rep sells every unit type.
• Stores building a new internet muscle and needing volume practice for everyone.
• Shifts where you cannot staff a true specialist bench.
• After-hours buckets that must be split at open without a manager sitting in the chair.

Rules that keep round robin from becoming a lottery ticket

• Eligibility, not just a name list. Off the clock, on a deal, or already over a daily cap means skip. A loop that assigns to a rep at lunch is not fairness.
• Daily cap. A conservative operating standard: no one person should absorb an entire morning dump because they happened to be first in the loop. Set a cap, overflow to the next eligible, then to a manager.
• Same-unit exception. If the customer already talked to Jordan on that VIN, Jordan keeps it. Round robin does not get to reset a conversation.
• Skill veto for defined exceptions. Write the two or three unit types that never go to a brand-new associate (for example, commercial diesels, rebuild titles if your store sells them). That is still round robin with a short skip list, not a secret skill model.

Failure mode to watch

Reps learn to "be busy" when a weak lead is next and "be free" when a truck hits. If you cannot see who skipped, round robin is theater. The skip log is part of the system.

Skill-Based Routing: When the Unit or the Buyer Needs a Specialist

Skill-based routing sends the lead to the person whose skill matches the work: trucks, BHPH conversations, Spanish, commercial, luxury, or simply "can run a Marketplace thread without sounding like a bot."

Where skill-based routing is justified

• Franchise used departments with a real mix of cars, trucks, and CPO-adjacent units.
• Lots that sell a specialist product (diesel, enthusiast manuals, commercial upfits).
• Bilingual markets where the first response language is the whole game.
• High-priced units where a junior first call creates a discount conversation you cannot recover.

How to define "skill" without folklore

Skills must be binary and observable:

• Licensed / permitted to discuss a product the store actually sells.
• Documented product knowledge (for example, the truck desk, not "good closer energy").
• Language.
• Role: BDC first-response vs floor close. That is a handoff design, covered in BDC vs floor handling, not a personality rating.

Do not route on "who sells the most." That is a popularity contest with a CRM badge.

Failure modes to watch

• Hoarding. Specialists sit on twenty open leads and still receive the next diesel.
• Starvation. Newer reps never see a truck, then never become able to see a truck.
• Undefined skills. If "luxury" is a vibe, everything expensive routes to one person until they quit.

Cap open internet leads per specialist. Overflow to the next qualified person, then to the manager, not back into a black hole.

Lead Assignment in Practice: A Hybrid Most Used-Car Desks Can Run

Pure models look clean in a memo. Hybrid is what most stores need.

A practical split

Write this table into the CRM playbook. If it is only in the internet manager's head, it is not a system.

Time caps beat perfect matching

A conservative operating pattern: if the skilled owner has not made first contact inside your speed standard, the lead is eligible for the next qualified person. Skill that is too slow is not skill. It is delay with a title.

Inventory assignment is not the same as lead assignment

Do not confuse "who posts the car" with "who owns the buyer." Posting queues can be manager-assigned to associates while leads route to licensed salespeople. See assigning inventory to floor reps. Mixing those two systems is how an associate gets yelled at for a deal they were never allowed to close.

Implementation Checklist for the Internet Manager

1. Name the objects. Lead, owner, source, VIN, first-attempt clock.
2. Pick the default (round robin or skill) for each lead type in the table above.
3. Write skip and overflow rules. Off-shift, over cap, same-VIN, language.
4. Align pay. First response, appointment, and close cannot all be unpaid favors.
5. Publish the dispute rule. When two reps claim the same customer, the CRM timestamp plus the written exception list decides, not who talks louder. Ownership fights get their own playbook; do not leave them to the parking lot.
6. Review weekly. Open-lead counts by owner, first-attempt times, skip rates, and aged new leads. If one person is always "next" in round robin, the eligibility list is broken. If one specialist has a private inventory of internet leads, the cap is broken.

Roles that should not be in the round robin

Using the store's real job design, not folklore:

• Associates who are posting-only should not receive sold-unit closing leads if policy says they cannot take the deal.
• Managers can be overflow, not the default dump, or they will never coach.
• Admin logins are not a sales queue.

Map people to admin, manager, sales rep, and associate the same way you map posting rights. Shared logins make both posting and lead assignment un-auditable.

How PostToMarket Automates This

Round robin vs skill-based routing fails in practice when nobody can see who owns the work, which unit is live, or which source produced the inquiry. PostToMarket does not replace your CRM's assignment engine. It gives the floor a clean inventory and a visible posting queue so routing decisions are about people, not about hunting for the car.

Make the unit assignable

• Unlimited inventory with statuses so you do not assign a lead on a sold or failed listing.
• Mark as sold and archive so yesterday's Marketplace inquiry does not get routed as a live opportunity.
• Capture from auction and wholesale sites plus CSV/Excel import with row-level errors, so new units enter inventory fast enough that VIN-specific leads have a real card.

Make the people assignable

• Roles: admin, manager, sales rep, associate — posting-only associates are not accidentally treated as closers.
• Manager assignment of vehicles to associate queues; sales reps self-queue from shared inventory.
• Team queue view to release a claim so overflow routing has somewhere to send the unit work.
• Leads inbox so managers can see unanswered conversations when the assigned owner is stuck.

See source before you argue about fairness

• Posting analytics by rep and source so you know whether a source even produces work worth routing.
• Mobile dashboard so a rep can reorder posting work between customers without dropping a lead they were just assigned.

PostToMarket is independent software, not a Meta product. It will not magically pick the best closer. It keeps the inventory and queue honest so your assignment rules can run.

Choose a Routing Rule You Can Audit on Monday

Lead assignment — round robin vs skill-based routing — only works if a stranger could read the table, look at the CRM, and agree who owns the next internet lead. Fairness without speed is a waiting room. Skill without overflow is a bottleneck. Write the hybrid, cap the specialists, skip the off-shift names, and review the skip log.

PostToMarket supports that operating system with per-rep queues, manager assignment, a leads inbox, and inventory statuses that prevent routing a buyer to a car that already left. Starter is $59 per month for a solo operator, one login. Dealership is $299 per month for a team of up to 13 logins, including two manager seats.

Start your 10-day free trial on secure Stripe checkout. Import the lot, assign the queues, and stop treating the next lead as a parking-lot argument. Cancel anytime.