Why agencies should track sequence queue depth per client, not just daily send volume

Daily send volume tells you what left the building. Queue depth tells you what is about to explode.

Agency dashboards love the first number. Sends today. Sends this week. Opens if anyone still trusts them. Then Monday arrives, five client campaigns all fire step two, and two mailboxes hit the cap while a third sits idle. Lemlist's outreach-queue docs exist for this exact failure: planned actions versus sender limits, color-coded so you see orange before you ship a spike. Hunter's sequence sending notes make the same point from the other side. Limits apply per sender account, not per sequence, and older sequences can starve newer ones when capacity is shared.

LobsterMail's capacity-planning write-up is blunt about the downstream risk. A backlog that finally clears can dump volume in bursts that invite ISP throttling and soft bounces. Mumara's queue guidance adds the diagnostic cut: depth by destination domain and pool, so you can tell a Gmail-wide throttle from one unhealthy sender pool.

What queue depth should mean in a multi-client workspace

Track these per client workspace, not as one agency blob:

• Steps due today, tomorrow, and the next three send days
• Steps waiting on sender capacity versus steps waiting on a send window
• Age of the oldest queued step
• Share of queue sitting on each mailbox and each LinkedIn seat
• Channel split: email versus LinkedIn invitations versus LinkedIn messages

Lemlist's capacity math is useful even if you build the view yourself. Email capacity is scheduled sends divided by daily email limit. LinkedIn capacity is scheduled invites plus messages divided by those limits. Green means headroom. Red means you are about to block actions or burn reputation with a catch-up blast.

Daily send volume alone hides three agency failure modes:

1. Starvation. A hot client campaign shows low sends because an older campaign owns the mailbox queue.
2. Monday pileups. Holiday and weekend delays stack due steps into one morning.
3. False health. Yesterday's send count looked fine while tomorrow's queue is already 2x the safe cap.

Ops moves when depth is the scoreboard

1. Read the next three to five send days before launching another campaign into the same client workspace.
2. Spread steps when a day is orange or red instead of "just sending more."
3. Prioritize positive-reply follow-ups and warm referral touches ahead of cold step ones when capacity is tight.
4. Rotate or add healthy senders only after auth, warmup, and isolation checks, not as a panic move mid-spike.
5. Put queue depth on the weekly client scorecard next to conversations booked, not next to vanity reply rate.

GTM runs find → qualify → write → send/reply/book with per-client send windows, domain limits, and isolated workspaces. Capacity only stays honest if each client queue is visible on its own.

If you want outbound capacity and reply handling managed inside client-isolated workspaces, join the waitlist.