Loading tutorials…
Loading tutorials…
Sequences are where Apollo earns its $99/seat. They are also where most operators destroy their sender reputation. This walks the right step structure, cadence, personalization layer, and reply handling that books meetings without burning inboxes.
Who this is forBDRs, founders, and demand-gen leads launching their first Apollo sequence — or fixing one that is generating sends but no meetings. If your reply rate is below 2% you may need tutorial 8 first.
What you'll need
Step 1
Pick 4-7 steps over 14-21 days. Mix channels (email, LinkedIn touch, call). Define the goal for each step (open vs reply vs meeting book).
Sequence length: 4-7 steps is the sweet spot for cold outbound. Under 4 = not enough touches to break through. Over 7 = harassment pattern that destroys reply rates.
Cadence: 3-5 days between email steps. Day 1 (initial), Day 4 (follow-up), Day 9 (value-add), Day 14 (different angle), Day 21 (breakup).
Multi-channel: insert manual LinkedIn connect/view tasks between emails. The platform context shift (email → LinkedIn → email) increases response by 20-30%. Apollo supports both auto-send email steps and manual task steps.
Per-step goal: Step 1 = get opened. Step 2 = reframe value. Step 3 = give a free resource. Step 4 = change angle (different pain point). Step 5 = breakup ('OK to close the loop?'). Each step has a single conversion goal.
Decide reply handling upfront: When a contact replies, do they (a) exit the sequence entirely (default), (b) move to a different sequence, (c) get assigned to a rep? Apollo handles all three via Sequence Settings → "On Reply."
Step 2
Apollo → Sequences → New Sequence. Pick sending inbox(es), schedule, audience source. Add steps one at a time.
Open Apollo → top nav → "Engage" → "Sequences" → "Create New Sequence."
Name the sequence by persona + offer: "B2B SaaS Marketing Leaders — Demo Q2." Avoid generic names like "Outbound 2026."
Select sending inboxes: under "Sender Settings," choose which connected inboxes will send. For multi-inbox sequences, Apollo round-robins automatically — 50/50 across 2 inboxes, 33/33/33 across 3, etc.
Schedule: under "Schedule," set sending window. Default 8am-5pm in recipient time zone is correct for B2B. NEVER send outside business hours (lower opens, higher spam reports).
Audience: link to a saved People search OR upload a CSV. Linked saved searches auto-add new matches as Apollo refreshes data.
Add steps one at a time. Each step: Step Type (Auto Email or Manual Task), Delay (days from previous step), Subject, Body, Reply Handling.
Step 3
Step 1 is the only step recipients read fresh. Subject under 6 words, opening line that proves you researched, value prop in 2 sentences, soft CTA.
Subject line: 3-6 words, lowercase, no spam triggers (no "FREE," "GUARANTEED," "urgent"). Examples: "quick question, Sarah," "noticed [Acme] is hiring," "your thoughts on demand gen."
Opening line: prove you researched. Reference something specific — a recent LinkedIn post, a job posting, a funding announcement. NEVER 'Hope this finds you well.' Recipients delete in under 3 seconds when they see template openers.
Body: 2 sentences max. State a pain point you know they have based on the research. State your value prop in their language.
CTA: soft. NOT 'Can I book a 30-min demo?' YES 'Worth a 15-min chat to compare notes?' or 'Want me to send the case study?' Lower the commitment for the first ask.
Length total: under 75 words. Mobile preview shows only the first 100-150 chars. If the value prop is buried below the fold, it does not exist.
Personalization tokens: Apollo supports {{first_name}}, {{company_name}}, {{title}}, plus custom fields. Use 1-2 max per email. Stacking 4+ tokens reads robotic.
Step 4
Apollo → step → "Add Variant." Run 2-3 variants per step to learn what works. Apollo splits sends evenly and reports reply rate per variant.
In the sequence editor, click "+ Add Variant" on each step. Apollo allows up to 5 variants per step.
Test ONE variable per A/B: subject line OR opening line OR CTA. Changing 3 things at once produces no learning.
Variant A vs Variant B examples for Step 1: (A) 'quick question, Sarah' subject vs (B) '15 sec read, Sarah' subject. Or (A) curiosity-led opening line vs (B) data-led opening.
Apollo splits sends 50/50 between variants. After 200+ sends per variant, the reply rate column shows the winner with statistical significance.
Promote the winning variant: pause the loser, send 100% to the winner, then start a new A/B test on a different element. Run 2-3 test cycles per sequence (4-6 weeks of testing) to optimize meaningfully.
Step 5
Sequence Settings → "When contact replies." Options: pause contact (default), pause all in account, advance to next sequence, notify rep.
Open Sequence Settings → 'Reply Handling.'
Default behavior: when a contact replies, Apollo pauses them in the current sequence (good — prevents the next step landing after they responded).
Better behavior: enable 'Pause all contacts at this account when one replies.' If one person at Acme replies, do not keep emailing 5 other people at Acme — collision and embarrassment risk.
Auto-handoff: enable 'Notify sequence owner via Slack/email' so reps see replies in real time. Email replies sitting unanswered for 4+ hours convert 50-70% lower.
Negative replies: Apollo's reply detection auto-classifies replies as Positive / Negative / Neutral / Out of Office. Out-of-office is delayed (not bounced). Negative ('not interested') exits and adds to suppression. Positive triggers rep notification.
Bounce handling: bounced emails auto-exit AND auto-add to your suppression list. Verify this is ON under Sequence Settings → Bounce Handling.
Step 6
Sequence Settings → "Daily send limit." For new sequences on new inboxes, start at 25 contacts/day enrolled. Ramp 10/day per week.
In Sequence Settings → 'Daily send limit per inbox.' Apollo's default is 200. For new inboxes, this is a domain-destruction event.
Week 1: 25 contacts enrolled/day per inbox. Week 2: 35/day. Week 3: 50/day. Week 4-6: 75-100/day. Hold at 100-150/day per warm inbox indefinitely. Never exceed 200/day per inbox, ever.
Multi-inbox capacity: if you have 5 connected inboxes at 100/day each, your real daily send capacity is 500/day enrolled — not '500 emails sent' (each contact gets 4-7 emails over the sequence lifetime, not all at once).
Stagger sequence launches: do not enroll 1,000 contacts on a Monday morning. Spread across 7-10 days to keep inbox sending patterns natural.
Apollo throttles automatically if it detects your inbox approaching provider limits. Trust the throttle — overriding it triggers the spam burst detection.
Step 7
Launch with 50-100 contacts. Monitor: open rate (target 30-50%), reply rate (3-5% baseline), bounce rate (under 3%), spam complaint rate (under 0.1%).
Launch with a small batch: 50-100 contacts for the first week. Treat week 1 as a controlled test, not a campaign.
Day 2-3: check Apollo Sequence dashboard → Performance tab. Open rate should be 30-50% (above 50% may be bots; below 30% is a deliverability or subject-line issue).
Day 4-7: reply rate should appear. 3-5% is baseline B2B; below 2% means copy or audience is off (see tutorial 8); above 7% is excellent.
Bounce rate: above 3% means your data has decayed (Apollo emails may be stale). Pause and re-verify in Apollo or via NeverBounce/ZeroBounce before resuming.
Spam complaint rate: anything above 0.1% is an emergency. Pause the sequence, audit the copy and audience, fix before resuming. Spam complaints permanently damage sender reputation.
After week 1: if all metrics are healthy, scale enrollment by 50-100% per week up to your daily inbox limit. If anything is unhealthy, fix before scaling.
Common mistakes
Using Apollo template library copy unedited
What goes wrong: Apollo's template library is used by tens of thousands of operators. Recipients in B2B SaaS, marketing, and sales recognize the patterns instantly and delete in under 3 seconds. Reply rates collapse below 1%. You spent Apollo credits to send the same email everyone else is sending.
How to avoid: Write from scratch. Templates are starting points for structure only. Use buyer language pulled from your actual sales calls or community discussions in your category.
200/day enrollment on new inboxes
What goes wrong: Apollo's default daily limit triggers Gmail and Outlook's spam burst detection within 3-5 days. Your inbox is silently blacklisted. The $30-60/mo inbox spend wasted; you discover via plummeting opens 7 days later.
How to avoid: Start at 25 contacts/day per fresh inbox. Ramp 10/day per week. Never exceed 200/day even on long-warmed inboxes.
Sending outside business hours
What goes wrong: Emails delivered at 2am-7am open at 40-60% lower rates than business-hour sends. Recipients wake up to a full inbox and clear by deleting. Your sequence delivered at the worst possible time.
How to avoid: Force send window 8am-5pm recipient local time. Apollo Sequence Settings → Schedule. Disable "send as soon as added."
A/B testing 3+ variables at once
What goes wrong: You change subject + opening + CTA between variants. Variant B wins by 2%. You cannot tell which change drove the lift. Three weeks of A/B testing produces no learning — you make wrong decisions for the next sequence.
How to avoid: Test ONE variable per A/B cycle. Subject in cycle 1, opening line in cycle 2, CTA in cycle 3. Wait for 200+ sends per variant before declaring winner.
No suppression on account-level reply
What goes wrong: One person at Acme replies 'not interested.' Five other Acme contacts continue receiving sequence steps. Sales-team-collision risk; reputation risk; reply rate at the account drops to negative (angry escalation replies).
How to avoid: Enable "Pause all contacts at this account when one replies" in Sequence Settings. Apollo will halt sequencing for everyone at the domain after the first reply.
No reply monitoring or rep notification
What goes wrong: Positive reply lands in the sequence sender's inbox. Sender sees it 36 hours later. By then the prospect's interest has cooled. You converted a positive reply into nothing.
How to avoid: Enable Slack notifications on reply via Apollo → Settings → Notifications → Slack integration. Set SLA: respond to positive replies within 1 hour during business hours.
Recap
Done — what's next
How to set up Apollo filters and personas for high-precision prospecting
Read the next tutorial
Hand it off
Sequence copy is the leverage point for Apollo. Good filters + bad copy = no meetings. Bad filters + good copy = wrong meetings. A demand generation specialist will write 3-5 sequences, run A/B cycles, and tune reply handling for $200-500 total upfront, plus ongoing optimization at $14-16/hr. Compare to 90 days of sub-2% reply rates and burned inbox reputation.
See specialist rates
4-7 steps over 14-21 days is the sweet spot for cold B2B outbound. Under 4 steps = not enough touches; over 7 steps = harassment pattern. Adjust for sales cycle: longer enterprise cycles can support 7-9 steps over 30 days; SMB transactional should stay at 4-5 over 14 days.
Video links (Loom): yes, in step 3 or 4 after initial value has been established. GIFs in step 1: no — they slow load, trigger spam filters, and are too casual for cold outreach. Attachments in cold email: never. Use a link to a hosted PDF instead.
Apollo can create LinkedIn tasks (manual: rep clicks to send) but does not auto-send LinkedIn DMs — LinkedIn detects and bans accounts for automated DMs. For automated LinkedIn outreach, you need a separate tool (Expandi, Dripify, Lemlist) — but at high risk to your LinkedIn account.
Apollo bundles sequences with its prospect database, so you can search → enroll in one flow. Lemlist focuses harder on personalization (image/video personalization at scale). Instantly focuses on inbox-rotation deliverability at high volume (10,000+ sends/day). Apollo is best for SMB-mid-market B2B teams under 5,000 sends/day.
Yes. The breakup email ("OK to close the loop?" or "Last note from me") consistently produces the highest reply rate of any step (often 8-15%). Many recipients are too polite to reply earlier — the breakup gives them permission. Always include as the final step.
Apollo.io
Apollo's database is 275M+ contacts — meaningless without precision filters. This walks the persona builder, Boolean title logic, and the signal filters that separate qualified prospects from credit drain.
Apollo.io
Warm-up is the boring 6-8 weeks that determines whether your Apollo investment pays back. Skip it and you torch the inbox in week 2. This walks the exact ramp schedule, the tools, and the signals that tell you the inbox is ready for real sends.
Apollo.io
Apollo's send infrastructure is fine. Your deliverability problems are 95% on your end — DNS, content, sending patterns, and reputation. This walks the full deliverability stack: authentication, monitoring, content rules, and recovery.
Apollo.io
Apollo reply rate below 2% means something is structurally wrong — and it could be any of 8 causes. This walks the diagnostic order so you fix root causes, not symptoms.
Apollo.io
DIY Apollo is a fine idea — until it isn't. This is the honest framework: when the cost of self-managing exceeds the cost of hiring, and how to tell which side you're on.