Order queue open · Verified lists delivered within 24–48 hours
How many emails can you send per day per inbox? The safe limit is 30-50 for warmed accounts. This guide covers warmup phases, inbox rotation, and volume math.
Sarah Okonkwo
Sales ops specialist, deliverability obsessive · Updated June 23, 2026
Last updated: July 2026 · Sarah Okonkwo, Sales ops specialist, deliverability obsessive
TL;DR — 5 things to know before reading
The daily sending limit question is one of the most common and most misunderstood in cold email. The answer is not a single number — it depends on inbox age, warmup status, and how your sending volume is distributed across accounts.
The short answer is 30–50 emails per inbox per day for a fully warmed account. But the more useful answer involves understanding why this limit exists and how to scale volume beyond it without damaging deliverability.
Mailbox providers like Gmail and Outlook use sending patterns to assess whether a sender is trustworthy. An inbox that suddenly sends 200 emails on a given day when it has been sending 20 per day for a month looks like a compromised account or a spam source. The safe limit is not arbitrary — it reflects what a normal human business sender looks like to the algorithms that decide inbox vs spam routing. Woodpecker's 2025 cold email benchmark study shows average reply rates of 8.5% across cold email campaigns, with top-quartile senders at 15–20% — and the gap is largely explained by infrastructure discipline, including staying within per-inbox sending limits.
Instantly enforces per-inbox sending limits automatically and distributes sending volume across connected accounts. Understanding the numbers behind those settings helps you configure them correctly rather than just accepting defaults.
Mailbox providers evaluate sender reputation at the inbox level, not just the domain level. When an inbox sends more email than its history supports, the sudden volume spike is a negative signal that can trigger:
The per-inbox limit is the rate at which you can send without triggering these signals. It is not the maximum your email provider technically allows — it is the maximum you should send while maintaining deliverability.
The core mechanism is sending history analysis. Mailbox providers look at an inbox's historical sending volume and treat sudden departures from that baseline as suspicious. An inbox that has been sending 30 emails per day for two months and suddenly sends 150 triggers the same algorithmic response as an account that has been dormant and suddenly activates at high volume. The algorithm cannot distinguish between a legitimate volume increase and a compromised account — it responds to the anomaly.
This is why warmup matters: warmup is the process of building a sending history that supports progressively higher volumes. By the time you want to send 40 emails per day, the inbox's historical pattern already shows 35 per day, 38, 40 — a gradual, normal-looking ramp that does not trigger anomaly detection.
| Warmup stage | Inbox age | Safe daily limit |
|---|---|---|
| New inbox (no warmup) | Day 1–7 | 10–20 (warmup emails only) |
| Early warmup | Week 2–3 | 20–30 (warmup + small campaigns) |
| Mid warmup | Week 4–6 | 30–40 (warmup + active campaigns) |
| Fully warmed | Week 7+ | 40–50 (full campaign volume) |
Source: Woodpecker's guide on daily sending limits — verified June 2026
Woodpecker's email warmup guide recommends 2–4 weeks minimum warmup, with up to 12 weeks before treating an inbox as fully mature. During warmup, the inbox exchanges simulated real emails with other accounts to build engagement signals that mailbox providers use to assess reputation.
Instantly automates this process through its warmup network. Connected inboxes participate in the network automatically, building reputation without manual coordination.
Understanding what happens during warmup explains why the timeline cannot be compressed without cost. The warmup process builds three distinct reputation signals:
Domain reputation: When a new domain sends its first emails, mailbox providers have no data on which to assess it. The domain's reputation starts at zero (neutral) and builds based on engagement with early sends. Domain reputation is shared by all inboxes on that domain, which is why starting warmup with all inboxes on a new domain simultaneously is more effective than warming them sequentially.
Inbox-level reputation: Each inbox within a domain has its own sending pattern history. Even when the domain has Good reputation from prior inboxes, a new inbox on that domain still needs to establish its own pattern history before cold campaigns can run at full volume.
IP reputation: Microsoft 365 and Google Workspace share IP pools among many users. The IP delivering your emails contributes its reputation to your deliverability outcomes. Warmup networks like Instantly's generate positive IP signals by creating engagement patterns (opens, replies) on the emails sent from those IPs.
Week-by-week warmup progression for a new Microsoft 365 inbox on Inframail:
| Week | Warmup emails sent | Warmup emails received | Cold campaign emails | Total daily activity |
|---|---|---|---|---|
| Week 1 | 10–15 | 10–15 | 0 | 10–15 |
| Week 2 | 15–20 | 15–20 | 0–5 | 20–25 |
| Week 3 | 15–20 | 15–20 | 5–10 | 25–30 |
| Week 4 | 10–15 | 10–15 | 15–20 | 25–35 |
| Week 5–6 | 10–15 | 10–15 | 25–30 | 35–45 |
| Week 7+ | 8–12 maintenance | 8–12 | 30–40 | 40–52 |
The warmup network emails (sent and received) remain active throughout the inbox's life — even when running full cold campaigns. The warmup provides a positive engagement baseline that partially offsets the neutral or negative signals from cold email sends.
The per-inbox limit is fixed, but you can scale total daily volume linearly by adding inboxes. This is inbox rotation: distributing your outbound volume across multiple sending accounts so each individual account stays within safe limits.
| Inboxes | Emails per inbox per day | Total daily volume |
|---|---|---|
| 1 inbox | 40 | 40 |
| 5 inboxes | 40 | 200 |
| 10 inboxes | 40 | 400 |
| 20 inboxes | 40 | 800 |
This is the math that makes cold email scalable for agencies and high-volume outbound teams. A single inbox can never safely send 800 emails per day. Twenty inboxes each sending 40 can.
Inframail provides unlimited Microsoft 365 inboxes at a flat monthly rate. Creating 20 inboxes in Inframail costs the same as creating 1 — there is no per-seat inbox fee. That structure makes inbox rotation economical at any scale.
Inbox rotation in Instantly distributes campaign sends across all connected inboxes automatically. When you add inboxes to a campaign in Instantly, sends from that campaign are distributed across those inboxes according to the configured daily limits per inbox. This means:
Even distribution: Instantly distributes sends to avoid sending all emails from one inbox before rotating to the next. The distribution is weighted by each inbox's configured daily limit and current daily send count.
Reply routing: When a prospect replies, the reply goes to the inbox that sent the original email — not to a generic mailbox. This maintains the 1:1 conversation history and ensures Instantly's reply detection can accurately identify and pause sequences.
Inbox health monitoring: If an inbox develops a deliverability issue during a campaign, Instantly's monitoring can detect the drop in inbox-specific performance and alert you to investigate. A well-configured rotation means one underperforming inbox does not tank the entire campaign's metrics — it just reduces its contribution to the daily volume.
The inbox-to-campaign assignment model: For maximum flexibility, configure inboxes as a pool that can be assigned to campaigns selectively. High-priority campaigns with warm ICP contacts run from your best-performing inboxes. Volume-test campaigns with new contact sources run from newer or lower-priority inboxes. If a volume-test campaign generates higher bounce rates or spam complaints, the damage is contained to the inboxes assigned to it.
Staggered sending within rotation: Instantly spaces sends throughout the configured sending window (e.g., 7am–5pm) rather than sending all emails at once at campaign start. This staggered pattern looks more like natural human sending behavior to mailbox provider algorithms and avoids burst-sending that could trigger temporary rate limiting.
Even with per-inbox limits respected, there are domain-level considerations that affect overall sending volume.
Inbox-to-domain ratio: Running too many inboxes from a single domain can concentrate reputation risk. A common practice is to use 3–5 inboxes per sending domain and spread volume across multiple domains. If one domain develops a deliverability problem, it does not contaminate inboxes on other domains.
Primary domain protection: Your company's main website domain (yourcompany.com) should never be used for cold email. Register separate sending domains (yourcompany-outreach.com, yourc.io) for cold campaigns. If a sending domain develops a reputation problem, the primary domain remains clean.
Domain warmup: Each new sending domain goes through the same warmup process as an individual inbox. Warmup at the domain level happens in parallel with inbox warmup — the warmup emails from inboxes on a new domain build reputation for both the inbox and the domain simultaneously.
Sending domain names affect both deliverability and reply rates. Domains that look like legitimate business email addresses perform better than domains that look like bulk email infrastructure.
Effective naming patterns:
Patterns that damage trust:
DNS configuration before warmup begins:
All three authentication records must be in place before any warmup email is sent from a domain. Inframail configures SPF, DKIM, and DMARC automatically for all provisioned inboxes on its platform. For manually configured domains:
Verify all three using MXToolbox before the first warmup email is sent. Authentication records broken after setup is a common failure mode — DNS changes by one team member can invalidate authentication configuration set up by another.
The sending provider type matters for per-inbox limits and warmup strategy.
Microsoft 365 (via Inframail): Microsoft 365 inboxes have higher bulk-sending tolerance than Gmail, making them better suited for cold email volumes. Microsoft's algorithms focus heavily on engagement signals (opens, replies) from the warmup network, making Instantly's warmup particularly effective for Microsoft 365 inboxes. Microsoft 365 inboxes on Inframail are provisioned on a shared but carefully managed IP pool that is distinct from consumer Microsoft email.
Google Workspace: Google Workspace inboxes have more restrictive sending limits per inbox and stricter spam signal processing, which makes per-inbox safe limits lower (typically 30–40 vs the 40–50 achievable with Microsoft 365). Google also applies reputation signals at both the inbox and domain level more aggressively. Google Workspace is significantly more expensive per inbox than Inframail, making large-scale inbox rotation economically impractical for most teams.
Custom SMTP providers: Some teams use custom SMTP providers (SendGrid, Mailgun) for cold email volume. These providers have their own IP pools and reputation management, but they are not the same as a human inbox from the perspective of mailbox provider algorithms. Bulk SMTP IPs are filtered more aggressively than IPs associated with Microsoft 365 or Google Workspace infrastructure.
For high-volume cold email where inbox rotation is the scaling mechanism, Inframail + Microsoft 365 is the standard setup among professional operators: the flat-rate pricing makes large inbox counts economical, and the Microsoft 365 infrastructure supports higher per-inbox limits than alternatives.
Within the per-inbox daily limit, the pattern of sends within the day also matters. Mailbox provider algorithms process not just the volume but the timing distribution of sends.
Behaviors that look like legitimate human sending:
Behaviors that look like bulk email automation:
Instantly handles much of this automatically through its staggered send timing and natural randomization. Configuring a sending window of 7am–5pm and allowing Instantly to distribute sends throughout that window produces a more natural sending pattern than scheduling sends at a fixed time each day.
Google Postmaster Tools shows the reputation tier of your sending domains on Gmail. If a domain moves from Good to Medium or Low, you have exceeded safe sending parameters and need to reduce volume and allow the domain to recover before resuming high-volume campaigns.
Spam complaint rates above 0.1% are a warning signal. Above 0.3% and Gmail actively filters your emails to spam regardless of content. Postmaster Tools shows this rate per domain — check it weekly during active campaigns.
Monitoring cadence for active cold email operations:
| Monitoring action | Frequency | What to look for |
|---|---|---|
| Google Postmaster Tools domain reputation | Daily in first 2 weeks; weekly after | Drop from Good to Medium |
| Google Postmaster Tools spam complaint rate | Weekly | Above 0.05% is a warning; above 0.1% requires action |
| MXToolbox blacklist check | Weekly | Any new blacklist listing on active domains |
| Per-campaign open rate in Instantly | Daily | Open rate below 15% suggests spam folder routing |
| Per-inbox bounce rate | After first 200 sends; weekly after | Above 2% requires pausing the campaign |
| Warmup score in Instantly | Weekly | Scores dropping below 50 indicate engagement decline |
Setting up this monitoring routine takes 30 minutes initially and 15 minutes per week to review. The cost of missing a deliverability signal early is weeks of recovery, which makes the monitoring investment one of the highest-ROI activities in cold email operations.
"We run 15 inboxes across 5 domains, all through Inframail and Instantly. Each inbox stays at 35 per day, so the total is around 525 per day. We have maintained that volume for eight months without any deliverability issues on any domain. The key is keeping per-inbox volume conservative and monitoring Postmaster weekly. The moment we see a domain's reputation dip, we pause campaigns on it for a week." — G2 reviewer, Instantly reviews on G2
Instantly holds a 4.9/5 rating from 2,800+ verified reviews on G2, with sending limit management and inbox rotation among the most frequently praised features by high-volume outbound teams.
The settings below represent the production configuration for a high-volume cold email operation running 5,000–10,000 contacts per month. Each setting maps directly to a deliverability risk that incorrect configuration creates.
| Inbox age / warmup stage | Daily send cap in Instantly | Warmup target |
|---|---|---|
| Week 1–2 (new inbox) | 15–20 per day | Warmup only, no cold campaigns |
| Week 3–4 (early warmup) | 25–30 per day | Warmup + 5–10 cold emails |
| Week 5–6 (mid warmup) | 35–40 per day | Full warmup + 20–30 cold emails |
| Week 7+ (fully warmed) | 40–50 per day | Warmup maintenance + 35–45 cold emails |
Set the Instantly per-inbox daily cap 10% below the absolute maximum for each stage. This provides a buffer for days when the warmup network sends slightly higher than usual, preventing combined warmup + cold email from accidentally breaching the safe ceiling.
| Schedule parameter | Setting | Reason |
|---|---|---|
| Active send days | Monday–Friday | No weekend sends to B2B audiences |
| Send window | 7am–5pm prospect local time | Business hours only, matches when prospects are checking email |
| Time zone setting | Prospect's local time zone | Sends during their business hours, not sender's |
| Daily volume distribution | Spread evenly across window | Avoids burst-sending that looks like automation |
| Stagger between sends | Enabled | Naturally distributes sends to prevent within-day volume spikes |
| Total inbox count | Sending domains | Inboxes per domain | Notes |
|---|---|---|---|
| 1–4 inboxes | 1 domain | All inboxes | Acceptable at low volume |
| 5–8 inboxes | 2 domains | 3–4 per domain | Splits risk between 2 domains |
| 9–15 inboxes | 3 domains | 3–5 per domain | Standard agency setup |
| 16–24 inboxes | 4–6 domains | 3–4 per domain | High-volume team or agency |
| 25+ inboxes | 6+ domains | 3–4 per domain | Enterprise scale |
Never run more than 5 inboxes on a single domain. At 6+ inboxes per domain, reputation problems at the domain level affect more inboxes simultaneously than the redundancy can protect against.
Configure the following alert thresholds in Instantly and in your monitoring routine:
| Metric | Warning threshold | Pause threshold | Action at each threshold |
|---|---|---|---|
| Hard bounce rate | 1.5% | 2% | Warning: investigate list; Pause: pause campaign immediately |
| Open rate (per campaign) | Below 20% | Below 12% | Warning: check Postmaster; Pause: investigate spam routing |
| Spam complaint rate | 0.05% | 0.1% | Warning: review sequence length; Pause: pause campaign, investigate |
| Domain reputation | Medium | Low | Warning: reduce volume 50%; Pause: pause all campaigns on domain |
Symptoms: A campaign that was performing well suddenly shows a sharp decline in open rate, with no changes to the email content or contact list.
Cause: Domain reputation has deteriorated, causing Gmail to route emails from the affected domain to spam. The most common trigger is a spike in spam complaints from a contact segment that was more likely to use spam-marking as a way to opt out. A secondary cause is the campaign reaching higher-volume segments of the contact list that generate more complaints per send.
Fix: Check Google Postmaster Tools for the sending domain. If domain reputation shows Medium or Low, pause all campaigns from that domain immediately. Do not adjust copy or contact list until the infrastructure problem is addressed — copy changes do not help when emails are routing to spam. Reduce warmup volume to maintenance level (8–12 per day). Wait for domain reputation to return to Good before resuming, which typically takes 14–30 days of reduced volume.
Symptoms: The inbox sends 40 emails before 10am and the remaining sends queue to the following day. The campaign is not sending at the intended cadence.
Cause: The daily send cap is set to 40 but the sending window is only 2–3 hours, so all 40 sends happen in that window before the window closes. The sending is technically within the cap but the burst pattern looks like bulk automation.
Fix: Extend the sending window to 7am–5pm and enable staggered sending. With a 10-hour window and 40 daily sends, each send is spaced approximately 15 minutes apart — a natural pattern that is not distinguishable from a person sending individual emails throughout the workday. In Instantly, set the campaign schedule to match business hours and confirm staggered sending is enabled.
Symptoms: Instantly's warmup score for an inbox fell from 75+ to below 30 over 2–3 weeks.
Cause: The warmup network engagement rate has declined. This can happen if the inbox's warmup emails are being flagged by the recipient's mailbox (reducing positive engagement signals), if the inbox has been sending at volumes that generate spam complaints (reducing the engagement-to-complaint ratio), or if the inbox was temporarily disconnected from the warmup network during a credentials issue.
Fix: Check that the inbox is still connected to Instantly with active credentials. If credentials expired or were reset, reconnect. Pause cold campaigns from this inbox for 1–2 weeks to allow warmup to rebuild without the negative signal contribution of cold email. Reduce cold email volume on this inbox to 5–10 per day when campaigns resume, allowing the warmup score to rebuild before returning to full volume.
Symptoms: Per-inbox daily send report shows 65 sends when the cap is set to 45.
Cause: The daily cap setting was applied to the campaign but not overriding an older higher limit at the inbox level. Or the warmup network emails are being counted toward the daily send limit in the reporting view (some reporting configurations include warmup in daily send counts).
Fix: Check the per-inbox configuration in Instantly to confirm the daily limit is set at the inbox level, not just the campaign level. Verify whether the daily count in reporting includes warmup emails. If warmup is included in the count, reduce the cold email cap to leave room for warmup sends (e.g., if warmup sends 15 per day, set cold email cap to 25–30 to stay under 45 total). Correct the misconfiguration before the next campaign day.
Symptoms: A weekly MXToolbox blacklist check reveals the sending domain is listed on one or more email blacklists, despite all inboxes staying within per-inbox daily limits.
Cause: Blacklisting is more likely caused by a spam trap hit than by volume alone. Spam traps are email addresses that were once valid but are now monitored by blacklist operators — sending to a spam trap address is treated as evidence of poor list quality regardless of the sending volume. The contact list used in the campaign contains at least one spam trap address from an unverified source.
Fix: Submit a blacklist removal request through the blacklist operator's delisting portal. Simultaneously investigate the contact list source: if the list was not from a verified provider, it is the likely source of the spam trap. Remove all contacts from that list source and replace with verified contacts from Quarvio. After delisting and list replacement, allow 48–72 hours before resuming campaigns to confirm the delisting has propagated.
Symptoms: Inbox A on outreach-domain.com has a 38% open rate; Inbox B on the same domain has a 14% open rate, despite identical campaign configuration and similar contact segments.
Cause: The two inboxes have different individual sending histories, which can create inbox-level reputation variation even on the same domain. A more common cause: Inbox B was configured after Inbox A and has been in use for a shorter time, so its warmup history is less mature. Or the contact segments assigned to Inbox B are less ICP-aligned and generating more spam complaints per send.
Fix: Check the warmup score in Instantly for each inbox individually. If Inbox B has a significantly lower warmup score, it is not fully warmed and should have its cold campaign volume reduced until warmup completes. If warmup scores are comparable, review the contact segments: pull the contact list segments assigned to each inbox and compare the ICP quality. Rebalance the segment assignments to distribute ICP-quality variation more evenly across inboxes.
Symptoms: Added 5 new inboxes to a campaign expecting to increase daily volume from 200 to 400, but the campaign is still sending approximately 200 emails per day.
Cause: The new inboxes are not yet enrolled in the campaign correctly, or they are enrolled but their per-inbox daily caps are set to 0 or to a very low number. Another cause: the campaign's contact list has been exhausted (no new contacts to send to), so the additional inbox capacity is idle.
Fix: In Instantly, verify each of the 5 new inboxes is enrolled in the campaign and check their individual daily caps. Confirm the campaign's contact list has sufficient unsent contacts remaining. If the list is near exhaustion, add a new contact import. If the inboxes are enrolled but still not sending, verify their warmup scores (inboxes below 50 may be restricted to lower volume by Instantly's safety controls). If the warmup scores are sufficient, check that the inboxes are enabled (not paused) in the Instantly workspace.
Symptoms: Google Postmaster Tools shows the sending domain with Good reputation, but test emails sent to Gmail accounts land in the spam folder consistently.
Cause: Domain reputation in Postmaster Tools is an aggregate signal that takes time to update. A domain can have Good reputation but be delivering to spam for a specific subgroup of Gmail users (those who have previously flagged similar emails from this domain or domain category). Another cause: the spam folder routing is based on content filtering rather than domain reputation — specific words or phrases in the email body are triggering content-level spam filters independent of domain reputation.
Fix: Test the email content using a spam-checking tool (Litmus, Mail-Tester, or similar) to identify content-based spam signals. Remove any phrases, formatting patterns, or link combinations that score highly on content filters. Additionally, confirm that the email is not using image-heavy formatting or multiple tracked links in the same email — both can trigger content filtering even when domain reputation is Good. If content changes do not resolve the spam routing, investigate whether the sending IP (not domain) has a separate reputation issue by checking IP blacklisting through MXToolbox.
When preparing to scale from a low to high volume, running warmup in parallel on multiple new domains and inboxes simultaneously compresses the timeline. Instead of sequentially warming one domain (6 weeks), then the next, then the next, warming three domains simultaneously completes all three in the same 6-week period.
The practical setup: in week 1 of a scale-up plan, register all three new domains and provision all their inboxes through Inframail. Enroll all inboxes in the Instantly warmup network on the same day. After 6 weeks, all three domains are warmed simultaneously and ready for campaign use. Total elapsed time: 6 weeks for 3 domains, versus 18 weeks sequentially.
The constraint is cost: Inframail's flat-rate model makes this economical because there is no incremental per-inbox fee. The inboxes are provisioned and running regardless of whether they are in warmup or campaign use.
When a campaign generates an elevated spam complaint rate, the natural response is to pause the campaign. But pausing cold emails while keeping warmup running at full volume is more effective than pausing everything.
During a complaint-driven pause:
This approach reduces recovery time compared to a full pause because the warmup network's positive engagement continues to influence the reputation metric while complaints decay.
At steady-state scale (10,000+ contacts per month), rotating new domains into the active pool on a regular schedule prevents the gradual reputation decay that affects domains running high-volume cold email for extended periods.
The 4-domain rotation model:
Each domain runs at full volume for 6 months, then is retired as a fresh replacement is warmed. No domain runs high-volume cold email for more than 6–9 months before being replaced. This prevents accumulated minor reputation degradation from becoming a major deliverability problem.
With Inframail's flat rate and no per-domain cost escalation, this rotation model is economical. The cost of a new domain ($10–15/year) plus Inframail's monthly rate does not change with the number of domains in rotation.
A subtle but important sending discipline: match the contact import volume to the inbox capacity available for the campaign. If a campaign has 6,000 contacts imported but only enough inbox capacity to send 500 per day, the campaign takes 12 days to complete. This creates a problem: the contacts imported on day 1 are in the campaign queue until their turn comes on day 8–12, by which time any follow-up emails to contacts from day 1–3 are out of sync with the sequence timing.
The correct approach: import contacts in batches that match the campaign's daily sending capacity. If you can send 500 per day and the sequence is 4 emails over 14 days, import 500–1,000 contacts per week to keep the campaign running fresh contacts rather than aging a large batch through a slow sequence.
A healthy inbox contributing to a healthy cold email operation should show these benchmarks per Woodpecker's 2025 cold email benchmark study:
| Metric | Healthy range | Investigate if below |
|---|---|---|
| Open rate | 25–50% | 20% (deliverability issue likely) |
| Reply rate | 6–15% | 4% (copy or ICP issue) |
| Bounce rate | Under 1.5% | 2% (list quality issue) |
| Warmup score | 60–90 | 50 (reduce campaign volume) |
| Domain reputation (Postmaster) | Good | Medium (review and investigate) |
If any metric falls below the investigate threshold, diagnose before increasing volume. Scaling volume on an inbox showing warning signs amplifies the underlying problem rather than solving it.
| Need | Tool | Notes |
|---|---|---|
| Verified B2B contacts | Quarvio | One-time purchase, no subscription |
| Email inboxes | Inframail | Microsoft 365 inboxes, auto DNS |
| Cold email sending | Instantly | Sequences, warm-up, reply tracking |
| LinkedIn outreach | Aimfox | Connection campaigns, Unibox |
What is the maximum number of cold emails you can send per day from one inbox?
The safe maximum for a fully warmed inbox is 30–50 per day. This is not a technical limit imposed by email providers — it is the rate that keeps sending patterns within what mailbox providers accept as normal for a business sender. Exceeding this limit increases the risk of spam filtering and account-level sending restrictions.
How many inboxes do I need to send 1,000 cold emails per day?
At 40 emails per inbox per day, you need 25 fully warmed inboxes to safely send 1,000 emails per day. A more conservative setup at 30 per inbox requires about 34 inboxes. Inframail makes this economical with unlimited inboxes at a flat rate.
Do I need a separate sending domain for each inbox?
No. A common setup is 3–5 inboxes per sending domain, with multiple sending domains running in parallel. This spreads risk across domains so that a deliverability problem on one domain does not affect the others. Avoid running cold email from your primary company domain entirely.
How long does it take for a new inbox to reach its full sending limit?
Plan for 6–8 weeks to fully warm a new inbox and reach the 40–50/day safe ceiling. The warmup process accelerates with a dedicated warmup network like Instantly's, but rushing the timeline risks deliverability problems that take longer to recover from than the warmup time saved.
Is 50 emails per day really the hard limit, or can I push higher for a few days?
50 per day is the recommended ceiling, not a hard technical limit. Pushing to 60–70 for a few days is possible and some senders do it. The risk is that the spike looks anomalous to mailbox provider algorithms and triggers increased spam filtering, exactly when you are trying to generate more activity from that inbox. The marginal sends above 50 are not worth the deliverability risk they create.
What happens to warming progress if I disconnect an inbox from Instantly?
If you disconnect an inbox from Instantly, the warmup network participation stops and the inbox's warmup score begins to decay. When you reconnect, the warmup resumes at the score level where it left off, but the score will be lower than when you disconnected if significant time has passed. For this reason, keep all inboxes connected to Instantly continuously, including inboxes that are not currently assigned to active campaigns.
Should I run warmup on weekends or only on weekdays?
Instantly runs warmup 7 days a week by default, which is actually beneficial for inbox reputation because the positive engagement signals (warmup emails being opened and replied to) accumulate faster with 7-day operation. Cold campaigns, however, should only run Monday–Friday during business hours. The warmup provides the steady positive signal; the cold campaigns provide the revenue activity. Running warmup on weekends and cold campaigns on weekdays is the correct configuration.
How do I know if warmup is actually working on a new inbox?
The key indicator in Instantly is the warmup score. A new inbox enrolled in warmup should show an increasing warmup score over its first 4 weeks. If the score is not increasing or is decreasing, something is wrong with the warmup configuration (likely an authentication issue or a credentials problem). Check that SPF, DKIM, and DMARC are correctly configured for the inbox's domain, and that the inbox credentials in Instantly are current and have correct permissions.
Can I run cold campaigns on an inbox while it is warming?
Yes, from week 3 onward, but with tight volume controls. In weeks 3–4, limit cold campaign sends to 5–10 per day from the warming inbox while warmup continues. In weeks 5–6, increase to 15–20 cold emails per day while warmup remains active. After week 7, the inbox is considered fully warmed and can run at 35–45 cold emails per day with warmup maintained in the background.
What is the difference between open rate dropping slowly vs. dropping suddenly?
A slow, gradual decline in open rate over 4–6 weeks typically indicates domain reputation decay from accumulated spam complaints — the reputation downgrade is gradual and reflects a chronic issue with complaint rate that has been building. A sudden drop (40% to 12% in 3–4 days) typically indicates a blacklisting event or a single large complaint spike from a specific contact segment. Both require investigation, but the rapid decline is more urgent — check MXToolbox for blacklist status immediately and check Postmaster Tools for the spam complaint rate spike date, which points to the campaign or contact segment that triggered it.
How do I safely test a new contact source without risking my main sending domains?
Create a dedicated test domain with 1–2 warmed inboxes that are not part of your main campaign infrastructure. Run new contact sources through this test domain first, with a test campaign of 200–300 contacts. If the bounce rate stays below 2% and spam complaints stay below 0.1% after the test campaign, the contact source is acceptable for use on main domains. If the test produces higher bounce rates or complaints, the source quality is a problem — reject it and use Quarvio for verified contacts that reliably pass this test.
Is there a way to send more than 50 per inbox per day without deliverability risk?
The 30–50 limit reflects the realistic safe ceiling under current mailbox provider algorithms. Some practitioners report running at 60–70 per day on well-established, highly reputable domains without visible deliverability impact. However, this is fragile: the margin between 50 and "safe at 60" is narrow and varies by domain age, IP reputation, engagement rate, and complaint rate. Building scale through more inboxes rather than pushing individual inboxes harder is the durable approach — inbox count scales linearly, per-inbox limits do not.
More inboxes means more volume — but only if your contacts are verified
Inbox rotation only scales if the contact data is clean. Sending high volume to unverified lists generates bounces that damage every inbox you have spent weeks warming. Quarvio delivers verified B2B contacts as a one-time purchase — no subscription, no stale records.
