Telephony and Pipedrive
The call happens in one system. The record of it lives in another.
Reps make calls in JustCall. Deals live in Pipedrive. Nothing connects the two on its own, so every call outcome gets written down twice: once for the phone system, once for the CRM. The second one is the one that stops happening. A few weeks in, the pipeline reports no longer match what actually happened on the phone.
What gets built
The call outcome moves the deal by itself.
We have built JustCall-to-Pipedrive integrations for several clients. The core idea is always the same: the disposition a rep picks at the end of a call (the dropdown for "left voicemail", "not interested", "booked a demo") is written back onto the right Pipedrive deal as a field. That field then triggers whatever should happen next in Pipedrive, without the rep opening the CRM at all.
Alongside that, calls are logged against the correct deal automatically, and SMS or voicemail activity can feed the same pattern. Exactly what gets built depends on how a given team sells. The dispositions, the stages and the triggers are set up to match that pipeline, not a generic template.
| Call outcome in JustCall | What happens in Pipedrive |
|---|---|
| Left voicemail | Deal field updated, follow-up activity scheduled a few days out |
| Not interested | Deal marked lost with the reason recorded |
| Booked a demo | Deal advanced a stage, demo activity created for the right owner |
| No answer | Call logged against the deal, next attempt queued |
How it is put together
Make.com sits in the middle, and the account is yours.
JustCall does not talk to Pipedrive on its own. The connection runs through Make.com, an automation platform that watches for events in JustCall and carries them across to Pipedrive as deal updates, notes or triggers. It is not a plugin you install and forget. It is a small set of scenarios built around how your team actually dispositions calls.
The Make.com account is yours. You can open it, see every run, and see exactly what data moved and when. If something needs changing later (a new disposition, a different field) it is visible and editable rather than buried inside a black box.
Honest limits
What this does not fix.
- It does not make reps select a disposition. If nobody picks an outcome on the call, there is nothing for the automation to act on.
- It is not a packaged product. Each build maps to one team's dispositions and stages, so there is setup work before anything runs.
- It covers JustCall. If your team is on a different telephony platform, say so before we scope anything. We have not built this for other vendors.
- It is worth doing when reps are already disciplined about dispositions and the pipeline simply is not hearing about them. If the discipline problem sits upstream of that, we should talk about that first.
Next step
Bring your JustCall setup and I will tell you what is realistic.
A 30-minute call is enough to see how your team dispositions calls today, and what a Pipedrive connection would actually need to do. It costs nothing.