Imagine if Opportunities view and Conversations view had a baby. Then their baby had a baby.

Merge Conversations and Pipelines into One Unified Workspace

Conversations and Opportunities often represent the same customer interaction, but HighLevel currently treats them as separate systems with independent statuses.

Users recreate the Conversations inbox inside pipelines because they need visible stages, drag-and-drop organization and additional opportunity information. Pipelines, however, lack the simplicity and familiarity of an inbox.

Could HighLevel treat Conversations and Pipelines as two views of the same workspace?

Proposed views:

Inbox: Optimized for reading and replying, with Unread, Recent, All and Starred filters.

Pipeline: The same contacts and conversations organized into customizable stages.

Split: Pipeline stages and the selected conversation visible together.

Shared functionality:

• Conversation status and opportunity stage become one shared, customizable status.

• Moving a pipeline card changes the stage shown in Conversations.

• Changing the stage from a conversation moves the pipeline card.

• Inbox cards display opportunity value, stage, source, assignment and other pipeline information.

• Pipeline cards display unread status, starred status and the latest message.

• Opening a record from either view displays the same conversation, contact and opportunity information.

• Unread and Starred remain message indicators, not separate workflow stages.

• Starred conversations remain visible in the inbox until manually unstarred.

• Global Unread and Starred counters remain visible in the navigation or header throughout HighLevel.

The recently added conversation slide-in within Opportunities is a strong first step. Combining these areas into one workspace would eliminate duplicate statuses and reduce the workflows currently required to keep Conversations and Opportunities synchronized.

The attached UI concept shows how the Inbox and Pipeline views could share the same records, stages and conversation information while preserving the important functionality of both areas.