How to set up Apollo.io for B2B outbound, from mailboxes to first report
By Dimitrije Jimmy Rešetar · 7 min read
WORKSHOP

Most people buy Apollo to find leads, and Apollo makes that easy. You can search, save a list, write a sequence, and send on the first day. That is exactly the problem: nothing stops someone with no cold email experience from sending to unverified emails, from mailboxes that were never warmed, on the company’s main domain. By the time the replies dry up, the domain has already taken the damage.
This guide sets Apollo up in the order that keeps your domains alive: a separate sending stack, mailboxes properly warmed, every email verified before anyone receives it, and a launch that a person decides on. It is the same order we use when we take over an account, and it puts the slow parts first so the fast parts can run.
Before you start
You need an Apollo plan with email sequences, admin access to your company’s domain registrar, and about three weeks before the first real send. The three weeks are not padding. Warmup takes 14 days minimum and 21 is better, and nothing else can shorten it.
Step 1: build a separate sending stack
Never send cold email from your company’s main domain. It carries one reputation, and it is the one your invoices, your support desk, and your CEO’s inbox depend on. Cold email goes out on dedicated sending domains that can absorb the risk. If one degrades, you retire it, not the business’s email.
Size the stack from the volume you want, not the other way round:
The ceiling is 25 cold sends per mailbox per day. Plan below it, never above.
Two or three mailboxes per sending domain keeps each domain’s footprint small.
Worked example: 300 cold sends a day is 12 mailboxes, across four to six domains. Do not solve it with four mailboxes at 75 a day each. That burns them.
On every sending domain, set SPF, DKIM, and DMARC, point MX at your mailbox provider, and redirect the domain to your real website so a curious prospect lands somewhere legitimate.
You can buy mailboxes inside Apollo or set up your own with a mailbox provider. If you buy them in Apollo, know what they cost before you click: in unified credits, a shared mailbox is 300, Google 800, and Outlook 1,500. Three Google mailboxes is 2,400 credits, which on a 4,000-credit plan is most of a month’s enrichment budget. Mailboxes and list enrichment draw on the same pool.
Step 2: start warmup, and leave it on forever
Turn warmup on for every mailbox the day it exists. 14 days minimum, 21 optimal, before any cold send. Warmup never turns off: it keeps running beside live campaigns for as long as the mailbox sends.
While it runs, keep total volume per mailbox, warmup plus outreach, at 50 a day or less.
Step 3: turn on Bounce Guard, then tighten it
Apollo can pause a sequence automatically when bounces climb. It is account-wide and lives in the deliverability settings. Turn it on, then change the defaults, which are looser than a new domain can afford:
Setting | Apollo default | Set it to |
Warning threshold | 4% | 3% (the lowest Apollo accepts) |
Auto-pause threshold | 6% | 4% |
Minimum volume | 200 emails | 200 (fixed) |
Time range | Past 7 days | Past 7 days |
The minimum volume is the trap. Bounce Guard does not evaluate at all until a sequence has sent 200 emails inside its seven-day window. A test cohort of 20 contacts, or a slow ramp in its first days, is not protected however badly it bounces. Treat the guard as the backstop. The control is verifying the list before it goes anywhere near a sequence, which is step 5.
Step 4: set the sending schedule
Send on weekdays, inside business hours, in the prospect’s timezone. Apollo’s stock “Normal Business Hours” schedule runs 8 to 17, so if your policy is 9 to 18, change it rather than assume it. Turn on the recipient-timezone option for any list that spans more than one timezone.
One consequence catches people on launch day: a US-wide list activated at 9:00 Eastern sends to the East Coast immediately and holds the West Coast for two more hours. An empty queue right after activation is usually the schedule working, not a broken campaign.
Step 5: build the list in the order that saves credits
The expensive step in Apollo is enrichment, so everything cheap happens before it.
Search narrow, then check what came back. A filter expresses your intent; it does not guarantee the result. Read the titles and the industry mix of what the search returned before you spend a credit. The detail is in Apollo filters that inflate your TAM.
Filter to verified emails at search time. The email status filter costs nothing and removes people whose addresses would be thrown away after enrichment. In one real run it cut 3,240 people to 2,742 before a single credit moved.
Take out the people you should never email. Current customers, open deals, and anyone who has asked not to be contacted come off the list before it goes near a sequence.
Enrich, then verify 100% of what you will send to. Unverified addresses bounce, and bounces are what kill domains. Keep the bounce rate under 2%.
Step 6: write the sequence, and build it switched off
Three steps minimum, with two variations of each, and one idea per email. Keep subject lines short and lowercase, and reuse them across steps so the emails stay in one thread. Give every merge field a fallback, so a contact with no first name never receives “Hi ,”.
Apollo also has its own AI personalization. It uses credits, though the allowance is generous, and it is worth testing once the basics work. If you are new to cold email, start with templated emails instead: a template you have read and approved is far easier to fix than a thousand AI-written first lines you have not.
Build the sequence in Apollo inactive. Nothing about writing or building it should be able to send an email.
Step 7: enroll, check, then launch by hand
Enroll the verified list into the inactive sequence and check what Apollo actually did. An enrollment can show as done and still leave some contacts out, so open the sequence and compare the number of active contacts with the number you added. Then confirm four things before a human turns it on: the sender is a warmed, dedicated mailbox, the schedule is the one you meant, the copy is the approved version, and Bounce Guard is on for this sequence.
Activation is the one step that cannot be undone for anything already sent, so it is always a person’s decision.
Step 8: report on what actually happened
Start reporting from the analytics, grouped by sequence, not from the sequence list. Three traps make an Apollo report lie:
Replies are not positive replies. The reply rate includes unsubscribes and “not interested”. Report positive replies separately, as positives divided by delivered emails.
One-off emails inflate replies. Grouped by month, one account showed 30 sent and 19 replies because replies to individual emails were counted. Grouped by sequence, they drop out.
Mailboxes can cap a campaign quietly. If a campaign is “barely sending”, check each mailbox’s daily limit. A limit left at its warmup value makes everything look healthy and send almost nothing. Mailboxes multiplied by daily limit is your real ceiling.
If an agent sets it up for you
More teams now run Apollo through Claude or ChatGPT, over the API or Apollo’s MCP. An agent should do a few checks a person would never do by hand:
Drop records with no email before enriching. People search returns a has-email flag on every row. Filtering on it first took one list from 2,259 to 2,019 people and the enrichment yield to 99.7% verified.
Dedupe by person, not by row. Pages have overlapped on our pulls: a 3,238-row pull held 2,933 unique people. Enrichment charges for every row, so every duplicate is a credit spent twice.
Read the skipped contacts in the enrollment response, not just the success message.
Never activate. The agent builds the sequence inactive and enrolls; a person turns it on.
The order, on one screen
Step | What | Why it comes here |
1 | Separate sending domains and mailboxes | Protects the company’s real email |
2 | Warmup, 14 to 21 days, never off | The slow part, so it starts first |
3 | Bounce Guard at 3% and 4% | A backstop before anything can bounce |
4 | Sending schedule | Decides when anything happens |
5 | List: narrow, check, verify, remove who you should never email, then enrich | Credits are spent last, on people who survive |
6 | Sequence, built inactive | Nothing can send by accident |
7 | Enroll, check, launch by hand | The only irreversible step stays human |
8 | Report by sequence, positives over delivered | So the first number anyone sees is true |
If you inherited an account instead
Run the Apollo account audit first. It checks the same ground in 15 steps, read-only, and it finds the accounts that look live and send nothing.
Run it yourself, or have it run
Every step above is encoded in Apollo Operator, the free, open-source toolkit we built on Apollo and run on our own campaigns. If you would rather have it set up and run inside your own Apollo account, that is Apollo Managed. If you want a second pair of eyes first, the audit and 14-day trial is $1,500: we audit the account, write the next 90 days down, and spend 14 days building the system with you.
We run outbound for B2B companies and build the system underneath it, which you own. Start with a $1,500 audit and 14-day trial: we audit your setup, write a 90-day plan, and build the infrastructure, sequences, and lists with you.
LATEST
FEATURED






