Answered by a group, owned by a person
We log the call against whoever took it and leave the Apollo contact owner untouched, so reporting is accurate and ownership does not churn.
Integration · Dialpad to Apollo.io
Dialpad and Apollo integration
Apollo thinks in individuals: a contact, an owner, a sequence, a task. Dialpad thinks in groups: departments that share calls across a team. We connect them so a call answered by anybody still lands on the right contact without quietly rewriting who owns it. 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
Dialpad
Apollo.io
One call ends in Dialpad. In Apollo.io:
- Call on a Dialpad numberDepartment, contact centre or direct
- Logged on the Apollo contactWith whoever actually spoke
- Sequence and owner updatedWithout reassigning the contact
- 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.
Group phone system, individual CRM
A Dialpad department exists so a call gets answered. It rings a group, somebody picks up, and which somebody is not important — that is the whole design. Contact Centers go further with routing, monitoring and analytics, on a Sell or Support licence, and admin rights come in six types so that different people can run different parts of it.
Apollo is the opposite shape. Every contact has an owner, every sequence belongs to a rep, and reporting is built on who did what. Join the two naively and one of two things happens: calls get logged to the contact owner who was not on the phone, so the activity report is fiction; or the integration reassigns the contact to whoever answered, so ownership churns every time somebody covers a queue. Neither is what anyone wanted. We record the person who spoke and leave ownership alone.
- Teams with a shared inbound lineWhoever answers, the call still reaches the contact.
- Reps covering for each otherActivity is credited accurately without ownership moving.
- Contact centres feeding a sales pipelineRouted calls land on the same contacts your sequences use.
What we connect between Dialpad and Apollo.io
A typical setup. We adjust each line to how your team uses Dialpad and Apollo.io.
When this happensThis is what you get
A call endsA call record on the matching Apollo contact, with the person who spoke
The Dialpad user who answeredRecorded on the call, separate from the contact owner
The call outcomeThe Apollo disposition and contact stage you choose
The call recordingLinked from the call record
A conversation that books a meetingThe sequence stops for that contact, and the owner is notified
A caller not in Apollo yetA new contact under the right account, checked for duplicates first
Field mapping, event by event
Each Dialpad event and exactly what it writes in Apollo.io. Pick an event to see its fields.
1. Trigger · Dialpad
When a call ends
Every call made or received in Dialpad
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
Date started15 Sep, 4:00 pm
Shown in your time zone
Date started15 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
Direction
Call directionInbound
Inbound or outbound
Call directionInbound
Inbound or outbound
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
Contact
Matched by phone number+1 415 555 0142
A new contact is created only if none match
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 Dialpad calls
Your team builds and maintains every step
Where it runs
In your own Dialpad 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 Dialpad and Apollo.io setups usually go wrong
Tasks need a destination
A missed department call has no natural owner. We agree whether the follow-up task goes to the contact owner or to a queue, rather than letting it land nowhere.
Contact Centers are licensed separately
They need a Dialpad Sell or Support licence and each has one routing type. Worth confirming before the design assumes routing you are not licensed for.
Contacts under the right account
Apollo files contacts under accounts, and a switchboard number belongs to a company rather than a person. We match to the contact where we can and the account where we cannot.
How we set it up
- 1
Agree what connects
Which numbers, departments and contact centres are in scope, who owns a shared call and its follow-up, and which outcomes change Apollo. You get a written scope with a fixed one-time price.
- 2
Access for the setup
Dialpad admin at the narrowest of its six permission types that covers the work, and an Apollo user with a suitable permission profile.
- 3
We connect and test
We call a department and answer from different members, miss calls on purpose, and check every contact, disposition, task and owner.
- 4
Handover
A short document of what is connected, including the ownership rules. 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 Dialpad 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 Dialpad and Apollo.io
Who is the call logged to when a Dialpad department answers?
The person who actually spoke is recorded on the call. The Apollo contact owner stays as it was, so activity reporting is accurate without ownership moving around.
Are calls from the Dialpad app and desk phones included?
Yes. Any call on a number in scope reaches the contact, not only calls placed from inside Apollo.
Do we need a Dialpad Contact Center licence?
Only for contact centre routing and analytics, which need a Sell or Support licence. Departments work without one and the integration supports both.
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 Dialpad plans are unchanged.
Rather talk it through?
Thirty minutes on how your team uses Dialpad 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