Inbox Rotation for Cold Email: What It Spreads and What It Doesn't

Inbox rotation is sending one cold campaign from several mailboxes, so each mailbox carries a small share of the daily volume. It is useful for keeping per-inbox numbers low and for surviving the loss of one mailbox. It does not spread domain reputation, list quality or complaint rates. Mailboxes on the same domain still share that domain's standing, and a bad list damages all of them at once.

This post explains what rotation does in the two tools most people use for it, what it leaves untouched, and how to size and run a rotation without creating new problems. Tool behaviour is taken from Instantly's and Smartlead's own documentation.

How rotation works in practice

You connect several mailboxes, assign them to a campaign, and the tool spreads sends across them. Instantly's campaign options describe the "Accounts to use" setting:

"This selection determines which inboxes will send messages for this campaign. Please select all the accounts you want to use for this campaign, and the system will start sending emails from all of these accounts automatically."

Instantly lets you assign accounts by tag, sets a default minimum gap between emails, and recommends "30 campaign emails + 10 warmup emails per day per email account". Its limits article separates two numbers: the account limit, the maximum each account sends "across all campaigns", and the campaign limit, the total "from all accounts in a specific campaign". Its suggested campaign limit is the number of accounts multiplied by 30.

Smartlead's API documentation says it "automatically rotates between your connected email accounts" to "distribute sending load" and "avoid ESP limits", and setup includes adding "sender accounts for rotation".

What rotation genuinely spreads

Per-mailbox volume and single-mailbox risk. Three real benefits:

1. Each mailbox stays far below provider caps. Google Workspace allows 2,000 unique external recipients per user per day; our post on cold emails per day per inbox covers the limits in detail. Rotation keeps each inbox at a tiny fraction of that.
2. One suspended mailbox does not stop the campaign. If a provider locks an account, the others continue.
3. Per-mailbox reply load stays manageable, which matters if replies are read in each inbox rather than a unified view.

What rotation does not spread

Anything measured at the domain, the list or the recipient's mailbox provider. This is where most rotation setups go wrong.

Risk	Is it spread by rotation?	Why
Domain reputation	No, not within a domain	Every inbox on getacme.com signs with and sends from the same domain
Bulk sender classification	No	Google's bulk sender FAQ counts "all messages sent from the same primary domain", subdomains included
Spam complaints	Only the per-inbox count	Complaints still land against the domain and its authentication
Bounces from a bad list	Only the per-inbox count	The list is the same whichever inbox sends to it
Shared tracking domain	No	Every inbox in the tool may use the same tracking host unless you set a custom one
Shared IP reputation	Depends on provider	Google notes that activity of "any senders using a shared IP address affects the reputation of all senders for that shared IP address"

The common mistake is to treat ten inboxes as ten independent senders. If all ten sit on one domain and the list has a 6% bounce rate, all ten send that 6% and the domain absorbs it. Splitting inboxes across several secondary domains isolates domains from each other, but each domain still lives or dies by the list you put through it.

Follow-ups and threading

Follow-ups should come from the same mailbox as the first email, and the tools are built to do this. Instantly's article on keeping sequences in the same thread says:

"Instantly sends all follow-ups from the same sending account by default."

It also warns what happens if you change the rotation mid-campaign: when you remove an account, "leads will receive follow-ups from another active account, which will create a new thread." A prospect who gets step one from Sam and step two from Alex, in a new thread, sees an obvious mass campaign.

Rules that follow from this:

• Do not remove inboxes from a live campaign unless they are compromised. Let their sequences finish, then stop adding new leads to them.
• Keep the sender name consistent with the mailbox. A rotation of five mailboxes all named "Sam" on different domains looks odd if a prospect compares them.
• Leave follow-up subject lines empty in Instantly so they inherit the first subject, per the same article.

Sizing a rotation

Size from total daily sends including follow-ups, then divide by a conservative per-inbox cap. A worked example, with assumptions you should change for your case:

Input	Value
New prospects per day	120
Steps per sequence	3
Steady-state daily sends	360
Per-inbox cap	30 (Instantly's recommendation)
Inboxes needed	12
Inboxes per domain	3
Domains needed	4

In Instantly terms, that is 12 accounts with an account limit of 30 each, and a campaign limit of 12 × 30 = 360. Every new inbox needs warm-up before it joins the rotation; see the warm-up schedule.

Rotation and unsubscribes

An unsubscribe sent to one inbox must stop mail from all of them. A prospect who replies "remove me" to the mailbox that emailed them, and then hears from a sibling mailbox next month, has not been removed. In the UK and EU that is also a failure to honour an objection. Keep one suppression list at workspace level, not per inbox, and check new lead imports against it.

The same applies to bounces. A hard bounce recorded against one inbox should suppress that address everywhere, or the next campaign will send to it again from a different mailbox.

Clean the list before you scale the rotation

Rotation multiplies whatever is in your list. Adding inboxes adds capacity, and capacity sends the same bad addresses faster. Verify before upload, separate catch-all addresses into smaller batches, and remove role addresses you do not mean to email. SimpleVerifier verifies CSVs up to 100,000 rows and exports valid, risky and invalid addresses separately, which maps directly onto a "main rotation" and "small cautious batch" split. Any verifier that separates those categories will do the job.

The short version

Rotation is a capacity and resilience tool, not a reputation tool. Use it to keep each mailbox around 30 cold sends a day, keep follow-ups on the original mailbox, suppress unsubscribes and bounces across the whole workspace, and spread inboxes across several properly authenticated domains. Then remember that every inbox is only as safe as the list you feed it. If bounces are already climbing, start with why cold emails bounce before adding inboxes.