Our use case:
We have various pipelines, for various sales cycles and sometimes various types of contacts or companies.
The Deal's information we need to access depend on the pipeline the deal is in. Since the "default deal properties" is made to display the "most important" information of a deal, we need this group of "most important" information to be pipeline specific.
To propose to create multiple "default deal properties", each one having a name. Then, admin should be able to decide to which pipeline to apply this "default deal properties". A "default deal properties" may be applied to one or more pipelines. It's ok to have a limit on the possible numbers of possible "default deal properties" if needed. 10 or 20 maximum would already be amazing.
Note: I've written the above with the understanding that "default deal properties" are controlling both the "about" section on the deal and the properties available when creating a new deal on the card that's opening on the right of the screen.
@ Hubspot Product Managers: this 'Pipeline specific Default Deal Properties' is actually one use case for this more general idea 'Conditionally display and/or make mandatory properties'
I'm seeing that this has been a request since 2017 and 130+ upvotes.
@bsn , Is this something that is being worked on? It seems like many user would greatly benefit from this feature.
we would love this feature 🙂
Today is the 2nd years anniversary of this feature request. It got 143 upvotes and 43 replies but has not been moved yet to "Planning" by Hubspot. I hope this happens soon.
@VagaeNatus agreed! This seems to be an important capability for many. Businesses will likely outgrow HubSpot quickly for pipeline management if features like this aren't prioritised.
+1 from me.
I can see real use for the powerful pipeline tools outside of the sales stage, such as where there are processes to be completed after a sale is complete.
Use case: Onboarding pipeline
(Although we need this feature in "Tickets" as well, but the main idea remains the same).
It makes sense to have different properties for different pipelines in the process. We currently see Pipeline A as our daily business process for complaints, but pipeline B (that could be returns in our case) are completely different ticket properties.
You may want to ask in pipeline A why the ticket has been opened (product damaged/shipping in delay etc.), but you never would want to see these "default" properties in your pipeline B, since (in respect to returs) you may want to set properties like why the parcel has returned for example.
Therefore I really hope HS takes this request that has been opened for a long time now into action and tickets/deals will be available with different properties due to the choosen pipeline they are in.
Really all we really need in our company , is to define what properties we'd like to see when we create a deal in certain pipeline... there are some initial properties that do not apply to all pipelines... right now we have to add an option in each property that says "N/A" to show that that property in particular does not apply to that pipeline... sounds easy to do
"N/A" to all "useless" properties in various pipelines also screws your reports...why is there no action from Hubspot since 146 need this urgently?
+1 for us
150 upvotes and two years time. Let's get this feature added!
PLEAASSE DO SOMETHING HERE HUBSPOT!
Submitting on behalf of my customer, who was looking for a similar feature.
Use Case is they run financial services, and would like to have the About section of the deal different for each of their pipeline to quickly get an over view of the deal properties most important to that pipeline.
155 Votes, more than 2 years since initial request, 0 reaction from HubSpot. This is really disgrace.
Hi HubSpot Community,
We really appreciate the continued feedback on this post. Allowing pipeline specific deal properties is certainly something we hope to look in to. However, at this stage the work has not been planned or scheduled. Please continue to provide examples and use-cases for this feature - it will help us build a better solution when the time comes. We'll update this post when we have further clarity on when we plan to build this functionality.
We could really use this on the Service Hub Pipeline side. We've got three pipelines on Service Hub, with different users using different pipelines. There are many extra steps to see all the fields for the appropriate data to be entered into the ticket. Pipeline Default Properties or Default Property Views would solve this issue.
We definitely want this feature to make different default deal properties per pipeline. Besides using Hubspot for sales we would really like to use it as well for funding/investor relations and supplier selection. Hopefully Hubspot will implement this feature asap 🙂
Please add this feature asap, we really need this to have other departments easily working with pipelines as well (like investor relations, supplier selection).
Also, a suggestion could be to change the name Sales to Pipeline as the dealflow/pipeline functionality is applicable for other departments as well.
@TomSelten You may want to look into utilizing Tickets for departments outside of sales. So once a deal reaches a certain stage you can have a workflow create a ticket and assign it to the desired deptment. Creating the ticket using a workflow automatically associates the ticket to the correct deal as well so it a bit neater.
The rule we adopted is: If there is not a dollar amount then it is not a deal.
I am very surprised this is not an obvious inclusion in the system. It is urgently needed. My sales team are very frustrated seeing totally unrelated fields on their deals.
I am a bit surprised this isn't a feature yet and that HubSpot still need more use cases to consider implementing this.
When working with enterprise customers we notice a bigger demand for this. We have several customers who have sales offices across the world. There are properties used in the US that wouldn't be used in Europe and Asia. Also working across various industries in the same company there are custom properties that is used in one business unit but not in the others.
This should also be implemented in the Ticket Pipelines
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.