Opportunities & Pipelines

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…

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.

Overview We would like to suggest a native enhancement for Opportunities/Pipelines inside HighLevel. Currently, Products exist separately inside Payments/Products, but there is no seamless native way to associate multiple products directly within an Opportunity record in a scalable and sales-friendly workflow. This creates friction for SaaS businesses, agencies, CRM resellers, and subscription-based companies using Opportunities for forecasting and revenue management. Suggested Improvement When creating or editing an Opportunity, allow users to: Select one or multiple products directly from the existing Products catalog Automatically calculate the total Opportunity Value based on selected products Support recurring and one-time products Display selected products visually inside Pipeline cards and Opportunity views Use selected products in Forecasting, Reporting, Automations, and Revenue Analytics Proposed Workflow Inside Opportunity Add Products Select products from existing Payments → Products Multi-product selection Quantity selector Discounts Recurring or one-time billing indicators Automatic Calculations Example: Product Price Enterprise Plan $750 Voice AI Add-on $100 WhatsApp Add-on $50 Automatically update: Opportunity Value = $900 Benefits Sales Teams Faster deal creation More accurate quoting Better visibility of sold solutions Forecasting Revenue forecasting becomes product-aware Better MRR/ARR tracking More accurate expected revenue SaaS Businesses Native SaaS sales workflow Expansion revenue tracking Upsell/Cross-sell visibility Automation Allow workflows such as: IF Opportunity contains Product = Voice AI THEN trigger onboarding automation Visual Pipeline Enhancements Display selected products directly on Opportunity cards: Example: Enterprise Voice AI WhatsApp This would make pipelines significantly more actionable and revenue-oriented. Why This Matters Today many HighLevel users use: Custom fields Smart tags Manual value updates to simulate product association. A native product-to-opportunity relationship would elevate HighLevel closer to: HubSpot Salesforce Pipedrive Monday CRM especially for SaaS and subscription businesses. Additional Suggestions Future improvements could include: Native MRR/ARR tracking Product-level forecasting Revenue expansion tracking Subscription linkage Product-based reporting Revenue operations dashboards

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.

Currently, the sequences are shown in the order from the last modified or created to the oldest, but this is impractical because if the account manages several Sequences, it may be necessary to group them and show them in a specific order.

Similar to how we can see how many tags, show how many tasks are either overdue or existing for a contact.

Current Limitation • Pipeline Smart Tags can only be created and managed within individual sub-accounts. • When pipelines are included in a snapshot, Smart Tags are not transferred into the target sub-account. • As a result, workflows and automations referencing those tags break or require manual reconfiguration. Expected Behaviour When applying a snapshot to a sub-account: • Pipeline Smart Tags should: • Be automatically created in the sub-account • Remain correctly mapped to their respective pipeline stages • Retain references used by workflows and triggers • All automations relying on these tags should function immediately post-deployment. Why This Matters • Snapshots are intended to enable repeatable, no-touch deployments. • Manual Smart Tag recreation: • Slows onboarding • Introduces errors • Undermines snapshot reliability for agencies and SaaS users

Can we add a fun feature? When you mark someone in Opportunities as "Won" there should be confetti the bursts on the page. Similar to the iPhone message feature. I have had several clients request this, too. :)

As it stands, there isn't much you can do with opportunities in workflows. You can create or update, if it's for the same contact (assuming you have duplicate opportunities disabled). But you can't for example "Find Opportunity" (by ID or name or anything) and "Add Additional Contacts" or even "Change Primary Contact". USE CASE I built out a Pipeline for a mortgage company, titled "Loans in Process". Zapier finds when a loan in their system has been updated, and sends a single webhook with all the loan and contact data over to HL. This then creates/updates the contact for primary borrower, and creates/updates an Opportunity (in this case, a Loan). Due to limitations with workflows only being able to create one contact at a time, I have to send additional webhooks over to extra workflows to create each additional contact. Which is fine, it works. -- HOWEVER, I can't add these contacts to the Opportunity (Loan) in those workflows. They're created in the system, but they have to manually be linked to the Opportunity. DISCLAIMER I'm technically using Opportunities as a sort of workaround, because we don't have custom objects yet. Once that's released, all of this will most likely become obsolete, since ideally a loan would live as its own Object, instead of an Opportunity.

Dear Team, We would like to request a new permission feature in GoHighLevel (GHL) that prevents certain users from deleting Opportunity Forms. Requested Feature Add a user permission setting that allows administrators to disable the ability to delete Opportunity Forms for selected users or roles. Purpose This feature will help us: Protect important opportunity data from accidental deletion Maintain data integrity and auditability Limit sensitive actions to administrators only Improve overall access control within the platform Suggested Permission Setting Delete Opportunity Forms: Enable / Disable When this permission is disabled, the user should still be able to view and edit Opportunity Forms, but should not be allowed to delete them. Business Impact Opportunity Forms contain critical sales and customer information. Restricting deletion rights will reduce the risk of losing valuable data and ensure better operational control. We believe this enhancement would be highly beneficial for organizations that require stricter user permissions and data protection. Thank you for considering this feature request. Best regards,