How to Set Up Lead Routing in Your CRM

A lead that reaches the right rep four hours late has already cooled. A lead that reaches the wrong rep instantly is just as wasted. Most setups fix one and ignore the other: a tidy round-robin that runs in a nightly batch, or a fast rule that ignores territory and starts two reps on the same logo. Good routing is both correct and immediate. It qualifies the lead, decides whose it is, assigns the owner in the CRM, and tells the rep, all in the minutes that matter. This is how to build routing that is right and fast.

What you need before you start:

• A Clay account connected to your CRM: Salesforce or HubSpot, with write access to the owner field.
• Your lead sources flowing into Clay: Form fills, demo requests, or a CRM list.
• Your routing rules written down before you build: Territories, segment splits, account-ownership policy, and the rep pool for each — routing logic you cannot state plainly is routing logic you cannot automate.

Step 1: Qualify the lead before you route it

Routing junk to a rep is worse than not routing it at all.

The first job of a routing workflow is to decide whether a lead deserves a rep, not which one. As leads arrive, enrich them and run a quick fit-and-intent qualification (the same enriched fields a lead score uses), so only leads that match your ICP enter the routing logic. Everything else goes to nurture, self-serve, or disqualified. This keeps rep queues full of workable leads and stops the round-robin from handing out noise, which is the fastest way to get reps to stop trusting routed leads at all.

Step 2: Decide whose lead it is, with rules before round-robin

Round-robin is the last step of routing, not the whole thing.

Most leads are not a blank round-robin draw, because territory, segment, and existing relationships decide ownership first. Apply those rules in order: route to the existing account owner if the company is already in the CRM, then by territory or segment for the rest, and only then distribute the leftover unowned leads round-robin. In Clay this is conditional logic plus the assignment actions: conditional runs send a lead down the branch that matches its region or segment, and the Round-robin and Weighted round-robin actions pick the rep at the end. Getting the order right is what stops two reps from working the same account.

To split leads into territory or segment branches cleanly, a Use AI column can classify a lead into the right bucket when the raw fields are messy:

Step 3: Distribute the pool fairly, by capacity not just turn

A plain round-robin assumes every rep has the same room. They do not.

For the unowned leads that reach the round-robin, decide whether even is actually fair. A Standard round-robin assigns in strict rotation, one each in turn, which is right when reps are interchangeable. A Weighted round-robin gives more leads to the reps who can handle them (a senior AE at full ramp, fewer to someone onboarding or near capacity), which is right when they are not. Weighting by capacity keeps fast reps fed and stops your newest hire from drowning while the rotation treats them as equal.

Step 4: Assign the owner in the CRM and tell the rep

A routing decision that does not write to the CRM and ping the rep is a decision nobody acts on.

Once the rep is chosen, write it where work happens. Use the CRM action to set the owner field on the record (the Salesforce owner, or the HubSpot owner resolved with Find owner), keyed on the record ID so the assignment lands on the right lead and never spawns a duplicate. Then trigger the handoff: post the lead to the rep's Slack or Teams channel with the enriched context and the reason it was routed to them, and enroll it in the right sequence. The rep gets a routed, owned, context-rich lead in their CRM and their inbox at the same moment, not a row they have to discover.

Step 5: Make it fast, and keep it fast

Routing speed is the whole point, and it decays quietly.

The reason to automate routing is speed-to-lead: the gap between a lead raising a hand and a rep reaching out is the single biggest lever on whether the conversation happens, and minutes beat hours. Run the qualify-route-assign-notify workflow on the trigger (a new form fill, a new CRM record), not on a nightly batch, so a lead that comes in at 2pm is owned and contacted by 2:05, not tomorrow. Then watch the edges: reps go on PTO, capacity shifts, territories get redrawn. Keep the rep pools and weights current and add fallbacks (if the assigned rep is out, reassign rather than let the lead sit) so the routing that was fast in January is still fast in June.

When routing runs on the trigger, the lead is owned and contacted while it is still warm.

Common failure modes, and how to avoid them

Most lead-routing setups fail the same few ways. Watch for these.

• Routing before qualifying: A round-robin that hands out every form fill fills queues with noise and trains reps to ignore routed leads. Qualify first; only workable leads enter the routing logic.
• Round-robin before rules: Distributing every lead evenly ignores territory and existing ownership, so two reps end up on one account. Apply owner and territory rules first, round-robin only the remainder.
• Even when even is not fair: A strict rotation buries a ramping rep and starves a senior one. Weight the round-robin by capacity.
• Deciding without assigning: A routing rule that does not write the owner to the CRM and notify the rep is a decision nobody sees. Set the owner field and ping the rep with context in the same run.
• Batch routing: A nightly run turns a five-minute speed-to-lead into an overnight one. Trigger routing on the new lead, not on a schedule.

Outcomes teams report after automating lead routing and qualification with Clay