Loading tutorials…
Loading tutorials…
Apollo Meetings replaces Calendly. Dialer replaces Aircall for outbound calling. Used together they collapse 3 tools into 1 — but only if the configuration is correct. This walks setup, round-robin, recording compliance, and CRM sync.
Who this is forSales teams using Apollo for outbound who want to consolidate calendar booking and phone dialing into the Apollo stack. Especially relevant if you currently pay $30+/seat/month for Calendly + Aircall.
What you'll need
Step 1
Apollo → Settings → Calendar Settings → Connect Calendar. OAuth-connect Google Calendar or Microsoft 365 Calendar. Same flow as inbox.
Open Apollo → top right gear → "Calendar Settings."
Click "Connect Calendar." Choose Google or Microsoft. OAuth permission flow.
After connection, Apollo can read your availability (busy times) and write events to your calendar.
Each user connects their own calendar. For round-robin Meetings (covered in step 4), all participating reps must connect their calendars.
Set your default working hours: Calendar Settings → "Available Hours." 9am-5pm in your local time zone is standard. Define per-day if you do not work Fridays or want different hours different days.
Set buffer time: 5-10 min between meetings is standard. Buffers prevent back-to-back booking that leaves no prep time.
Step 2
Apollo → Meetings → New Meeting Type. Set name, duration, location (Zoom/Google Meet/phone), questions, redirect URL.
Open Apollo → top nav → "Engage" → "Meetings" → "Create Meeting Type."
Name the meeting type by purpose: "Discovery Call — 30 min," "Demo — 45 min," "Quick Intro — 15 min." Avoid generic ("Call with John") names.
Duration: 15 min for qualification calls, 30 min for discovery, 45-60 min for demos. Shorter is better for cold inbound (lower friction to book).
Location: integrate Zoom or Google Meet for automatic conferencing link. Apollo creates the meeting URL and embeds it in the calendar invite + confirmation email.
Custom questions: ask 1-2 qualifying questions on the booking form (Company size? Current solution? Timeline?). Each additional question drops booking rate 10-15% — use sparingly.
Redirect URL: after booking, redirect to a thank-you page or content page. Track conversions via UTM parameters on the redirect URL.
Confirmation email: customize the auto-sent confirmation with calendar invite, location/link, prep materials. Apollo defaults to a basic template — replace with branded copy.
Step 3
Meetings → New → Round Robin. Add 2-5 reps. Apollo distributes bookings by availability + load balance.
For team booking: create a Round Robin Meeting Type. Apollo → Meetings → "New" → "Round Robin."
Add team members. Each must have calendar connected (step 1).
Distribution algorithm: choose "Pure Round Robin" (rotate by booking order), "Load Balanced" (rep with fewest meetings this period gets the booking), or "Priority" (Apollo prefers specific reps when available).
Set fallback: if no rep available in the prospect's preferred slot, Apollo can show next available with any rep OR show "no availability." Pick based on whether routing the right rep matters more than booking the meeting.
Buffer + working hours apply per-rep. If Rep A works 9-5 PST and Rep B works 9-5 EST, round-robin shows the union — but books the appropriate rep based on local availability.
Test with your own browser in incognito: open the booking link, walk through booking, verify the right rep gets the booking and calendar event.
Step 4
Apollo → Settings → Dialer → Buy Number OR Bring Your Own. Purchase Dialer Minutes pack. Configure local presence numbers per state.
Apollo Dialer requires the Organization plan ($149+/seat/mo) or a Dialer add-on.
Open Apollo → Settings → "Dialer Settings."
Buy a phone number: Apollo lets you purchase a US or international number through Twilio (Apollo's underlying provider) for ~$2-5/month per number.
Buy Dialer Minutes: outbound calls consume per-minute credits. US outbound: $0.02-0.05/min. Buy in packs ($50-500). Set monthly auto-recharge.
For local presence (caller ID matching prospect area code): purchase a number per state/region you call into. 5-10 local numbers = ~$25-50/month. Local presence boosts pickup rate 30-50%.
Bring Your Own Number: if you already have a Twilio, RingCentral, or Aircall number, integrate via Apollo → Settings → Dialer → BYO Number. Saves the per-month number cost; minute costs still apply.
Step 5
Dialer → Recording Settings. Set per-state recording rules. Enable announcement ("This call may be recorded") for two-party consent states.
Open Apollo → Settings → Dialer → "Recording Settings."
Two-party consent states (CA, CT, FL, IL, MA, MD, MI, MT, NV, NH, PA, WA): legally required to inform the called party AND obtain their consent before recording.
One-party consent (most other US states + federal): only the rep needs to consent. Default in most states.
Enable automatic announcement: when recording, Apollo plays "This call may be recorded for quality and training" at call start. Required for two-party states.
Recording storage: Apollo stores recordings indefinitely on Organization plan. Recordings linked to the call activity in the contact record.
EU/UK/Canada: GDPR + PIPEDA + UK Data Protection require explicit consent. Cold-call recording in EU is high legal risk; consult counsel before enabling for EU prospects.
For safety: enable recording for inbound only, OR for outbound only after manual consent. Disable automatic recording on cold outbound calls.
Step 6
Apollo → Settings → CRM Integrations. Map meeting bookings → CRM activities, call logs → CRM tasks, recordings → CRM notes.
Open Apollo → Settings → "CRM Integrations." Connect HubSpot, Salesforce, Pipedrive, or Zoho.
Map meeting bookings: when a prospect books via Apollo Meetings, create a Meeting activity in CRM. Includes meeting type, time, link, rep, prospect.
Map call logs: when a rep makes a Dialer call, create a Call task in CRM. Map outcome (Connected/Voicemail/No Answer/Wrong Number) to CRM-native disposition values.
Map call recordings: Apollo can attach recording URL to the CRM call task. Recordings remain hosted in Apollo; CRM stores the link.
Map meeting outcomes back: after a booked meeting completes, Apollo can ask the rep to log outcome (Showed / No-show / Rescheduled). Outcome flows back to CRM.
Verify the sync end-to-end: book a test meeting, make a test call, check CRM 5 minutes later. Both should appear with correct contact, rep, and notes.
Step 7
Daily: rep reviews dialer queue. Weekly: manager reviews booking conversion rate, no-show rate. Monthly: audit per-rep dialer minutes usage.
Daily rep workflow: open Apollo → "Engage" → check dialer queue (contacts ready to call). Make calls. Log outcomes. Sync to CRM automatic.
Daily rep workflow: check Meetings dashboard for upcoming bookings. Confirm prep time. Add prep notes to Apollo contact record.
Weekly manager review: Apollo → Analytics → Meetings → Booking Conversion Rate (% of meeting-link clicks that result in booking). Target 30-50%. Below = booking flow is broken (too many questions, wrong duration).
Weekly manager review: Apollo → Analytics → Meetings → No-Show Rate. Target under 20%. Above = qualification or reminder cadence problem.
Monthly review: Dialer Minutes usage per rep. Top reps usually use 800-1,500 minutes/month. Reps using under 300 may be avoiding calling — coach.
Quarterly: review Local Presence number ROI. Numbers with under 10 calls/month should be released to save $2-5/month each.
Common mistakes
Running Calendly and Apollo Meetings in parallel
What goes wrong: Prospects see two booking links from your team. Reps get double-booked because Apollo cannot see Calendly bookings (and vice versa). Lost deals from double-booking; rep frustration; $400-1,200/year wasted on duplicate Calendly subscriptions.
How to avoid: Pick one. Apollo Meetings is sufficient for 80% of teams. Keep Calendly only if you need its routing-form features for high-volume inbound. If keeping both, sync via shared Google Calendar — Apollo reads from there.
Recording cold calls in two-party consent states without announcement
What goes wrong: California Penal Code 632 violation: $2,500 fine per call + civil liability. A single complaint from a recorded CA prospect can trigger a class action. Real cases have settled $50K-500K against B2B sales teams.
How to avoid: Enable Apollo Dialer recording announcement globally. OR disable automatic recording on outbound cold calls; only record after explicit verbal consent.
15+ minute meetings with 5+ qualifying questions
What goes wrong: Booking conversion rate drops below 20%. Prospects abandon the form. You optimized for "qualified meetings" and got fewer meetings, period.
How to avoid: For cold-inbound bookings: 15-min meetings, 1-2 questions max. Get the meeting first; qualify on the call. Apollo Meetings supports this; many teams over-engineer the form.
No local presence numbers for Dialer
What goes wrong: All outbound calls show your home-state caller ID. Prospects in other states see "out-of-state number" and let it go to voicemail. Pickup rate 5-15% vs 20-40% with local presence.
How to avoid: Buy 5-10 local presence numbers covering your top calling regions. $25-50/month. Apollo auto-picks the matching local number per call.
No CRM sync for Dialer activity
What goes wrong: Reps make 50 calls/day. Zero land in CRM because sync was not configured. Sales manager cannot see call activity. Performance reviews use Apollo data; pipeline forecasts use CRM data. Numbers do not match; reps blamed unfairly.
How to avoid: Configure CRM Integration on day 1. Map call activity, call outcome, and recording URL. Test end-to-end before scaling.
No no-show reminder cadence
What goes wrong: Booked meeting no-show rate climbs to 35-50%. Reps waste prep time on meetings that do not happen. Pipeline forecast is inflated by ghost meetings.
How to avoid: Apollo Meetings auto-sends reminder 24 hours and 1 hour before. Verify both are enabled in Meeting Type settings → Notifications. For high-value meetings, add a manual touch (rep sends a personal "looking forward" email morning-of).
Recap
Done — what's next
How to set up an Apollo.io account the right way
Read the next tutorial
Hand it off
Apollo Meetings and Dialer can replace Calendly + Aircall, saving $30-60/seat/month. But the configuration (round-robin, recording compliance, CRM sync, local presence) takes 4-8 hours to set up correctly. A demand generation specialist will consolidate the stack in one afternoon. Compare to running parallel tools for 6 months because nobody finished the migration.
See specialist rates
Apollo Meetings for 80% of B2B teams. It is included in Pro plan, integrates natively with sequences (one click to send booking link in sequence step), and syncs to CRM via the same Apollo integration. Calendly wins only if you need its routing-form features (route by company size, lead score, etc.) for high-volume inbound.
Apollo Dialer is per-minute pricing (cheaper for under 2,000 min/month). Aircall and RingCentral are per-seat ($30-50/month per rep). For low-volume outbound (under 500 calls/month per rep), Apollo Dialer is cheaper. For high-volume teams that also need inbound, full PBX, and call center features, Aircall/RingCentral are better.
Configurable per Dialer settings. Default is OFF for new accounts (safest). Turn ON manually after legal review of states/countries you call into. Always enable the recording announcement if recording in two-party consent states (CA, FL, MA, etc.).
Start with 5 covering your top calling regions. If 80% of your calls are to CA, NY, TX, FL, IL — buy those 5 local presence numbers. Add more as you expand. Beyond 15 numbers, the per-number cost outweighs the pickup-rate lift.
You cannot redirect a Calendly URL (different domain). Best migration: replace Calendly links across your site/sequences/email signatures with Apollo Meetings links over a 2-week window. Keep Calendly active during the transition; cancel after 30 days of confirmed no traffic.
Apollo.io
Apollo has the cheapest entry into B2B sales intelligence, but the default account configuration will silently torch your domain reputation. This walks the exact setup order that keeps your inbox warm and your credits efficient.
Apollo.io
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.
Apollo.io
Apollo + CRM is where most B2B teams shoot themselves in the foot. Wrong sync direction, missing dedup, mapping mistakes — and within 30 days your CRM has 4,000 duplicate contacts. This walks the safe integration order.
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.