HubSpot ends duplicate call records for recorded meetings starting July 31, 2026
The main change is that, effective July 31, 2026, HubSpot logs any recorded meeting as one meeting record instead of creating both a meeting and a call, removing long‑standing duplicate call entries. HubSpot’s documentation confirms the switch and notes that recordings, transcripts, and AI summaries now live on the meeting record itself, while actual phone calls continue to use the call object. In practice, this cleans up activity counts but requires immediate workflow and reporting updates.
HubSpot changes recorded meeting logging to one meeting record on July 31, 2026
HubSpot’s recorded-meetings guidance states that “recorded meetings will no longer create duplicate call records,” with the new behavior taking effect on July 31, 2026; going forward, a recorded Zoom, Teams, or Google Meet session creates only a meeting record, and all related assets sit on that record rather than a separate call entry. The same page outlines that HubSpot is backfilling key properties from historical call records to their associated meetings so reporting remains usable after the cutover. See the change in HubSpot’s own recorded meetings will no longer create duplicate call records note.
Recorded meetings no longer trigger call-based workflows or call reports
Because recorded sessions now log as meetings, any automation that relied on call-based triggers will stop firing for those interactions. Admins should review enrollment criteria and swap call-object triggers and properties for the meeting equivalents before activity restarts under the new model. HubSpot flags this impact directly in its settings article on conversation recording, which reiterates the July 31 effective date and advises teams to rebuild enrollment using meeting-based logic; details are in configure conversation recording and transcription options.
Meeting transcripts, recordings, and AI summaries move to the meeting timeline
Under the one‑record model, users will no longer find recorded-meeting assets on the Calls index. Instead, recordings, transcripts, and AI summaries appear only on the meeting record and the Meetings index. For teams that review call timelines for quality assurance or coaching, this is a behavior shift worth communicating to reps. HubSpot’s Notetaker documentation points to this exact change and the July 31 timing in record and take notes in Zoom meetings with Notetaker.
Admin checklist for today’s recorded‑meetings change
A common issue is broken automation or miscounted activities when object behavior changes underneath existing processes. To avoid surprises as of July 31, 2026:
- Update workflows that enroll on call objects to use meeting-based triggers and properties; HubSpot notes some teams may need to opt into the Meetings in Workflows beta described in the change notice for recorded meetings.
- Refresh dashboards that count calls or filter by the Call object so recorded meetings don’t disappear from metrics after the cutover.
- Train managers and reps that meeting recordings and transcripts are accessed from the meeting timeline, not the Calls index, as explained in the Notetaker guide.
- Expect fewer total “calls” in historical activity charts beginning with meetings recorded on or after July 31, since duplicates are no longer created.
Why this fix matters for sales activity hygiene
Duplicate logging has frustrated operators for years because a single video meeting inflated activity counts and complicated attribution. Earlier this year, a HubSpot product manager told customers the team planned to stop creating a duplicate call object for recorded meetings, signaling this exact direction; that discussion is visible in the community thread on duplicate meetings and calls. With today’s change in place, recorded meetings finally align to one interaction and one CRM record, which is how most teams expect to measure activity and coach performance.
Share With Others
Platinum
