Blog / HubSpot And CRM Integration

HubSpot Calls Not Logging? 9 Fixes by Symptom

A vendor-neutral troubleshooting tree for HubSpot calls that do not log, sync or record. Start with your symptom, run one isolation test, and apply the matching fix.

HubSpot calls usually stop logging for one of five reasons: the integration's authentication expired, the wrong calling provider is selected, the agent's email does not match a HubSpot user, the caller's number does not match a contact, or the line is not enabled for logging. This guide walks you from symptom to fix, in the order that finds the cause fastest.

It applies whether you use HubSpot's own calling, a CTI (a computer telephony integration that adds a dialer inside the CRM), or a sync app that pushes calls from your phone system.

Key takeaways

  • A single test call (one inbound, one outbound, from a known contact) tells you in about four minutes whether the problem is the connection, a setting, or the data.
  • HubSpot says the Record button disappears when "Allow call recording" is off under Settings > Calling > Call Configurations, and recording requires the call to connect and reach Completed status.
  • By default, HubSpot compares First Name, Last Name, Email, IP country, Phone number, Zip Code and Company Name when flagging potential duplicate contacts, so shared phone numbers can send calls to the wrong record.
  • Storing phone numbers in E.164 format (for example +14155550134) removes the most common number-matching failures.
  • Validity's 2025 survey of 602 CRM users found 76% say less than half of their CRM data is accurate and complete, which is why logging bugs are often data bugs.

Why are HubSpot calls not logging? Start with the symptom

HubSpot calls not logging is rarely one bug. It is a symptom of a failure in one of four layers: connection, settings, user mapping, or data matching. Sorting your symptom first saves you from re-authenticating an integration that was never broken.

Quick decision table: all calls, some calls, or recordings only

If nothing logs for anyone, or the calling window itself misbehaves, start here:

What you seeMost likely causeGo to
No calls log for anyone, starting on a specific dateExpired authentication or disconnected integrationFix 1
Calling window is blank, or the wrong dialer opensWrong or desynced provider, cookies, extensionsFix 2
One rep's calls never log, others fineAgent email mismatch or user permissionsFix 3-4

If calls log but land in the wrong place, or only some call types are missing, use this one:

What you seeMost likely causeGo to
Calls from some numbers or contacts log, others do notNumber format, country code, extension, match settingsFix 5-6
Call logs, but on the wrong contactDuplicate contacts or shared numbersFix 7
Call is on the contact but not the company or dealAssociation behaviorFix 8
Call logs but no audioRecording setting, consent, status or expired URLFix 9
Only inbound calls or voicemails are missingCalling path does not support themNumbers section

Also note three splits that narrow things fast: new calls versus old calls, one user versus all users, and inbound versus outbound. A problem that began on a single date points to a connection or settings change. A problem limited to one user points to mapping or permissions.

Four-minute isolation test

Run this before changing anything:

  1. Pick a contact whose record has one phone number, stored in E.164 format, and no duplicates.
  2. Using an affected rep's account, place an outbound call that connects and lasts at least 30 seconds.
  3. Call that number back from a different phone to create an inbound call.
  4. Leave one voicemail and let one call go unanswered.
  5. Wait five minutes, then check the contact timeline. Write down the time of each call.

If the clean contact logs correctly, your problem is in the data (number format, duplicates). If it fails too, the problem is the connection, provider, mapping or settings. Keep these timestamps; you will need them if you escalate to support.

Is the integration connected and the right calling provider selected?

Check the connection first, then the provider. An expired token or a mis-selected provider stops logging for everyone at once, and both take under five minutes to rule out.

Fix 1: Reconnect or re-authenticate the integration

Many integrations stop logging silently when authentication expires or an admin changes a password or permission. One contact-center vendor's help documentation, for example, states its HubSpot integration stops logging calls until reauthentication is completed, and that calls on numbers not enabled in the integration's connected-numbers list are not logged. Treat that as a pattern that applies to most providers.

Do this:

  • Open the integration's settings in your phone system and look for a "reconnect," "re-authorize" or "connection status" prompt.
  • Confirm the HubSpot account it is connected to is the right portal, and that the connecting user is still active.
  • Check the vendor's status page for an incident on your failure date.
  • Confirm each phone line or number you expect to log is enabled in the integration.

Calls placed while the connection was broken generally do not backfill on their own. Plan to log important ones manually.

Fix 2: Check the calling provider, cookies and extensions

In HubSpot's calling window, the provider is the dialer that places and logs the call. If the wrong provider is active, calls go through a path that does not log to your timeline. The same vendor's CTI troubleshooting article says most calling-window problems come from the CTI not being registered as the active calling provider in the browser session, and that it relies on third-party cookies being allowed.

Work through this list:

  • Use the calling window's "Change provider" option and select your phone system explicitly.
  • Sign out of the phone system and HubSpot, then sign back in to both in the same browser.
  • Allow third-party cookies for the HubSpot and phone-system domains.
  • Test in a private window with extensions off. Ad blockers and privacy extensions commonly break embedded dialers.
  • Try a second browser to confirm it is not a profile issue.

Do user permissions and agent email mapping block call logging?

Yes. If the person on the call is not matched to an active HubSpot user, or lacks the access to create call activities and view the contact, the call can fail to log even when everything else is healthy. Check this whenever one rep is affected and others are not.

Fix 3: HubSpot user permissions

Reps need to be able to see the contact they are calling and create call activities. A rep restricted to "own records only" may not see a contact owned by someone else, so a call to that contact can fail or land unattached.

RoleWhat to verify
RepCan view the contact (check contact access is not limited to owned records) and create call activities
ManagerSame as rep, plus visibility into team records if you expect to review their calls
AdminCan reconnect integrations and change calling settings
Super AdminFull account control, including calling configuration

HubSpot's exact permission names change over time, so confirm each item in your own portal's user settings rather than relying on a generic list. Anything above marked as "verify" is a check, not a documented guarantee.

Fix 4: Agent email must match the HubSpot user

Most integrations identify who made a call by the agent's email address in the phone system. If that email differs from the user's HubSpot email (a nickname alias, an old domain, a typo), the integration cannot find the user. A 3CX community thread describes exactly this: calls failing to log when the HubSpot user matching the agent's email is not found.

Export your phone system's agent list and your HubSpot user list, then compare them side by side. Fix mismatches in the phone system, since changing a HubSpot login email has wider consequences.

Why do phone numbers fail to match HubSpot contacts?

Phone numbers fail to match when the number in the call and the number on the contact record are stored differently. Formatting, missing country codes, extensions and match-digit settings all decide whether an incoming number finds its contact. Unmatched calls then either vanish or create unwanted new contacts.

Fix 5: E.164, country codes and extensions

E.164 is the international phone number standard: a plus sign, country code, and number with no spaces or punctuation. Phone systems send numbers in this format. HubSpot records often hold whatever a rep typed.

Stored on the contactE.164 equivalentLikely to match?
(415) 555-0134+14155550134Risky, depends on integration
415-555-0134+14155550134Risky
4155550134+14155550134Often fails without country code
+1 415 555 0134 ext. 22+14155550134Extension can break the match

The same 3CX thread recommends storing numbers in E.164 and tuning the phonebook match-digit setting. Put extensions in a separate property instead of the phone field.

Fix 6: Match-digit, "log only on match" and unknown callers

Check three settings in your phone system's HubSpot integration:

  • Match digits: how many trailing digits must agree. Too many digits rejects numbers with different prefixes. Too few can match the wrong contact.
  • Log only when a match is found: if this is on, calls from unknown numbers are skipped by design.
  • Create new contact for unknown callers: if this is off, new prospects never get a record. If it is on, formatting mismatches can spawn duplicates of contacts you already have.

Audit and normalize existing numbers

  1. Export contacts with their phone and mobile phone properties.
  2. Flag values missing a country code, containing extensions, or using inconsistent punctuation.
  3. Convert them to E.164 in a spreadsheet and re-import to update existing records, or use a HubSpot workflow if your plan supports it (verify in your portal).
  4. Re-run the isolation test on a corrected contact.

Do this in batches and keep a backup export.

How do duplicate contacts change where a call lands?

Duplicate contacts split your history. When two records share a phone number, the integration attaches the call to one of them, usually the first match, so the other record looks like it never got a call. This is the most common reason a call "logged" but nobody can find it.

Why shared numbers send calls to the wrong record

By default, HubSpot flags potential duplicate contacts by comparing First Name, Last Name, Email, IP country, Phone number, Zip Code and Company Name. Shared office lines, a receptionist's number on five contacts, or a spouse's number on two records all create ambiguity. The integration cannot know which person called.

Using Manage Duplicates safely

Merging is done from Contacts > Actions > Manage Duplicates. Before you merge:

  • Open both records and confirm they are the same person, not two colleagues on one main line.
  • Decide which record is the primary and which phone number should survive.
  • Check owners, lifecycle stages and deal associations on both.
  • Review HubSpot's current page on undoing merges before you click, because merges are consequential and may not be reversible.

Prevention

Store one direct number per contact. Put switchboard numbers on the company record, not on individual people. Turn off automatic contact creation until your number formats are normalized.

Why does a call show on the contact but not the company or deal?

A call is an activity associated with one or more records. Which records it attaches to depends on how the integration creates the association, so a call can appear on a contact timeline and be absent from the company or deal. HubSpot's docs and each vendor's docs differ here, so verify behavior in your portal.

Contact, company and deal

What is generally true: a call logged against a contact appears on that contact. Company visibility usually depends on the contact being associated with that company. Deal visibility depends on whether the integration associates the call with deals or only with the contact.

What varies by integration: whether a call is associated with open deals automatically, which deal is chosen when a contact has several, and whether associations are set at call start or after the call ends. If your reports need calls on deals, test this explicitly with a contact that has one open deal.

If a call is missing from a company, check that the contact is associated with the company first. Open the call record itself and look at its associated records to see what the integration actually attached.

Inbound versus outbound

Outbound calls from the calling window typically attach to the record you were viewing. Inbound calls attach based on number matching, so they inherit every problem from the number-matching and duplicate sections above. When inbound calls log wrongly and outbound calls log correctly, suspect matching, not associations.

Missed calls, voicemails and forwarded calls

These are the least consistent. Whether a missed call, a voicemail or a call forwarded to a mobile number creates an activity depends on the calling path and the integration's settings. Test each one in your isolation test and write down which ones log. Do not assume.

Why is the HubSpot call recording missing?

A missing recording has two very different causes: the call was never recorded, or it was recorded but the audio did not reach HubSpot. Separating them is the key to a fast fix, because the remedies are unrelated.

Never recorded

HubSpot's recording troubleshooting article lists the checks:

  • Account setting: if "Allow call recording" is off under Settings > Calling > Call Configurations, the Record button does not appear.
  • Consent: in states requiring two-party consent (HubSpot cites 13 U.S. states), the user must click Record and confirm "I have informed them," or the call is not recorded.
  • Call status: the call must connect, and its status must be Completed, for the recording to appear.

Recording laws vary by state. HubSpot's call recording laws article separates "One Party Consent" states from "All Party" states, says its examples are not exhaustive, and recommends getting consent when unsure and seeking legal counsel. This guide is not legal advice.

Recorded but not syncing

If your phone system shows the recording but HubSpot does not play it, the problem is the link between them. Community reports describe recording URLs that expire or fail on older calls, and tokens that lapse after re-authentication problems. Play the recording in the phone system first. If it plays there, send the recording URL and call ID to the vendor. If newer calls play and older ones do not, link expiry is the likeliest cause.

Deleted recordings

Recordings can be deleted manually by users with the right access. Ask your admins who can delete recordings and check whether anyone cleaned up the timeline before blaming the integration. For a broader look at how recordings and notes reach the CRM, see this buyer's guide to call recording and CRM notes.

Which numbers can actually log calls to HubSpot?

Not every number logs every call type. Which path you use (a number HubSpot provides, a registered outbound number, or a connected third-party line) decides whether inbound calls and voicemail reach the timeline.

What each path logs

PathOutboundInboundVoicemail
Number provided by HubSpotLogsVerify in your portalVerify in your portal
Registered outbound numberLogsReported not to logReported not to log
Third-party phone system, line enabledLogs if enabledDepends on integrationDepends on integration

One vendor's HubSpot calling troubleshooting guide reports that calls placed through registered outbound numbers cannot log inbound calls, voicemails or forwarding. That is a vendor claim, so confirm it against HubSpot's documentation before you redesign anything. If you rely on inbound logging and use registered numbers, you may be on the wrong calling path.

For a wider comparison of how phone systems sync with HubSpot, see the guide to HubSpot phone integration setup and the comparison of VoIP options by CRM sync depth.

What should you send support if nothing works?

Send support a single message with timestamps, call IDs, the affected user and contact, and screenshots. Complete evidence turns a three-week back-and-forth into one reply, and it forces you to confirm that the failure repeats.

Evidence checklist

  • Date, time and time zone of each test call, plus whether it was inbound or outbound
  • The affected user's name and email in both systems
  • The contact's HubSpot record URL and the number as stored
  • The call ID from the phone system
  • The recording URL, if the issue is audio
  • Screenshots of the phone system's call log and the HubSpot timeline
  • Browser console errors or a HAR file (a recorded log of network requests) if the calling window fails
  • What you already tried: re-auth, provider change, private window

HubSpot or the phone vendor?

ProblemContact
Record button missing, Call Configurations, permissions, duplicates, associations on HubSpot recordsHubSpot
Integration disconnects, auth errors, number lists, recording URLs, agent mappingPhone vendor
Calling window blank or provider missingStart with the vendor, then HubSpot

HubSpot's help content often redirects integration issues to the vendor, so lead with your isolation-test results to show where the failure sits.

How do you prevent logging failures with a phone system?

Choose a phone system whose HubSpot sync handles the failure points above by design, then keep your data clean. Prevention is mostly about matching, mapping and visibility, not features on a checklist.

Data quality is the underlying risk. Validity's State of CRM Data Management in 2025 surveyed 602 CRM users and stakeholders and found that 76% say less than half of their organization's CRM data is accurate and complete, and 37% say they lost revenue directly because of poor data quality.

What to look for

  • Auto-log with a clear status view: you can see when the connection is healthy or expired.
  • Number mapping: E.164 handling, extension support and configurable match rules.
  • Duplicate handling: a clear rule for unknown callers and shared numbers.
  • User mapping: agents tied to HubSpot users, with visible mismatches.
  • Recording and summary sync: recordings and notes that land on the same record as the call. See the comparison of AI call summary tools.

How Voicalyst approaches this

Voicalyst is a browser-based business phone system with a HubSpot calling integration, call recording and AI call summaries. Because calling and sync live in one product, there is no separate CTI to fall out of registration, and you have one place to check when a call is missing. If you manage a larger team, the small call center setup guide covers agent setup. To see how the HubSpot sync would work with your records, book a demo or visit Voicalyst.

Frequently Asked Questions

Why are my calls not logging in HubSpot?

The usual causes are an expired integration connection, the wrong calling provider selected, an agent email that does not match a HubSpot user, a number that does not match any contact, or a line not enabled for logging. Run one test call to see whether the failure affects all calls or only some.

Why is my call recording missing in HubSpot?

Either the call was never recorded or the recording did not sync. Never recorded usually means "Allow call recording" is off, consent was not confirmed in an all-party state, or the call never connected. Recorded but missing points to the phone vendor's recording URL or token.

Does HubSpot log missed calls and voicemails?

It depends on the calling path. Numbers provided by HubSpot and connected third-party systems can behave differently, and vendor documentation reports that registered outbound numbers cannot log inbound calls or voicemail. Test a missed call and a voicemail on your own setup, then confirm against your vendor's documentation.

Can I log a call manually in HubSpot?

Yes. You can create a call activity by hand on a contact record and enter the outcome, duration and notes. Manual logging is a stopgap for important calls, not a fix. It will not attach a recording, so still diagnose why automatic logging failed.

Put this into practice with Voicalyst

Voicalyst is the cloud phone system US sales and support teams set up in minutes: a business phone system with cloud telephony, AI call summaries and texting.

Start free trialBook a demo
VE

Voicalyst Editorial Team

Guides and research from the team building Voicalyst.