Summary I would like to report what appears to be a recent regression in the Opportunities → View Conversations → Contact Details workflow. Approximately one week ago, this workflow had a very useful navigation behavior that now appears to have been removed. When a user opened a contact from an Opportunity card using “View Conversations”, the Contact Details view opened over the Opportunities Pipeline. In the upper-left corner of the Contact Details view, there was a control that allowed the user to collapse/minimize the Contact Details view without leaving the Opportunities page. This was extremely valuable because the underlying Pipeline remained intact, including its current horizontal scroll position. That behavior is now gone. I am requesting that the previous behavior be restored, or that an equivalent non-destructive navigation mechanism be provided. Exact Previous Workflow Go to Opportunities. Open a Pipeline in Kanban view. Horizontally scroll to the desired stage. Locate an Opportunity card. Click the “View Conversations” icon. HighLevel opens Contact Details. Contact Details covers the Opportunities board. In the upper-left corner, there was a button/icon that allowed Contact Details to be collapsed/minimized while remaining in the Opportunities context. Clicking it returned the user directly to the same Pipeline. Most importantly, the Pipeline did not need to reload or reconstruct. The user could immediately continue working from exactly the same location. Why This Was Different From Simply Going Back to Opportunities The previous behavior was not simply a Back button. It preserved the state of the Opportunities board. For example, imagine a Pipeline with 30 stages: Stage 01 → Stage 02 → ... → Stage 24 → Stage 25 → Stage 26 → ... → Stage 30 If the user was working on Stage 25, they could open an Opportunity, inspect the conversation, and collapse Contact Details. They would return directly to: Stage 25 The Pipeline remained horizontally positioned exactly where they had been. Current Behavior / Regression Today, after opening: Opportunities → Opportunity Card → View Conversations the Contact Details view takes over the screen. To return to the Pipeline, the user effectively has to navigate back to Opportunities. The Opportunities board is then reloaded/reinitialized, and the horizontal Pipeline position is lost. For example: Before opening Contact Details: Stage 01 → ... → Stage 24 → [Stage 25] → Stage 26 → ... → Stage 30 After returning to Opportunities: [Stage 01] → Stage 02 → Stage 03 → ... → Stage 30 The user must manually drag the horizontal scrollbar through 25+ stages to return to where they were. For large Pipelines, this is extremely frustrating and significantly slows down the workflow. Why This Is a Significant UX Regression This is not merely a cosmetic UI preference. A Pipeline is a working environment. Users often process Opportunities sequentially while moving between the Pipeline and Contact Details. The natural workflow is: Pipeline → inspect contact → read conversation → return → continue working The previous implementation made this almost instantaneous. The current behavior introduces unnecessary navigation, reloads the Pipeline and causes users to lose their working position. This creates a significant context-switching penalty, particularly for agencies and businesses managing large Pipelines. Real-World Example Suppose a user is processing Opportunities in a Pipeline with 30–50 stages and is currently working around Stage 25. Previously: Click View Conversations. Review the contact/conversation. Click the collapse control. Immediately continue working around Stage 25. Now: Click View Conversations. Review Contact Details. Navigate back to Opportunities. Wait for the Pipeline to reload. Pipeline returns to the beginning. Manually scroll horizontally through 25+ stages. Find Stage 25 again. Continue working. The difference is substantial when repeated dozens or hundreds of times. This Is a Restoration Request, Not Simply a New Feature Request This distinction is important. I am not requesting a completely new Quick View feature. I personally used this functionality approximately one week ago, and it was working as described above. It subsequently disappeared. Therefore, this should be treated as a regression/removal of an existing productivity feature, rather than merely a request for a new feature. Screenshots Screenshot 1 — Opportunities The user is inside: Opportunities → Pipeline → Kanban View Each Opportunity card contains the “View Conversations” icon. Clicking it opens Contact Details. Screenshot 2 — Contact Details Contact Details covers the Opportunities board. In the previous interface, the area indicated in the screenshot contained a control that allowed Contact Details to be collapsed/minimized. That control allowed the user to return to the Pipeline without leaving the Opportunities context and without reloading the Pipeline. That control is now missing. Expected Behavior When Contact Details is opened from an Opportunity, HighLevel should provide a way to: Collapse / close Contact Details while preserving the underlying Opportunities board state. The following state should remain intact: Current Pipeline Current Pipeline view Current horizontal scroll position Current vertical position, if applicable Loaded Opportunity cards Filters Sorting Current stage position Other relevant transient UI state The ideal workflow is: Opportunities → Opportunity Card → View Conversations → Contact Details → Collapse → Exact Same Pipeline State No full Opportunities page reload should be necessary. Important UX Requirement Please do not solve this simply by adding another link that navigates back to Opportunities. The key requirement is: Return to the existing Opportunities board instance without reconstructing/reloading it whenever possible. The value of the previous behavior was precisely that the Pipeline remained alive underneath Contact Details. A side-panel, overlay, split-screen or equivalent implementation would also be acceptable, provided that the underlying Pipeline remains active and preserves its state. Relationship to the Recent CRM Redesign I understand that HighLevel has recently been redesigning the Contact Detail Page and Conversations experience. HighLevel's own product updates describe a major redesign of Contact Details and a new Conversations experience as part of the broader CRM redesign. This request is particularly relevant because the removed behavior was part of the interaction between Opportunities, Contact Details and Conversations. I am not asking only for conversations to be displayed on Opportunity cards. The specific request is to restore the non-destructive Contact Details collapse/navigation behavior that allowed users to inspect a contact and then return to the exact same Pipeline state. Suggested Product Behavior When Contact Details is launched from: Opportunity → View Conversations provide a control such as: ← Collapse / Return to Pipeline The control should: Keep the user in the Opportunities context. Avoid reloading the Pipeline. Preserve horizontal scroll position. Preserve filters and sorting. Preserve the selected Pipeline. Preserve the existing Kanban state. Return the user to exactly where they were before opening Contact Details. Acceptance Criteria I would consider this issue resolved if: Open Contact Details View Conversations continues to open Contact Details. Return without reload A control allows the user to close/collapse Contact Details and return directly to Opportunities. Preserve horizontal position If the user was viewing Stage 25 of a 30-stage Pipeline, returning keeps them at Stage 25. Preserve Pipeline state Filters, sorting, selected Pipeline and other relevant board state remain unchanged. Avoid unnecessary reconstruction The Opportunities board is not fully reloaded merely because the user inspected a Contact. Fast workflow The user can perform: Opportunity → View Conversation → Read → Return without losing context. Why This Should Be Restored A CRM Pipeline is fundamentally a workspace, not simply a list of records. Users establish a position in that workspace and process Opportunities sequentially. The previous behavior eliminated unnecessary context switching: Review → Act → Continue It was simple, fast and highly efficient. Removing it forces users to repeatedly reload the Pipeline and manually recover their previous position. For users working with large Pipelines, this creates a substantial productivity loss. Request Please consider restoring the previous Contact Details collapse / return-to-Pipeline behavior when Contact Details is opened from an Opportunity. This does not need to be implemented exactly as before; an equivalent solution is completely acceptable. The essential requirement is: Allow users to inspect Contact Details and then return to the exact same Opportunities Pipeline state without losing their position or unnecessarily reloading the Pipeline. This was a very effective workflow, and restoring it would provide a meaningful improvement in CRM usability and productivity.