Required Fields to Move Opportunity Stages | Voters

Required Fields to Move Opportunity Stages

complete

Brian Pappalardo

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.

August 18, 2023

Pallavi Kothari

updated the status to

complete

Hi 
Thanks for upvoting this idea - its now live
https://ideas.gohighlevel.com/changelog/conditional-custom-fields-for-opportunities
Please try it out and share your feedback

Ty Averett

Pallavi Kothari Thanks for all the hard work you and your team put into making GHL awesome!

I've been testing this today and have a few observations:

I thought it wasn't working but then refreshed. Might be good to note that somewhere.
It appears you cannot make a field visible AND mandatory. This is especially important for 'lost reason'- I would love to make that mandatory but I can't.
If a field involved is in the same folder as the trigger, it shows up 2x on the opportunity card. I think it would be helpful if the field is in another folder, but if it's in the same folder, it makes it cluttered.
There aren't any options for contact fields. It would be awesome if we could make contact fields visible or mandatory OR trigger opportunity fields mandatory/visible based off contact fields that are on the opportunity card.
It seems like these need to be rebuilt manually in each subaccount rather than being pushed via snapshot? It would save a ton of time and make things run smoother to add these conditional rules (along with other pipeline settings such as colors, smart tags, custom views, etc) to snapshots.

Thanks again!

Josh Herman

Pallavi Kothari This is amazing, and I couldn't wait for this to be released. Would it be possible for you to expand this more than 10 conditional rules allowed? We could definitely benefit with more than 10.

Brian Pappalardo

Pallavi Kothari Thank you!! This is such a big step in the right direction for opportunities!

I wonder, if we're showing a folder when a condition is met, whether the folder can just appear in the sidebar rather than also showing up underneath the field. It feels a little cluttered the way it's currently displaying. But again, we've been waiting for this for a long time and really appreciate you all prioritizing it!

Cindy Greenway

Do we have an ETA on when this will go live? This is absolutely critical

Yariel Benavides

IMPORTANT OBSERVATION: The scenario to include is when an opportunity is marked as "Lost". In that case, selecting a "Lost Reason" should be mandatory before the status change can be completed.
This would improve data quality, make loss reporting more reliable, and help teams understand why opportunities are not converting.
Most of teams forget to enter de lost reason as it's not mandatory.

Liam Holmes

Yes, a key feature.

READ-ONLY fields based on user permissions would be also be useful.

Rami Adra

Pallavi Kothari do we have an update on progress for this? are there calls running for this to give feedback on requirements and the way it works happy to jump on a call to dicuss and provide feedback 
this needs to take into consideration 
contact fields mapping to opps
workflow triggers that move stages auto
opp card drop down change vs drag and change etc.

Davit Kikvadze

any update?

John Pearson

We are on a trial at the moment (currently with Pipedrive) and this is vital the success of not only our migration so the we can use GHL internally, but also to our offering to our niche of GHL as a service

Randall Chalan

Pallavi Kothari do you have an update when this will go live?

James Moorhouse

Can you please implement this? For future automations to run properly, we need to ensure certain fields are complete - this can sometimes be mistakenly missed by staff using the app.

Ryan Hamilton

There is also no need for "status" and "stage" seperated, the system should know what stages are closed won or lost. System should also know what stages are "open". When you move through the Kanban view the automation should know our progress in each stage of the funnel and know when we close a deal. Currently if you move to a "closed" stage it is not officially recognized until you move the status manually. This is standard for CRM, it needs to change!

Michael Angrave

Ryan Hamilton 100%. Linking each stage to a status seems to make massive sense to me.

→