Operations

How do you handle inbox rotation across multiple campaigns?

opsguru_nat · 2026-03-19 · 289 views

This is becoming the hardest operational problem in my cold email setup and I never see anyone talk about it. I'm running 8 active campaigns simultaneously across 3 different client segments (SaaS founders, agency owners, and ecom brands). I have 42 inboxes across 14 domains. And managing which inboxes go to which campaigns without burning any of them is genuinely difficult.

The problems I keep running into:

What I've tried: A spreadsheet with inbox assignments, status (warmup/active/resting), and campaign tags. Works okay at 20 inboxes but at 42 it's becoming unmanageable. Smartlead has inbox rotation built in but it doesn't solve the cross-campaign overlap problem.

What I want: A system — whether it's a tool, a process, or a mental model — for rotating inboxes across multiple campaigns at scale without stepping on my own toes. How are people running 50+ inboxes handling this?

Comments (6)

scaledsam · 2026-03-19

running 60 inboxes across 4 clients and the spreadsheet approach broke down for me around inbox 30. what works now: I assign inboxes to "pools" — each pool is tied to one client segment. pools never overlap. when an inbox needs to rest I pull it from the pool and tag it as cooling down in Smartlead. every Monday I review which inboxes are resting and swap them back in. it's not perfect but it keeps the cross-contamination problem under control

opsguru_nat · 2026-03-19

the pool model is interesting. do you ever have a situation where one pool runs out of active inboxes because too many are resting at the same time? that's my fear — I'd rather over-assign than have a campaign go dark for a week

scaledsam · 2026-03-19

@opsguru_nat yeah it's happened twice. the fix was to build in buffer inboxes — I keep 2 extra warmed inboxes per pool that aren't assigned to any campaign. they're just sitting there doing warmup. when an active inbox needs to rest I swap in a buffer. it's a few extra bucks a month but saves you from campaign downtime

automationali · 2026-03-19

I built a simple Airtable base for this. columns: inbox email, domain, pool, status (warmup/active/resting/retired), campaign, daily limit, last rest date, next scheduled rest. then I set up an automation that flags any inbox that has been active for more than 3 weeks without a rest period. took about 2 hours to set up and it's saved me way more time than that in the last 3 months

coldkingdom · 2026-03-19

the overlapping audience problem is the one that burns people the most. if prospect X gets email from john@getacme.com about your SaaS tool AND from john@getacme.com about your consulting service, that's an instant credibility killer. I flag this by running a dedupe check on my prospect lists across campaigns before launching. takes 10 minutes and prevents embarrassing overlap

agency_pete · PipelineForge · 2026-03-19

At our scale (200+ inboxes, 14 clients) we rotate inboxes on a fixed 3-week cycle: 3 weeks active, 1 week rest. No exceptions. Each client gets a dedicated pool and we never share inboxes across clients even if the audiences don't overlap. It's more expensive but eliminates an entire category of ops problems. The buffer inbox idea from @scaledsam is exactly right — always have warm reserves ready.