Two dialers, one record
Apollo’s own dialer is still there. We agree which calls are logged by which system, so a rep who dials from inside Apollo does not end up with the same conversation recorded twice.
Integration · Nooks to Apollo.io
Nooks and Apollo integration
Apollo has a dialer, and it calls one number at a time. Nooks calls two to five at once and only brings the rep in when a person answers. We connect them so the call tasks in your Apollo sequences feed the Nooks list, and every outcome comes back to the contact. It is a one-time setup by our team, not a monthly middleware subscription.
- From $100, one-time setup
- No monthly fees from us
- Tested on your own calls before go-live
Nooks
Apollo.io
One call ends in Nooks. In Apollo.io:
- Call task comes due in ApolloAdded to the rep’s Nooks list
- Nooks dials two to five at onceThe rep joins a live answer
- Outcome saved on the contactAnd the task is closed
- One-time setup
- From $100
- Monthly fee from us
- $0
- Working days to a written scope
- 2
- Working days to build and test
- 5–10
Got it, thank you.
Check your inbox for a confirmation. We will reply within 2 working days with what we would do and what it would cost.
Why Apollo teams add a parallel dialer
Apollo produces call tasks faster than anyone can work them. A mailbox will send up to Apollo’s default 400 emails a day, and even a cautious team starting near 50 per mailbox builds a long list of people who have seen an email and not replied. Every one of those becomes a call task, and Apollo’s dialer works through them one number at a time.
Nooks is the other half of that arithmetic. It dials between two and five prospects at once and connects the rep only when someone real picks up, so a call block can actually clear the queue. What it does not do on its own is know which Apollo task it just answered. Connecting them means the dial list is built from the sequence, the outcome closes the task, and the contact shows the call next to the emails that preceded it.
- Teams whose call tasks pile upThe backlog becomes a dial list rather than a number in the corner of the screen.
- Reps splitting time between email and phoneOne call block covers the day’s tasks, with outcomes written back automatically.
- Managers comparing channelsCalls and emails sit on the same contact, so it is clear which touch produced the meeting.
What we connect between Nooks and Apollo.io
A typical setup. We adjust each line to how your team uses Nooks and Apollo.io.
When this happensThis is what you get
A call task comes due in ApolloAdded to the Nooks list for the rep who owns the contact
A call connects to a live personA call record on the Apollo contact, with the rep and the disposition
The Nooks dispositionThe Apollo call disposition and contact stage you choose
The completed callThe Apollo task closed, so the sequence moves on
A voicemail dropped by NooksLogged on the contact as a message left, not as a conversation
A meeting booked on the callThe sequence stops for that contact, and the account is updated
Field mapping, event by event
Each Nooks event and exactly what it writes in Apollo.io. Pick an event to see its fields.
1. Trigger · Nooks
When a call ends
Every call made or received in Nooks
2. Action · Apollo.io
Log the call record
In Apollo.io, on the contact — Where your team already works
Apollo.io field
Mapped from
What happens
Activity date
Call time15 Sep, 4:00 pm
Shown in your time zone
Call time15 Sep, 4:00 pm
Shown in your time zone
Call length
Call length3 min 04 s
Stored the way Apollo.io expects
Call length3 min 04 s
Stored the way Apollo.io expects
Call outcome
Call outcomeInterested
Matched to your own list of outcomes
Call outcomeInterested
Matched to your own list of outcomes
Recording
Call recordingPlayable audio
Added once the file is ready
Call recordingPlayable audio
Added once the file is ready
Call notes
Ai summaryAsked for pricing
Saved as note text
Ai summaryAsked for pricing
Saved as note text
Owner
Rep nameMaria Lopez
Matched to the same person in Apollo.io
Rep nameMaria Lopez
Matched to the same person in Apollo.io
Contact
Matched by phone number+1 415 555 0142
A new contact is created only if none match
1. Trigger · Nooks
When an outcome is set
A rep marks how the call went
2. Action · Apollo.io
Update the account
In Apollo.io — Moves one record, not all of them
Apollo.io field
Mapped from
What happens
Which account
Most recent open accountNorthwind — 12 seats
On the matching contact, owned by the rep on the call
Stage
Call outcomeInterested
Looked up in the outcome-to-stage list we agree with you
Call outcomeInterested
Looked up in the outcome-to-stage list we agree with you
Sample values are made up. The exact fields are agreed with you in your scope.
A one-time setup, not a monthly middleware bill
We are not a middleware. We plan the connection, set it up, test it on your calls and hand it over.
Web Repay integration setup
Middleware subscription
What you pay
One-time setup, from $100 (one-off)
A monthly plan, often priced by tasks or operations
As call volume grows
The same price, no per-task charges
Costs rise with every call that syncs
Who builds and tests it
We do, on your own Nooks calls
Your team builds and maintains every step
Where it runs
In your own Nooks and Apollo.io accounts, documented
Inside the middleware vendor’s platform
When something changes
Additional support as needed, when you request it
Your team fixes the broken steps
Where a small connector layer is the most reliable route, we say so in your written scope, set it up in your own account and choose the option with the lowest running cost.
Where Nooks and Apollo.io setups usually go wrong
Tasks that never close
If the task stays open after the call, the sequence stalls. Every disposition closes it, including the ones where nobody answered.
No voicemail set means No Answer
When a rep has no recorded voicemail, Nooks logs the call as No Answer and moves on. We check every rep has one before go-live.
Contacts under the right account
Apollo files contacts under accounts. We match the person to an existing contact and account before creating anything, so one company does not end up as three.
How we set it up
- 1
Agree what connects
Which sequences feed the dialer, what each Nooks disposition changes in Apollo, and which calls Apollo’s own dialer keeps. You get a written scope with a fixed one-time price.
- 2
Access for the setup
An Apollo user with a permission profile covering the work, and admin access to Nooks. Nothing for your reps to install.
- 3
We connect and test
We push test contacts to a call task, take and miss the calls ourselves, and check every disposition, note, closed task and stopped sequence.
- 4
Handover
A short document of what is connected. It runs in your own accounts, with no monthly fee from us.
Test call passedEvery field in the table checked
LiveWatched for the first week
What it costs
From
$100 one-time setup
Starting price for connecting Nooks and Apollo.io, built and tested. Larger mappings get a fixed quote in writing before we start.
No monthly fee from us. Additional support is available as needed, whenever you request it.
Free download
The integration health check
10 checks to make sure your website, CRM and dialer really are passing information between them.
From the blog
Further reading
Integrations
How to log every call from your dialer in your CRM
Every call on the right contact, with the outcome, the rep and the recording, and nobody typing notes afterwards. What to connect, how to match callers, and what to test.
CRM
Why your CRM is full of duplicates, and how to stop new ones
Duplicates come in through forms, imports, integrations and manual entry. Here is how to clean up what is there, and close the doors so they do not come back.
Dialers
Why fewer people answer your calls: spam labels and caller ID
When answer rates drop, the cause is often a warning label on your caller ID. How US carriers check and label calls, and what you can do about it.
Questions about Nooks and Apollo.io
Can Nooks dial Apollo call tasks?
Yes. When a call task comes due, the contact is added to the right rep’s Nooks list, and the outcome closes the task back in Apollo.
Apollo has a dialer. Why use Nooks?
Apollo dials one number at a time. Nooks dials two to five at once and only connects the rep to a live answer, which is what clears a task backlog rather than sampling it.
Will calls be logged twice?
No. We agree up front which system logs which calls, so a conversation is recorded once whether it started in Apollo or in Nooks.
Is there a monthly fee?
No. You pay once for the setup. Unlike Zapier, Make and similar middleware subscriptions, there is no monthly or per-task charge from us. Your Apollo and Nooks plans are unchanged.
Rather talk it through?
Thirty minutes on how your team uses Nooks and Apollo.io. You leave knowing what we would build and what it would cost.
Call ended03:04 · inbound
Contact stage updatedMeeting booked
Call-back taskAssigned to the contact owner