Home › Blog

Lead Generation Email Warm-Up for 50–500 Agency Inboxes

By BobWork07 Nov 202611 min read
Agency email warm-up dashboard showing mailbox health, spam rate and domain groups for a large inbox fleet

For lead generation email warm-up at 50–500 inboxes, split senders across domains, start every mailbox at 3 emails/day, ramp by +2/day, and report spam rate per sender over 7 days. If you manage by fleet averages, one bad inbox can damage a client domain. This guide gives the setup, pool choice, reporting checks, and outbound limits.

Agencies fail warm-up differently from solo senders. The problem is rarely one mailbox. It is 80 inboxes connected too fast, 20 domains missing DKIM, and a client report that hides bad senders behind a healthy average. If you are building the wider stack, pair this with cold email infrastructure for agencies and the 50+ inbox cost guide.

The goal is not to make every mailbox look busy. The goal is to prove that each sender can receive, reply, avoid spam, and stay authenticated before it touches a prospect list.

How many inboxes per domain?

Plan the fleet before you connect anything. Decide the number of inboxes, domains, clients, and outbound caps first. Then let each mailbox warm on its own schedule.

Use this baseline:

For a new domain, allow 2–3 weeks before serious outbound. For an existing clean domain, 7 days can be enough to begin lightly. Treat readiness as mailbox-by-mailbox. One inbox may be ready while another is blocked, unauthenticated, or landing in spam.

Use this table before you sell capacity to clients.

Fleet sizeDomains at 2–5 mailboxes/domainWarm-up volume once rampedOutbound capacity at 30/dayOutbound capacity at 50/dayBobWork monthly cost, new account
50 inboxes10–25 domainsUp to 1,500/dayUp to 1,500/dayUp to 2,500/day$141/mo
100 inboxes20–50 domainsUp to 3,000/dayUp to 3,000/dayUp to 5,000/day$194/mo
200 inboxes40–100 domainsUp to 6,000/dayUp to 6,000/dayUp to 10,000/day$394/mo
500 inboxes100–250 domainsUp to 15,000/dayUp to 15,000/dayUp to 25,000/day$994/mo

The warm-up volume assumes the default 30/day cap per mailbox after ramp. The outbound capacity is a planning ceiling, not an inbox placement promise. Prospect quality, domain history, authentication, bounce rate, copy, and complaints still decide outcomes.

If a client asks for more volume, do not push 100–200 cold emails per day from one mailbox. Build more mailboxes, spread them over more domains, and let each sender earn volume slowly.

Which pool model fits agencies?

Warm-up works by exchanging normal office-style email between inboxes. The pool model decides who those mailboxes can talk to.

A shared warm-up network is useful when you have a small number of inboxes. One mailbox can start because it has peers in the network. It also gives more provider and domain variety.

A private pool is better once your agency has enough mailboxes. In a private pool, only your account’s mailboxes write to each other. Nobody outside the account receives those warm-up addresses. The trade-off is that you need at least two mailboxes, and better results come when your own fleet has enough provider and domain variety.

Fleet stagePool choiceWhy
1–10 inboxesShared networkOne mailbox can start, and you get outside peers.
10–49 inboxesShared or privateUse private only if you have enough domain variety.
50+ inboxesPrivate pool recommendedYour fleet is large enough to warm internally.
Client-isolated setupPrivate pool per accountPrivate pool is account-level, so plan isolation around accounts.

BobWork Email Warm-up uses a shared warm-up network by default, with a private pool option in Mailbox pool → Pool mode. The shared network handles peer selection and timing automatically. Switch to private when your agency has enough inboxes to keep the pool active on its own.

Do not treat private pool as a deliverability shortcut. Private mailboxes still need SPF, DKIM, DMARC, realistic sending windows, and clean reply behaviour. A private pool protects isolation. It does not fix bad DNS or aggressive outbound.

How should you build domains?

Your domain plan matters more than the warm-up tool. If you put 50 inboxes on one new domain, you create a single point of failure. If that domain’s reputation drops, every mailbox under it becomes harder to use.

Use secondary domains for cold outreach. Keep the main company domain away from first-touch cold campaigns unless the risk is clearly accepted. For domain planning, see how many domains you need for cold email and secondary domain setup.

A practical agency layout looks like this:

Before warm-up starts, authenticate every domain.

You need SPF, DKIM, and DMARC. SPF says which servers can send. DKIM signs the message. DMARC tells receivers how to handle alignment and failures. For cold email, start with DMARC at p=none if you need monitoring before enforcement.

Google’s sender guidelines require SPF or DKIM, and DMARC for bulk senders. Google also says spam complaint rates should stay under 0.1% and should never reach 0.3%. Read the current source in Google’s email sender guidelines.

Yahoo requires SPF and DKIM, DMARC at least p=none, aligned From domains, one-click unsubscribe for bulk senders, and spam rates under 0.3%. Check the current wording in Yahoo’s sender best practices.

Microsoft applies requirements to high-volume Outlook.com and Hotmail senders. For domains sending over 5,000 emails per day, Microsoft states SPF, DKIM, and DMARC alignment requirements. The complaint threshold is not stated in the available Microsoft guidance, so do not invent one.

If you need a fast DNS pass, use SPF, DKIM and DMARC for cold email or run checks with the free SPF checker, DKIM checker, and DMARC checker.

How do you onboard in bulk?

Manual setup is fine for five inboxes. It breaks at 100. You need a repeatable connection process, a standard CSV, and a safe retry path for failures.

For bulk IMAP setup, use rows with these fields.

FieldWhat it meansExample
emailFull mailbox addressalex@example.com
app_passwordApp password or mailbox passwordProvider-specific
nameSender display nameAlex Morgan
imap_hostIMAP host for custom domainsimap.examplehost.com

For Gmail, Yahoo, and iCloud, hosts can be filled from the preset. For other providers, add the IMAP host. Each row should receive the same IMAP and SMTP login test as a single mailbox connection. Failed rows should be listed with the reason. Already-connected rows should be skipped, so a re-upload is safe.

Provider-specific passwords matter. Gmail and Google Workspace usually need an app password for the IMAP route, which requires 2-Step Verification. Yahoo and iCloud also use app passwords. Zoho can use the Zoho Mail API route on the free plan, or IMAP on Mail Lite and above. Lark uses IMAP with a mail-client password.

If you manage Gmail at scale, read the Gmail warm-up guide before creating app passwords. For Zoho, use the Zoho Mail warm-up guide. For generic fleet onboarding, use the CSV import guide.

BobWork’s default account limit is 200 mailboxes. Larger fleets, including 500 or 1,000 mailboxes, can request a higher limit at info@bobwork.ai. Mailboxes above the free limit need billing active before they connect.

Do not start real sending on the day the login test passes. A login test only proves access. It does not prove stable sender reputation. Warm-up needs time, received mail, replies, and spam-folder checks.

Use this connection workflow:

  1. Create the domains and mailboxes.
  2. Publish SPF, DKIM, and DMARC.
  3. Wait for DNS propagation.
  4. Connect 10–20 test inboxes first.
  5. Fix provider-specific failures.
  6. Upload the full CSV in batches.
  7. Keep failed rows separate.
  8. Start warm-up before assigning prospects.

At 500 inboxes, batch discipline saves days. You do not want to discover after launch that 90 inboxes used regular passwords where app passwords were required.

What should reports show?

Agency reporting should never show only the average. A domain can look fine while three mailboxes are failing. A client can appear ready while one sender is blocked. Report at the mailbox level first, then roll up to domain and client views.

Use these mailbox fields as the reporting minimum.

Report fieldGood stateAction when bad
Login statusConnectedReconnect or replace the mailbox.
SPFPassingFix DNS before sending.
DKIMPassingEnable signing or correct selector.
DMARCPresent and alignedAdd record or fix alignment.
Warm-up age7+ daysKeep warming before outbound.
Received warm-up mail30+ in 7 daysWait for more data.
7-day spam rate10% or lessDo not send outbound if higher.
Early warning spam rateUnder 5% preferredPause for a few days above 5%.
Health statusHealthy preferredInvestigate Watch, At risk, or Blocked.

Spam rate should be sender-based. That means the percentage of a sender’s warm-up mail that receiving mailboxes found in Spam over the last 7 days. This is more useful than checking whether the sender’s own inbox contains spam.

A ready mailbox should meet three conditions:

Do not override the ready gate because a client is waiting. If a mailbox is above 5% spam, pause it for a few days and investigate. Look for missing DKIM, sudden volume jumps, poor domain history, provider locks, or a bad prospect list.

For agency operations, use status buckets.

StatusMeaningClient-safe wording
HealthyReady or close to readyAvailable for controlled sending.
WatchSome risk signalsWarming continues; no scale-up yet.
At riskSpam or DNS issuePaused from outbound until fixed.
BlockedLogin or permission failedNeeds reconnection or replacement.

This gives account managers a plain-language report without hiding the engineering detail. It also stops the common mistake of moving all mailboxes forward because the fleet average looks acceptable.

If you need reporting in your own dashboard, use an API instead of screenshots. A useful warm-up API should expose mailboxes, warm-up stats, domain checks, and campaign readiness. For implementation ideas, see the email warm-up API guide.

How do you start outbound?

Warm-up does not make bad cold email safe. It prepares the mailbox to behave like a normal sender. Your outbound still needs low bounce rates, relevant targeting, unsubscribe handling, and controlled volume.

Start with your cleanest segment. Avoid scraped, old, or role-heavy lists. Remove obvious invalid addresses before sending. A mailbox with good warm-up history can still fail quickly if the list bounces or recipients complain.

Use this first-campaign ramp after the mailbox is ready.

Campaign dayCold emails per mailboxWarm-up settingNotes
1–210–2010–15/dayWatch bounces and replies.
3–520–3010–15/dayKeep copy and segment stable.
6–1030–4010–15/dayIncrease only healthy senders.
11+30–5010–15/dayAdd mailboxes for more volume.

Do not scale every sender together. Scale only the mailboxes with clean stats. If one domain has several Watch or At risk senders, hold the whole domain group until you know why.

Every cold campaign should include unsubscribe support. For bulk-style sending, one-click unsubscribe is part of modern sender expectations. The technical format is described in RFC 8058. You should also suppress unsubscribes and bounces across the account forever, not just within one campaign.

Replies should stop the sequence for that contact. Continuing to send follow-ups after a reply creates avoidable complaints.

If you send from warmed mailboxes, keep warm-up running. Dropping warm-up to zero during campaigns removes a source of normal received mail and replies. Use lower warm-up volume, steady outbound, and mailbox-level monitoring.

For sequence structure, use a short campaign with clear stop rules. The 4-step cold email sequence template gives a simple timing model. If your team handles replies across many inboxes, a unified inbox for cold email helps prevent missed replies and accidental follow-ups.

Do this now

Use this checklist before the first prospect email leaves any client mailbox.

StepActionHow to verify
1Group the fleet by client, domain, and provider.You can list every mailbox under one domain and owner.
2Keep domains to 2–5 mailboxes each.No domain carries the whole campaign risk.
3Publish SPF, DKIM, and DMARC.DNS checks pass for every sending domain.
4Choose shared or private pool.Private pool is enabled for 50+ inbox fleets if isolation is needed.
5Upload a small test batch first.Login tests pass before the full CSV upload.
6Start every mailbox at 3/day.The ramp shows +2/day toward the mailbox cap.
7Wait for the ready gate.Each sender has 7+ days, 30+ received, and spam rate ≤10%.
8Pause risky senders early.Any mailbox above 5% spam is held for a few days.
9Start outbound at 10–20/day.First campaign metrics are reviewed before scale-up.
10Report per mailbox weekly.Client reports show status, DNS, spam rate, and readiness per sender.

For 50–500 inboxes, the operating discipline is the product. The warm-up tool enforces the schedule and measures signals. Your process decides whether the fleet stays usable.

If you want a free setup for the warm-up part, start with BobWork Email Warm-up. New accounts get up to 3 mailboxes free with no card and no time limit. Extra mailboxes are volume-priced, and large fleets can use CSV upload plus a shared warm-up network or a private pool per account.

Frequently asked questions

How many inboxes should a lead generation agency warm up first?

Start with the number your client volume needs, not the biggest number possible. For most cold outreach, plan around 30–50 real emails per mailbox per day, then add mailboxes instead of pushing one inbox harder.

Should agencies use a private warm-up pool?

Use a private pool once you have enough mailboxes to sustain it, typically 50 or more. A private pool keeps warm-up inside your own account. It needs at least two mailboxes; a shared network can start with one.

How long should 50–500 inboxes warm up?

Use at least 7 days for existing domains and 2–3 weeks for new domains. Do not start outbound until each mailbox has warmed for 7+ days, received 30+ warm-up emails and has a 7-day spam rate of 10% or less.

What spam rate should trigger a pause?

Pause any mailbox above 5% spam rate for a few days before it sends cold email. For sender complaints, keep Google complaint rate under 0.1% and never above 0.3%; Yahoo lists under 0.3% in its sender guidance.

How many domains do agencies need for 500 inboxes?

A typical planning range is 2–5 mailboxes per domain. At 500 inboxes, that means roughly 100–250 domains. The exact number depends on client risk, domain age, authentication, and sending volume.

Can one bad mailbox hurt the whole fleet?

Yes, if you manage by averages only. Report every mailbox separately. Watch 7-day spam rate, DNS status, login failures, and whether the mailbox is ready for outbound before assigning campaign volume.

Can agencies warm up and send cold email together?

Yes, but reduce risk. Keep warm-up running at about 10–15 emails per day during campaigns, send only from ready mailboxes, and keep real cold outreach around 30–50 emails per mailbox per day.

Warm up your mailboxes free

Connect Gmail, Google Workspace, Zoho or Lark. Your mailboxes warm on a shared network, or in a private pool of your own, starting today.

Start free