Apollo deliverability settings: the checklist
By Teodora Rafailović · 9 min read
WORKSHOP

If you already send from Apollo, or you’re about to, most of what decides whether your emails land is set before you write a word. It sits in a handful of settings screens. Some settings are fine where they start. Others start somewhere different from how we run, and those are worth setting before your first sequence goes live.
This is that list, screen by screen: where each setting lives, what it starts at, and what we set it to. Every path and value below was checked in the Apollo app on 20 November 2026, and the warmup details against Apollo’s help centre the same day. Apollo moves things around, so if a path doesn’t match your screen, search the settings menu for the setting’s name.
Why the settings matter more than the copy at the start
A new mailbox has no sending history, so mailbox providers judge it on how it behaves in its first weeks. Too much volume too soon, bounces, or a missing DNS record in that window does damage that takes weeks to repair, and no subject line fixes it.
Apollo gives you a fast way to see where you stand. Go to Settings > Outbound > Domains & Mailboxes, click Mailboxes only, and click See details in the Setup column. The guided setup lists six items: email warmup, signature, sending limits, opt-out link, tracking subdomain, and domain authentication, each marked done or to fix. On our account, three of the six needed fixing. The sections below go through the ones that matter most.
Mailbox settings
Everything in this section lives on the mailbox itself, so you set it once per mailbox. Four things matter: the domain it sends from, warmup, the daily limit, and the hourly limit with its delay.
The sending domain
Send cold email from a separate domain, never your company’s main one. If a sending domain gets into trouble, you replace it. If your main domain gets into trouble, everything else your company sends from it is affected too. Apollo’s own Diagnostics page says the same: send from a secondary domain to protect your primary domain’s reputation.
In Domains & Mailboxes, the Domains first view lists every domain with a Redirect URL column. Point each sending domain at your real website, so a prospect who types it in lands somewhere they recognise. If you need domains, Apollo can buy them for you under Get a new domain, or you can set them up with a mailbox provider. Our sending infrastructure guide covers how many to buy.
Warmup
Warmup sends and replies to emails between your mailbox and a private network of inboxes, so providers see normal traffic before they see cold email. In Apollo it’s off until you turn it on: in Mailboxes only, toggle Start warm up beside the mailbox.
You’ll choose a mode, an end date, and daily volumes. Apollo recommends Progressive, at least two weeks, and 10 to 40 warmup emails a day.
We run warmup for 14 days at the minimum and 21 when we can, before any cold email goes out. Then we leave it on, for as long as the mailbox sends. Apollo’s warmup runs until an end date you set, so when the first run finishes, we start a second one at a steady 15 to 20 a day.
The daily limit, the hourly limit, and the delay
Each mailbox carries three numbers. Open them from the mailbox’s actions menu (…) > Configure mailbox > Sending limits. Apollo recommends 50 emails a day, six an hour, and 600 seconds between emails, and that’s what a new mailbox starts at.
Keep the hourly limit and the delay as they are. The daily limit is where we differ. Ours is 25 a day, because we send cold email from new domains set up only for outbound, and a new domain needs careful handling while it builds its sending reputation. A new mailbox starts at five a day and rises in weekly steps to 25.
Two things to know about how the limit behaves:
It’s a rolling 24 hours, not a calendar day. Capacity comes back gradually as each send passes the 24-hour mark, and emails over the limit stay scheduled until then.
A limit left at its starting value makes a healthy sequence send almost nothing. If you ramp by hand, set a weekly reminder to raise it.
Read the limit from the mailbox’s own settings, not from a report. On our account, an analytics figure showed 775 for a mailbox that was really set to 25.
Domain authentication
SPF, DKIM, and DMARC tell mailbox providers that your mailboxes are allowed to send for your domain. You set them at your DNS host, not in Apollo, but Apollo shows you whether they pass.
There are two places to look:
Settings > Outbound > Domains & Mailboxes, Domains first: the Email authentication health column gives one verdict per domain.
Sequences > Diagnostics > Domain setup: SPF, DKIM, and DMARC listed separately for each domain and mailbox.
Anything other than a pass on all three is a fix before the first send. Check it again whenever you add a domain, and after any change at your DNS host.
Sequence settings
These settings apply across sequences, not to one mailbox. Most are under Settings > Outbound > Sequences and Settings > Outbound > Sending policies. Four of them matter here.
The schedule
The schedule decides which days and hours a sequence sends. Find it in Settings > Outbound > Sequences > Schedules. Apollo’s default, Normal Business Hours, sends Monday to Friday from 8am to 5pm Pacific, with “use the contact’s local time zone” turned on and US holidays skipped.
We send 9am to 6pm in the prospect’s time zone, on weekdays. So we edit the hours and leave the contact’s time zone option on. Any sequence without its own schedule uses the default, so change the default rather than relying on each sequence.
Bounce Guard
Bounce Guard pauses sequences when the bounce rate gets too high. It’s in Settings > Outbound > Sending policies, it’s account-wide, and it was on when we checked. It starts at a 4% warning and a 6% auto-pause, measured over the past seven days.
We set the warning to 3%, the lowest Apollo accepted when we set it, and the auto-pause to 4%. Our target is a bounce rate under 2%.
The setting to understand is minimum volume: 200 emails. The guard doesn’t evaluate a sequence until it has sent that many in the seven-day window. Apollo lets you lower it to 50, but we keep it at 200: on a small sample, two bounces in 50 is already 4%, and the guard would pause on noise.
So a sequence that sends fewer than 200 emails a week isn’t covered, and one mailbox at 25 a day sends 125. Until yours passes 200, verify the list before it goes in and check the bounces by hand.
Two more settings sit close to Bounce Guard:
Catch-all domain protection, at the top of Sending policies, filters risky catch-all addresses before they’re sent. Leave it on.
Ignore email bounce protection in Sequences, at the bottom of the Default ruleset (Settings > Outbound > Sequences > Sequence rulesets > Default). Leave it off.
The daily cap per ruleset
The same ruleset page has a field called “Maximum # of emails to send per 24-hour rolling period”. It was empty on our account, so a sequence sends as much as its mailboxes allow.
Use it when you want one group of sequences to send less than the mailboxes could, for example a test running beside a live campaign on the same mailboxes. The mailbox limit is still the ceiling.
Skipping unverified emails
Apollo can refuse to enroll contacts whose email isn’t verified. It’s in Settings > Outbound > Sequences > Enrollment criteria, as “Skip contacts whose email is not verified”, and it was off on our account.
We turn it on. Every address we send to is verified first, and this stops an unverified one from slipping in through a list someone else built. Apollo checks once, when the contact is added. Apollo’s verified status is a good first filter, and we still run our own check on top of it, for the reasons in Apollo verified emails and catch-all, explained.
Tracking and the unsubscribe link
These four settings are in Settings > Personal > Profile > Email settings. Because they’re under Personal, each person sending from Apollo should check their own. All four were off on our account.
Setting | What we set |
|---|---|
Enable open tracking | Off |
Enable click tracking | Off |
Include an opt-out message in sequence emails | On, before the first contact is enrolled |
Include one-click unsubscribe | Apollo recommends it for teams sending 5,000 or more emails a day |
We keep open and click tracking off and send plain text: no images, no HTML formatting, and no links apart from the opt-out.
The opt-out message turns any text you wrap in <% and %> into an unsubscribe link, for example <%Unsubscribe here%>. Your default ruleset finishes a contact in the sequence when they unsubscribe, and that trigger only works with opt-out links on.
You can also end every email with one plain sentence, along the lines of “If this isn’t relevant, let me know and I won’t reach out again.” It reads more naturally than a link, but it only works if every reply is read and acted on: set the contact’s stage to Do Not Contact, which your Default ruleset marks as Not Sent.
The checklist
Here is everything above in one table.
Setting | Where in Apollo | What we set |
|---|---|---|
Sending domain | Domains & Mailboxes | A separate domain for cold email |
Redirect | Domains & Mailboxes, Domains first | Each sending domain redirects to the main site |
Warmup | Domains & Mailboxes, Mailboxes only | On, 14 days minimum and 21 optimal before any send, then kept on |
Daily limit | Configure mailbox > Sending limits | 25, reached in steps |
Hourly limit | Configure mailbox > Sending limits | Six |
Delay between emails | Configure mailbox > Sending limits | 600 seconds |
SPF, DKIM, and DMARC | Domains first, and Sequences > Diagnostics | Passing on every sending domain |
Schedule | Sequences > Schedules | 9am to 6pm, contact’s time zone on, weekdays |
Bounce Guard | Sending policies | On, warning 3%, pause 4% |
Bounce Guard minimum volume | Sending policies | 200 |
Catch-all protection | Sending policies | On |
Ignore bounce protection | Sequence rulesets > Default | Off |
Daily cap per ruleset | Sequence rulesets > Default | Set only to hold a group of sequences below the mailbox limit |
Skip unverified emails | Sequences > Enrollment criteria | On |
Open and click tracking | Personal > Profile > Email settings | Off |
Opt-out message | Personal > Profile > Email settings | On, before the first contact is enrolled |
Once it’s set, the Overview tab under Settings > Outbound is the weekly check. It shows today’s sending capacity, anything that needs your attention, how many risky emails Apollo held back, and how many sequences it paused. For a fuller check of your sending that works in any tool, run our deliverability health check. If something looks off, what bad deliverability costs covers what to do next.
If an agent runs it for you
This section is for an AI agent working in Apollo through the MCP server or the CLI. If you set Apollo up by hand, skip it, or paste it into your agent’s instructions.
Some of these settings can be read through the API. Read what it exposes, compare it against the checklist above, list the rest as manual checks, and report. Don’t change anything.
Mailboxes:
apollo_email_accounts_indexlists each mailbox’s address. Flag any mailbox on the company’s primary domain or a free-mail domain (is_free_domain). It doesn’t return sending limits.Limits: read
email_daily_threshold,max_outbound_emails_per_hour, andseconds_delay_between_emailsfrom the CLI (apollo email-accounts list). Never use the analytics fieldemail_daily_limitas the ceiling.Schedule:
apollo_emailer_schedules_indexreturns each schedule’s hours, time zone, anduse_contacts_time_zone.Bounce Guard:
apollo_emailer_campaigns_showreturnsauto_pause_enabledandauto_pause_configfor each sequence (sequence search doesn’t). Comparemin_volumewith what the sequence really sends in seven days.A sequence that isn’t sending: start with
sending_diagnosticsonapollo_emailer_campaigns_show.Set in the app: mailbox limits, warmup, tracking, the opt-out message, Bounce Guard thresholds, and enrollment criteria. Report what needs changing and leave it to the person who owns the account.
If the owner asks you to cap one sequence: set
max_emails_per_daywithapollo_sequences_update. Build the call fromapollo_emailer_campaigns_show: send back every step and touch with their ids, because the update deletes any you leave out, and pass the sequence’s currentactivevalue, because passingtruestarts sending. This leaves the mailbox limit untouched.
Set it once, check it weekly
The settings that cause the damage are the ones nobody opened, so open each one before your first enrollment and check the Overview tab every week after that.
For the rest of the account, run the Apollo account audit, and if you’re starting from zero, the Apollo.io setup guide goes in order. More on sending in the deliverability hub. If you’d rather we set it up on your account, that’s what Apollo Managed and our audit and 14-day trial are for.

Teodora is a GTM Manager at Creatop, where she designs and runs outbound campaigns for clients. She specializes in highly personalized sequences written with AI models.
We run outbound for B2B companies and build the system underneath it, which you own. First campaigns live in two weeks.
LATEST
FEATURED







