Order queue open · Verified lists delivered within 24–48 hours
How to set up inbox rotation in Instantly 2026: the math on how many inboxes you need, per-inbox limits, domain distribution, scaling steps, and troubleshooting.
Ryan Mercer
SDR turned cold email consultant, 8 years outbound · Updated June 24, 2026
Last updated: June 2026 · Ryan Mercer, SDR turned cold email consultant, 8 years outbound
TL;DR — 7 things to know before reading
Inbox rotation is the feature that separates practitioners who understand cold email infrastructure from those treating Instantly as a simple email sender. The concept is simple to state: spread your sends across multiple inboxes so that no single inbox bears the full load. But the operational complexity — how many inboxes, how many per domain, at what per-inbox limits, in what sequence to add them, how to monitor per-inbox health — is where most practitioners make expensive mistakes.
This guide covers the math. Not just "use inbox rotation" but the exact calculations for any target send volume, the domain distribution formula that prevents a single incident from taking down your entire rotation, the ramp schedule for adding inboxes without triggering anomaly detection, and the monitoring cadence that catches per-inbox problems before they spread across your campaign.
After 8 years as an SDR and cold email consultant, the single most expensive mistake I see is teams that build rotation pools incorrectly — either too few inboxes per domain (so domain risk is concentrated), too many inboxes added too quickly (so the new inboxes go unwarmed into active sends), or no per-inbox monitoring (so one failing inbox hides inside the pool's averaged metrics until the damage is done).
Inframail provisions Microsoft 365 inboxes efficiently across multiple sending domains with automatic DNS setup. Instantly manages the rotation logic once inboxes are connected and warmed. Quarvio provides the verified contacts that the rotation distributes to — and contact quality is inseparable from inbox health, because high bounce rates from invalid contacts damage the inboxes in your rotation. Aimfox covers the LinkedIn channel running alongside.
Without rotation, a single sending account sends all the emails in a campaign. As campaign volume scales, this inbox sends more and more per day. Email providers — Microsoft, Google, and others — monitor volume patterns at the inbox and domain level. A sudden increase from 30 emails per day to 200 per day from the same inbox is a behavioral anomaly that triggers deliverability scrutiny.
The anomaly detection is not based solely on absolute volume. It is based on:
Inbox rotation addresses the volume anomaly risk directly. By distributing sends across 10 inboxes each sending 30 per day, the aggregate 300 sends per day produces no volume anomaly on any individual inbox. Each inbox is operating within its historical pattern.
The starting point for any inbox rotation setup is the capacity formula:
Total daily capacity = number of inboxes × per-inbox daily limit
At the recommended 30–40 emails per inbox per day, this produces:
| Target daily volume | At 30 emails/inbox/day | At 40 emails/inbox/day |
|---|---|---|
| 100 emails/day | 4 inboxes | 3 inboxes |
| 200 emails/day | 7 inboxes | 5 inboxes |
| 300 emails/day | 10 inboxes | 8 inboxes |
| 500 emails/day | 17 inboxes | 13 inboxes |
| 750 emails/day | 25 inboxes | 19 inboxes |
| 1,000 emails/day | 34 inboxes | 25 inboxes |
| 2,000 emails/day | 67 inboxes | 50 inboxes |
The correct column to use is the 30 emails/inbox/day column for new rotation setups. The 40/day limit is appropriate for inboxes with 8+ weeks of warmup and a consistent sending history above 30/day. Default to conservative limits; you can increase per-inbox limits over time as the warmup score stays consistently above 85 and per-inbox open rates remain stable.
The 30–50 per inbox per day guideline from Woodpecker guide on daily sending limits reflects the documented threshold above which per-inbox volume anomaly detection becomes a measurable deliverability risk for cold outreach specifically.
Marketing emails from warmed newsletter senders can safely exceed these limits because the recipients have opted in and the engagement rates are higher. Cold outreach — where recipients have not opted in and reply rates are below 10% — operates under tighter volume scrutiny. The cold outreach context is what makes the 30–50 limit the relevant guideline.
Some practitioners push to 60–70 per inbox per day for inboxes with very high warmup scores and strong historical engagement. This is not the default recommendation; it is an advanced option for inboxes with 6+ months of established history and proven open rates above 35% consistently.
The most common infrastructure mistake in inbox rotation is concentrating many inboxes on a single domain. Understanding why this is dangerous requires understanding how domain reputation works.
When Instantly sends an email from hello@yourdomain.com, the receiving email provider evaluates:
Domain reputation is shared across all inboxes on that domain. If hello@yourdomain.com accumulates a high bounce rate or a spam complaint, the domain reputation for yourdomain.com is affected. This affects deliverability for hi@yourdomain.com, team@yourdomain.com, and every other inbox on that domain.
If you have 10 inboxes all on the same domain, a single domain reputation incident (triggered by one inbox in the rotation) affects all 10 simultaneously. Your entire rotation pool is compromised by a single domain event.
The recommended ceiling is 2–3 inboxes per sending domain. This limits the blast radius of a domain reputation event to 2–3 inboxes rather than your entire rotation pool. To reach meaningful rotation pool sizes, distribute inboxes across multiple domains:
| Domains | Inboxes per domain | Total inboxes | Daily capacity at 30/day | Daily capacity at 40/day |
|---|---|---|---|---|
| 3 domains | 2–3 each | 6–9 inboxes | 180–270/day | 240–360/day |
| 5 domains | 2–3 each | 10–15 inboxes | 300–450/day | 400–600/day |
| 8 domains | 2–3 each | 16–24 inboxes | 480–720/day | 640–960/day |
| 12 domains | 2–3 each | 24–36 inboxes | 720–1,080/day | 960–1,440/day |
Sending domains should be variations of your primary brand domain, not random unrelated domains. Email providers evaluate domain reputation in context — a sending domain that looks entirely unrelated to the brand website it links to is a trust signal mismatch.
Common approaches:
yourbrand.io, yourbrand.co, yourbrand.email (TLD variants)hello.yourbrand.com, hi.yourbrand.com (subdomain variants if the primary domain supports this)yourbrandapp.com, yourbrandteam.com (brand extension variants)Avoid purchasing random keyword domains that have no relationship to your brand. The domain registration history, the website content at the domain, and the sending pattern together create a trust profile that experienced spam filters evaluate holistically.
Inframail provisions Microsoft 365 inboxes with automatic SPF, DKIM, and DMARC configuration on each domain. This eliminates the manual DNS configuration that is one of the most common sources of deliverability problems on self-managed domains.
For each new sending domain:
The DNS configuration is critical. Per Mailgun SPF, DKIM, and DMARC setup guide, improperly configured SPF, DKIM, and DMARC records mean that even high-quality emails can fail authentication checks and land in spam regardless of sender reputation. Inframail's automatic configuration eliminates this failure mode.
Before adding any inbox to a rotation pool in Instantly, verify that it meets all four prerequisites. An inbox that fails any prerequisite should not be in any active campaign rotation.
Navigate to Email Accounts → Add Account in Instantly and connect each inbox. For Inframail-provisioned Microsoft 365 inboxes, select Microsoft 365 as the connection type and follow the OAuth authorisation flow. The inbox appears in your Email Accounts list once connected.
Failure mode: Connecting inboxes using app passwords rather than OAuth can produce authentication failures after Microsoft security policy updates. Use OAuth connection where available.
Every inbox must complete its own independent warmup period before being added to any campaign. Per Woodpecker's email warmup guide, 2–4 weeks minimum warmup is required before any inbox sends cold outreach.
Warmup in Instantly operates by sending and receiving emails between Instantly's warmup pool accounts, building the inbox's engagement history with email providers. An inbox with a warmup score below 80 has insufficient positive engagement history to sustain cold campaign sends without triggering deliverability scrutiny.
Critical rule: An inbox does not become warmer faster by being included in a rotation pool with already-warmed inboxes. Each inbox is evaluated independently by email providers. An unwarmed inbox in a rotation pool drags its own metrics down while the other inboxes in the pool continue operating normally. The damage is localised but real.
Check warmup scores in Instantly at Email Accounts → [Account] → Warmup. Only add inboxes that show warmup score 80+.
Do not disable warmup when an inbox starts sending campaign emails. Instantly is designed to run both warmup and campaign sends simultaneously. Warmup continuing during active campaign sends provides ongoing positive engagement signals that counterbalance any negative signals from campaign non-replies.
Configure warmup to run in the background for the lifetime of the inbox. Treat warmup as a permanent infrastructure layer, not a one-time setup step.
Verify SPF, DKIM, and DMARC are correctly configured on each sending domain. For Inframail-provisioned domains, this is automatic. For any domain provisioned outside Inframail, manually verify using MXToolbox or Google Postmaster Tools before adding any inbox from that domain to a campaign.
A sending domain with a missing or misconfigured DKIM record will fail email authentication checks. This creates deliverability problems that look like volume or content issues but are actually authentication failures. Authentication must be resolved before rotation configuration.
Before opening Instantly, calculate how many inboxes you need using the capacity formula. Be specific:
Benchmark: Most practitioners underestimate the inbox count needed because they set per-inbox limits optimistically. Use 30/day as the planning assumption, not 50/day. This builds in buffer and allows you to increase limits per inbox over time rather than discovering limits are too high after deliverability issues emerge.
Failure mode: Calculating needed inboxes based on the maximum safe limit (50/day) and discovering that at 50/day the rotation is strained and per-inbox deliverability starts declining after 2–3 weeks. Plan at 30/day; treat 40/day as the ceiling for established inboxes.
Navigate to Campaigns → New Campaign (for a new campaign) or open an existing campaign to modify its rotation settings.
Sub-step: Before opening the campaign, ensure all inboxes you plan to add have been individually verified as warmed (score 80+) in the Email Accounts section. This verification takes 2–3 minutes but prevents the most common rotation mistake.
In the campaign configuration screen, navigate to the Email Accounts section (sometimes labeled Sending Accounts depending on your Instantly version).
Click Add Account or Add Sending Account and select each warmed inbox you want to include in the rotation pool. Instantly will show the connected inboxes from your Email Accounts list.
Add all the inboxes that meet the warmup prerequisite. Do not add inboxes that are still warming up, even if their warmup score is close to 80. The threshold is 80+, not "approaching 80."
Sub-step: When adding inboxes, add them in batches sorted by domain. This makes it easier to verify that you are not exceeding the 2–3 inboxes per domain limit. If the Email Accounts list is long, filter by domain before adding to prevent accidentally adding 5 inboxes from the same domain.
After adding inboxes to the campaign's rotation pool, configure the per-inbox daily limit for each one.
For newly warmed inboxes (warmup score 80–85):
For established inboxes (warmup score 85+ with 6+ weeks of campaign history):
Also configure for each inbox:
Benchmark: Campaigns configured with 9:00–17:00 sending windows matched to audience timezone consistently outperform 24-hour sending windows on open rates, per practitioner reporting on Instantly reviews on G2. The open rate difference is typically 5–12 percentage points in favour of business-hours-only sending.
Failure mode: Setting all inboxes to 50 emails/day from launch to hit volume targets faster. Consistently running inboxes at or near their maximum limits without observing per-inbox open rate trends. New inboxes should always start conservative.
Inbox rotation does not operate in isolation from the campaign's other settings. Several campaign-level settings directly affect how rotation performs:
Stop on reply — must be enabled: When a contact replies, all remaining sequence steps for that contact should stop automatically. This is a non-negotiable setting regardless of rotation. If stop-on-reply is disabled, contacts who replied (interested or unsubscribed) will continue receiving emails from whichever inbox in the rotation picks them up next. Enable this in campaign settings.
Sequence step timing — set appropriately per step: The gap between sequence steps affects how rotation distributes sends across a list. If your sequence sends Step 1 to 1,000 contacts over 7 days and then Step 2 to the same 1,000 contacts starting day 8, the Step 2 send can be distributed to different inboxes in the rotation than Step 1. This is normal and correct — Instantly assigns inboxes at the time of send, not at the time of campaign enrollment.
Daily send cap at campaign level — verify it exceeds your inbox pool capacity: If you have 10 inboxes at 30/day capacity (300 emails/day total), the campaign-level daily send cap must be set above 300 to allow the full rotation capacity to run. A campaign-level cap of 200 with a 300-capacity pool means only 200 emails are sent per day, with 100 of your rotation capacity sitting idle.
After launching, the campaign-level metrics in Instantly show aggregated performance across all inboxes. This is useful for overall campaign assessment but masks per-inbox problems.
Per-inbox monitoring location: Navigate to Email Accounts → [Individual Account] to see that inbox's specific performance data for the current period.
Monitoring cadence:
What to look for per inbox:
Rotation pools can grow over time as you warm new inboxes and scale volume. The process for adding a new inbox to an active campaign rotation:
A new inbox added to an active campaign rotation should not start at the same per-inbox limit as the established inboxes in the pool. Even a fully warmed inbox (score 80+) benefits from a gradual ramp when entering an active campaign to avoid sudden volume spikes from the email provider's perspective.
Recommended ramp for new inboxes added mid-campaign:
| Week | Per-inbox daily limit |
|---|---|
| Week 1 | 15–20 emails/day |
| Week 2 | 25–30 emails/day |
| Week 3 | 30–35 emails/day |
| Week 4+ | Full limit (35–40 emails/day) |
This 4-week ramp is in addition to the 2–4 week initial warmup period. The total timeline from a new inbox being provisioned to contributing its full capacity to a campaign rotation is approximately 6–8 weeks for a conservative, reliable setup.
During the first 2 weeks in active rotation:
The rotation pool should scale in proportion with your target volume, not all at once. A common mistake is purchasing and warming 20 inboxes simultaneously, then adding them all to the rotation in one step. This is operationally risky because:
The staggered build approach:
Start with a core pool of 4–6 inboxes. Run this pool for 3–4 weeks and establish a per-inbox performance baseline. Then add 2–4 new inboxes every 2–3 weeks, following the ramp schedule above. This builds volume gradually and provides clear performance attribution — if performance degrades after adding the week 6 batch of inboxes, you know exactly which inboxes to investigate.
| Phase | Timeline | Inbox count | Daily capacity |
|---|---|---|---|
| Launch | Week 1–4 | 4–6 inboxes | 120–180/day |
| Scale 1 | Week 5–8 | 6–10 inboxes | 180–300/day |
| Scale 2 | Week 9–12 | 10–16 inboxes | 300–480/day |
| Scale 3 | Week 13–16 | 16–24 inboxes | 480–720/day |
| Mature | Month 5+ | 24–36 inboxes | 720–1,080/day |
| Setting | Location | Recommended value | Notes |
|---|---|---|---|
| Email accounts per campaign | Campaign → Email Accounts | All warmed inboxes for this campaign | Warmup score must be 80+ for each |
| Per-inbox daily limit | Per account in campaign | 30 emails/day (new), 35–40 (established) | Never exceed 50 without 6+ week history |
| Sending window | Per account in campaign | 9:00–17:00 audience local time | Match audience timezone, not sender |
| Random send delays | Per account in campaign | Enabled | Never use fixed intervals |
| Warmup during campaign | Email Accounts → Warmup | Enabled (always) | Never disable warmup when sending |
| Warmup score minimum | Email Accounts → Warmup | 80+ before adding to any campaign | Check before each campaign add |
| Inboxes per domain | Domain distribution | 2–3 max | More increases domain-level risk |
| Domains per rotation pool | Infrastructure | 1 domain per 2–3 inboxes | Diversify domains to isolate risk |
| DNS configuration | Domain DNS (Inframail auto) | SPF + DKIM + DMARC all configured | Inframail handles this automatically |
| Stop on reply | Campaign settings | Always enabled | Non-negotiable |
| Campaign-level daily cap | Campaign settings | Above total rotation capacity | Must not cap below inbox pool total |
| New inbox ramp period | Per account daily limit | 15–20/day for first 2 weeks | Ramp up over 4 weeks to full limit |
| Per-inbox monitoring | Email Accounts → individual | Weekly (established), daily (first 4 weeks) | Pool average hides individual issues |
If you run campaigns targeting fundamentally different audiences (e.g., enterprise VP Sales vs. SMB founders), consider running separate inbox pools for each campaign type rather than sharing the same pool across all campaigns.
The benefit: if the enterprise campaign generates higher bounce rates (common when enterprise contact data is less current), the deliverability impact stays isolated to the enterprise pool inboxes and does not affect the SMB campaign pool's performance.
The cost: more inboxes overall, more warmup time, more monitoring to maintain. This is worth the investment at campaign volumes above 500/day where a single pool failure has significant revenue impact.
Warm 2–4 inboxes that are reserved exclusively for re-engagement campaigns (contacting prospects from previous campaigns who did not respond). These inboxes send lower volume (10–20/day) on a less frequent schedule and maintain a distinct sending pattern from your primary campaign pool.
The benefit: re-engagement campaigns have different engagement characteristics (lower open rates because the prospect has already seen prior outreach) and it is useful to isolate this signal in dedicated inboxes rather than having it pull down the performance metrics of your main pool inboxes.
The aggregate performance of your rotation pool is a sensitive indicator of contact list quality. If you add a new contact list to a campaign using an established rotation pool and per-inbox open rates drop across the pool within 7 days, the new contact list likely has quality issues (higher bounce rate, lower engagement) that are affecting all inboxes in the pool.
Track per-inbox open rates before and after adding new contact lists. A consistent 5%+ drop across the pool after a list change is a contact quality signal, not an inbox problem.
When launching a new campaign with a large contact list (3,000+ contacts), stagger the initial send across the pool's inboxes rather than having all inboxes start simultaneously. Configure Instantly to release the campaign over 3–5 business days for the first batch, letting the rotation distribute the initial volume gradually.
This prevents a spike in aggregate sending volume from the entire pool on day one, which can trigger domain-level anomaly detection even when individual inbox volume is within the safe range.
If you run multiple concurrent campaigns using the same inbox pool, monitor the combined per-inbox send volume across all campaigns. The per-inbox daily limit applies to the total number of emails sent from that inbox across all campaigns combined, not per campaign.
If inbox A has a 30/day limit and is shared across Campaign 1 (sends 20/day) and Campaign 2 (sends 15/day), the inbox is being asked to send 35/day — above its configured limit. Instantly will cap the total to 30, distributing the send reduction across campaigns, but the combined load is worth monitoring explicitly.
Poor deliverability caused by content: If your email content triggers spam filters — through spam trigger words, excessive link density, or identified bulk-sender patterns — distributing the sends across more inboxes does not fix the content problem. It distributes the content-triggered deliverability issue across more inboxes. Diagnose and fix content issues before building rotation.
High bounce rates from invalid contacts: A campaign with 15% bounce rate damages every inbox in the rotation pool that sends to invalid contacts. Rotation distributes the bounce damage but does not prevent it. Verified contact data from Quarvio prevents the bounce problem at its source. Per Mailmodo B2B email marketing statistics, bounce rates above 5% are the most common cause of deliverability degradation across active campaigns.
Missing or misconfigured DNS authentication: If SPF, DKIM, or DMARC are not correctly configured on a sending domain, every inbox on that domain fails authentication checks regardless of rotation. Authentication configuration must be resolved before any inbox from that domain is added to a campaign.
Low warmup scores on individual inboxes: Rotation across inboxes with warmup scores of 50–60 simply means your campaign is using multiple underwarmed inboxes instead of one. Each inbox's deliverability performance is based on its own warmup history. Warmup cannot be distributed across a pool; it must be built individually.
Symptom: The campaign has been running for 2+ days since adding a new inbox, but the new inbox shows 0 sends while other inboxes in the pool are sending normally.
Cause: The daily sending limit for the new inbox was not configured after adding it. When a new account is added to a campaign, the per-inbox limit may default to zero or require manual setting.
Fix: Navigate to the campaign's Email Accounts section, find the new inbox, and verify its daily sending limit is set to the intended value (15–20 for a ramp-phase new inbox). If it shows 0, update it. Check that the inbox is not paused in the Email Accounts main section.
Symptom: An inbox that was at warmup score 85+ has dropped to 70–75 since being added to an active campaign.
Cause 1: The campaign bounce rate is high enough to affect the inbox's reputation. Check the campaign bounce rate for sends from this specific inbox.
Cause 2: The per-inbox campaign send volume is too high relative to the inbox's warmup history. The inbox may have been added at too high a per-inbox daily limit before it was ready.
Fix: Reduce the inbox's campaign sends immediately to 10–15 per day and let warmup continue in the background for 2–3 weeks before increasing campaign volume again. Also check the campaign bounce rate and ensure it is below 3%. If bounce rate is above 5%, pause the campaign and audit the contact list quality.
Symptom: The per-inbox open rate across all inboxes in the rotation has declined by 5–10 percentage points over 2 weeks, with no obvious infrastructure change.
Cause: This is almost always a content issue, not an infrastructure issue. If all inboxes decline simultaneously, the common factor is the campaign content (same template across the full rotation pool) not the sending infrastructure. A new spam filter pattern targeting your specific content, a trigger word in a recent template update, or a subject line that has accumulated repetition signals can all cause this pattern.
Fix: Run an A/B test of email content (new template vs. existing template) with a subset of the rotation pool. If the new template produces better open rates, the existing content is the problem. Review the template for recent changes and audit against spam trigger word lists.
Symptom: Across 10 inboxes in the rotation, nine show 30–35% open rates and one shows 12–15%.
Cause 1: The underperforming inbox has a DNS configuration issue (failed DKIM authentication).
Cause 2: The inbox is sending from a domain that has been blacklisted or has a poor domain reputation from previous use.
Cause 3: The inbox was added to the rotation before reaching a sufficient warmup score.
Fix: First, remove the underperforming inbox from the campaign rotation immediately to prevent it from pulling down campaign averages. Then diagnose: check DNS configuration using MXToolbox, check the domain against email blacklist databases, and check the inbox's warmup score. Address the root cause before re-adding the inbox.
Symptom: The campaign shows 28%+ open rate but reply rate is below 1%. Spintax is in place. Rotation appears to be working.
Cause: This is not a rotation problem. A high open rate with low reply rate indicates that emails are reaching inboxes (good deliverability) but the message is not compelling enough to generate replies. This is a copy and targeting quality issue.
Fix: Audit your email copy, personalisation depth, offer clarity, and audience ICP quality. Per Instantly's cold email benchmark report, the average reply rate is 3.43% and elite senders achieve above 10%. A 28% open rate with 0.5% reply rate is a copy problem. Inbox rotation has done its job; the message needs work.
Symptom: A new inbox was added to a rotation mid-campaign and the unsubscribe rate spiked for the 3 days following the add.
Cause: The new inbox is picking up contacts who are late in the sequence (Step 3 or Step 4) and receiving follow-up emails from what appears to be a different sender (new inbox address) than their previous emails came from. Recipients who have not replied by Step 3 are less interested; combined with an apparent "new sender," the unsubscribe intent is higher.
Fix: When adding a new inbox to an ongoing campaign, configure it to only send Step 1 (initial outreach) to new contacts entering the campaign, rather than picking up mid-sequence contacts. Alternatively, add a brief pause of 2–3 days after adding the new inbox before it starts sending, so the campaign cycle aligns.
Symptom: You have 10 inboxes configured at 35/day each (350/day total capacity) but the campaign is only sending 180–200 emails per day.
Cause 1: The campaign-level daily send cap is set below the pool's total capacity.
Cause 2: The contact list is exhausted or nearing exhaustion — fewer contacts remain in the sequence than the pool's daily capacity can handle.
Cause 3: Several inboxes in the pool are paused (manually or automatically due to deliverability issues) and not contributing to daily sends.
Fix: Check the campaign-level daily cap setting (increase if below total pool capacity). Review the contact list count vs. contacts remaining in sequence. Check individual inbox statuses in Email Accounts to identify any paused inboxes.
Symptom: After 6 weeks, inboxes in the pool are showing a range of open rates from 18% to 42%, when they started within 5 percentage points of each other.
Cause: Inboxes have developed different reputation trajectories based on which contacts they sent to (random rotation means some inboxes happened to send to contacts with higher engagement rates), different warmup score trajectories, or differences in the domains they are on.
Fix: This is a normal pattern over time. Lower-performing inboxes should be audited for domain reputation, DNS configuration, and warmup score. High-performing inboxes can have their per-inbox limit gradually increased. Consider retiring and replacing inboxes that persistently underperform by 15+ percentage points below the pool average after 3+ months.
Instantly reviews on G2 show inbox rotation as one of the most frequently mentioned scaling features, with practitioners crediting it as the enabler of campaign volume above 200 emails per day without deliverability degradation. Multiple G2 reviewers specifically describe the transition from 3–4 inboxes to 12–20 inboxes as the inflection point where cold outreach became a reliable lead generation channel rather than a sporadic one.
Inframail reviews on G2 show practitioners specifically citing the ease of provisioning multiple inboxes across multiple domains as the feature that makes rotation practical at scale — reducing the infrastructure management time that previously limited rotation pool size to what one person could manually configure and monitor.
"I went from 3 inboxes to 15 inboxes over 6 weeks. Each new inbox was warmed for 3 weeks before I added it to any campaign. My total daily capacity went from 90 sends to 450 sends with zero deliverability degradation. The rotation setup in Instantly takes about 5 minutes per campaign once the inboxes are connected. The bottleneck is the warmup time, not the configuration."
— Verified G2 reviewer, cold email agency founder, Instantly reviews on G2
"The mistake I see most often is people adding unwarmed inboxes to a rotation to hit a volume target faster. Every time, the campaign's deliverability suffers for 2–3 weeks while the inbox gets penalised. Warm first, then rotate. The sequence is non-negotiable."
— Verified G2 reviewer, outbound consultant, Instantly reviews on G2
| Need | Tool | Notes |
|---|---|---|
| Verified B2B contacts | Quarvio | One-time purchase, no subscription |
| Email inboxes | Inframail | Microsoft 365 inboxes, auto DNS setup |
| Cold email sending | Instantly | Sequences, rotation, warm-up, analytics |
| LinkedIn outreach | Aimfox | Connection campaigns, Unibox |
How many inboxes do I need for inbox rotation in Instantly?
The number depends on your target daily send volume and the per-inbox daily limit you operate at. At the recommended 30 emails per inbox per day for new rotation setups, divide your target daily volume by 30 to get your inbox requirement. For 300 sends per day: 300 / 30 = 10 inboxes. For 500 sends per day: 17 inboxes. Always add 20% buffer capacity so that if 1–2 inboxes are paused for maintenance or remediation, the campaign continues at near-target volume. Start with your core pool and add inboxes incrementally every 2–3 weeks as demand grows.
What is the safe per-inbox daily limit in Instantly for cold email?
Per Woodpecker guide on daily sending limits, 30–50 emails per inbox per day is the documented safe range for warmed accounts sending cold outreach (not opted-in marketing email). Start at 30 per inbox for new rotation setups. After 4–6 weeks of stable open rates above 30%, you can test increasing to 35–40 per inbox. The 50/day limit is the ceiling for inboxes with 6+ months of positive sending history and consistently high engagement metrics.
Does inbox rotation work with email accounts from different providers in the same campaign?
Yes. Instantly supports adding email accounts from different providers — Microsoft 365, Google Workspace, and others — to the same campaign rotation pool. Each account is connected and warmed independently. In practice, using Microsoft 365 inboxes from Inframail for all rotation inboxes keeps the infrastructure consistent and the DNS configuration standardised, which simplifies monitoring and troubleshooting.
How many inboxes should I put on a single sending domain?
The recommended maximum is 2–3 inboxes per sending domain. All inboxes on the same domain share that domain's reputation. If one inbox on a domain accumulates deliverability problems (high bounce rate, spam complaints, blacklist entry), all inboxes on that domain are affected. Spreading inboxes across multiple domains via Inframail limits the blast radius of any single domain incident to 2–3 inboxes rather than your entire rotation pool.
Should I use one campaign with inbox rotation or multiple separate campaigns each with one inbox?
One campaign with inbox rotation is the recommended approach for standard volume scaling. It gives you one set of campaign-level metrics, one lead list to manage, and one sequence to maintain. Instantly handles the send distribution automatically. Multiple campaigns per inbox is useful only when you are testing dramatically different message variants for a specific ICP segment and need strict variant isolation. For volume scaling, one campaign with rotation is simpler and sufficient.
What happens to the campaign if one inbox in the rotation is flagged for spam?
The campaign continues sending normally from the other inboxes in the rotation. In Instantly, you can remove or pause a specific inbox from a campaign without stopping the campaign entirely. When you identify a deliverability problem on one inbox (low open rate, warmup score dropping, bounce rate spike), remove it from the rotation immediately, diagnose the root cause, resolve it, and only re-add the inbox after the warmup score recovers to 80+.
Can I add inboxes to an active campaign rotation mid-campaign?
Yes. You can add inboxes to an active campaign's rotation at any time. However, new inboxes added mid-campaign should start at a reduced per-inbox limit (15–20/day for the first 2 weeks) and ramp to full capacity over 4 weeks, even if the inbox has a warmup score above 80. This prevents sudden volume increases from the provider's perspective and allows you to monitor the new inbox's behavior in the active campaign context before relying on it for full capacity.
How do I monitor per-inbox performance in Instantly?
Per-inbox performance is visible in Email Accounts → [Individual Account] in Instantly, which shows sends, open rate, reply rate, and warmup score for the selected inbox. Campaign-level analytics aggregate across all inboxes in the rotation pool; per-inbox metrics require navigating to the individual account. Check per-inbox metrics weekly for established rotation pools and daily for new inboxes in their first 4 weeks of active sending.
What is the warmup score threshold before adding an inbox to a campaign?
The minimum warmup score before adding any inbox to any active campaign rotation is 80. Below 80, the inbox's engagement history is insufficient to sustain cold outreach sends without elevated deliverability risk. Check the warmup score at Email Accounts → [Account] → Warmup immediately before adding an inbox to any campaign. Do not add inboxes with scores below 80, even if they are "close" or "approaching" the threshold.
Why is my campaign sending fewer emails than my rotation pool capacity?
Three common causes: (1) the campaign-level daily send cap is set below the total pool capacity — check campaign settings and increase the cap to at least 10% above your pool total; (2) one or more inboxes in the pool are paused or have zero per-inbox limits — check each inbox's status individually in Email Accounts; (3) the contact list is nearly exhausted relative to the campaign volume — the number of contacts remaining in the sequence is lower than the pool's daily capacity can fill.
Does keeping warmup running while sending campaigns hurt campaign deliverability?
No. Continuing warmup during active campaign sends is the recommended configuration. Warmup sends generate positive engagement signals (opens, replies from the warmup pool) that counterbalance the lower engagement rates typical of cold outreach. Instantly is designed to manage both warmup and campaign sends simultaneously. Disabling warmup when campaigns start removes a layer of positive reputation maintenance without providing any benefit.
How long does it take to build a 500-email-per-day rotation capacity?
Building responsibly to 500 emails/day requires approximately 12–16 weeks from the first inbox provision. Timeline: weeks 1–4 warmup of first 4–6 inboxes (160–180/day capacity); weeks 5–8 add 4–6 more inboxes and ramp (280–360/day capacity); weeks 9–12 add 4–6 more inboxes (400–480/day capacity); weeks 13–16 add final batch to reach 500+/day. Attempting to reach 500/day in 4 weeks requires adding unwarmed inboxes, which consistently produces deliverability problems that cost more time to remediate than the accelerated schedule saves.
More inboxes means more reach — but only if the contacts are valid.
Inbox rotation scales your sending capacity; contact quality determines what that capacity produces. Quarvio delivers verified B2B contact lists with pre-delivery email verification — low bounce rates keep every inbox in your rotation pool healthy. One-time purchase, credits valid for 12 months, no subscription.