Opportunities & Pipelines

Increase the limit of 10 associations max between Custom Object and an Opportunity. In the image I have a custom object "Policy" , in the insurance field, but also on real state and health field, I can think in tons of biz fields where this applies, we need to have more than 10 associations per object. We are in an insurance field, where there are tons of supplementary policies (products), to differentiate each of them and link them with the specific Opportunity, we need to be able to create more than 10 associations between the custom Policy object and an Opportunity. See attached image, voting please to increase the cap of 10 max.

Have a setting or Automation that allows the contact owner to automatically become the Opportunity owner when it is created

It would be awesome if we had at least 12 or 15 fields shown on the opportunity card. 8 is too low! We need more important information there, so it is not necessary to click the card every time just to check some info!

Currently, the 'All' tab within the Contacts section is visible to any user with access to the area. There is no setting to hide or remove this tab at the individual user or role level. Even if you use the “Only Assigned Data” setting to filter records, or assign specific Smart Lists to the various members of the team, the main “Everyone” tab always remains present and clickable in the interface. Required solution: Add a toggle or a dedicated setting within Roles & Permissions that allows administrators to completely disable the display of the 'Everyone' tab for certain users or groups. Why it's important: This feature would allow creating a much cleaner and more focused work environment for team members. By removing the 'Everyone' tab, operators would work exclusively within the Smart Lists created and assigned specifically for them, avoiding distractions and optimizing navigation in the CRM.

When a contact is assigned to a specific user and a different follower. Once an opportunity is created by the workflow, the owner of the opportunity will be the same owner on the contact tab. However the follower on the opportunity will remain empty it will not be changed automatically to the follower in the contact tab. It would be great if this update will be pushed. And also, if we can choose the opportunity follower using the workflow.

Currently, Notes must be associated with a specific object (Opportunity, Contact, Company, etc.), making it difficult to capture information that applies across multiple records or that should remain independent of any single object. We would like the ability to create and manage Notes without requiring an association to an Opportunity, Contact, or Company. Desired Functionality: Allow standalone notes that are not tied to any specific record. Provide an option to remove or change associations without deleting the note. Allow a single note to be linked to multiple objects while maintaining one source record. Create a centralized Notes repository where users can search, filter, and organize notes independently. Allow admins to control whether notes require associations. Use Case: In many organizations, users capture meeting notes, project updates, internal discussions, strategy notes, research, and planning documents that do not belong exclusively to a single Opportunity. For example: Current Behavior: ❌ Strategic discussion note → Must be attached to Opportunity A Later: ❌ Opportunity A is closed or deleted → Finding the note becomes difficult Desired Behavior: ✅ Strategic discussion note exists independently Optional associations: Opportunity A Company B Contact C The note remains accessible regardless of changes to associated records. Benefits: Improved knowledge management Better cross-project collaboration Reduced risk of losing important information when records change More flexibility for project management and account management workflows Easier documentation of internal discussions, meeting notes, and strategic planning Current Behavior: ❌ Notes are dependent on associated objects and can become difficult to locate when relationships change. Requested Behavior: ✅ Notes can exist independently while optionally being linked to one or more Opportunities, Contacts, Companies, or other CRM records.

Currently, Opportunities are tightly linked to the Primary Contact and Company, causing automatic updates and dependencies that don't fit all sales processes. We would like the ability to independently manage: Opportunity Name Primary Contact Company/Account without forcing one field to control or update the others. Desired Functionality: Allow Opportunity Names to remain static even when the Primary Contact changes. Allow users to change the Primary Contact without automatically renaming the Opportunity. Provide a setting to disable auto-population of Opportunity Name from Contact or Company. Allow multiple opportunities under the same company without requiring contact-based naming conventions. Give admins the option to choose naming behavior at the pipeline level. Use Case: In complex B2B sales environments, opportunities often represent projects, products, manufacturing requests, commercialization initiatives, or RFQs rather than individual contacts. Users need the flexibility to name opportunities based on the project or business opportunity itself while still associating contacts and companies for communication purposes. Benefits: More accurate forecasting and pipeline management Better support for enterprise and multi-contact sales processes Reduced accidental renaming of opportunities Improved flexibility for custom sales workflows and CRM implementations

Would be very halpful if notes auto saved

The colors of the notes in the contact details view work pretty well. I’d also like to see them in the opportunity details view. (Every piece of data in the pictures is fictional)

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