Inboxes for Apollo

Apollo is where a lot of teams start cold email, because the data and the sequencer are in one place and the first sequence can go out the same afternoon from the Google account you already have. That convenience is the problem. The account you already have is on your company domain, and cold email generates the signals no company domain should carry: bounces from an unverified list, the occasional complaint, a hundred strangers deleting unread. Receivers file those against the domain, and the domain is the one your invoices, your support replies and your contracts go out on.

The fix is not a different sequencer. It is separate sending domains with their own mailboxes, connected to Apollo as additional senders, so that a bad week in outbound stays in outbound. That is what we build, and this page is about connecting it to Apollo and running it at a pace that lasts. We sell the mailboxes, not Apollo, and this is not a review of it.

Register variants of the brand on .com, forward them to the real site so a prospect who types one in lands somewhere, and put two or three mailboxes on each. The infrastructure guide is the full setup; our prewarmed orders arrive with the domain included, forwarded and authenticated.

• Real mailboxes, your admin. Every inbox we deliver is an official Google Workspace, Microsoft 365 or Azure mailbox with you as admin. Apollo connects to it the way it connects to any business mailbox.
• Authentication already published. SPF, DKIM, DMARC and forwarding are configured before handover. Confirm it with the authentication checker; a minute now against a quiet campaign later.
• The list verified. Apollo’s verified flag is a database fact, not a send-time one. Read whether to re-verify before the first send from a new mailbox, because bounces are the signal that burns fastest.
• Two-factor decided. Disable 2FA on the receiving account before delivery day, or keep it on and grant restricted sub-account access to [email protected]. Orders where neither has happened take longer than 48 to 72 hours.

Written as what you are doing rather than as a click path, because Apollo’s menus move and a page full of yesterday’s button labels makes everything around it look stale.

1. 1Add each mailbox as an additional sender, by provider. The Google path for Google Workspace mailboxes, the Microsoft path for Microsoft 365 and Azure, authorising over OAuth. No password stored, nothing breaks when one is rotated.
2. 2If you use IMAP/SMTP on Microsoft, enable SMTP AUTH first. Authenticated SMTP is off by default on recent Microsoft tenants, at the tenant and per mailbox, and it fails looking exactly like a wrong password. OAuth avoids the question.
3. 3Set the daily limit per mailbox. Apollo lets you cap sends per mailbox per day. Set it to the figure for the platform below, before the first sequence, and treat it as policy.
4. 4Assign the sequences to the new senders, not the company account. The step that actually moves cold volume off the main domain. Check which mailbox each live sequence is sending from; the default is usually the one you signed up with.
5. 5Display name and signature, one pass across the fleet. A first cold email with no display name and a bare signature is advertising exactly that. One line of signature, no links in it.

Apollo’s database makes it easy to build a list far bigger than the fleet can send to at a sane pace, and the temptation is to raise the cap rather than add mailboxes. Size the fleet for the volume with the calculator, and if the list is bigger than the fleet, the list waits.

Prewarmed inboxes arrive with sender history; fresh inboxes are warmed by us for 14 to 21 days before handover. Our warmup then keeps running at 30 emails per inbox per day underneath your campaigns for as long as you hold the inboxes. A second warmup from the sequencer is more mail from the same mailbox against the same daily budget, so leave it off, or count it inside the cap.

One sender’s reply rate falling while the rest hold, bounces climbing on one domain: pause that mailbox in Apollo so the sequence reroutes, check the domain with the blacklist checker, run the bounce analyzer on its bounces to tell the list from the domain, and message us on WhatsApp at +1 904 736 2539. Replacement inboxes are part of the package when deliverability drops, and keeping a few spare senders is what makes a flagged mailbox an inconvenience rather than a paused sequence.

Prewarmed inboxes include a free prewarmed .COM or .CO domain and send from the day they land: $8.00 per inbox per month on Google and Microsoft, $7.00 on a two-month commit, $6.00 quarterly. Azure is billed per tenant, $69 monthly, $60 on two months, $50 quarterly, with up to 100 inboxes on one domain, which at capacity is $0.69, $0.60 and $0.50 per inbox. Fresh inboxes on your own branded domains, warmed for 14 to 21 days first, run $3.50 to $2.00 per inbox per month on Google, $3.00 to $2.00 on Microsoft 365, and $50 flat for an Azure tenant. Every price is at /price.md, and how it works covers everything between paying and the first send.

Can I send Apollo sequences from my main company email?

You can, and it is the most common way a company domain gets burned. Cold outreach collects bounces, complaints and unsubscribes that your invoices, support replies and contracts then share a reputation with. Send from separate domains and mailboxes built for cold email, connected to Apollo as additional senders, and keep the company domain for the conversations that follow.

Do you load the inboxes into Apollo for me?

Apollo is not one of the sequencers our portal exports into directly (those are Instantly, Smartlead, PlusVibe and EmailBison). You get full admin on every mailbox and the credentials to connect them yourself through Apollo’s Google or Microsoft path, and if you would rather we did it by hand, ask on WhatsApp and we will.

What daily limit should each mailbox have in Apollo?

Fifteen a day on Google Workspace, eight on Microsoft 365, two on a full Azure tenant of 100. Apollo lets you set a per-mailbox daily limit; set it there and leave it. The number that matters is the one a mailbox holds for months, not the one it survives for a fortnight.

Are Apollo’s verified emails safe to send to as-is?

Treat database verification as a starting point, not a send-time guarantee. Our article on Apollo verified emails covers why a database’s verified flag and an address’s validity today diverge, and when a second verifier pays for itself. Bounces are the loudest signal a new mailbox sends, so the list is worth a second pass before the first campaign.

Do prewarmed inboxes need Apollo’s warmup?

No. Prewarmed inboxes arrive with sender history and our warmup keeps running at 30 emails per inbox per day underneath your campaigns for as long as you hold them. A second warmup is more mail from the same mailbox against the same daily budget; leave it off, or count it inside the cap.

How fast do the mailboxes arrive?

Within 48 to 72 hours of payment, prewarmed and fresh alike, with SPF, DKIM, DMARC and forwarding configured before you log in. Prewarmed means no warmup wait once they land, not that they are delivered the same day.