Skip to content

Lead distribution across a shared SDR roster

Distribute leads across a shared SDR pool without collisions: rosters per client, expiring lead reservation, inbound routing and scoped visibility.

Updated 9 October 2026ForManagers allocating work across a shared rep pool
inbound call · Tremont DentalNorthgate Ltd
  1. 1Lead reserved byno active reservationnone
  2. 2Last outbound touchSMS · Dave Moss · Tue 14:20owner
  3. 3Project rosterfallback · 3 SDRsif unanswered
Ringing Dave MossSMS counts for calls too
Illustrative example — sample data, not a customer screenshot.

What this gets you

A named SDR roster per client project, separate from the account manager

Expiring reservation so two reps never work the same company

Inbound calls and SMS routed to whoever actually owns the conversation

Permission-scoped visibility — contractors see only their rostered clients

Capacity-aware allocation using per-rep, per-client rates

Lead distribution for an agency is not round-robin

Most lead distribution tools split one pool by a rule: round-robin, weighted or by territory. In an agency, SDRs are shared across clients with different scripts, prices and commission. “Who owns this lead right now” needs one answer at every moment, including when the prospect calls back.

Each client project has a named roster

The roster is the set of SDRs assigned to a client project, kept separate from the account manager who owns the client. It is stored, not inferred from activity, so “who is working Client A this week” and “who gets credit for this booking” each have one answer.

Within the roster, SDRs claim leads

Pre-assigned leads

  • Leads sit against an SDR who touched them once
  • Lists stall while other SDRs have nothing to call
  • Two SDRs still call the same company when assignments overlap

Expiring reservation

  • Opening a lead reserves it to that SDR, with an expiry
  • Calling or logging an outcome extends it; a final outcome releases it
  • A background job clears stale holds, and leads with real contact keep theirs

Callbacks reach the SDR who had the conversation

One resolver handles every inbound call and SMS, in this order:

  1. 1

    Reserved lead

    The SDR holding the reservation gets it.

  2. 2

    Last outbound touch

    Otherwise the SDR who last called or texted. An SMS counts for an inbound call, and the other way round.

  3. 3

    Project roster

    Otherwise the roster. An unanswered call falls through to a wider set instead of dropping.

Visibility follows permissions

An SDR without an all-access grant sees only the client projects they are rostered on. Granting the Employee template gives the same person full access with no role change. That keeps contractors out of each other’s clients.

Allocation uses capacity

Meetings-per-hour rates per SDR per client, with manager overrides, against hours net of public holidays and absences. See capacity planning for the rates, and lead management for how lists are prepared. The routing rules themselves are covered in the lead routing guide.

Book a walkthrough

Put every client on one floor

A walkthrough on your own roster, clients and commission model — from an imported list to a sent invoice. Judged on your operation, not a demo dataset.

One booked meeting pays for an SDR's seat for the month.

EU-hosted · eu-central-1 · integrates the CRM, calendar and telephony you already run