How to set daily sending limits in Instantly 2026: per-inbox math, domain health, and scaling safely

Last updated: June 2026 · Marcus Chen, outbound sales trainer, 150k+ emails sent

---

---

Our take

Sending limits are the most commonly misconfigured element in cold email infrastructure, and also the element where misconfiguration produces the slowest, most insidious damage. Unlike a bounce rate problem (which shows up in campaign analytics within 48 hours), sending limit damage accumulates in domain reputation over weeks. By the time deliverability noticeably declines, the root cause may be 3–4 weeks old.

After 150,000+ emails sent across dozens of campaigns and ICP segments, the patterns are consistent: practitioners who treat sending limits as a minor configuration detail regularly rebuild entire sending domains 6–9 months into successful campaigns because the limits were set too aggressively from the start. Practitioners who understand the math behind why the limits exist — and build their infrastructure accordingly — scale to 2,000+ emails per day without deliverability problems.

The unique angle of this guide is the math. Not just "set 30–50 per day" but: why 30–50, what happens above 50, how to calculate how many inboxes you need for your target volume, what domain health metrics to watch at each scale stage, and how to increase limits safely as the infrastructure matures.

Quarvio delivers the verified B2B contacts that go into the campaigns. Inframail provides the pre-configured sending inboxes that the limits apply to. Instantly manages the sending limits, warm-up, and deliverability reporting. Aimfox runs LinkedIn outreach parallel to email and does not count toward email sending limits.

Why daily sending limits exist: email provider volume detection

To understand why sending limits matter, you need to understand what email providers (Gmail, Outlook, Yahoo) are looking for when evaluating whether a sending domain is legitimate or a source of bulk or spam email.

How email providers detect suspicious sending patterns

Email providers monitor sending patterns at two levels: the sending IP address and the sending domain.

Volume anomalies: A brand-new domain that suddenly sends 500 emails on its first day of existence is statistically unusual. Legitimate business email domains ramp up gradually as a business grows. An immediate high-volume send from a new domain is a spam pattern signal.

Velocity spikes: Even an established domain that normally sends 30 emails per day but suddenly sends 500 on one specific day is triggering a velocity spike alert. Email providers flag this as potentially compromised domain behaviour.

Reputation signals aggregation: Email providers share sending reputation data across networks. A domain flagged as suspicious by Gmail's filters faces increased scrutiny from Outlook and Yahoo as well. Reputation damage is not siloed to one receiving provider.

Engagement rates: Email providers monitor how recipients interact with incoming emails from a given domain. Low open rates combined with high volume is a spam signal. High delete-without-open rates trigger spam classifications. Low complaint rates (below 0.3%) are required for Google Postmaster Tools to show a good reputation score.

Why the 30–50 per day limit is the safe range

The 30–50 emails per inbox per day threshold cited by Instantly's cold email benchmarks is not an arbitrary number. It reflects the volume pattern of a legitimate business professional using their email for outreach: active, consistent, professional, but not operating a mass mailer.

At 30–50 per day per inbox, the volume is:

• Below the threshold that triggers volume anomaly alerts at major providers
• Within the range where warmup-phase reputation signals have established the domain as a normal professional sender
• Low enough that a reply rate of 8.5% (the benchmark average) produces 2–4 replies per inbox per day, a plausible level for a real person's inbox activity

At 100+ per day per inbox:

• The volume pattern is statistically inconsistent with a single person's natural email usage
• Even properly warmed inboxes face increased scrutiny when volume doubles
• Reply-to-send ratios decline because volume grows faster than replies, making the sending pattern look increasingly like bulk mail

The warmup period: why it matters before any production sending

Email warmup simulates natural inbox activity before production sending begins. The purpose: establish a sending reputation for a new domain by generating positive engagement signals (sends, opens, replies between warm-up partner inboxes) that build the domain's reputation score before real prospects receive any emails.

Without warmup:

• A new domain starts with zero reputation history (neutral/unknown status)
• The first cold emails land in spam or promotions folders at a significantly higher rate
• Early campaign performance is poor because deliverability is poor, which makes the campaign appear to be about contact quality when it is actually an infrastructure problem

Per Instantly's cold email benchmarks, the minimum warmup period is 2–4 weeks. Instantly's built-in warmup system handles this automatically when enabled, but the warmup must be active for the full required period before production campaign sending begins.

The two-level limit system in Instantly

Instantly uses two separate sending limit controls, and both must be configured correctly. A common error is setting only one and assuming the other defaults to something reasonable.

Level 1: Inbox-level daily limits

Located in: Settings → Inboxes → select inbox → Sending Limit

The inbox-level limit controls the maximum number of emails this specific inbox will send per day across all campaigns it is assigned to. This is the primary deliverability control.

Key behaviours:

• The inbox will not send more than this number of emails in any 24-hour period, regardless of how many campaigns it is assigned to or how many contacts are queued
• The warmup emails count separately; the warmup and production campaign limits are tracked independently
• If multiple campaigns share the same inbox, the inbox-level limit is the cap across all of them combined

Inbox-level limit by warmup stage:

Level 2: Campaign-level daily limits

Located in: campaign settings → Schedule → Maximum emails per day per campaign

The campaign-level limit controls the maximum number of emails this specific campaign sends per day across all its assigned inboxes. It is a campaign-wide cap that applies regardless of how many inboxes the campaign is using.

Campaign limit formula:

Campaign daily limit = (number of assigned inboxes) × (per-inbox daily limit)

For a campaign with 10 inboxes, each set to 40 emails per day, the campaign's maximum possible send volume is 400 per day. Setting the campaign-level limit below 400 creates a throttle; setting it above 400 is ineffective because the inboxes cannot send more than their individual limits regardless of the campaign limit.

When to set campaign limit below the theoretical maximum:

• Ramp-up periods: Set the campaign limit lower than the theoretical maximum while contact quality is being verified on an initial test batch
• Budget pacing: If you want the campaign to run its contact list over a specific number of days, calculate: total contacts divided by desired days = daily limit
• ICP testing: For a new ICP segment being tested before full rollout, limit the campaign to 50–100 per day to preserve contacts for the full campaign after testing

The sending limit math: calculating safe caps for your volume target

How many inboxes do you need?

Required inboxes = target daily send volume divided by safe per-inbox limit (40)

Why use 40 as the per-inbox safe rate rather than 50:

Using 40 (slightly below the 50 upper bound) provides a safety margin. On any given day, inbox warmup activity, random queue timing, and contact bounce patterns may push actual daily sends slightly above the expected average. Using 40 as the planning rate means inboxes rarely touch their 50 limit, which maintains a comfortable buffer below the threshold where provider algorithms begin increasing scrutiny.

Domain distribution across inboxes

Do not put all sending inboxes on one domain. Standard recommendation: 2–3 inboxes per sending domain.

Why distribute across multiple domains:

If a single sending domain is flagged for reputation issues (high bounce rate, spam complaints), all inboxes on that domain are affected. Distributing across multiple domains provides isolation — a problem on one domain does not take down the entire campaign infrastructure.

Inframail provisions Microsoft 365 inboxes with automated DNS setup (SPF, DKIM, DMARC) per the Mailgun SPF/DKIM/DMARC authentication guide, making it practical to manage multiple sending domains without manual DNS configuration.

Step 1: Set inbox-level daily limits

Navigate to Settings → Inboxes in Instantly. For each sending inbox, click into the inbox settings and set the Sending Limit field.

Sub-step 1.1: Set limits based on inbox age

Check the creation date of each inbox. New inboxes must start at warmup-phase limits even if the account plan supports higher limits. Setting a new inbox to 50/day immediately bypasses the ramp that establishes reputation.

New inbox rule: Any inbox under 30 days old gets a maximum limit of 20–30/day during the warmup period, even if assigned to a production campaign. The warmup period must complete before full production limits apply.

Sub-step 1.2: Verify warmup is enabled for every inbox

In each inbox's settings, confirm that Instantly's warm-up feature is enabled. Warmup and production sending run concurrently — the inbox sends warm-up emails via the Instantly warmup network alongside campaign emails. The warmup limit (typically 10–30 warmup emails per day) is separate from the production sending limit.

Benchmark: For a newly provisioned inbox, a healthy warmup score (visible in each inbox's analytics) should show a positive trend after 14 days. A warmup score that is flat or declining indicates a warm-up configuration problem worth investigating before using the inbox for production campaigns.

Failure mode: Setting a new inbox to a high production limit and disabling warmup. The inbox starts sending campaign emails without any reputation history, producing poor inbox placement from the first send and potentially triggering provider-level flags that damage the domain's reputation for all future campaigns.

Sub-step 1.3: Set sending time windows

In addition to the daily count limit, configure the sending time window: the hours during which the inbox can send emails. Recommended: Monday through Friday, 8:00 AM to 5:00 PM in the target contact's timezone.

Why time windows matter for the limit: Distributing 40 sends across an 8-hour window means approximately 5 sends per hour — a plausible natural sending pattern for a professional. Sending 40 emails in a 1-hour burst is an anomaly signal even if the daily total is within limit.

Enable the random send delay option in Instantly (typically 3–10 minutes between sends) to create a natural, non-uniform sending cadence. Sends with perfectly even intervals are detectable as automated; random delays simulate natural human sending patterns.

Sub-step 1.4: Audit all inboxes before campaign launch

Before launching any campaign, audit all assigned sending inboxes and confirm:

• All inboxes have a sending limit set (not zero or unlimited)
• All inboxes have warmup enabled
• All inboxes have a time window configured
• All inboxes under 30 days old are at warmup-phase limits

Benchmark: A campaign infrastructure audit before launch takes 10–15 minutes for up to 20 inboxes. Catching a single misconfigured inbox before launch prevents the downstream problem of discovering it after 48 hours of sending at incorrect limits.

Step 2: Set campaign-level daily limits

Navigate to campaign settings and locate the daily send limit field under Schedule or Sending settings.

Sub-step 2.1: Calculate the correct campaign limit

Apply the formula: total inboxes × per-inbox limit = theoretical daily maximum.

For a campaign with 15 inboxes at 40/day each: 15 × 40 = 600 per day theoretical maximum. Set the campaign limit to 500–550 (slightly below theoretical maximum) to provide a buffer.

Sub-step 2.2: Set lower limits for new contact sources

For any campaign using a contact list from a new source (new list provider, new ICP segment, new data enrichment approach), set the campaign limit to 50–100 per day for the first 3–5 days. Monitor the bounce rate during this test period. If bounce rate stays below 3%, increase the campaign limit to full production volume.

Why test with a reduced limit: A contact list with 12% invalid addresses will produce 12 bounces per 100 sends. At 50 sends/day, that is 6 bounces per day — manageable for a quick test. At 500 sends/day from the first day, that is 60 bounces per day — sufficient to materially damage domain reputation within 3–4 days.

Sub-step 2.3: Configure campaign limit ramp-up for large campaigns

For large campaigns (2,000+ contacts) that will run for multiple weeks, use a staged campaign limit increase:

• Week 1: Set campaign limit to 30% of target daily volume
• Week 2: Increase to 60% of target daily volume
• Week 3 onward: Full target daily volume

This staged campaign ramp provides an additional layer of protection beyond the inbox-level ramp and gives the infrastructure more time to establish consistent sending reputation before peak volume begins.

Step 3: Configure the sending schedule

The sending schedule controls when during the day and week campaign emails are sent. Proper schedule configuration is as important as the limit numbers themselves for maintaining natural sending patterns.

Sub-step 3.1: Set days and hours

Configure the sending schedule to Monday through Friday only. Remove Saturday and Sunday from the sending window. Cold outreach sent on weekends has materially lower open rates and the weekend send pattern is more common in bulk campaigns than in legitimate professional outreach.

Time window: 8:00 AM to 5:00 PM in the recipient's primary timezone. For campaigns targeting multiple timezones, set the schedule to the primary timezone.

Sub-step 3.2: Enable sending time randomisation

Activate the random delay option between sends. Set a randomisation window of 3–10 minutes. This creates a natural sending pattern rather than a fixed mechanical interval.

Benchmark: The natural email sending pattern of a person doing outreach varies between 2 minutes and 25 minutes between sends. A random delay range of 3–10 minutes sits within this natural range.

Sub-step 3.3: Do not send during warmup-only periods

For inboxes in their first 14 days, do not assign them to production campaigns. Warmup runs best when the inbox is dedicated to warmup activity in the early period, establishing a clean reputation base before any cold outreach is added.

Failure mode: Assigning a day-3 inbox to a production campaign to get it sending early. The early production sends occur before any positive reputation signals have been established, landing in spam at a higher rate and potentially damaging the domain before the warmup has any chance to build it.

Step 4: The 5-week ramp schedule

Key insight from this table: In weeks 1 and 2, zero production emails should be sent from newly provisioned inboxes. The warmup period is not optional acceleration — it is the minimum time required to establish sending reputation. Practitioners who begin production sending in week 1 consistently experience worse deliverability than those who complete the warmup first.

Sub-step 4.1: Increase inbox limits at week boundaries, not daily

Increase inbox-level sending limits once per week at the transition between warmup stages. Increasing daily creates unpredictable volume patterns. Increasing weekly creates a consistent step-up pattern that email providers see as organic growth.

Sub-step 4.2: Monitor deliverability metrics at each step increase

Every time you increase sending limits, watch the following metrics for 3–5 days before the next increase:

• Bounce rate: must stay below 3%
• Open rate: should not decline materially (significant open rate decline after a limit increase indicates inbox placement degradation)
• Domain reputation in Google Postmaster Tools: should stay at High or Medium
• Blacklist status in MXToolbox: no new listings

If any of these metrics show negative movement after a limit increase, pause the increase and investigate before continuing.

Sub-step 4.3: Apply the warmup period to every new inbox added mid-campaign

When you scale the infrastructure by adding new inboxes to a running campaign, the new inboxes must complete their own warmup period before being added to production. Do not add a week-1 inbox to a campaign just because the rest of the infrastructure is at full capacity.

Staggered build approach: When scaling up, provision new inboxes in batches. Start warmup on batch 2 while batch 1 is completing warmup. By the time batch 1 is ready for production, batch 2 is 2 weeks into warmup — ready 2 weeks after batch 1 goes live. This creates a continuous scaling runway without gaps.

Step 5: Monitor deliverability after limit changes

Monitoring converts limit-setting from a one-time configuration into an ongoing management practice. The following checks should be performed weekly at steady state and daily after any limit change.

Sub-step 5.1: Check Google Postmaster Tools weekly

Google Postmaster Tools provides domain-level metrics visible only to verified domain owners. The most important metrics:

• Domain reputation: High, Medium, Low, or Bad. High is optimal. Any decline from High toward Medium warrants investigation before the next limit increase
• Spam rate: The percentage of emails from your domain that Gmail recipients marked as spam. Must stay below 0.3%
• Authentication results: SPF, DKIM, and DMARC pass rates. Should be 100% for all three

How to interpret domain reputation changes: A single-week dip from High to Medium is not necessarily alarming if it recovers the following week. A two-week sustained Medium or a move to Low is a clear signal to pause limit increases and investigate list quality, bounce rates, and sending patterns.

Sub-step 5.2: Check MXToolbox blacklist status for all sending domains

MXToolbox checks sending domains against major email blacklists. Any listing means emails from that domain are blocked or filtered by receiving mail servers that use the relevant blacklist.

Check every sending domain weekly. For new domains, check every 3 days during the first 4 weeks. A newly blacklisted domain should be investigated immediately.

Sub-step 5.3: Monitor bounce rate per campaign

In each campaign's analytics, check the bounce rate daily during the first week of sending and weekly thereafter. Targets:

• Hard bounce rate below 2%
• Total bounce rate (hard + soft) below 5%

If bounce rate exceeds 3% for hard bounces, pause the campaign, investigate the contact list source, and verify the list before resuming.

Sub-step 5.4: Monitor open rate trend as a proxy for inbox placement

A sudden decline in open rate (5+ percentage points within a week) without a change in sequence copy or targeting often indicates that emails are landing in spam or promotions folders at a higher rate. If open rate declines after a sending limit increase, reduce the limit back to the previous value and allow 1–2 weeks for domain reputation to stabilise.

Domain health indicators and what they mean at scale

The consequences of ignoring daily sending limits

Immediate consequences (within days):

• Open rate decline (emails routing to spam folder)
• Bounce rate increase if the limit violation triggers inbox-level reputation flags at receiving servers

Short-term consequences (1–3 weeks):

• Domain reputation in Google Postmaster Tools declines from High to Medium or Low
• Some receiving mail servers start blocking the domain entirely

Long-term consequences (4–12 weeks):

• Domain listed on one or more email blacklists
• Campaign performance becomes severely degraded across all contacts
• A new domain requires another 4–6 weeks of warmup before production sending can resume

The cost calculation: A single sending domain with 3 inboxes at 40/day represents 120 emails/day of capacity. Infrastructure damage from preventable limit misconfiguration forces a rebuild that costs both time and money. Contacts from Quarvio at $129/5,000 represent $0.026 per contact — contacts that land in spam rather than the primary inbox due to domain reputation damage are wasted spend.

Configuration reference: sending limits in Instantly

Advanced sending limit tactics

Tactic 1: Use the inbox age buffer for outbound scaling

When planning to scale to a target volume, provision the required number of inboxes 5 weeks before you need them at full capacity. The provisioning timeline:

• Provision inboxes based on the formula (target volume divided by 40)
• Weeks 1–2: warmup only
• Weeks 3–4: warmup plus soft production (limit set to 20)
• Week 5: warmup plus full production (limit set to 40–50)

If you wait until you need the volume to provision inboxes, you wait 5 weeks for delivery. Planning ahead eliminates the scaling delay.

Tactic 2: Segment campaigns by inbox group to contain damage

Rather than assigning all inboxes to all campaigns, create inbox groups dedicated to specific campaigns or ICP segments:

• Group A (5 inboxes): assigned to Campaign A targeting ICP Segment 1
• Group B (5 inboxes): assigned to Campaign B targeting ICP Segment 2

If Campaign A produces a high bounce rate due to contact list quality for Segment 1, only Group A inboxes are affected. Group B inboxes continue operating at full health for Campaign B.

Tactic 3: Never reduce limits to zero without pausing the campaign first

If you need to stop sending from a specific inbox (for maintenance, credential renewal, or limit adjustment), remove the inbox from the campaign first, then adjust the limit. An inbox with zero limit assigned to a campaign produces confusing analytics and can cause queue buildup if the total campaign capacity drops unexpectedly.

Tactic 4: Scale LinkedIn outreach alongside email to reduce per-channel pressure

Running Aimfox LinkedIn outreach in parallel with Instantly email campaigns means the same contact can be reached via two channels without increasing email sending volume. The LinkedIn channel operates completely separately from email limits. Per Instantly's cold email benchmarks, combining email and LinkedIn increases reply rates 40–60% without requiring more sending capacity on the email channel.

Tactic 5: Set per-inbox limits slightly below the daily limit for timing variance

If your inbox-level daily limit is set to 50, on some days the actual send count may briefly approach 50 due to timing rounding and queue flush patterns in Instantly's sending engine. Setting the inbox limit to 45 instead of 50 provides a 5-email buffer that ensures the inbox never actually exceeds the safe threshold even with minor timing variance.

Troubleshooting sending limits in Instantly

Problem 1: Campaign is not sending at all despite active inboxes

Symptom: The campaign has been active for 48 hours but shows zero sends.

Cause 1: The campaign-level daily limit is set to zero. Cause 2: All assigned inboxes have sending limits set to zero. Cause 3: The sending schedule is configured for hours that have not yet occurred (launched on Friday night, schedule only covers weekday hours, and today is Saturday). Cause 4: The campaign is in draft mode, not active mode. Cause 5: The contacts have not been successfully imported (the campaign shows zero contacts enrolled).

Fix: Check campaign status (Active vs. Draft). Verify the sending limit in campaign settings is above zero. Verify all assigned inboxes have sending limits above zero. Check that the current day and time falls within the configured sending schedule.

Problem 2: Open rate dropped significantly after a sending limit increase

Symptom: Open rate declined by 8–15 percentage points within 5 days of increasing the sending limit.

Cause: The limit increase pushed sends per inbox above the threshold where email providers increase spam filter scrutiny, causing more emails to land in spam or promotions folders.

Fix: Reduce the inbox-level limit back to the previous value immediately. Allow 1–2 weeks for domain reputation to stabilise (check Google Postmaster Tools to see if reputation recovers). When attempting the increase again, use a smaller increment (increase by 5–8 per day rather than 15–20 at once) and monitor for 5 days before the next increment.

Problem 3: Bounce rate is high despite using verified contacts

Symptom: Bounce rate is above 5% on a campaign using a recently sourced verified contact list.

Cause 1: The contact list was verified before import but email addresses have changed since verification due to job changes or company restructures. Cause 2: The email verification used was syntax-only (format check) rather than SMTP-verified (confirming the email address exists at the mail server). Cause 3: The domain or inbox has been partially blacklisted, causing emails to bounce rather than land in spam.

Fix: Check MXToolbox for blacklist status of sending domains. If clean, the issue is contact list quality. Pause the campaign and verify the contact list source used SMTP-level verification. Source fresh contacts from Quarvio for the next batch.

Problem 4: Google Postmaster Tools shows Low or Bad domain reputation

Symptom: Domain reputation has dropped from High to Low or Bad in Google Postmaster Tools.

Cause: Accumulated spam complaints, high bounce rates, or sending above sustainable limits for the domain's age have degraded the domain's reputation score.

Fix: Pause all campaigns using this domain immediately. Check Postmaster Tools for the spam rate and bounce/reputation trend. If spam rate is above 0.3%, the primary cause is spam complaints — investigate contact list quality and campaign copy. If bounce rate is the primary driver, the contact list has too many invalid addresses. Allow the domain to recover (typically 2–4 weeks of no sending) before resuming at reduced limits. For severe cases (Bad reputation), the domain may need to be retired.

Problem 5: Sending stops mid-campaign despite limits not being reached

Symptom: The campaign was sending normally and suddenly stopped sending mid-day, well below the daily limit.

Cause 1: One or more sending inboxes have disconnected (credential expiry, OAuth revocation) and the campaign has no available inboxes. Cause 2: The contact list for the campaign has been exhausted. Cause 3: The campaign was manually paused by a team member. Cause 4: Instantly's sending engine paused the campaign due to a detected deliverability threshold being crossed.

Fix: Check campaign status. Go to Settings → Inboxes and verify all inboxes show Active status. Check the campaign's contact list to confirm remaining contacts exist. If all inboxes are healthy and contacts remain, check Instantly's notifications for any system-level alerts about the campaign being auto-paused.

Problem 6: Multiple inboxes on the same domain producing high bounces

Symptom: All inboxes on a specific sending domain show high bounce rates, but inboxes on other domains are performing normally.

Cause: The sending domain itself has a deliverability problem: either it has been blacklisted, the DNS records (SPF/DKIM/DMARC) are misconfigured, or the domain's IP reputation has been damaged.

Fix: Check MXToolbox blacklist status for the domain. Check Google Postmaster Tools for domain reputation. Verify SPF, DKIM, and DMARC records using MXToolbox's DNS lookup tools. For misconfigured DNS, correct the records through the domain registrar or through Inframail, which handles DNS automatically for provisioned inboxes. For blacklisted domains, submit delisting requests and pause sending until delisted.

Problem 7: Campaign sending at much lower volume than expected

Symptom: A campaign with 20 inboxes at 40/day each should send 800 emails per day but analytics show only 200–300 sends per day.

Cause 1: The campaign-level daily limit is set to 300, throttling the campaign below its inbox capacity. Cause 2: Several inboxes assigned to the campaign are disconnected or at zero limit, reducing effective inbox count. Cause 3: The contact list has fewer remaining contacts than expected. Cause 4: The sending time window is too narrow to allow full daily capacity to be reached.

Fix: Verify the campaign-level limit is set to at least 800. Verify all 20 inboxes are active and at 40/day limit. Check the contact list remaining count. Check the sending schedule time window width.

Problem 8: Domain blacklisted despite sending within recommended limits

Symptom: Domain appears on an email blacklist despite sending at 40 per inbox per day on a 4-week-old domain.

Cause 1: The contact list had a higher bounce rate than expected (above 5%), generating enough negative signals to trigger a blacklist. Cause 2: Some contacts marked the emails as spam and the complaint rate crossed the threshold that caused a listing. Cause 3: The domain was purchased as an aged domain that was previously used for spam and already carried a pre-existing negative reputation.

Fix: Submit a delisting request to the specific blacklist (each has its own process; MXToolbox links to the delisting pages). Investigate the cause: check bounce rate and complaint rate. For a new domain, verify it was not previously used. For contact list quality issues, source verified contacts from Quarvio. Pause the domain during delisting; do not continue sending while blacklisted.

Community evidence

Instantly's cold email benchmarks establishes the 30–50 per inbox per day benchmark across a large dataset of cold email campaigns. Campaigns operating within this range show materially better deliverability rates than campaigns exceeding it, even when other infrastructure factors are held constant.

Mailmodo's B2B email marketing statistics guide shows that inbox placement rates decline significantly when sending infrastructure is not properly configured, with bounce rates above 5% and spam complaint rates above 0.3% identified as the primary triggers for inbox placement degradation.

Google Postmaster Tools documentation confirms that domains maintaining spam rates below 0.1% reliably receive Good reputation scores, while domains above 0.3% face active spam filtering.

"The ramp schedule felt slow when I started — two weeks of warmup and no sending felt like wasted time. By week 6 I understood why it matters. My colleague skipped the warmup on a parallel domain and was at Medium reputation by week 3. My domain was still at High. The difference in open rates between our two setups was about 12 percentage points."

— Verified G2 reviewer, outbound sales manager, B2B technology, Instantly reviews on G2

Our actual stack

Frequently asked questions

How do I set daily sending limits in Instantly?

Sending limits are configured at two levels: inbox-level (Settings → Inboxes → select inbox → Sending Limit) and campaign-level (campaign settings → Schedule → Maximum emails per day). Set the inbox-level limit based on inbox age: 5–20 for inboxes under 14 days (warmup only), 20–40 for inboxes aged 14–30 days, and 40–50 for fully warmed inboxes over 30 days. Set the campaign-level limit to slightly below the theoretical maximum (total inboxes × per-inbox limit).

What is the maximum safe daily sending limit per inbox in Instantly?

The maximum safe limit per inbox is 50 emails per day for properly warmed inboxes (30+ days of warmup history). Per Instantly's cold email benchmarks, 30–50 per inbox per day is the range where properly warmed inboxes maintain good deliverability. Exceeding 50 per day per inbox consistently increases the risk of triggering spam filter algorithms at major email providers, even for well-established inboxes.

Does inbox warmup count toward the daily sending limit in Instantly?

No. Instantly's built-in warmup email activity is tracked separately from production campaign sends. Warmup emails generated by the Instantly warmup network do not count against the campaign-level sending limit or reduce the inbox-level sending limit available for production campaigns. Both warmup and production sending operate within the inbox simultaneously, but their counts are tracked independently.

How many emails can I send per day in Instantly?

Total daily volume capacity equals number of warmed inboxes × 40–50. For 10 warmed inboxes: 400–500 emails per day. For 25 warmed inboxes: 1,000–1,250 emails per day. There is no platform-level daily send cap in Instantly beyond your subscription plan's contact limits; the practical cap is set by the number of warmed inboxes available and their individual sending limits.

Why is my open rate dropping in Instantly after increasing sending limits?

The most common cause of open rate decline after a limit increase is inbox placement degradation — emails routing to spam or promotions rather than the primary inbox. Check Google Postmaster Tools for domain reputation changes. If reputation has declined, reduce the inbox-level limit back to the previous value, allow 1–2 weeks for stabilisation, and increase again in smaller increments (5–8 per day rather than 15–20).

How should I ramp up sending volume in cold email?

Follow the 5-week ramp: Weeks 1–2 warmup only (no production sends), Week 3 limited production (20–30 per inbox), Week 4 mid-production (30–40), Week 5 full production (40–50). Increase inbox limits at weekly intervals rather than daily. Monitor bounce rate and Google Postmaster domain reputation at each stage before proceeding to the next increase. Never skip the warmup period for new inboxes.

What is the difference between inbox-level and campaign-level sending limits in Instantly?

Inbox-level limits control the maximum sends from one specific inbox per day across all campaigns that inbox is assigned to. Campaign-level limits control the maximum sends from one specific campaign per day across all inboxes assigned to it. The inbox-level limit is the primary deliverability control; the campaign-level limit is a campaign throughput control. Both must be set. The campaign-level limit cannot cause the campaign to exceed the inbox-level limit for any individual inbox.

What happens if I exceed daily sending limits in Instantly?

Instantly enforces inbox-level limits mechanically — the inbox will not send more than the configured number per day. However, setting limits above the safe range (50+ per day per inbox) and operating at those limits consistently degrades domain reputation over time. The consequences are not immediate but become significant after 1–4 weeks: low domain reputation in Google Postmaster Tools, possible blacklist listings, and materially reduced campaign performance.

How do I check if my domain is blacklisted?

Use MXToolbox. Enter your sending domain and run the blacklist check. MXToolbox checks against 100+ email blacklists and shows which lists have flagged your domain. Check all sending domains weekly at steady state and every 2–3 days during warmup or after significant sending limit changes. If a domain is listed, submit a delisting request to each blacklist that has flagged it and pause sending from that domain until the listing is removed.

Can I set different sending limits for different campaigns in Instantly?

Yes. Campaign-level sending limits are set per campaign and can differ for each campaign. You can also assign different groups of inboxes to different campaigns, creating separate sending capacity pools per campaign. For example, Campaign A (testing a new contact source) can be set to 50 emails per day with 5 inboxes, while Campaign B (established contact list) runs at 500 emails per day with all available inboxes.

When should I increase my daily sending limit in cold email?

Increase the inbox-level daily limit only when: (1) the inbox has been active and sending for at least 7 more days since the last increase, (2) the bounce rate is below 2%, (3) domain reputation in Google Postmaster Tools is High, (4) no new blacklist listings have appeared in MXToolbox. Increase in increments of 5–10 per day maximum per step. Never increase by more than 50% of the current limit in a single step.

How many inboxes do I need to send 1,000 emails per day?

To send 1,000 emails per day at the safe limit of 40 emails per inbox per day: 1,000 divided by 40 equals 25 inboxes. Distribute across 8–12 sending domains (2–3 inboxes per domain) to contain potential domain-level reputation issues. Provision these inboxes 5 weeks before you need full capacity to allow the warmup period to complete. Inframail supports bulk inbox provisioning with automated DNS setup for teams scaling to this volume.

---