Feature Request: Deduplicate Email Activities Across Connected Channels

HubSpot Ideas
1

Current Behavior

When an email thread includes multiple connected HubSpot channel addresses—for example, an Account Manager’s connected inbox and the Support team email address—HubSpot can log the same email more than once in the contact activity timeline.

This commonly occurs when:

  • A conversation begins through a connected personal inbox.
  • A team email address, such as Support, is later added in CC.
  • The team email address is connected as a Help Desk or Conversations channel.
  • A ticket is created from the conversation.

HubSpot then creates separate activity entries for the same email because it has been processed through multiple channels. One entry may originate from the standard email-logging process, while another originates from the Help Desk or Conversations channel.

This results in duplicate activities with the same sender, recipients, subject, content and timestamp.

Requested Feature

Add an optional setting:

Log only one activity per email thread across connected channels

When enabled, HubSpot should create only one consolidated activity for an email thread, regardless of how many connected channel addresses are included in the From, To or CC fields.

All messages belonging to the thread should remain accessible within that consolidated activity. The email should still retain all relevant associations, including contacts, companies, deals, tickets and conversations.

Expected Behavior

With the toggle enabled:

  • HubSpot recognizes when the same email or thread is received through multiple connected channels.
  • Only one activity is displayed in the CRM timeline.
  • Additional replies are added to the existing thread activity instead of creating duplicate activity cards.
  • All participating channel addresses remain visible in the email details.
  • Ticket creation and Help Desk functionality continue to work normally.
  • The activity retains associations created by every relevant channel.
  • The setting applies to future activities and does not automatically change historical records.

With the toggle disabled, HubSpot should retain its current logging behavior.

Suggested Deduplication Logic

HubSpot could identify matching emails using available email metadata, such as:

  • Email Message-ID
  • Conversation or thread ID
  • Sender and recipient information
  • Subject
  • Sent timestamp

The Message-ID should be used as the primary identifier wherever available.

Example

An Account Manager exchanges emails with a customer and has email logging enabled. Support is later added in CC, and the Support address is connected as a Help Desk channel.

Current result:
The same email appears twice in the contact timeline—once through the Account Manager’s email connection and once through the Support channel.

Expected result with the toggle enabled:
The email appears once. The activity shows that both the Account Manager’s inbox and the Support channel were involved, and it remains associated with the corresponding support ticket.

Business Impact

Duplicate email activities:

  • Make the contact timeline difficult to read.
  • Give users the impression that multiple emails were sent.
  • Complicate reporting and activity analysis.
  • Create uncertainty about which activity should be used.
  • Require users to change their natural email workflow to prevent duplication.
  • Increase the risk of incorrect follow-up decisions.

A channel-level or account-level deduplication setting would provide a clean CRM history without requiring users to disable logging or avoid including team addresses in email conversations.

Acceptance Criteria

  1. An administrator can enable or disable the setting.
  2. When enabled, one physical email is represented by no more than one CRM activity, even when processed through multiple connected channels.
  3. Replies belonging to the same thread are grouped within the same thread activity.
  4. All relevant contacts, companies, deals, tickets and conversations remain associated.
  5. All participating channel addresses remain visible.
  6. Ticket creation, routing, assignment and SLA functionality remain unchanged.
  7. Disabling the setting restores the existing logging behavior.
  8. Existing historical activities are not merged unless a separate administrator action is provided.