Opportunities & Pipelines

❌ 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!

For contacts that have multiple opportunities, we need to be able to leave notes specifically for each opportunity rather than it being saved under the main contact notes section. It gets too messy when leaving notes for specific jobs related to the same contact. HIGHLVL-I-5531

Is it possible to add a feature to assign tasks to specific opportunities and show them as a column in the task list? Currently, I have to switch between two screens to associate a task with an opportunity, which is an inefficient workflow.

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

In the legacy version of Create/Update Opportunity, we have the option to check a box if we want to allow the creation of duplicate opportunities for the same contact, regardless of how that's set up at the subaccount level (business settings). I'd love to see that in the new Create Opportunity action. Here's the use case: An elderly couple signs up to a service via a form submission. A contact gets created for the first one to sign up, while it just updates for the second because they share phone numbers, have no emails and contact duplication is just insane. However, that form submission also triggers a webhook to the client's software where they each get assigned a unique ID. With the legacy action, after GHL got a response from that webhook, it would create individual opportunities for each person in an existing clients pipeline for the business, where they each get separate treatment and are easily identifiable by their IDs. Now I'm getting errors on the last step because I can't have duplicate opportunities. I know I could just allow duplicate opps at the global level, but that would be troublesome for the overall process, and - in this specific case - I only need it for this purpose. We used to be able to work beautifully by allowing it at a workflow level so, can we have that back, please? Thanks in advance!

To make opportunities more useful it would be nice to update an opportunity so that it does not have to be a manual process. Right now there is no way to update an opportunity via automation from forms or other third-party input options. If you use a form it only creates a new opportunity, it will not update. The idea is to pre-populate the form with the opportunity_ID via url=paramaters or manual entry, which would tie the form to the opportunity. Similar to how if you pre-populate a contact's email address, you can submit the form and update a contact field. Upon submit the opportunity fields on the form would update the opportunity based on the opportunity_ID or possibly any customField value. This would open up a world of possible use cases. For example, in real estate: The opportunity is a Listing at a particular address. There are many different interested parties who need to interact with the opportunity: buyers, sellers, appraisers, inspectors, Agents, contractors etc. if we could send a form to the seller, they could fill out information about their home onto the opportunity. We could send another form to the title company for them to fill out the property description, notes, title policy cost etc. We could send another form to the buyer's agent and have them upload their offer, which would be saved to the opportunity. In any scenario where the opportunity involves many different players, we could design systems that can be automated to keep everyone informed and data about that particular "Listsing opportunity" in the case of real estate can be consolidated in the opportunity instead of trying to make it work in contacts, which is just impossible.

Our company has 3 divisions. It would be a great help for user overload if you can restrict Which pipelines users can see.

Being able to clone/duplicate pipelines. Its a headache having to imitate pipelines when I am using it multiple times.

the possibility to select the products that the customer is interested in but also the products that he purchased from the list of products and to be saved in the opportunity cards

After creating the custom fields inside the opportunities, we could be able to organize them the way we want. For example: I created A field, B field and C field. But in a few days i went to analyze for some inovations and i though that the order should be B field, C field and then A field, right now i have to delete the custom fields and make it again to put it the order i want. Would be very easy and faster if we could just edit the order of the custom fields inside the opportunities