Display Side Conversations in the User Profile Conversation History | Community
Skip to main content
Submitted

Display Side Conversations in the User Profile Conversation History

Related products:Proactive SupportCore InboxMessenger
  • May 28, 2026
  • 0 replies
  • 13 views

Problem Statement / Use Case:
Currently, side conversations do not surface in a customer’s Intercom profile under their "Latest conversations" or complete conversation history.

This creates a significant blind spot for support and operations teams. When an agent reviews a customer's profile to get a quick snapshot of their history or active issues, they completely miss parallel threads, third-party escalations, or external updates happening inside side conversations unless they manually dig into every single parent ticket.

Proposed Solution:
We would like to see side conversations integrated into the customer profile timeline. A few ways this could be implemented include:

  • Nested Visibility: Display side conversations as indented or nested items directly beneath their respective parent conversations within the profile history list.
  • Timeline Toggle/Filter: Add a filter or toggle on the user profile (e.g., "Include Side Conversations") so agents can opt into a truly comprehensive timeline of interactions.
  • Cross-Referencing: If an external side conversation is spun up regarding a customer's ticket, a log or reference link to that side conversation should automatically appear on the primary customer's profile.

Business Impact / Value:

  • True 360-Degree Context: Agents will no longer miss critical background context or parallel threads involving third parties (like vendors, partners, or internal teams) regarding a customer.
  • Increased Efficiency: Eliminates the need for agents to click into multiple old parent tickets just to check if a side conversation was ever initiated, answered, or resolved.
  • Better Customer Experience: Ensures any agent stepping into a case has immediate visibility over the entire operational picture, preventing communication silos and repetitive internal overlapping.