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.

Hi GHL Team, I'd like to submit a feature request for the Smart Tags functionality within the Pipeline settings. Currently, the 'Last stage change date' filter only supports Day, Week, Month, and Year as time units. For many businesses, particularly in sales and fitness, lead response times are measured in hours, not days. A lead that sits in a stage for 6-12 hours without movement can already be considered stagnant and at risk of going cold. The requested improvement is simple: add Hours as an available time unit alongside the existing Day, Week, Month, and Year options. This would make Smart Tags significantly more powerful for businesses with fast-moving sales pipelines where sub-24-hour stagnation tracking is essential. I'd appreciate confirmation that this has been logged as a feature request.

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, 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, the Business Name field is closely tied to the Primary Contact, making it difficult to manage B2B accounts where contacts change frequently or where multiple contacts belong to the same company. We would like the ability to manage Business Names independently from Primary Contacts. Desired Functionality: Allow Business Name to remain unchanged when the Primary Contact is updated. Prevent automatic updates to Business Name based on contact information. Allow admins to disable contact-to-business auto-linking. Support multiple contacts under a single business without affecting the company record. Provide account-level settings to control this behavior. Use Case: In B2B environments, companies often have multiple stakeholders involved in a project. Sales teams may need to change the Primary Contact throughout the sales cycle, but the Business Name should remain tied to the organization, not the individual. For example: Business Name: GreenSeed Contract Packaging Primary Contact: John Smith Later: Business Name: GreenSeed Contract Packaging Primary Contact: Sarah Johnson The company should remain unchanged while contacts can be updated as needed. Benefits: Better support for account-based selling Easier management of multi-contact organizations Reduced data inconsistencies More flexibility for enterprise and manufacturing sales workflows Improved CRM data quality and reporting Current Behavior: ❌ Business records can become dependent on contact records, creating confusion when contacts change. Requested Behavior: ✅ Business records remain independent entities while maintaining associations with multiple contacts.

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

Please add a feature that requires users to complete specific custom fields before they can change an Opportunity stage. Example: * If a user moves an Opportunity to "Lost," they must fill in a required field such as "Loss Reason." * If a user moves an Opportunity to another stage, they must complete any custom fields assigned to that stage. The stage change should be blocked until all required fields are completed. This feature would help ensure accurate data collection, improve reporting, and prevent users from changing stages without providing the necessary information.

please fix it to where you can edit the won date