Blog / HubSpot And CRM Integration

HubSpot Call Tracking: Outcomes, Properties and 6 Report Recipes

HubSpot tracks call activity natively but not campaign source. This guide gives you an outcome naming convention, a property schema and six call report recipes built on real HubSpot call properties.

HubSpot call tracking means two different things, and HubSpot handles only one of them fully. Natively, HubSpot logs every call's direction, duration, status, outcome, call type, notes and recording against the right contact, deal or ticket. What HubSpot does not do natively is tell you which ad or campaign made the phone ring, because it has no dynamic number insertion or tracking number pools. This guide covers the logging side in depth: how to name your call outcomes so reports build in one filter, which custom properties to create, and six report recipes you can build today. A short section at the end covers attribution add-ons.

Key takeaways

  • HubSpot's six default call outcomes are Busy, Connected, Left live message, Left voicemail, No answer and Wrong number, stored in hs_call_disposition as internal IDs.
  • HubSpot custom call outcomes require Professional or Enterprise, are capped at 30 per account and 50 characters each, and cannot be edited after saving.
  • HubSpot's "Make call outcome required" setting covers only outbound browser calls and already-logged calls, so inbound, mobile and imported calls can lack outcomes.
  • HubSpot stores call duration (hs_call_duration) in milliseconds in the API, so connect rate should come from call outcome, not a duration threshold.
  • A prefix scheme for HubSpot call outcomes (CONN, NC, BAD) groups connected, not-connected and bad-data results so every report starts from three buckets.

What does "HubSpot call tracking" actually mean?

HubSpot call tracking refers to either activity logging, which records what happened on each call inside the CRM, or source attribution, which ties an inbound call to the campaign, keyword or page that generated it. HubSpot handles activity logging natively on its paid Sales and Service Hub plans. Source attribution requires tracking numbers from a third-party tool.

Activity logging: what happened on each call

Activity logging is the record of the call itself: who called whom, when, for how long, what the result was and what was said. This is what sales managers need for connect rates and coaching, and what support leads need for missed-call follow-up. HubSpot does this well once the outcomes and properties are set up deliberately.

Source attribution: which campaign made the phone ring

Source attribution answers "did this call come from Google Ads, a mailer or the pricing page?" It usually relies on dynamic number insertion, which is a script that swaps the phone number shown on your website based on the visitor's traffic source, so each source gets its own trackable number. HubSpot does not offer that natively.

What this guide covers and what needs an add-on

Everything from outcomes through report recipes works inside HubSpot. The final section explains what to look for if you also need campaign attribution or a phone system that writes richer call data back to HubSpot. If you have not connected calling yet, start with our HubSpot phone integration setup guide.

What does HubSpot log on every call by default?

HubSpot logs each call as an activity record with a status, outcome, call type, direction, duration, from and to numbers, owner, notes, recording and associated CRM records. Status, outcome and call type are three separate fields that answer three separate questions, and mixing them up is the most common reason HubSpot call reports show numbers nobody trusts.

Status vs. outcome vs. call type: three different fields

  • Status (hs_call_status) is the technical result set by the phone system. Valid values are BUSY, CALLING_CRM_USER, CANCELED, COMPLETED, CONNECTING, FAILED, IN_PROGRESS, NO_ANSWER, QUEUED and RINGING, according to HubSpot's calls API documentation.
  • Outcome (hs_call_disposition) is what happened from a business point of view: connected, voicemail, wrong number. The rep or the dialer sets it.
  • Call type (hs_activity_type) is the purpose of the call: Discovery, Demo, Follow-up, Support.

A call can have a status of COMPLETED (the line connected technically) and an outcome of "Left voicemail." If you count COMPLETED calls as conversations, voicemails inflate your connect rate.

Core call properties

Property labelInternal nameWhat it answersSet by
Call statushs_call_statusDid the call technically go through?System
Call outcomehs_call_dispositionWhat happened on the dial?Rep or dialer
Call and meeting typehs_activity_typeWhy was the call made?Rep
Call directionhs_call_directionInbound or outbound?System
Call durationhs_call_durationHow long was the call?System
Has voicemailhs_call_has_voicemailIs the recording a voicemail?System
From / to numberhs_call_from_number / hs_call_to_numberWhich numbers were involved?System
Activity assigned tohubspot_owner_idWhich rep owns it?System or rep
Call noteshs_call_bodyWhat was discussed?Rep or AI summary

Two details matter for reporting. The default outcomes are stored as internal GUIDs rather than readable labels, and hs_call_duration is stored in milliseconds, per HubSpot's developer docs. A 45-second call exports as 45000.

Plan and seat requirements

What you can do depends on tier. Custom call outcomes need Professional or Enterprise. HubSpot calling minutes are pooled across the account, adding minutes requires Professional or Enterprise, and transcription requires an assigned Sales or Service seat, according to HubSpot's call settings documentation. Check your current plan in HubSpot before you design around a feature, because packaging changes.

How should you name HubSpot call outcomes before creating them?

HubSpot call outcomes should follow a fixed prefix convention, planned in full before the first one is created, because a saved outcome cannot be edited. Prefixing every custom outcome with CONN, NC or BAD groups connected, not-connected and bad-data results together, so connect-rate reports and contact lists filter on one clean set of values.

Why you cannot rename outcomes later

HubSpot does not allow edits to a custom call outcome after it is saved, because changing it could alter historical reporting data (HubSpot knowledge base). A typo or a vague label like "Good call" stays forever. Deleting an outcome also removes it from workflows and segments that reference it.

Governance rule: deprecate, don't rename. When an outcome is wrong, create the replacement, tell reps to stop using the old one, and keep the old one until your reporting window no longer needs it.

A naming convention that makes reports one filter

Use a short uppercase prefix, a spaced hyphen, then plain language:

  • CONN = a live conversation with the right person
  • NC = no conversation (no answer, voicemail, busy)
  • BAD = data problem or compliance stop (wrong number, do not call)

Because outcomes sort alphabetically in filter dropdowns, every CONN value sits together. Building "connected calls" means selecting the CONN block once, and connect rate becomes CONN divided by all outcomes. The prefixes cost 7 characters, leaving 43 of the 50 allowed for the description.

HubSpot's six defaults keep their original names. Either instruct reps to use only the prefixed custom set, or add Connected and Left live message to your CONN filters, No answer, Busy and Left voicemail to NC, and Wrong number to BAD.

  1. CONN - Meeting booked
  2. CONN - Interested, send info
  3. CONN - Callback requested
  4. CONN - Not interested
  5. CONN - Not a fit
  6. CONN - Gatekeeper, referred
  7. NC - No answer
  8. NC - Voicemail left
  9. NC - Busy
  10. BAD - Wrong number
  11. BAD - Do not call
  12. BAD - Number disconnected
  1. CONN - Resolved on call
  2. CONN - Escalated to ticket
  3. CONN - Callback scheduled
  4. NC - Missed inbound
  5. NC - Voicemail received
  6. NC - Callback attempted, no answer

Together that is 18 outcomes, leaving 12 of the 30 slots for future needs. Leaving headroom matters more than covering every edge case on day one.

Mapping dialer dispositions to HubSpot outcomes exactly

Third-party dialers and phone systems write to hs_call_disposition, and the value they send must match an existing HubSpot outcome exactly. "Voicemail left" in your dialer and "NC - Voicemail left" in HubSpot are different values, and mismatches usually produce blank or unmapped outcomes.

Create the HubSpot list first, then copy each label character for character into the dialer's mapping screen. Integrations that map by internal ID are more reliable than ones that match on text. Our power dialer for HubSpot comparison covers how sync depth differs between tools.

How do you set up call outcomes, call types and required logging in HubSpot?

HubSpot call outcomes are created under Settings > Calling > Call Configurations > Track call outcomes > Edit options, on Professional or Enterprise plans. Call types are managed in the activity settings, and the "Make call outcome required" toggle enforces outcomes on outbound browser calls. Recording, transcription and inbound consent messages live in the same calling settings area.

Create custom call outcomes (step by step)

  1. Write the full outcome list in a spreadsheet and get sign-off from sales and support leads.
  2. In HubSpot, go to Settings > Calling > Call Configurations.
  3. Under Track call outcomes, click Edit options.
  4. Add each outcome, checking spelling and spacing before saving. Each is limited to 50 characters, with a maximum of 30 custom outcomes.
  5. Save, then test by logging a call and confirming the value appears in a report filter.

Set up call types

Call types live in the "Call and meeting type" property (hs_activity_type), which you manage in HubSpot's activity settings. Keep the list short, for example Discovery, Demo, Follow-up, Renewal, Support and Inbound inquiry. Do not put outcomes in call types or call types in outcomes. "Demo - No show" belongs as call type Demo plus an outcome.

Turn on "Make call outcome required" and its blind spots

In call settings, enable Make call outcome required. HubSpot states this applies only to outbound calls placed from the HubSpot browser or to calls already logged; inbound, mobile and imported calls are not affected. If your support team takes inbound calls or reps call from their phones, expect gaps. The clean-data section below covers workarounds.

HubSpot lets you enable call recording and play a consent message on inbound calls. Transcription requires an assigned Sales or Service seat.

Compliance note. US recording law varies by state. States commonly cited as requiring consent from all parties include California, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania and Washington, and Connecticut has its own rules.

Interstate calls can pull in the stricter state's law. Turn on the inbound consent message, tell outbound callers they are being recorded, and have counsel review your policy. This is not legal advice.

Which custom properties should you create for call reporting?

HubSpot's native call properties describe single calls, so contact-level and deal-level custom properties are needed to answer questions like "how many dials before we connect?" or "who has gone quiet?" Four contact properties and two deal properties cover most sales and support reporting, populated by workflows or by a phone system integration.

PropertyObjectField typePopulated byPowers
Last Call OutcomeContactDropdown (same values as outcomes)Workflow or integrationLists, re-engagement workflows
Last Connected DateContactDateWorkflow on CONN outcomes"Not reached in 30 days" lists
Connected Call CountContactNumberWorkflow increment or rollupEngagement scoring
Dials Since Last ConnectContactNumberWorkflow increment, reset on CONNDials-to-connect recipe
First Call DateDealDateWorkflow or rollupSpeed-to-first-call
Calls Before MeetingDealNumberRollup or workflowSales efficiency
Call Lead SourceCallSingle-line text or dropdownCall tracking integrationAttribution reports

Workflows that populate them

The pattern for each workflow is the same: trigger when a call is logged with a given outcome, then update the associated contact or deal.

  • CONN outcome logged: set Last Call Outcome, set Last Connected Date to today, add 1 to Connected Call Count, reset Dials Since Last Connect to 0.
  • NC outcome logged: set Last Call Outcome, add 1 to Dials Since Last Connect.
  • BAD - Do not call logged: set Last Call Outcome and remove the contact from active sequences and call lists.

Call-based workflow triggers, calculated properties and rollups depend on your Hub and tier, so confirm what your account supports before committing. If workflows are unavailable, a phone system that writes these fields directly is the alternative.

Six HubSpot call report recipes

The six recipes below use HubSpot's custom report builder with Calls as the primary data source, unless noted. Before building, look at the built-in sales analytics metrics for calls made and calls connected, then use these recipes for what they cannot show: outcome-based connect rate, follow-up gaps and talk time by purpose.

1. Connect rate by rep

  • Goal: compare real conversations per rep
  • Data source: Calls
  • Filters: Call direction = Outbound; Create date = last 30 days
  • X axis: Activity assigned to
  • Y axis: Count of calls
  • Breakdown: Call outcome, grouped into CONN / NC / BAD
  • Chart: 100% stacked bar
  • Tip: if your tier supports report formulas, add CONN count divided by total. A rep with high volume and a low CONN share may be calling bad lists, not underperforming.

2. Outcome mix by week

  • Goal: spot shifts in answer rates or list quality
  • Data source: Calls
  • Filters: Outbound; last 12 weeks
  • X axis: Create date, weekly
  • Y axis: Count of calls
  • Breakdown: Call outcome
  • Chart: stacked column
  • Tip: a rising BAD share points to data quality; a rising NC share points to timing or caller ID problems.

3. Dials-to-connect ratio per contact

  • Goal: find contacts being over-dialed
  • Data source: Contacts
  • Filters: Dials Since Last Connect is greater than 5
  • Columns: Contact owner, Dials Since Last Connect, Last Call Outcome, Last Connected Date
  • Chart: table, sorted descending
  • Tip: set a team rule such as moving contacts to email after 8 unanswered dials.

4. Connected calls to meetings booked

  • Goal: measure whether conversations turn into meetings
  • Data source: Calls, plus Meetings as a second data source joined through associated contacts
  • Filters: Call outcome is any CONN value; last 30 days
  • X axis: Activity assigned to
  • Y axis: Count of connected calls and count of meetings
  • Chart: grouped bar
  • Tip: for a simpler version, report on "CONN - Meeting booked" against all other CONN outcomes per rep.

5. Inbound missed calls and voicemails awaiting follow-up

  • Goal: make sure no inbound caller is ignored
  • Data source: Calls
  • Filters: Call direction = Inbound; Call outcome is NC - Missed inbound or NC - Voicemail received, or Has voicemail = true; last 7 days
  • Columns: Create date, From number, Associated contact, Activity assigned to
  • Chart: table
  • Tip: hs_call_has_voicemail separates voicemails from ordinary recorded inbound calls, which keeps this list accurate even when reps forget to set an outcome. Pair it with voicemail transcription so agents can triage without listening.

6. Talk time by call type

  • Goal: see where rep time actually goes
  • Data source: Calls
  • Filters: Call outcome is any CONN value
  • X axis: Call and meeting type
  • Y axis: Sum or average of Call duration
  • Chart: bar
  • Tip: a long average for Follow-up calls often means discovery is happening too late.

Building the call dashboard

Put recipes 1, 2 and 5 on one dashboard for daily stand-ups, and recipes 3, 4 and 6 on a weekly review dashboard. Add the unlogged-calls report from the next section to both.

How do you keep HubSpot call data clean?

HubSpot call data stays clean when every call gets an outcome, connect rate is calculated from outcomes instead of duration, and a weekly report catches gaps the required-outcome setting misses. Three habits do most of the work: a follow-up task for empty outcomes, a weekly audit, and watching answer rates for caller ID problems.

Workflow: task the owner when a call has no outcome

Create a workflow that enrolls calls where Call outcome is unknown and the call is older than 2 hours, then creates a task for the call owner: "Add outcome to call with [contact]." This catches the inbound and mobile calls the required toggle skips.

Weekly unlogged-calls audit report

Build a Calls report filtered to Call outcome is unknown, last 7 days, broken down by owner and direction. Review it in the weekly meeting. If one rep or one direction dominates, fix the process there. If calls are not appearing in HubSpot at all, our guide to HubSpot calls not logging covers fixes by symptom.

Why connect rate should use outcome, not duration

It is tempting to define a connect as any call over 30 seconds. That fails often: voicemail greetings run long, IVR menus and hold time count as duration, and a quick "not interested" is a real conversation lasting 10 seconds. Duration is also in milliseconds in the API, so a filter written as "greater than 30" catches almost every call. Use outcomes for connect rate and duration for talk time.

Handling answer-rate drops from spam labeling

When NC outcomes climb across every rep at once, suspect caller ID before blaming the list. Calls that arrive without intact STIR/SHAKEN authentication, the industry framework carriers use to verify that a caller is entitled to use a number, are more likely to be labeled as spam. Register your business numbers with the major carrier analytics registries, use consistent local numbers, and track outcome mix by week (recipe 2) to see whether fixes work.

When do you need more than native HubSpot call tracking?

Native HubSpot call tracking is enough when you need activity logging and rep reporting. Teams need an add-on when they want campaign-level attribution through tracking numbers, inbound queues and IVR routing, a power dialer, or AI summaries written into call notes. The deciding factor is how completely the add-on writes data back into HubSpot's call properties.

Campaign and source attribution with tracking numbers

HubSpot has no dynamic number insertion or campaign-level number pools. Call tracking tools assign numbers per source and push the source to HubSpot, ideally into a call-level property like Call Lead Source, so you can break down recipe 4 by channel.

Phone systems that sync calls, outcomes and AI summaries to HubSpot

A phone system with deep HubSpot sync logs every inbound, outbound and missed call with the right outcome, recording link and notes, which removes most of the clean-data work above. AI call summaries matter here because they fill hs_call_body consistently; see our AI call summary guide. Voicalyst is one option: a browser-based phone system with queues, voicemail, a power dialer and AI call summaries, plus a HubSpot calling integration that maps outcomes to your HubSpot list.

Checklist for evaluating a HubSpot-integrated phone system

  • Maps dispositions to HubSpot outcomes by internal ID, including custom outcomes
  • Syncs recording URLs and transcripts to the call record
  • Logs inbound, missed and voicemail calls, not just outbound
  • Associates calls to contacts, companies, deals and tickets
  • Logs texts as HubSpot activities
  • Writes call type, not just outcome
  • States whether minutes are per user or pooled
  • Handles consent messages for recorded calls

For a side-by-side view, see the best VoIP options for HubSpot compared on sync depth. If you want to see outcome mapping and missed-call logging working inside your own HubSpot portal, try Voicalyst.

Frequently Asked Questions

Does HubSpot have call tracking?

HubSpot has native call activity tracking. It logs direction, duration, status, outcome, call type, notes, recordings and the associated records for every call. HubSpot does not natively offer dynamic number insertion or campaign-level tracking number pools, so attributing calls to a specific ad or campaign requires a third-party call tracking tool or phone system that syncs source data.

Can HubSpot record calls automatically?

HubSpot can record calls placed through its built-in calling tool when recording is enabled in your call settings, and it can play a consent message on inbound calls. Transcription requires an assigned Sales or Service seat. Before recording, confirm consent rules for every state you call, because several US states require consent from all parties.

How many custom call outcomes can I create in HubSpot?

HubSpot allows up to 30 custom call outcomes per account on Sales Hub or Service Hub Professional or Enterprise. Each outcome can be up to 50 characters long. An outcome cannot be edited after it is saved, so plan your full outcome list and naming convention before you create anything in Settings.

What is the difference between call outcome and call type in HubSpot?

A HubSpot call outcome (hs_call_disposition) records what happened on the dial, such as connected, no answer or left voicemail. A HubSpot call type (hs_activity_type) records the purpose of the call, such as discovery, demo or support. Keeping them separate lets you report connect rate and talk time by purpose without mixing the two.

Does HubSpot track call duration?

HubSpot tracks call duration on every logged call in the hs_call_duration property. Through the API, hs_call_duration is stored in milliseconds, not seconds, so exports and integrations need converting. Duration is useful for talk-time reporting, but connect rate should be based on the call outcome, because short calls are not reliably connects.

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.