HubSpot VoIP integration: connecting calls without a new phone system

What HubSpot VoIP integration means

VoIP, voice over internet protocol, is calling that runs over your internet connection rather than a traditional phone line. HubSpot VoIP integration is the link that lets those calls appear inside HubSpot. When the link is in place, an inbound call opens the matching contact record, an outbound call can be placed by clicking a number in HubSpot, and every call is logged on the contact timeline with its time, duration, and outcome.

The reason teams want this is the same reason any CRM-to-phone link matters. Without it, calls live in one system and customer records live in another, so reps copy notes by hand, calls go unlogged, and managers cannot see call activity next to deal activity. With it, the call becomes part of the customer record automatically and your call data joins the rest of your sales and service reporting.

HubSpot Calling SDK versus native versus third-party

There are three ways to get VoIP calling into HubSpot, and they differ in cost and in how much of your existing setup you keep.

HubSpot native calling

HubSpot includes a calling tool that lets reps place calls from inside the CRM using HubSpot-provided minutes, with limits that depend on your subscription tier. It is the fastest to switch on and needs no other phone system. The limits matter: included minutes are capped, additional calling capability sits behind higher tiers, and you are effectively running a second phone system alongside any PBX you already pay for. For a small team with no phone system, native calling can be enough. For an established team, it usually duplicates infrastructure.

Marketplace calling apps and the Calling SDK

HubSpot publishes a Calling SDK, a developer framework that lets a phone system or calling provider build a call widget that runs inside HubSpot. Apps built on the SDK appear in the HubSpot call switcher, so reps can choose your phone system as their calling provider directly in the record. The SDK handles the call window, the inbound and outbound events, and the logging back to the timeline. This is how a third-party phone system, including 3CX through an integration, presents itself inside HubSpot without replacing anything.

Third-party integration over your existing phone system

The path most teams with an existing PBX take is an integration layer that uses the Calling SDK to surface your phone system inside HubSpot. Your 3CX deployment keeps handling the actual calls, routing, and recording. The integration feeds call events into HubSpot for screen pop and logging, and passes outbound click-to-dial requests back to 3CX. Nothing about the phone system changes, so there is no migration and no number porting.

Keeping your existing phone system versus HubSpot-bundled calling

The choice between bundled calling and keeping your phone system is mostly a cost-and-control decision. HubSpot-bundled calling adds cost that scales with seats and tiers, and it asks your team to make calls inside a tool that is primarily a CRM, not a phone system. Your existing 3CX deployment already handles call routing, queues, and recording the way your team expects, and it is already paid for.

Consider a 10-seat team. Moving everyone onto bundled CRM calling means buying minutes and, often, stepping up a subscription tier to lift calling limits, which can add several thousand US dollars a year on top of what you already spend on the phone system you have. Keeping 3CX and adding an integration layer leaves the calling infrastructure untouched and adds a single integration line item that scales with call volume rather than seat count. The phone system you already bought is not re-charged every month.

There is also a feature dimension. A dedicated phone system handles things bundled CRM calling tends to do poorly or not at all: multi-level queues, complex routing, on-premises or hybrid deployment, and recording at the depth compliance teams expect. Keeping the phone system keeps those features. The integration simply makes the calls visible in HubSpot.

Wiring 3CX call data into HubSpot

When you connect 3CX to HubSpot, the integration uses the Calling SDK so 3CX appears as a calling option inside the HubSpot record. The flow works in both directions. Inbound: 3CX signals a ringing call, the integration matches the caller number to a HubSpot contact, and the record opens for the rep. Outbound: the rep clicks a number in HubSpot, the request passes to 3CX, and 3CX places the call. After the call, the integration writes a logged call activity to the contact timeline with duration and direction, and attaches a recording where 3CX provides one.

Because 3CX stays in charge of the call, you keep your routing, your extensions, your queues, and your recording policy. HubSpot becomes the place the call is recorded against the customer and reported on, not the place the call runs. This is the same pattern that works for any CRM: the phone system you own does the calling, the CRM does the customer context. For the step-by-step connection, see our guide to 3CX HubSpot integration. For how VoIP and CRM connect more generally, the VoIP CRM integration guide covers the patterns, and the computer telephony integration guide sets out the category.

Cost comparison at a glance

The simplest way to frame the decision is per-seat versus per-call. Bundled CRM calling charges per seat, every month, regardless of how much each rep actually calls, and steps up with subscription tier. A kept-PBX-plus-integration model charges for the phone system once, as you already do, and adds an integration cost that tracks call volume. For a team that already runs 3CX and makes a normal volume of calls, keeping the phone system is almost always the lower three-year cost, and it avoids the migration project entirely.

Frequently asked questions

About this article

Written by the Connect Zero team, an Australian-built Insights sold by Auswide IT, an Australian MSP integration vendor based in Adelaide. Last updated 29 May 2026.