Routing Leads Fairly Between Inbound and Outbound SDR Pods

Inbound and outbound aren't sequential funnels that never touch; they run in parallel and target the same market, so overlap is the normal case, not the exception. A contact who's been in an outbound sequence for weeks can independently discover your site and submit a form, and a contact who requested a demo can also show up on an outbound list built from a different signal entirely.

Treating overlap as rare and dealing with it ad hoc guarantees inconsistent decisions. Treating it as a routine event that needs a standing rule is what actually makes the routing predictable.

Write the rule down in one place everyone can see, and pick a rule that's easy to check against a timestamp rather than one that requires judgment calls. "Whichever channel had the first documented touch keeps the lead" is checkable. "Whichever pod worked harder on it" is not, and it invites exactly the kind of dispute you're trying to avoid.

Get both pod leads to agree to the rule before it's tested by a real case, not while they're already arguing about a specific lead. Once a real dispute is on the table, everyone has an incentive to argue for whatever version of the rule favors them.

A routing rule holds up when it meets these tests:

• It is written down in one place where everyone on both pods can see it.
• It can be checked against a timestamp, such as the channel with the first documented touch keeping the lead.
• It avoids judgment calls like whichever pod worked harder, which invite exactly the disputes you want to prevent.
• Both pod leads agree to it in advance, before a specific disputed lead makes the debate personal.
• It is revisited on a set schedule as your inbound and outbound motions mature.

A first touch rule, where the channel that generated the earliest documented interaction keeps the lead regardless of what happens after, avoids rewarding whoever's fastest at updating the CRM after the fact. It also matches how most attribution models already work, which keeps your routing rule and your reporting numbers consistent with each other instead of contradicting one another.

The exception worth carving out explicitly is a lead that goes cold on one channel for an extended stretch and then re-engages through the other. Decide in advance how long a lead has to be untouched before it's considered open for the other channel to claim, rather than leaving that judgment call for the moment it happens.

This is the case that causes the most friction: an outbound rep spent weeks warming up a contact, and that contact converts by filling out a form, which inbound's routing logic then assigns to whoever's next in the inbound queue. Under a first touch rule, the lead should stay with the outbound rep who originated it, even though the conversion event looked inbound.

Make sure your CRM's automated routing rules actually reflect this. A lot of teams write the policy correctly on paper but never update the automated assignment logic to match, so the system keeps routing based on the form submission alone and quietly overrides the agreed rule every time.

Track how often routing disputes actually reach a manager for a manual decision. A working rule drives that number toward rare and occasional; a rule with gaps or ambiguous edge cases keeps generating disputes no matter how many times you remind people of the policy.

Also watch whether one pod starts quietly avoiding leads that might get reassigned to the other, which is a sign the rule feels unfair even if it's technically consistent. A rule that's followed grudgingly and undermined in small ways isn't actually working, even if it looks fine on paper.

As your inbound and outbound motions mature, the balance that made sense when outbound was newer and needed protection may stop making sense once inbound volume grows. Revisit the rule on a set schedule rather than treating it as permanent, and change it deliberately rather than letting it drift through informal exceptions that never get written down.

Apollo and lemlist both log enough activity history, including exact first touch timestamps, to settle a disputed case against the documented rule rather than relying on anyone's memory of what happened first.