Short answer
Use HubSpot native calling if you mainly dial from the record and receive few calls on a shared line: a call only rings when a user is available with the calling window open, and the minutes limit is set per account. Choose a phone system integrated through CTI if you need queues, to keep your number, 900 or 400 numbering, or recording handled outside HubSpot, and name who will maintain the connector.
Key verification: Call the inbound number while the only available user has the calling window closed, and check whether it rings, goes to voicemail or is missed.
Sources and limitationsHubSpot's native calling fits when the main job is calling from the record and receiving a modest number of calls on a shared number. Connecting an external phone system through a CTI integration makes sense when inbound calls, queues, Spanish numbers or recording already depend on a telephony system that HubSpot does not replace. You decide by checking six criteria in your own account before moving any number.
This is a documentation-based comparison. The HubSpot and CloudTalk conditions and the Spanish rules cited were consulted on 22 October 2026; we have not measured audio quality or support response times.
What each architecture means
Native means HubSpot's own calling tool: the user dials from the record, uses a HubSpot-provided number or registers their own number with verified caller ID, and the call is saved as an activity. The documentation on receiving calls states that a HubSpot number can receive calls in the browser and can be assigned to a calling channel in the conversations inbox or help desk so that several users answer the same line.
CTI integration means the phone system remains another provider's (Aircall, CloudTalk or your own) and HubSpot displays its widget and stores the log. Providers build these apps with the Calling Extensions SDK; the documentation states that authentication is handled by the calling app and that, when a call starts outside HubSpot, the app is responsible for creating the activity. As an example of a marketplace app, the CloudTalk with HubSpot guide says inbound calls can ring in the HubSpot CTI or in the CloudTalk app, depending on where the user is active, and that calls are logged as activities that may include a link to the recording.
This article decides the architecture. If you already have one and want to dial from the record and accept the log, follow the guide to click-to-call in the CRM. If your question is which HubSpot plan to buy, start with HubSpot free or Sales Hub Starter.
What the official documentation says
- Native inbound: a call only rings in the browser if at least one user assigned to the number is logged in, available and has the calling window open; otherwise it goes to voicemail or is logged as missed. Safari is not supported for inbound browser calling.
- Native IVR menu: the interactive voice response guide places it in Sales Hub or Service Hub Professional and Enterprise, with keypad or voice branches leading to a user, a team or a submenu. The page does not describe queues with hold music.
- Recording: the call settings page lets you record all calls, inbound only, outbound only, or exclude numbers, users and regions, and set the consent message played before an inbound caller is connected. Only a Super Admin can switch recording on or off. The same page lets you turn off HubSpot calling so that users work with another provider.
- Minutes: the documentation refers to HubSpot's Product and Services Catalog, which expresses the limit per account per month, not per user. Ask in writing for the figure in your contract, whether inbound calls consume it and the price of additional minutes.
- Inbound through an integration: the developer guide on receiving calls warns that HubSpot does not support receiving calls from several providers at once and that closing the call tab during a conversation disconnects it.
Decision matrix
| Criterion | Points to native | Points to CTI integration | Test that settles it |
|---|---|---|---|
| Inbound calls and queues | Few inbound calls, one shared line, voicemail acceptable | Queues with waiting, overflow, opening hours and several sites | Call while every agent is busy and note what the caller hears |
| Minutes | Expected usage below the contracted limit | High volume, or a per-minute rate already negotiated with the carrier | Monthly calculation with inbound included or excluded as the contract states |
| Spanish numbers | A local number for customer care is enough | You must keep the current number for inbound, a 900 number or a commercial 400 number | Written confirmation of the number type and how the current one is kept |
| Recording and consent | HubSpot's per-number notice and exclusions cover the case | Recording must live in the phone system with its own retention | Listen to the notice, check who has access and where the audio is stored |
| Logging on the record | Calls start in HubSpot and are associated automatically | Many calls start outside HubSpot, on a mobile or in another app | A call started outside HubSpot appears on the correct contact |
| Maintenance | Nobody in the team can take responsibility for a connector | There is an owner and the provider documents its app | Name of the person who reviews errors and updates |
If an essential criterion lands in the integration column, the native option's saving is no longer comparable. To compare connectors with external automation, see the guide on native integration or external automation.
Spanish numbers: type, registration and the 400 range
The supported countries table lists Spain with local numbers. The same page adds that a toll-free number cannot be registered as an outbound number and that registered numbers, because they are not owned by Twilio and use verified caller ID, are more likely to be marked as spam and blocked.
The Spain row also reflects the Spanish rule: from 17 October 2026, commercial calls must be made from the new 400 range, and calls to existing customers for customer care from geographic numbers or 800/900 numbers. If your team does cold prospecting, ask HubSpot and the phone system provider whether they can present a 400 number; the HubSpot documentation consulted only offers local numbers for Spain. For a team that only answers and returns customer calls, a geographic number may be enough.
Fictitious example: how much a small team uses
A fictitious company has three salespeople and two support staff. Assume its contract includes 3,000 minutes per month per account: this is an assumption for the calculation, not a confirmed figure for your plan.
| Item | Calculation | Minutes per month |
|---|---|---|
| Outbound sales calls | 3 people × 25 calls × 4 min × 21 days | 6,300 |
| Inbound support calls | 2 people × 40 calls × 5 min × 21 days | 8,400 |
| Excess if only outbound counts | 6,300 − 3,000 | 3,300 |
| Excess if both count | 6,300 + 8,400 − 3,000 | 11,700 |
The gap between 3,300 and 11,700 minutes hinges on a single contractual question: whether inbound calls consume the limit. In addition, 80 inbound support calls a day force you to decide what happens when both support staff are busy; if the answer is a queue with waiting, review the guide on a call queue with a waiting limit and check whether the native plan offers one before ruling out the phone system.
Test protocol before you decide
- Create a test contact with your own mobile number in international format.
- Make an outbound call from the record and check the number displayed, the duration and the activity association.
- Call the inbound number with one user available, another with the window closed and another busy; note whether it rings, goes to voicemail or is logged as missed.
- Enable recording for the test, listen to the full notice and check which profiles can play and download the audio.
- In the CTI option, start a call from the provider's app, outside HubSpot, and look for the activity on the record.
- Close the call tab during a test conversation and record the effect.
- Ask in writing for the minutes limit, inbound consumption, the type of Spanish number available and who maintains the integration.
For each step, keep the date, architecture, result and evidence.
How to close the decision
Choose native if all six rows of the matrix point to native and the protocol shows no calls lost to closed windows or the lack of a queue. Choose a CTI integration if inbound handling, the number type or recording depends on the phone system, and name the person who will be responsible for the connector. If the result is mixed, the deciding criterion is the one that affects the caller: an inbound call that nobody hears costs more than a few additional minutes.
Sources and limitations
Documentary review: . Content type: Documentation-based comparison.
Linked sources describe the terms and capabilities each provider publishes. Examples that use fictional data are labelled in the text.
- receiving callsknowledge.hubspot.com
- Calling Extensions SDKdevelopers.hubspot.com
- CloudTalk with HubSpothelp.cloudtalk.io
- interactive voice responseknowledge.hubspot.com
- call settingsknowledge.hubspot.com
- receiving callsdevelopers.hubspot.com
- supported countriesknowledge.hubspot.com
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
HubSpotOfficial plan catalogueThese links lead to official pages without affiliate identifiers. We do not yet have an active affiliate link for these options. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.