Opportunities & Pipelines

When we go through opportunities with our sales team, we usually look at the pipeline and open each opportunity we need to discuss. However, discussions suffer because we can't see which conversations have happened directly on the opportunity card. Instead, we have to load the contact to look at the conversations, then we have to go back to the pipeline to continue with the next opportunity. It is very cumbersome. It would be much easier if we could see the conversations directly in the opportunity so we don't have to load the contact and go back every time.

Making a scheduling connection between appointments and opportunities. Right now, the connection is between the appointment & the client, but in our niche of home service, a client can have several opportunities. Its limiting to not get the freedom to connect the opportunity to the appointment, it instead feels cut out.

In my business I operate as a middle man of sorts and the major issue I'm having with adapting GHL to my business is that once I get the lead to the end of my "Leads" pipeline and it becomes "won" it then becomes a product and/or opportunity in of itself and no longer needs to be connected to that person and/or company. But then would need to be connected to another person and or company at a later date.

I want to update anticipated close dates with workflows

Love that sorting fields can now be saved to Opportunity Smart Lists. It would be even more useful if we could add secondary sorting fields. For example, I use a custom field called Interest Level. If multiple opportunities have the same interest level—or no value at all—they appear in a random order each time the pipeline loads. It would be great to set: Primary sort: Interest Level Secondary sort: Date Created That way, high-priority opportunities stay grouped at the top, while opportunities with the same value are consistently sorted by date instead of randomly. There are probably other use cases for this too that would require more than 2 level of sorting, so perhaps having a variability to add as much levels of sorting priority would be the solution.

Currently, a GHL Opportunity has a single Opportunity Value and does not natively provide a dynamic order-line-item structure where multiple SKUs can be added under the same Opportunity. We need to enhance the Opportunity UI so that users can dynamically add multiple SKUs/line items within a single Opportunity. The number of SKUs should not be predefined or restricted to a fixed number of fields. The user should have an "Add SKU" / "Add Item" option in the Opportunity interface and be able to keep adding SKUs as required. Example One Opportunity may contain: SKU Quantity Unit Price Line Total SKU A 5 ₹500 ₹2,500 SKU B 2 ₹1,000 ₹2,000 SKU C 10 ₹200 ₹2,000 SKU D 1 ₹1,500 ₹1,500 Opportunity / Order Value = ₹8,000 Another Opportunity may contain 10 SKUs, while another may contain 20 SKUs. The system should support all these scenarios through the same dynamic UI rather than creating a fixed number of SKU fields. Required User Experience Within an Opportunity, provide an Add SKU / Add Item button. When clicked, a new line item should appear with fields such as: SKU / Product Quantity Unit Price Discount (if applicable) Line Total The user should be able to: Add as many SKUs as required. Remove an SKU if it was added incorrectly. Modify quantity and pricing for each SKU. View the calculated total for each line item. Automatically calculate the overall Opportunity / Order Value by summing all line items. Save all SKU-level information against the same Opportunity. Core Requirement The number of SKUs must be dynamic and user-controlled. Do not create a fixed structure such as SKU 1, SKU 2, SKU 3... SKU 10. Instead, the UI should function conceptually like an e-commerce cart, where the user can continuously click "Add SKU" and build an order containing 4, 10, 20, or any other number of SKUs under one Opportunity. The final Opportunity should represent the complete order, while the individual SKUs should be maintained as line items within that Opportunity.

When we get a new opportunity, our work flow isn't to create a new contact, and THEN add the opportunity. We add the opportunity as we are on the phone with them. However, when you do this the contact gets created, but the primary email does not attach to that contact. That's a bad UX. The primary email for the contact should be linked to the new contact that gets created in this circumstance.

WE WANT TO FILTER AN EXACT MESSAGE FROM A CONVERSATION BY DATE RANGE, NOW WE ARE USING APP LEVEL. IT IS POSSIBLE?

Clients have asked about the ability for us to make certain fields required when creating an opportunity card

We need the ability to track (and edit) an Opportunity's close date (whether it's the date it's marked as Won, Abandoned, or Lost.) This is critical for pipeline reporting, sales commissions or bonuses, reporting on KPIs, calculating demo-to-close rate, etc. There are also plenty of use cases where there's the need not only to track the close date, but edit it: EDIT ABILITY USE CASE #1: Sometimes a deal is closed but the Opp isn't updated right away. Without the ability to edit the date, the close date could be wrong. EDIT ABILITY USE CASE #2: When migrating data from other systems or other "batch" situations where a bunch of historical Opp data is being inserted into HighLevel for recording keeping or reporting. EDIT ABILITY USE CASE #3: We had incorrectly setup a "Stage" for Won Opps vs keeping track of that in the "Status". We fixed that structural issue and updated all the Won Opps via the correct "Status". If close date was tracked and there was no way to edit, all the close dates would be wrong.