Opportunities & Pipelines

it appears right now the Order of the Pipelines is simply in the order they were created, when viewing them in the dropdown. Additionally, in the mobile app, it appears you're only given the open to view the most recent Pipeline created, not all the pipelines, and not a default or preferred pipeline. Please allow us to order and prioritize the pipelines in any order we choose, and add all pipelines to the mobile app, thanks! HIGHLVL-I-1366

When a sales rep is manually moving a deal between stages, we often need to make sure that they're capturing certain data. So if they finish a sales call, we might want to know their confidence level, or the products/services they're interested in, etc. Here's an example of how it works in HubSpot: https://share.vidyard.com/watch/z9pfGzPc9umdQznYSRp1Wv ?. If you could recreate this type of functionality, that would be awesome.

Currently, if I set an advanced filter to check a specific salesperson's performance, that filter disappears the moment I switch to a different pipeline. This is a huge friction point for our daily operations. We’ve tried using Smart Lists as a workaround, but it’s not practical. When you have a large team with many salespeople across multiple pipelines, you end up with dozens of Smart Lists that just clutter the workspace. It’s messy and hard to manage at scale. We need a way to "lock" these filters so they stay active as we navigate through different pipelines. Manually re-applying the same filter over and over again is a waste of time. Please look into making these filters persistent or adding a toggle to keep them active across the entire session.

It would be great if we can have different fields/custom fields display in different pipelines. For Example: If I have Residential/Commercial Clients. I would like to run two different pipelines; one for Residential & one for Commercial. However it's hard to judge, categorize, and organize a large Commercial clients by the same field parameters as a Residential Client & vise versa. If we can have certain fields within certain pipeline that would allow us to provide much more attentive to detail services for our customers.

There are values computed by the system that teams managing specific custom objects shouldn't be able to modify. Example: 1- policy Number (generated following specific convention) 2- Dates that exist to track specific actions (ie: Policy got active, or cancelled, etc.) 3- There are multiple use cases where the system needs to generate a value, and people should not be able tto change those read-only values but others in the object. A simple approach would be to have a custom field that act as a label (just text), so when the system fill-out that custom field (that is just readable text), no one can change it out , except a system . See attached image where I show a custom field which is a Policy Number, and also some values managed by the system (people should not be able to modify them (green square)) the support managing the policy should not be able to change it at all, so instead a input field , it can be just a label text (as it looks on the red line value)

Thank you for giving us the fields for Additional Contacts and Followers of Opportunities. However, we use HighLevel because it does things, not as a data repository. The ability to take action on the data is as important as having access to the data. Therefore, please prioritize adding Workflow actions &/o filters that would allow sending emails and text to Additional Contacts and Followers with these options (maybe more): a. Primary Contact only (current behavior). b. Primary plus Additional Contacts. c. Primary Contact plus Additional Contacts and Followers. d. only Followers. e. Owner. f. Primary Contact and Owner. g. Primary plus Additional Contacts and Owner. h. Primary plus Additional Contacts and Owner with Followers. i. only Owner and Followers. I imagine Workflow triggers will still be cued off only the primary contact or opportunity. And I imagine that only the Opportunity or the Primary Contact could be in the Workflow. And some messages would only need to be seen by the primary contact. But we would also want the ability to communicate with the additional people involved in the process. https://www.facebook.com/groups/gohighlevel/posts/2254471355012387/ Regarding Point 4 & 5: Is there a planned release for Workflow options to notify only the Primary Contact (current behavior) or Primary plus Additional Contacts or Primary Contact plus Additional Contacts and Followers or only Followers? This is not a new feature. This is the obvious operational use of having Additional Contacts and Followers. Without the ability to take action, the fields are mere data, manually typed…

Estimates and Invoices are listed in the Opportunity Card under 'Payments', but they don't link to the Estimates and Invoices for quick viewing. This is a frustrating user experience for the client as they need to close the Opportunity and manually navigate to the estimate/invoice section, go thorugh drop down menus, then scroll through a list to find the invoice or esitmate that was mentioned in the Opportunity. Please can you make these clickable for quick viewing? Also, can you add some sort of information, like the invoice numbner or title, so you can tell them apart in the Opportunity list please? Thanks.

It would be great if we could hide fields in Opportunities similar to how we can in contacts

Add the ability for admins to turn on a feature which makes completing the lost reason field mandatory when marking a opportunity lost. This forces the Sales team to capture lost reasons, otherwise we are missing out on important sales intelligence/data.

❌ Problem: Documents, Estimates, Invoices, Tasks, etc, are tied to Contacts, not Opportunities Today, Estimates, Documents, and Invoices are technically sent to a Contact, but in 95% of real use cases, they are meant for the Opportunity. Why does this not make sense: Opportunities are where the actual sales process happens, not at the contact level. Opportunity fields are useless when everything is Contact-focused. Using contact-level fields for Opportunities leads to awkward workarounds. Sales teams think in terms of deals/projects (Opportunities), not people (Contacts). We lose context and tracking when documents are tied to contacts instead of the opportunity they belong to. Data should still be accessible at the Contact level, but always tied to the right Opportunity. ✅ Suggested Solution: Make Opportunities the primary object for sending and managing documents, estimates, invoices, tasks, etc. And if this doesn't work for all users, offer it as a toggle setting. But this logic fits any lead-driven business. ➕ Make the opportunity as the main / default receiver of Estimates, Documents and Invoices. ➕ Add the ability to easily Send Estimate, Document, or Invoice directly from the Opportunity card. ➕ Allow switching between Contact-based and Opportunity-based workflows. ➕ Opportunity workflows would finally allow the intended use of Custom Opportunity Values. ➕ Add activity history in Opportunity view (similar to what we have in Contact conversations). 🔥 Project Management: Convert Opportunities to Projects (or Custom Objects?) An Opportunity is essentially a project before it becomes a signed contract/won opportunity. The platform should reflect this. I don't know how this would be done or how it would make sense for GHL's existing roadmap with Custom Object, but this would make sense on a structural level. ➕ Allowing for automatically creating projects on signed / Won. ➕ Link Opportunity fields to Custom Object fields. ➕ Link Opportunity tasks to Project tasks (or Custom Object tasks?). ➕ Now the Opportunity-based workflows become a project-based (or Custom object-based) workflow. 👉🏼 Please let me know if this does or doesn't make sense and why!