Apollo Email Warmup: When Built-In Warm-Up Is Enough

Use Apollo’s built-in warm-up when you have one paid-plan mailbox to prepare, Apollo is already your outreach workspace, and its 10–40 emails/day recommendation with a 50/day cap fits your plan. If you ignore mailbox count, provider mix, or overlapping send volume, warm-up can hide risk. This guide shows when to use Apollo alone and when to add standalone warm-up.

What is the short decision?

Apollo is an outreach platform first. Warm-up is bundled into that workflow on paid plans. That is useful when your campaign, inbox, contacts, and warm-up all live in one place.

A standalone warm-up tool has a narrower job. It prepares mailboxes, monitors placement signals, checks DNS, and keeps activity running before campaigns start. If you need the mechanics first, start with how email warm-up networks work, then set your safe cold email volume per mailbox.

Use Apollo alone when you have one mailbox to warm and you already run outreach there. Add standalone warm-up when you have more mailboxes, need provider coverage outside your current Apollo setup, or want to warm accounts before they become campaign senders.

Do not treat warm-up as permission to send harder. Mailbox reputation still depends on authentication, complaint rates, bounces, user engagement, and list quality. Google asks bulk senders to keep spam complaints below 0.1% and avoid reaching 0.3%. Yahoo says spam rate should stay under 0.3%.

How does Apollo email warmup work?

The verified Apollo facts are specific, so stay inside them.

Apollo’s paid plans include warm-up. The vendor-page check from 17 October 2026 lists Basic at $49/month and Professional at $99/month. Credits are pooled per team, the product is seat-based, and warm-up uses credits.

Apollo’s paid plans warm one mailbox free. The listed recommendation is 10–40 warm-up emails per day, with a cap of 50 per day. Apollo describes the pool as “a private network of test inboxes.”

Provider support depends on the plan. The free plan is Gmail only, with numeric limits not stated in the checked table. Paid plans list Microsoft Office or any provider. The same table notes managed Microsoft 365 mailboxes as something Apollo does well.

That matters because Apollo is not just a warm-up product. It has a built-in B2B contact database, sequences, and managed Microsoft 365 mailboxes. If those are why you bought Apollo, using its built-in warm-up for the first mailbox is a reasonable default.

Prices and plan details change. Check Apollo’s current pricing page before you buy or budget around it.

When is Apollo enough?

Apollo’s built-in warm-up is enough when four things are true.

First, you are warming one mailbox. The checked table says paid plans warm one mailbox free. If that is your only sender, another system may add process without adding much value.

Second, your daily warm-up target fits Apollo’s listed range. A 10–40/day recommendation with a 50/day cap is enough for many normal cold outreach senders. You still need a conservative real sending plan.

Third, you want warm-up close to your outreach workflow. Apollo has sequences and a B2B contact database. That helps if your team already works inside Apollo all day.

Fourth, you need Microsoft support inside the same platform. Apollo’s paid plans list Microsoft Office or any provider. BobWork does not support Outlook or Microsoft 365 yet because Microsoft requires OAuth.

Apollo is also a better fit when your main problem is not warm-up cost. If your team needs a contact database, managed Microsoft 365 mailboxes, and sequences, a standalone free warm-up tool will not replace that platform. It can only handle the warm-up side.

You still need basic sending discipline. Keep campaign volume below the point where replies, complaints, and bounces start moving against you. BobWork’s published practice is real outreach at 30–50/day per mailbox, adding mailboxes rather than forcing more volume through one address.

When should you add standalone warm-up?

Add standalone warm-up when mailbox readiness is a separate operational problem.

The common case is mailbox count. Apollo’s checked table says paid plans warm one mailbox free. If you have five, ten, or twenty senders, check what each extra mailbox costs inside your outreach stack. A standalone free plan can remove that first cost layer.

BobWork Email Warm-up is free for up to 10 mailboxes per person or company domain, with no credit card and no time limit. Each active mailbox above 10 is $5/month, with lower per-mailbox pricing from 10 extra and 50 extra. That matters for agencies and teams that prepare mailboxes before assigning campaigns.

The second case is provider setup. BobWork supports Gmail and Google Workspace, Zoho Mail, Lark Mail, Yahoo Mail, iCloud Mail, Amazon SES, SendGrid, Mailgun, and any IMAP+SMTP mailbox. Zoho can connect through the Zoho Mail API, including on the free Zoho plan, or by IMAP on Mail Lite and above.

Gmail and Google Workspace can use IMAP with an app password, which requires 2-Step Verification. One-click Google sign-in also exists, but Google caps unverified apps at 100 users and shows an unverified-app notice unless a Workspace admin trusts the app.

The third case is separating pre-warm-up from campaigns. You may want mailboxes ready before sales uses them. A standalone tool lets you connect accounts, run a steady schedule, and watch health before the first prospect email goes out.

The fourth case is pool choice. BobWork runs a shared warm-up network by default, where active mailboxes exchange warm-up mail with the wider network. You can switch to a private pool per account in Mailbox pool → Pool mode. In private mode, only your own mailboxes write to each other, and you need at least two mailboxes.

The free pool does this step automatically: it sends plain-text office-style messages, receives replies, rescues its own warm-up mail from Spam, and measures spam landings directly in receiving mailboxes. It only touches mail carrying the engine’s own hidden header, or a known subject for Zoho API senders. Real mail is never read, moved, or answered.

For broader comparisons, use the verified free warm-up plan comparison or the cheapest per-mailbox warm-up table.

How do you avoid overlap?

Running Apollo and a standalone warm-up tool can work. The risk is double-counting activity.

A mailbox does not care which product sent the messages. It sees total sending, total replies, spam placement, complaints, bounces, and authentication. If Apollo sends warm-up and another tool also sends warm-up, your mailbox volume can climb faster than planned.

Pick one primary warm-up engine per mailbox. If the mailbox is already active in Apollo warm-up, do not also ramp it aggressively elsewhere. If you need standalone monitoring, set a low cap or pause one tool until you know the mailbox is stable.

BobWork’s default ramp starts at 3 emails/day, adds 2 per day, and caps at 30/day. Weekends run at 30%. Sends are spread between 09:00 and 18:00 in the mailbox’s own time zone, with randomness every 15 minutes. A pair never writes to each other twice within 3 hours. Peers on a different domain or provider are picked twice as often.

About 40% of received BobWork warm-up mail gets a reply. Threads end after 3 messages. Content is plain text, with no links and no images. That is deliberate. Warm-up should look like ordinary office conversation, not marketing.

Use Apollo for what it does better when you need it: contact data, sequences, and campaign execution. Use standalone warm-up for preparation, mailbox coverage, and independent DNS and spam-placement checks. BobWork’s exact engine behaviour is published, so you can set caps instead of guessing.

What limits should you set?

Start with DNS, not volume. SPF, DKIM, and DMARC should pass before you warm or send.

Google’s sender guidelines require authenticated mail for bulk senders and set clear spam complaint expectations. Yahoo’s sender best practices require SPF and DKIM, DMARC at least p=none, alignment with SPF or DKIM, one-click unsubscribe for bulk mail, and unsubscribes honoured within 2 days.

Microsoft’s consumer mailbox requirements for domains over 5,000 emails/day include SPF pass, DKIM pass, and DMARC at least p=none with alignment.

Use primary documentation when you check requirements:

• Google Email Sender Guidelines
• Yahoo Sender Best Practices
• Microsoft email authentication guidance

Then set mailbox limits.

For BobWork, a mailbox is “ready for outbound” after 7+ days warming, a 7-day spam rate of 10% or lower, and at least 30 warm-up emails received. Health score is 0–100: Healthy is 85 or above, Watch is 60–84, At risk is below 60, and Blocked means login or permission failed.

BobWork’s spam rate is the share of a sender’s warm-up mail that receiving mailboxes found in Spam over 7 days. It is measured directly inside receiving mailboxes, not through third-party seed lists.

During campaigns, keep warm-up running at a moderate level. BobWork’s published practice is 10–15 warm-up emails/day during campaigns. If a mailbox rises above 5% spam rate, pause it for a few days. If you need more daily cold email volume, add mailboxes instead of pushing one mailbox harder.

For campaign planning, read the 4-step cold email sequence template and the guide to warming up while sending cold email. If DNS is still uncertain, use the SPF, DKIM, and DMARC checklist before touching campaign volume.

What should you do now?

Use this checklist before you run Apollo warm-up and a standalone pool at the same time.

The safe setup is usually simple. One mailbox can live fully inside Apollo if Apollo is already your outreach workspace. Several mailboxes should be warmed, checked, and capped in a separate operating layer before campaigns start.

If you want that layer without another monthly subscription, use BobWork Email Warm-up. It is free for up to 10 mailboxes, uses a shared warm-up network by default, lets you switch to a private pool per account, and keeps warm-up running while you prepare the rest of your cold email system. It is not a replacement for Apollo’s database or sequences. It is the warm-up control panel for mailbox readiness.

Frequently asked questions