Inbox Rotation

Why it matters for outbound teams

Mailbox providers throttle or flag accounts that send high volumes of cold outreach from a single address, so spreading sends across dozens or hundreds of inboxes keeps per-inbox volume low and natural-looking. This is standard practice in tools like Smartlead and Instantly, which are built around managing large rotations. The tradeoff is that replies now land across just as many inboxes, which is the problem a unibox exists to solve.

How inbox rotation works

In a rotation, a campaign is not tied to one mailbox. The sequencer holds a pool of connected mailboxes and assigns each outgoing email to one of them, cycling through the pool or choosing by capacity. Each mailbox has a daily sending limit, so the total volume of the campaign is the sum of what the pool can send within those limits.

The idea is simple: ten mailboxes sending thirty emails each look more natural than one mailbox sending three hundred. Most teams combine it with warmup, several sending domains, and conservative daily limits. Sequencers such as Smartlead and Instantly are built around managing large pools, and teams keep them for sending for exactly this reason.

A good rotation also handles failure. If a mailbox is paused, disconnected or hitting limits, the sequencer skips it and the others carry the load.

How to set it up

• Group mailboxes by domain. Put a small, fixed number of mailboxes on each domain, so a problem with one domain does not touch the others.
• Set per-mailbox limits. Start low, raise slowly, and keep the limit the same for all mailboxes in a campaign so the load stays even.
• Warm every mailbox. New mailboxes need warmup before they carry campaign volume.
• Keep a spare. Hold a few warmed mailboxes in reserve to swap in when one is paused.
• Plan the reply side. Each mailbox in the pool will receive replies. Decide before launch where those replies will be read.

The reply side is where Master Inbox fits. Its Unibox reads the mailboxes themselves, so replies from every mailbox in a rotation arrive in one AI-labeled list, and the pool can grow without adding more places to check.

A worked example

This is an illustrative example with round numbers, not measured data. A team wants to send 1,000 emails a day. At 25 emails per mailbox per day, that needs 40 mailboxes. At three mailboxes per domain, that is about 14 domains.

If the team instead tried to send from 5 mailboxes, each would carry 200 emails a day, which is far above a cautious limit. With the rotation, each mailbox sends 25, and the load is spread. On the reply side, 40 mailboxes now receive replies. Without a shared view, someone checks 40 inboxes. With one, the replies appear in a single list, ready to label and answer.

Common mistakes

• Uneven limits. One mailbox sending triple the others becomes the weak point.
• Too many mailboxes per domain. Concentrating mailboxes on a few domains means one reputation problem affects many.
• Skipping the unibox. Rotation multiplies the places replies land. Plan the inbox side at the same time.
• Setting and forgetting. Check mailbox health and replace weak mailboxes on a schedule.

See deliverability for the wider picture of what protects inbox placement.

Finally, keep records. Note which mailbox belongs to which domain, which client it serves and when it was created. When something goes wrong, that map saves hours. Agencies running client workspaces usually keep one pool per client.

Frequently asked questions

What is inbox rotation in cold email?

Inbox rotation spreads a campaign's sends across many mailboxes and domains, so each one sends a modest, natural-looking amount. The sequencer cycles through the pool automatically, and the total volume is the sum of what each mailbox sends.

How many mailboxes do I need for rotation?

Divide your target daily volume by the safe daily limit per mailbox. For example, 1,000 emails a day at 25 per mailbox needs 40 mailboxes. Add a few spares so a paused mailbox does not reduce your volume.

Does inbox rotation make replies harder to manage?

It spreads replies across every mailbox in the pool, so you need one place to read them. A unibox or unified inbox gathers those replies into a single list, so rotation does not add work on the reply side.

Is inbox rotation enough to protect deliverability?

No. It helps by keeping per-mailbox volume low, but it works alongside warmup, clean lists, authentication and good copy. Think of rotation as one control among several, not a guarantee of inbox placement.

← All glossary terms