🔗 How to integrate your Phone System with your CRM: click-to-dial and screen pop

When your Phone System and your CRM do not talk, agents copy numbers by hand, look up the customer while greeting them and the call ends up in no history. Integrating them fixes all three. This guide explains what you can integrate and how.

The four integrations that pay off most

• Click-to-dial: one click on a number inside the CRM rings the agent's extension and, once answered, dials the customer. Nobody types numbers.
• Screen pop: when a call enters the queue, the CRM opens the customer record before the agent answers.
• Call logging: every call —inbound, outbound, answered or missed— lands in the customer's history with its duration.
• Recording on the record: the call audio is linked to the customer for later review.

How they connect: API and webhooks

There are two pieces. With the API, the CRM asks the phone system to do things: place a call, look up call records or fetch a recording. With webhooks, the phone system tells the CRM what is happening as it happens: a call entered the queue, is ringing, was answered, ended or was missed.

Screen pop, for example, runs on a webhook: the phone system says "a call from number X entered the sales queue", and the CRM looks up that number and opens the record.

What you need on your side

• A CRM that can call an API or receive HTTPS notifications.
• A person or vendor to build the connection in your CRM.
• Each agent's extension mapped to their CRM user.
• An API key with only the permissions needed and allowed IPs.

Common mistakes

• Matching customers only by the full number: numbers arrive with or without country code; normalize them first.
• Logging only answered calls: missed calls are the ones that most need a callback.
• Not verifying webhook signatures: anyone could send fake events to your CRM.
• Integrating everything on day one: start with click-to-dial and screen pop, which save the most time.

Integrate, or use a CRM that already includes calling?

If your company already lives in a CRM, integrating it is the way. If you do not have one yet, or barely use it, a CRM that already includes calling saves you the integration project: calling, messaging and scheduling from the record work from day one.

A step-by-step example

This is what an inbound call looks like with the phone system integrated with the CRM:

1. The call enters the sales queue. The phone system sends the call.queued event with the caller's number.
2. The CRM looks up the number in its contacts and prepares the customer record, or a new one if none exists.
3. The agent's phone rings. With the call.ringing event, the CRM shows the record on screen.
4. The agent answers (call.answered) knowing who the customer is, what they bought and what they asked for last time.
5. The call ends (call.completed): the CRM logs the duration and outcome in the history.
6. If nobody answered (call.missed), the CRM creates a callback task.
7. Later, the CRM fetches the recording through the API and links it to that call.

For an outbound call the path is reversed: the agent clicks the number, the API places the call and the same log lands on the record.

Integrations at TelHarbor

TelHarbor offers click-to-dial through the API, signed webhooks for call and message events, and access to calls, queues and recordings, with permission-scoped keys and an IP allowlist. If you would rather not integrate, TelHarbor's CRM already includes calling. See Integrations, what webhooks are or book a demo.