SOPs 10 min read

Inbox Rotation SOP: How to Rotate Sending Accounts Before They Burn

Rotation isn't something you do after inboxes burn — it's a scheduled maintenance practice that prevents burning. Here's the full rotation system: pools, triggers, cadence, and replacement flow.

Cold email inboxes are consumable infrastructure. Treat them like tires: rotate on schedule, replace at the wear-bar, and never run to blowout. Agencies that rotate proactively hold stable reply rates for years; agencies that run every inbox at full volume until it dies live in a permanent recovery cycle.

The three-pool model

Structure every client's sending infrastructure into three pools:

  • Active pool — inboxes carrying campaign volume right now, at 20–40 sends/day each.
  • Resting pool — inboxes on reduced or warmup-only volume, recovering engagement metrics. Target 25–35% of your fleet resting at any time.
  • Standby pool — warmed, tested, zero campaign history. This is your failover capacity. Minimum 20% of active capacity; agencies with SLA-style commitments hold 30–50%.

Size the pools with the inbox count calculator and cost them with the backup budget tool.

Rotation triggers

Rotate an inbox out of the active pool when any of these fires:

Mandatory rotation triggers

  • Reply rate for that inbox drops 40%+ below the domain's trailing average for 5+ sending days
  • A placement test from that inbox lands in spam or promotions
  • Bounce rate for the inbox exceeds 4% on any single day
  • The inbox hits 8–10 weeks of continuous full-volume sending (scheduled rotation — don't wait for symptoms)
  • The domain picks up any blacklist listing — rotate all inboxes on that domain and check with the blacklist tool

The rotation procedure

  1. Promote from standby. Move a standby inbox into the active pool. Start it at 50% target volume for 4–5 days before full load.
  2. Demote the flagged inbox to resting. Drop to warmup-only traffic. No campaign sends for a minimum of 14 days.
  3. Re-test before reactivation. A resting inbox returns to active only after a clean placement test and two weeks of positive warmup engagement. If it fails re-test twice, retire it.
  4. Backfill standby. Every promotion out of standby triggers a replacement order the same day. Standby capacity is only useful if it's always full. This is where pre-warmed inboxes earn their keep: ordering from WarmInboxes refills the standby pool in days, whereas warming replacements yourself leaves a 3–4 week capacity hole.

The standby pool is the whole system. Rotation without ready replacements is just controlled shrinkage — you'll end up overloading the surviving inboxes, which is exactly how whole domains burn.

Cadence summary

  • Daily: automated volume caps enforced per inbox (30–50 cold sends max)
  • Weekly: review rotation triggers during the weekly monitoring sweep
  • Every 8–10 weeks: scheduled rotation of active inboxes regardless of symptoms
  • Quarterly: retire the worst-performing 10–15% of the fleet permanently and replace with fresh pre-warmed capacity

Common rotation mistakes

  • Rotating inboxes but not domains. If a domain's reputation is damaged, every inbox on it inherits the problem. Rotation happens at the domain level too — plan domain counts with the domain calculator.
  • Resting for a weekend. Two days changes nothing. Minimum meaningful rest is two weeks of warmup-only activity.
  • Running standby at zero. The day you need standby capacity is the worst day to start building it. Keep it stocked — WarmInboxes pre-warmed accounts are the fastest way to hold that buffer without dedicating a month of internal warmup effort per batch.

Run the checks first

Before replacing anything, run a free inbox placement test. You might find the issue is DNS, not the domain — and save yourself a week of unnecessary work.

Free inbox placement test Check burn score

More guides

The Weekly Deliverability Monitoring SOP (Copy This Into Your Agency Playbook)New Domain Provisioning SOP: From Purchase to First Cold Email (Step by Step)Agency Client Onboarding SOP: The Deliverability Audit That Prevents Week-3 Fires