Ivona MikulčićNovember 4, 20268 min readLast update: Nov 4, 2026
Apollo limitations to know before you scale your outbound
Apollo is one of the most popular places to start outbound. You get a large B2B database, filters, sequences and a dialer in the same account, plus a free plan to try it. The limits show up later, once a team tries to send more volume, add LinkedIn to the mix or keep data costs predictable.
This guide walks through the Apollo limitations that come up most often in day-to-day outbound, based on Apollo's own pricing page and help center. It covers sending caps, credits, LinkedIn steps, channels and plan gates. For a full product verdict, read our Apollo.io review. For plan prices and credit math, see our Apollo pricing breakdown.
What Apollo does well
It's worth starting with the strengths, because they explain why so many teams pick Apollo first.
A large database with deep filters. You can search people and companies by title, industry, size, technologies and more, then save a list in a few clicks.
Prospecting and sending in one place. Contacts move from search to an email sequence without a CSV in between.
A free plan. Small teams can test prospecting before asking for budget.
A Chrome extension and a dialer. Reps can pull contact data while browsing and call from the same tool.
If your outbound is mostly email to a well-covered market at moderate volume, those strengths may cover everything you need. The limitations below start to matter when you scale or add channels.
Email sending limits that cap your volume
Apollo sends sequence emails through the mailboxes you link, and each mailbox has its own daily sending limit. The limit runs on a rolling 24-hour window, and Apollo's help center recommends starting low and raising it only when engagement is good. When a mailbox reaches its limit, the remaining emails stay scheduled and go out later, so a big launch can quietly stretch over several days.
That's sensible deliverability practice. The catch is how you add capacity. The number of mailboxes you can link depends on your plan, with the entry paid plan limited to one linked mailbox per user and more mailboxes reserved for higher tiers. On the free plan, you can only send from Gmail. If you want to spread volume across several mailboxes and domains, your plan decides how far you can go.
Apollo has added warmup and mailbox tools over time. Placement testing and ongoing monitoring across providers are still areas where many teams add a separate deliverability tool, especially once several domains are involved.
Credit limits on data, exports and mobile numbers
Apollo runs on credits. Revealing emails, revealing mobile numbers and other data actions draw from a credit balance that's pooled across the team and granted at the start of each billing cycle. Apollo's pricing page states that unused credits expire at the end of each cycle and don't carry over, add-on credits included.
Three things follow in practice. Mobile reveals cost more than email reveals, so phone-heavy teams drain the pool fastest. One rep's big export leaves less for everyone else, unless an admin sets per-user caps. And because credits reset, a quiet month doesn't bank anything for a busy one.
There's also a cap on how many records you can select at once. Apollo sets record selection limits by plan, with higher tiers getting higher limits, so building very large lists can take several passes on lower plans. Our Apollo pricing breakdown shows how this plays out plan by plan.
LinkedIn steps that stay manual
Apollo sequences can include LinkedIn steps, such as viewing a profile, sending a connection request, interacting with a post or sending a message. According to Apollo's help center, these steps create tasks that a rep completes by hand on LinkedIn. Apollo sends the reminder, and the rep does the action.
For a rep working a handful of key accounts, that can be fine. At volume, it changes the math. A contact stays on a LinkedIn step until someone completes the task, skips it or the auto-skip window passes, so the rest of the sequence waits too. Apollo's documentation also warns that doing too many LinkedIn actions quickly can get your LinkedIn account temporarily restricted, which leaves the pacing to each rep.
This is the main reason teams pair Apollo with a separate LinkedIn automation tool, and then have to keep two tools and two sets of sequences in sync.
Channels Apollo sequences don't cover
Apollo's sequence steps cover automatic and manual emails, phone calls, LinkedIn tasks and generic action items. We found no native SMS or WhatsApp step in Apollo's sequence documentation. If a market expects WhatsApp, or if you use text messages to confirm meetings, that part happens outside the sequence.
Replies follow the same pattern. Email replies come back into Apollo, while a reply on LinkedIn or WhatsApp stays in that app, so the full conversation with a prospect ends up split across tools.
Plan gates on mailboxes, recording and CRM sync
Several capabilities depend on the plan. That's normal for a SaaS product, but it's worth checking before you roll Apollo out to a whole team.
Mailboxes. The number of linked mailboxes per user grows with the plan, as covered above.
Call recording. Apollo lists call recording on its higher plans.
CRM sync. Core integrations come with the entry plan, while advanced CRM integrations sit on higher tiers.
Record selection. Bigger list pulls need higher plans.
None of these is unusual on its own. Together, they mean the plan that looks right for prospecting may not be the plan you need once outreach volume and reporting needs grow.
What teams add to work around these limits
When Apollo's limits start to bite, teams usually end up adding tools like these.
A LinkedIn automation tool, because LinkedIn steps stay manual
A deliverability or warmup tool, to monitor placement across several domains
A WhatsApp or SMS tool, for markets and moments where email isn't enough
An extra data provider, when one source leaves too many contacts without a verified email or phone number
Each tool solves one gap, and each one adds a subscription, a login and a sync to maintain. The more tools you add, the harder it gets to see one prospect's full history in a single place.
How lemlist covers these gaps
lemlist was built as an outreach engine first, so the parts Apollo leaves to other tools sit inside the same campaign builder.
More sending capacity without the guesswork
You can connect several mailboxes and spread sends across them with inbox rotation. lemlist caps daily sends per inbox and pauses before you reach unsafe limits. Our recommendation is no more than 40 emails a day per email account and 120 a day across a sending domain, warmup included. lemwarm, our warmup and deliverability booster, comes with every lemlist seat, and our email warmup guide explains how to ramp a new domain.
Credits you pay for only when they find something
lemlist's Email Finder and Verifier uses waterfall enrichment, which checks several data providers in turn. You're charged only when lemlist returns a deliverable or risky email, and the phone finder only charges when it finds a number. Credits from the enrichment add-on and one-off top-ups roll over. If you already pay for Apollo data, you can also connect your Apollo account in lemlist as an enrichment provider.
To be fair, lemlist also uses a shared credit pool, and the free credits included with a plan reset every month. The difference is what you pay for. A lookup that finds nothing costs nothing, and credits you buy on top keep their value from one month to the next.
LinkedIn steps that run automatically
Profile visits, likes, follows, connection requests, skill endorsements and messages are automatic steps in a lemlist sequence, with daily limits you control. You can keep a manual step where it's worth the time, like a recorded voice note for a high-value prospect, or use AI voice messages to do the same at scale.
Email, LinkedIn, calls, SMS and WhatsApp in one sequence
On the Multichannel Expert and Enterprise plans, SMS and WhatsApp messages are sequence steps next to email, LinkedIn and calls. Conditions let the sequence branch on what happens, for example checking whether a lead has a WhatsApp account before sending and falling back to email or a call if not. Replies from every channel come back to the lemlist inbox, and intent signals can add leads to a campaign as soon as something changes at their company.
When a lead replies on any channel, you can mark them Interested or Not interested, by hand or with AI auto-marking, and the sequence stops for that lead. A prospect who answered on WhatsApp won't get your next email an hour later.
Questions to ask before you scale on Apollo
Before you roll Apollo out to a whole team, go through these questions with your current plan in front of you.
How many mailboxes can each rep link, and how many do you need to reach your daily volume safely?
How many credits does your team use in a normal month, and what happens in the month you run a big push?
Who completes LinkedIn tasks, and how many can they realistically do per day?
Which markets on your list expect WhatsApp or SMS?
Where will replies from each channel land, and who reads them?
If the answers point to extra tools, count their cost and the time spent keeping them in sync next to the Apollo plan itself.
When Apollo's limits won't matter to you
Apollo is a good fit if your team mostly needs data, sends email at moderate volume from one mailbox per rep and handles LinkedIn by hand on a few accounts. In that setup, the limits above rarely get in the way.
They start to matter when you send from several domains, want LinkedIn and email to run in one automated flow, or prospect in markets where WhatsApp and SMS are part of normal business conversations. That's the point where many teams keep Apollo for sourcing, or connect their Apollo account to lemlist, and run the outreach itself in lemlist.
Find your next outbound tool
Discover a better way to find leads and run multichannel campaigns with lemlist.