How to rotate sends across your mailboxes
How-to guide Updated 12 July 2026
How do you rotate cold email across multiple mailboxes?
Set a per mailbox daily limit on the campaign, then attach a pool of mailboxes to it. HotHawk spreads every send across the pool in turn, so no single account sends too much too fast. From Claude that is two sentences, and it is how a workspace sends 40,000 emails a day and more without torching one domain.
No credit card required.
Before you start
You need a HotHawk account and the HotHawk MCP server connected to Claude. It takes a couple of minutes and no code. Full setup is on the MCP server page.
Step by step
-
1
You ask Claude
Create a campaign called Enterprise Q3 with a daily send limit of 40 per mailbox.
Claude callsmcp__hothawk__campaigns_createname "Enterprise Q3" type COLD dailyLimitPerMailbox 40Claude builds the draft and sets the per mailbox cap, so no single account ever sends more than the modest, human number you chose.
-
2
You ask Claude
Attach all twelve of my acme-outbound mailboxes to it.
Claude callsmcp__hothawk__campaigns_mailboxes_createcampaignId Enterprise Q3 mailboxIds 12 mailboxesThe pool is attached. HotHawk now spreads every send across the twelve inboxes in turn, so the campaign moves fast while each account stays gentle.
-
3
You ask Claude
That gives me plenty of headroom. Confirm the daily ceiling.
Claude callsmcp__hothawk__campaigns_mailboxes_getcampaignId Enterprise Q3Claude reads it back: twelve mailboxes at 40 a day each is 480 sends a day from one campaign, and that is before you widen the pool or add more campaigns.
Volume comes from the pool, not the inbox
Here is the maths that decides whether a cold email programme works. One mailbox can send maybe forty cold emails a day before its reputation starts to slip. Push it to four hundred and you are not scaling, you are lighting a fuse. The teams sending real numbers know this, so they never ask one inbox to do more than it should. They ask a lot of inboxes to each do a little.
That is inbox rotation, and it is the single most important piece of cold email infrastructure. The campaign fires as fast as you like because the sends are shared out, but every individual account stays modest and calm. Your daily ceiling is not a property of one mailbox. It is a property of how many you have pointed at the campaign.
Two sentences to wire it up
Rotation in HotHawk is a cap plus a pool. First you set the per mailbox daily limit when you create the campaign, so no account can ever overreach, no matter how big the list. Ask Claude for a campaign with a limit and it runs campaigns_create with that ceiling baked in.
Then you attach the mailboxes. Ask it to add your pool and it runs campaigns_mailboxes_create, and from that moment HotHawk spreads every send across the attached inboxes in turn. Twelve mailboxes at forty a day is 480 sends from one campaign, each account barely breaking a sweat. Add mailboxes and the number climbs in lockstep.
This is how you get to 40,000 a day
Scale the same idea up and the numbers get serious. Hundreds of warmed inboxes, each sending a sensible amount, is how a HotHawk workspace sends 40,000 emails a day and beyond without any one domain carrying the strain. There is no heroic mailbox in that picture. There is a wide pool, warmed on real Google and Microsoft inboxes, rotating quietly.
So when a campaign needs to send more, the move is never to lean harder on what you have. It is to widen the pool. Connect more mailboxes, check they are warmed and healthy, attach them, and the ceiling rises. Every one of those steps is a sentence in the same chat, which is rather the point of running your infrastructure from Claude.
The HotHawk tools behind this
Every action here is a real endpoint. Claude reaches it over the MCP server, and you can hit the same endpoints directly from the REST API if you would rather build it into your own stack.
-
mcp__hothawk__campaigns_createCreate the campaign and set the per mailbox daily limit -
mcp__hothawk__campaigns_mailboxes_createAttach a pool of mailboxes so sending rotates -
mcp__hothawk__campaigns_mailboxes_getRead back the attached pool and daily ceiling
Frequently asked
What is inbox rotation?
Instead of one mailbox sending your whole campaign, HotHawk spreads the sends across a pool of them. Each account sends a small daily amount and the campaign as a whole moves quickly. It is the core of how serious outbound teams send at volume.
Why not just send everything from one mailbox?
Because one inbox flogged hard is the fastest way to burn a domain. Mailbox providers notice a single account firing out hundreds of cold emails a day. Rotation keeps every account modest, so the volume comes from the size of the pool, not from overworking one inbox.
How do I get to 40,000 emails a day?
You widen the pool. Rotation means daily capacity is roughly your per mailbox limit times the number of mailboxes, so hundreds of warmed inboxes at a sensible cap each add up fast. HotHawk is built to run pools that send 40,000 a day and more without leaning on any one domain.
Are the deliverability protections still on when I set this up from a chat?
Yes. Rotation itself is one of them, and it applies whether a person or Claude attaches the pool. Warmup keeps running on real Google and Microsoft inboxes, the per mailbox cap is enforced, and open and link tracking stay off. Claude cannot turn any of it off.
Do I need to write code?
No. You add HotHawk as a connector in Claude once, then building the campaign and attaching the pool is two plain sentences. The same endpoints are in the REST API if you want to script rotation into your own stack.