HubSpot is making an important change to how recorded meetings are logged, and while it may sound like a small backend update, I think it matters a lot for reporting, automation, and general CRM cleanliness.
Starting in August 2026, HubSpot will simplify how recorded meetings are tracked when they come from Notetaker, Zoom, Google Meet, or Microsoft Teams. Today, those recorded meetings can create both a Call record and a Meeting record in HubSpot. After this update, they will only create a Meeting record.
Call records are not going away. Calls will still exist for actual phone activity. But recorded meetings will no longer create duplicate Call records.
As a HubSpot consultant and member of the HubSpot Partner Program, I see this as a smart move toward cleaner CRM data. It also means HubSpot admins and revenue teams need to take a closer look at any workflows, reports, or processes that currently rely on Call records for meeting activity.
What is changing in HubSpot?
Right now, if your team records meetings through HubSpot Notetaker or connected video tools like Zoom, Google Meet, or Microsoft Teams, HubSpot may log that activity in two places: as a Call and as a Meeting.
That can create confusion.
Was the interaction a call? Was it a meeting? Should it count toward call activity, meeting activity, or both? If your sales reports are already difficult to interpret, duplicate engagement records can make things even harder.
With this update, HubSpot is moving toward a cleaner model: one recorded meeting equals one Meeting record.
That Meeting record will become the place where related meeting details live, including transcripts, recordings, summaries, and meeting-related properties such as duration and transcript information.
Why this update matters
The biggest benefit is more accurate reporting.
When the same interaction creates both a Call and a Meeting record, it can inflate activity reporting. Sales teams may appear to have more call activity than they actually do, simply because recorded meetings were also being counted as calls.
Once HubSpot removes those duplicate Call records for recorded meetings, some dashboards may show a drop in Call volume. That drop does not necessarily mean your team is doing less. It means the data is becoming more accurate.
That distinction is important.
As a HubSpot consultant, I often see teams rely heavily on activity reporting to understand rep performance, sales follow-up, pipeline health, and customer engagement. If the underlying activity data is messy, the reports built on top of that data become harder to trust.
This update helps separate true phone calls from recorded meetings, which should make HubSpot reporting cleaner and easier to explain.
The workflows piece is just as important
Reporting is the obvious area to review, but workflows may be the bigger operational risk.
If you currently have workflows that trigger when a Call is created, and those workflows were intended to capture recorded meetings, those workflows may stop working for those meetings after this change goes live.
For example, you may have workflows that:
- Create follow-up tasks after recorded sales calls
- Update lifecycle or lead status based on meeting activity
- Notify managers when certain calls include transcripts
- Count meaningful conversations or sales activity
- Trigger internal alerts based on call duration or recording data
If those workflows are built on the Call object but the activity will soon live only on the Meeting object, they need to be reviewed and likely rebuilt.
HubSpot is adding key meeting properties to support the transition, including properties related to transcripts and duration. That means admins can begin recreating workflows and reports around Meeting records instead of Call records.
What HubSpot users should do before the change
This is one of those updates where the work is less about learning a new feature and more about preventing avoidable breakage.
Before the change goes live, I’d recommend auditing three areas of your HubSpot portal.
First, review any workflows that use Call-based triggers or Call properties. Pay special attention to workflows that are really intended to support meeting follow-up, recorded meeting analysis, or sales activity tracking.
Second, review your reports and dashboards. If any reports are filtering by Call activity or Engagement activity to measure meetings, those reports may need to be updated to use Meeting data instead.
Third, make sure your team knows where to find recordings and transcripts moving forward. HubSpot is shifting recorded meeting details to the Meeting index page and individual Meeting records, so teams that are used to looking on the Call index page may need a quick process update.
My take as a HubSpot consultant
I like this update because it supports something I care about in every HubSpot portal: cleaner data architecture.
HubSpot has become a much more powerful platform over the years, especially for companies using it across marketing, sales, service, operations, and customer success. But as portals become more complex, small data structure issues can create big reporting problems.
Duplicate activity records are one of those problems.
At first, they may seem harmless. More activity looks like more productivity. But eventually, teams start asking why reports do not line up, why workflows are firing unexpectedly, or why managers cannot get a clear view of what is actually happening with prospects and customers.
This update is HubSpot making the data model more logical. A meeting should be a meeting. A call should be a call. Recorded meeting intelligence should live on the Meeting record.
That is good for admins, good for reporting, and good for teams that want to trust the information inside their CRM.
Why this matters for growing teams
For smaller teams, this update may only require a few workflow and report changes.
For larger HubSpot portals, especially those with multiple sales teams, custom reporting, integrations, or RevOps processes, this is worth treating as a mini-audit.
The risk is not that HubSpot is removing useful data. The risk is that some portals have built useful processes around the old structure.
If your team has been using Call records as a proxy for recorded meetings, now is the time to clean that up.
The good news is that this change should make things better in the long run. Your reporting should be more accurate. Your activity data should be easier to interpret. And your team should have a clearer place to find meeting recordings, transcripts, and summaries.
What to do after the change goes live
Once the update is live, check your dashboards and activity reports carefully.
A decrease in Call volume may be expected because recorded meetings will no longer be counted as calls. Instead of treating that as a performance problem, validate whether meeting activity is now showing correctly under Meeting records.
Then, turn on or finalize any updated workflows that use Meeting-based triggers. Make sure any internal documentation, sales process notes, or team training materials point users to the Meeting index page for recorded meeting details.
Final thoughts
This is exactly the kind of HubSpot update that can be easy to overlook but important to act on.
It is not a flashy new feature. It is a data quality improvement. And those are often the updates that matter most.
Better reporting starts with better structure. By eliminating duplicate Call records for recorded meetings, HubSpot is helping teams get closer to a cleaner, more reliable view of sales activity.
If your portal uses recorded meetings, call-based workflows, or activity reporting, this is a good moment to audit your setup before the change goes live.
Read the HubSpot knowledge base article here.