Mailbox Density Per Domain for Outbound

Mailbox density per domain is the number of cold email sending seats you place on one dedicated outbound domain. It is one of the simplest controls you have and one of the first to break when someone chases volume. Common operator practice keeps about two or three mailboxes per domain, with a soft ceiling around five. Packing far past that concentrates risk: one complaint spike or bad list segment can stain every seat that shares the domain name receivers see.

This guide goes deeper on density ops. For the core rule and examples, see How Many Mailboxes Per Domain for Cold Email at /blog/how-many-mailboxes-per-domain-cold-email. For per mailbox caps, see Google Workspace Sending Limits for Cold Email at /blog/google-workspace-sending-limits. For spreading load, see Mailbox Rotation for Cold Email Infrastructure at /blog/mailbox-rotation-cold-email.

Understanding the differences:

• Density: seats on one domain.
• Volume: cold sends per seat per day (including follow ups).
• Rotation: how the sequencer spreads new conversations across seats and domains.

You can rotate beautifully across twelve seats that all sit on one domain and still overload that domain's reputation. Rotation without domain spread is theater.

Common operator practice:

Mailboxes per domain: Two or three; soft ceiling around five

Cold sends per warmed mailbox per day: Roughly 20 to 40 including follow ups

New seats: Lower caps until history exists

These are not Google rules. Google's sending limits page lists a daily sending limit of 2,000 messages per user account (1,500 for mail merge, 500 for trial accounts), with sending blocked for up to 24 hours once a limit is hit. Google says the limits exist to keep systems healthy and accounts safe. They sit far above cold email practice and are a ceiling, not placement guidance. Google's sender guidelines still expect authentication and low complaint rates on whatever density you choose.

Shared visible identity

Receivers weigh the sending domain, not only the individual address. In operator experience, many mailboxes do not create many independent reputations if they all send as @outbound.example.

Correlated list risk

Ops often feed the same segments to every seat on a domain. A bad file hits everyone together.

Operational blindness

Blended dashboards hide which seat failed. Domain level health drops and the team buys more seats on the same name.

Faster path to burn

When you finally need to retire the domain, you retire more inventory at once. See Why Cold Email Domains Burn and How to Slow It at /blog/why-cold-email-domains-burn and Burned Domains: When a New Batch Does Not Help at /blog/burned-domains-new-batch-mistake.

Setting up policy:

1. Write the number down. Example: default two mailboxes per domain; allow three; require lead approval above that; never above five without a written exception.
2. Tie exceptions to evidence. Only for domains with stable replies and clean bounces, temporary, reviewed weekly.
3. Provision against the policy. Humans and APIs both respect the cap. See API Provisioned Google Workspace Mailboxes for Cold Email at /blog/api-google-workspace-mailboxes-cold-email.
4. Name seats with domain codes so Smartlead or Instantly UIs make overcrowding obvious.
5. Review monthly by sorting domains by mailbox count and reply rate.

Scaling should add domains as you add seats. If daily volume doubles, domain count should roughly double at constant density and constant per mailbox caps, after warmup buffers. If seat count doubles on the same domains, you did not scale infrastructure; you packed it. That pattern shows up in post scale deliverability drops. See Deliverability Dropped After You Scaled: What Changed at /blog/deliverability-dropped-after-scaling.

Per client pools each get their own density budget. Do not borrow empty seats on Client A's domain for Client B. Multi organization separation is plan dependent; use it when available. See Cold Email Inboxes for Agencies: Isolation First at /blog/cold-email-inboxes-for-agencies.

On shared SMTP, neighbours outside your company can hurt you even at low density. Density policy does not fix a shared pool. Prefer official Google Workspace on dedicated domains you control. See Dedicated Google Workspace Versus Shared Cold Email Infra at /blog/dedicated-google-workspace-vs-shared-cold-email-infra.

Target: 400 cold sends per day.

• At 25 sends per mailbox: 16 mailboxes.
• At 2 mailboxes per domain: 8 domains.
• At 3 mailboxes per domain: about 6 domains.
• Plus domains still warming.

Authentication must pass on every domain before that math goes live. See Authentication for Cold Email on Google Workspace at /blog/authentication-cold-email-google-workspace.

Warning signs:

• Several mailboxes on one domain lose replies together.
• Provider health drops at domain scope first.
• Adding another seat on the same domain to rotate more does nothing.
• Retirement cost feels huge because too much capacity shared one name.

Response: pause the weak domain, lower caps, move new volume to new authenticated domains, do not pile more seats onto the patient.

Before creating the next mailbox:

1. Count existing seats on that domain.
2. Confirm the domain is under the soft ceiling.
3. Confirm auth still passes.
4. Confirm the daily cap plan for the new seat (warmup first).
5. Confirm the sequencer pool will rotate across other domains too.

If step 2 fails, buy or attach another domain instead. That single habit prevents most packing incidents.

Myth: More seats on one domain look more like a big company.
Reality: They look like concentrated outbound.

Myth: Sequencer rotation fixes density.
Reality: Rotation needs domain spread.

Myth: Google's user limit means density can ignore reputation.
Reality: Limits are not placement guidance.

New domains should not start at the soft ceiling. Open with one or two seats, warm them, then add the third only if replies and bounces look stable. Filling five seats on day one maximizes coordination cost when you need to pause the whole domain.

ColdMail is built around the density friendly shape: official Google Workspace on dedicated domains, automated SPF, DKIM, DMARC, and MX, admin panels with 2FA, and provider health indicators that make a weakening domain easier to spot. AI warmup is available as an optional add on; see coldmail.app for current add on pricing. Multiple organizations are available on supporting plans. Mailboxes are ready to connect in Instantly and Smartlead using the methods those tools support.

You still choose density. ColdMail does not invent a safe packing ratio beyond operator practice.

Set up your mailboxes on domains sized for your volume at coldmail.app, or Book a Strategy Call to translate a daily send target into domain count.