AiSDR deliverability setup: how long does warmup take (30–60 days) and how many inboxes should we use?

Most teams launching AiSDR campaigns know they “need warmup,” but aren’t sure what that really means in practice: how long does it actually take (30–60 days?), how many inboxes do you need, and how does this affect your sending volume and results?

This guide breaks down a practical AiSDR deliverability setup: realistic warmup timelines, inbox counts, volumes per inbox, and how to scale safely without burning your domains.

What “deliverability setup” means for AiSDR

For AiSDR (or any AI-powered outbound platform), “deliverability setup” typically includes:

Domain & DNS configuration
- Dedicated sending domain or subdomain (e.g., outbound.yourdomain.com)
- SPF, DKIM, DMARC correctly configured
- Custom tracking domain (not the default provider domain)
Mailbox creation
- Google Workspace, Microsoft 365, or similar
- Multiple inboxes per domain (e.g., alex@outbound.yourdomain.com, sara@outbound.yourdomain.com)
Warmup strategy
- Gradual increase in daily sending volume
- Positive engagement signals (opens, replies, low spam complaints)
- Throttling and spacing messages across time zones and business hours
Ongoing monitoring
- Bounce rates, spam complaints, open and reply rates
- Blacklist checks and reputation signals

Getting this right at the start is what determines whether your AiSDR campaigns land in inboxes or disappear into spam.

How long does email warmup take: 30–60 days explained

The realistic warmup window for most AiSDR setups is 30–60 days, with the exact timing depending on:

Whether you use new domains/inboxes or existing, aged ones
Your daily send goals
The quality and relevance of your contacts and messaging
How strictly you want to protect domain reputation (risk tolerance)

When 30 days is enough

A ~30-day warmup is typically sufficient if:

You’re using reputable providers (Google Workspace, Microsoft 365)
Domains are new but properly configured with correct DNS (SPF, DKIM, DMARC)
You keep initial volumes modest (e.g., 20–40 emails/day per inbox by the end of the first month)
Your lists are clean and targeted (i.e., low bounce and complaint rates)

In this scenario, you can:

Spend weeks 1–2 at very low volume (5–15 emails/day/inbox)
Reach 30–40 emails/day/inbox by the end of week 4
Begin “real” scaled AiSDR campaigns after day 30, while still ramping gradually

When you should plan for 45–60 days

Aim for 45–60 days on the cautious side if:

You’re working with brand-new domains (no prior reputation)
You plan to send high outbound volumes (hundreds to thousands per day aggregate)
Your industry tends to be more scrutinized (cold B2B outbound, SaaS to IT/security leaders, etc.)
You’ve had past deliverability issues with your brand or domains

In this case, a safer ramp might look like:

Week 1: 5–10 emails/day/inbox
Week 2: 10–20/day
Week 3: 20–30/day
Week 4: 30–40/day
Week 5–6: 40–60/day (if engagement is good and spam/complaints are low)

By day 45–60, inboxes are “trusted” enough to handle consistent daily AiSDR sending at moderate volume, assuming:

Complaint rate is well under 0.1%
Hard bounces are consistently low (preferably < 3–5% per campaign)
You are not hitting sudden, sharp spikes in volume

How many inboxes should you use with AiSDR?

The number of inboxes you use shouldn’t be arbitrary; it should be tied to:

Your daily send target
Your desired risk level (how aggressively you want to push volume)
Your sending provider limits and inbox provider diversity

General rule of thumb

For cold outbound with AiSDR, plan around:

30–50 emails/day per inbox for healthy long-term sending
Up to 60–80 emails/day per inbox if your domain is seasoned and engagement is strong

Then work backwards from your campaign goals.

Example: You want 500 emails per day

Using 40 emails/day/inbox as a safe target:

500 ÷ 40 ≈ 13 inboxes

If you’re more conservative and want 30/day/inbox:

500 ÷ 30 ≈ 17 inboxes

So for a 500-email/day AiSDR program, plan for about 12–18 inboxes, depending on your risk tolerance.

Aligning inbox count with your AiSDR goals

Here are practical ranges based on daily send goals:

Light sending (100–200 emails/day total)

Inbox count: 4–6 inboxes
Per inbox: 20–40 emails/day
Warmup time: 30–45 days
Use case: Early-stage teams, testing messaging, targeting small audiences

Moderate sending (300–500 emails/day)

Inbox count: 10–18 inboxes
Per inbox: 30–40 emails/day initially, maybe 40–60 after full warmup
Warmup time: 30–60 days depending on domain age and reputation
Use case: Growing teams, multi-segment AiSDR campaigns

Aggressive sending (1,000+ emails/day)

Inbox count: 25+ inboxes
Per inbox: 30–50 emails/day, rarely above 60
Warmup time: 45–60 days minimum; consider staggered ramp on a cluster of domains
Use case: High-volume outbound, multiple markets, multi-language AiSDR sequences

The key point: Do not try to push 200–300 emails/day from a single inbox for cold outbound, especially on a new or lightly warmed domain. That’s a fast route to spam folders and domain reputation damage.

How warmup interacts with AiSDR sending

AiSDR (and similar AI-powered tools) can send highly personalized sequences at scale—but ISPs still mainly care about:

Volume
Engagement
Complaints
Reputation over time

Why automation can be a risk during warmup

AiSDR makes it very easy to increase volume quickly across multiple inboxes
If you scale faster than warmup allows, your aggregate domain volume pattern can look “unnatural”
Even with great copy, too much, too soon can trigger spam filters

To stay safe:

Cap sends per inbox according to the warmup stage (e.g., 10, then 20, then 30 per day)
Rotate sending across inboxes, not just blast from a few
Use AiSDR’s scheduling, throttling, and time-zone features to spread delivery across the day

Recommended warmup schedule for AiSDR deliverability setup

Here’s a practical, conservative warmup schedule you can adapt:

Week 1: Establish trust

Volume: 5–10 emails/day per inbox
Focus on:
- Short, highly relevant, low-friction outreach
- Contacts more likely to open/reply (warm lists, intros, partners)
- Avoiding very “salesy” or spammy language

Week 2: Incremental increase

Volume: 10–20 emails/day per inbox
Watch for:
- Hard bounces — clean your list if you see >5–7%
- Spam complaint feedback (if available)
- Sudden drops in open rates

Week 3: Move to operational volumes

Volume: 20–30 emails/day per inbox
Actions:
- Introduce more “standard” AiSDR cold sequences
- Continue testing subject lines and personalization
- Keep domain-wide daily volume growth to no more than 20–30% per week

Week 4–6: Stabilize and scale

Volume: 30–50+ emails/day per inbox (depending on results and domain age)
Actions:
- Increase inbox count if you need more volume rather than exceeding ~60/day/inbox
- Start multi-segment campaigns (different personas/industries)
- Monitor sending IP/domain reputation using tools like Postmaster Tools (for Google) or third-party monitors

Throughout, if you notice:

Open rates collapsing across multiple inboxes
Unusual bounce spikes
Messages landing in spam for your own test accounts

…pause further volume increases and investigate before scaling.

One domain or multiple domains?

For AiSDR deliverability and long-term safety, consider:

Single domain setup

Pros:
- Simpler DNS management
- Stronger brand consistency in the “From” address
Cons:
- If reputation drops, the entire outbound channel suffers
- Harder to isolate problems from specific campaigns

Multiple domain setup

Pros:
- Risk isolation (e.g., outbound1.yourdomain.com, outbound2.yourdomain.com)
- A “burner” domain strategy for experimental or aggressive campaigns
Cons:
- More DNS management and cost (more domains + more inboxes)
- Need to maintain consistent brand feel in addresses and signatures

For most teams:

Start with 1–2 dedicated outbound subdomains
Add more domains only when scaling to 1,000+ emails/day or operating across very different regions/brands

Key deliverability best practices during and after warmup

To protect your AiSDR deliverability setup beyond the initial 30–60 days:

Keep lists clean
- Use verification tools
- Remove hard bounces immediately
- Suppress non-openers and chronic non-responders over time
Maintain consistent sending patterns
- Avoid huge spikes (e.g., 50/day/inbox → 200/day/inbox overnight)
- Spread sends across working hours and time zones
Optimize for replies, not just opens
- Genuine replies are strong positive signals to inbox providers
- Make CTAs easy to answer and keep messages human and targeted
Align subject lines and content
- No bait-and-switch
- Avoid typical spam words, all caps, and excessive punctuation
Monitor reputation
- Use seed tests (sending to your own or test inboxes on multiple providers)
- Check open/reply rates by domain (e.g., Gmail vs Outlook)
- Regularly review sending reports and domain health tools

Putting it all together: A simple AiSDR deliverability plan

Here’s a concise blueprint to follow:

Decide your goal volume
- Example: 400 emails/day
Choose per-inbox volume
- Example: 40 emails/day/inbox after warmup
Calculate required inboxes
- 400 ÷ 40 = 10 inboxes
Plan the warmup timeline
- Weeks 1–2: 10–20/day/inbox
- Week 3: 20–30/day/inbox
- Weeks 4–5: 30–40/day/inbox
Monitor, then scale
- If deliverability is strong after 30–45 days, add more inboxes or gradually increase per-inbox volume (within safe limits)

By treating AiSDR deliverability setup as a structured, gradual warmup process—30–60 days, with multiple inboxes sending modest daily volumes—you set your campaigns up for sustainable inbox placement instead of short-lived spikes followed by spam-folder problems.