Insights · CRM connectors
Pipedrive is where your reps live. Amazon Connect is where the calls actually happen. Joining them properly is the difference between a pipeline that reflects reality and one built on whatever people remembered to type in. Here's what Pipedrive does on its own, what a real CTI connector adds, and how the pieces fit.
Pipedrive is not phone-hostile. Phone numbers on a person or organisation are clickable, so a rep can start a call from the record. Pipedrive offers its own built-in calling, and its Marketplace carries a long list of telephony apps. Every call can be recorded as an activity against the person and the deal, and once it is, everything else Pipedrive does well — activity reminders, pipeline reporting, forecasting — works off it.
The stopping point is that Pipedrive is a CRM, not a contact centre. It has no queues, no skills-based routing, no IVR, no service-level targets, no supervisor view of who is on a call right now, and no compliance-grade recording regime with retention rules attached. That is not a criticism; it is a boundary, and it is the correct boundary for a sales CRM.
The second stopping point is subtler and costs more. Native and lightweight dialler integrations tend to be outbound-first. They make it easy to click a number and dial out. They are much weaker on the inbound side — the call that arrives from a number nobody typed, that needs to reach the right rep, and that has to land against the right record before the rep says hello. Inbound is where a CRM-plus-dialler arrangement quietly falls apart, and inbound is where most of the value of a real integration sits.
And whatever the mechanism, unless something writes the call back automatically, logging depends on a rep who has just finished a difficult conversation choosing to type it up. Some do. Enough don't that your reporting develops a lean.
A computer-telephony-integration connector puts the contact centre inside the CRM instead of beside it. With Amazon Connect on one side and Pipedrive on the other, that means five things:
Critically, none of this replaces your telephony. The connector links the Amazon Connect instance you already run to Pipedrive. There is no second dialler to buy, no second set of numbers, and no second place where call recordings end up.
Screen-pop sounds trivial and is the feature most likely to disappoint, because matching a phone number to a CRM record is genuinely fiddly. Three things decide whether it works in practice.
Number formatting. Amazon Connect presents caller ID in E.164 — +61412345678. Pipedrive holds whatever the rep typed: 0412 345 678, (02) 9000 1234, +61 2 9000 1234, sometimes with an extension appended. A match that only compares strings will fail on most Australian records. Matching has to normalise both sides before comparing, and it has to cope with the leading-zero national format that AU mobiles are almost always stored in.
Which entity wins. A number can belong to a person, to an organisation, or to several people at the same organisation — a switchboard number on twenty contacts is common in B2B. Popping the wrong one of twenty is worse than popping nothing, because the rep now believes something false. Sensible behaviour is to prefer a unique person match, fall back to the organisation, and where a number genuinely matches several records, present the choice rather than guess.
Which deal. The person is only half the answer for a sales team; the rep wants the open deal. Where a matched person has one open deal, that is the obvious context. Where they have four, the rep needs to be able to pick without leaving the call.
The pay-off is small per call and enormous in aggregate: the record is open before the greeting finishes, so the rep opens with the customer's situation instead of "can I take your name?".
Automatic logging is where the pipeline stops lying. When a call ends, the connector writes a Pipedrive activity carrying direction, duration, outcome and disposition, linked to the matched person and deal.
Beyond the basics, the ProUCX connector attaches what Amazon Connect already produced for that contact: a link to the call recording, the Contact Lens transcript, and an AI summary of the conversation. That combination changes who can use the record. A sales manager reviewing a stalled deal reads the summary instead of listening to twenty minutes of audio. A rep picking up a colleague's account sees what was actually promised. And because the recording stays in your own AWS account, your retention and access rules continue to govern it — the activity holds a link, not a copy.
A note on the discipline: automatic logging only helps if dispositions are a short, meaningful list. Thirty outcomes produce noise. Six produce a report someone will read.
Two capabilities matter more than they sound. Amazon Q assist surfaces answers from your knowledge base while the rep is on the call, inside Pipedrive, which is the difference between "I'll find out and call you back" and answering the question. And where you also run Live AI Agent, the AI's summary, detected intent and transcript arrive with the transferred call — so a rep taking an escalation opens the conversation already knowing what the caller wants.
On security, the arrangement is deliberately keyless: your Amazon Connect instance stays in your own AWS account and is read through a scoped, read-only role. There are no AWS access keys to hand over. Tenants are isolated from one another, and data residency is available in Australia, Singapore, the USA and Europe.
The sequence is short, and most of the elapsed time is your own change control rather than the install:
Pipedrive gives you a place to click a number and somewhere to record what happened. Amazon Connect gives you routing, recording and reporting. A CTI connector is what makes them one screen — inbound calls popping the right person and deal, every call logged with its recording, transcript and summary, and reps who never leave the CRM to make a phone call.
Screen-pop, click-to-dial and automatic activity logging, live in Pipedrive.