topic Re: Nested lost status for deals in Tips, Tricks & Best Practices

Nested lost status for deals

annahoyt — Wed, 16 Mar 2022 13:02:24 GMT

hi there,

We'd like to track different reasons for losing deals. What's the best way to do it? Can we set up nested lost statuses?

Re: Nested lost status for deals

karstenkoehler — Wed, 16 Mar 2022 13:43:45 GMT

Hi @annahoyt,

It's not possible to set up dependent fields in the CRM, unfortunately. However, other users have requested this in the HubSpot Ideas section and it's already being reviewed by the HubSpot product team: Field Dependencies for Contact Properties

For workarounds (until this feature is released), you can work with required properties for deal stages. This is a Sales Hub Professional or Enterprise feature.

This will only give you one level, not dependent fields. For example, if one property is set to "Competitor", it's not possible to require the user to select the competitor from another property. I'd recommend making the first Closed lost reason property required and intuitively naming the options, for example "Competitor (please specify in 'Competitor' field)". Not ideal, I know, but the closest we can currently get. It would rely on the good will of the user.

(With deal-based workflows, you could also remind users with an internal email notification that they forgot to fill a certain property. Let me know if you need help setting this up.)

Best regards!

Re: Nested lost status for deals

annahoyt — Wed, 16 Mar 2022 13:53:44 GMT

Hi Karsten,

I don't think it's quite what I am trying to accomplish.

Right now we have several lost statuses like lost becuase of no action, lost becuase of competition. What I am trying to do is to have one lost status but then have a substatus that would be from a picklist.

Re: Nested lost status for deals

karstenkoehler — Wed, 16 Mar 2022 13:57:16 GMT

Hi @annahoyt,

This is not possible. HubSpot does not have a feature for two-level-picklists. This would have to be two separate properties. The product team is currently reviewing dependies between fields (Field Dependencies for Contact Properties) but it's not delivered yet.

Best regards!