HubSpot calling lets eligible Sales Hub and Service Hub users place calls from CRM records and, with a HubSpot-provided number, receive supported inbound calls in HubSpot. The correct setup depends on whether you use a HubSpot-provided number, register an existing number for outbound caller ID, or connect a third-party calling provider.
That distinction matters. A registered outbound number can display your existing caller ID when a user calls from HubSpot, but inbound calls to that number continue to ring on the existing phone or landline. Teams that want inbound calls to ring in the HubSpot browser, mobile app, Conversations Inbox, or Help Desk need a supported HubSpot-provided or properly configured HubSpot-capable number. Compare HubSpot's calling paths and inbox number requirements.
Product details checked September 8, 2026. Setup and test checklists below are Selworthy recommendations, not a claim that your account is already configured.
HubSpot calling brings phone activity into the CRM workflow. Depending on the number type, subscription, seat, country, and configuration, users can:
See HubSpot's outbound calling and inbound calling guides for the supported workflows.
HubSpot calling is not a replacement for every phone system. It is a CRM-centered calling option with specific number, browser, seat, country, capacity, and compliance requirements.
A HubSpot-provided number is created and managed inside HubSpot and is powered by Twilio. Current HubSpot documentation says it can be used to make and receive calls in the HubSpot browser, forward calls to a personal device, or receive calls in the mobile app.
This is a native option for inbound calling. HubSpot's number-acquisition guide documents its setup. Porting an existing number for supported inbound use is a separate process from registering an outbound caller ID. Confirm eligibility before moving an existing business line.
A registered outbound number lets a user call from HubSpot while displaying an existing mobile or office number as caller ID. HubSpot does not own that number, and it is for outbound identification only.
Inbound calls to a registered outbound number do not ring in the HubSpot browser. They continue to ring on the personal device or landline associated with that number. Each user must register the number individually, even when the organization shares it. See HubSpot's outbound-number registration guide.
Teams can connect a calling provider from the HubSpot App Marketplace or use a custom calling app built with HubSpot's Calling Extension SDK. This can be appropriate when the business wants to keep an existing telephony system while placing, receiving, or logging calls through an integrated workflow.
Capabilities vary by provider. Verify number ownership, inbound routing, recording, transcript sync, activity logging, support, and cost in the selected provider's current documentation.
| Option | Call from HubSpot | Receive inbound calls in HubSpot | Main use case |
|---|---|---|---|
| HubSpot-provided number | Yes | Yes, when configured and supported | Native inbound and outbound calling |
| Registered outbound number | Yes | No; inbound continues to the existing device or landline | Keep an existing caller ID for outbound calls |
| Third-party provider | Provider dependent | Provider dependent | Retain external telephony with a HubSpot connection |
Current HubSpot documentation lists calling under Sales Hub and Service Hub Starter, Professional, and Enterprise, with feature-specific exceptions. Making calls requires an assigned Sales or Service seat. Phone-number capacity, calling minutes, recording, transcription, analysis, and shared-channel capabilities can vary by subscription and access.
Review your portal's current entitlements in Account & Billing. HubSpot limits phone numbers and pools calling minutes at the account level. Adding minutes requires Sales Hub or Service Hub Professional or Enterprise; do not assume every plan supports that add-on. See calling settings and minute limits.
Calling support and the countries where HubSpot-provided numbers are available can change. Some countries also require local business information or regulatory review. Check HubSpot's current supported-country list before acquiring or registering a number.
A Super Admin must acquire or reassign HubSpot-provided numbers and manage conversation recording and transcription settings. Turning call recording on or off can also be done with Account access permissions. Individual callers need the appropriate seat and record access.
Inbound browser calling requires a supported browser. HubSpot's current documentation says Safari is not supported for inbound browser calling. An eligible user must be assigned to the number, logged in, marked available, and have the inbound-calling window or HubSpot Sales Chrome extension active. If no eligible user is detected, the call can go to voicemail or be logged as missed. Follow the inbound browser requirements.
Document the intended number, caller ID, owners, shared teams, working hours, after-hours behavior, voicemail, recording rule, and reporting outcome. Select the number type from those requirements.
For a HubSpot-provided number, a Super Admin selects an available country and area code, completes any required regulatory information, names the line, selects recording-consent language, and assigns the number.
For an existing outbound number, each user enters the number and completes HubSpot's verification step. Registered outbound numbers cannot be used as native inbound numbers in HubSpot.
Use HubSpot's current calling setup instructions while configuring the portal. Interface labels and requirements can change.
For an individual HubSpot-provided number, select whether inbound calls ring in the browser, mobile app, or a forwarding number. Configure working hours, including the time zone, so unanswered or after-hours calls have a defined destination. HubSpot's voicemail requires call recording to be on and is available for inbound browser calls, not inbound forwarded calls. Verify the forwarding provider's behavior and costs separately.
For a team line, check the channel's requirements first: Help Desk calling requires Service Hub Professional or Enterprise and an assigned Service seat for calling; Conversations Inbox calling supports eligible Sales Hub or Service Hub Professional or Enterprise accounts. Assign the intended users or teams, set operating hours, and configure the supported voicemail behavior.
HubSpot's current routing and voicemail guide should be the action-time reference.
HubSpot enables call recording by default on new accounts. Check the current account setting and any direction, number, user, or region exclusions before testing. Its inbound recording-consent message plays before a representative answers. See recording settings.
Recording laws and consent requirements vary by jurisdiction and context. HubSpot states that the account and its users are responsible for understanding applicable obligations and obtaining appropriate consent. Treat HubSpot's recording guidance as operational information, not legal advice.
Recording and transcription are not identical. Eligible Sales Hub or Service Hub Professional or Enterprise users can access transcription and analysis for supported conversations. HubSpot's current transcript-sync guide places the controls under Notetaker. For phone calls, check the Phone calls, Conversation recording, and Transcription and analysis settings, the assigned seat, and calling requirements. Confirm a supported test transcript before building coaching or automation around it.
Decide which call outcomes users should select and which notes your process requires. HubSpot's required-outcome setting applies to outbound browser calls or already logged calls, not inbound, mobile, or imported calls. Define a separate team process for those gaps. Keep the outcome list short and useful for follow-up. See call-outcome controls.
A broader HubSpot operations framework should define who owns missed calls, how quickly follow-up is expected, which calls create tasks, and how call activity relates to lifecycle stages and deals.
Use controlled records, consenting participants, and phone numbers your team is authorized to test. Do not use a test to bypass an opt-out or contact someone who should not be called.
Record the expected result, actual result, date, portal, number, user, device, and browser. A passing test proves that scenario at that time. It does not establish that every country, user, number, or device has the same configuration.
Place one controlled outbound call from a contact record and one from the calling remote. Verify:
Do not assume that displaying a familiar caller ID prevents carrier spam labeling. HubSpot's registered-number guidance warns that carriers can mark or block calls using verified outbound caller ID.
Confirm that the number is configured for supported inbound use, the user is assigned and available, the browser is supported, notifications are permitted, and the calling window or extension is open. Also check working hours, forwarding, and voicemail settings.
That is expected. A registered outbound number is used for outbound caller ID. It does not convert the existing line into a native inbound HubSpot number.
Check the phone-number format, country support, user seat, number registration, account-wide calling setting, and available monthly calling minutes. When native calling minutes run out, an in-progress call can finish, but new calls cannot start until minutes reset or eligible additional capacity is available. Check the outbound call limit guidance.
Review the account's recording and transcription settings, the user's seat, consent requirements, supported conversation type, and integration behavior. A recording can exist without automatic transcription. Integrations sending completed transcripts may still sync them when HubSpot's transcription setting is off; integrations sending only recording URLs behave differently. Check the current transcript-sync rules.
Review the contact selected when the call started, phone-number formatting, duplicate contacts, activity associations, integration settings, and any workflow that changes ownership or associations. Correct the identity rule before scaling automation.
Yes, using a supported HubSpot-provided or properly configured HubSpot-capable number. A registered outbound number alone does not receive calls in HubSpot.
HubSpot can record supported calls when account settings permit it. Recording is subject to consent and legal requirements. Administrators can manage recording settings and exclusions.
Yes, eligible accounts can assign a HubSpot-provided number to a calling channel in Help Desk or the Conversations Inbox and route calls to selected users or teams. Help Desk and Inbox have different subscription and seat requirements, as noted above.
No. Transcription depends on the call source, settings, subscription, seat, supported conversation, and current product access. Verify the intended scenario in the portal.
No. HubSpot documents a pooled monthly calling-minute limit based on subscription. Current usage and available increases should be checked in Account & Billing.
Use HubSpot calling when the native CRM workflow and supported number model meet the business requirement. Use or retain a third-party provider when the organization needs telephony, routing, country coverage, reporting, or administration beyond the native setup. Test the actual integration before committing to a migration.
The useful outcome is not simply placing a call inside HubSpot. The process needs correct number ownership, routing, consent, CRM association, outcomes, follow-up, reporting, and a repeatable test.
Selworthy can help map that process across HubSpot Sales, HubSpot onboarding and training, and CRM operations. Talk with Selworthy about the calling workflow you need to configure or repair.
HubSpot's primary documentation below was checked on September 8, 2026. Subscription access, country support, and interface labels can change. Use the linked documentation and your account's current entitlements when configuring calling.