Multiple labels per deal?

Hello, we use labels for our deals but often run into an issue where a deal meets multiple criteria and we would very much appreciate the ability to have multiple labels for a deal.

Thanks!

1
1 votes

· Last Updated -

Comments

  • Helio_2884
    Helio_2884 Moderator Posts: 83
    10 Comments Pipedrive Team
    CUSTOMER SUPPORT
    edited February 2022 #2

    Hello,

    Thank you for your feedback! It has been shared internally.

    As a workaround, you could create a multiple option custom field and use it to label deals. You can learn more about custom fields here. If you'd like to explore this further and have any doubts, please reach out to our support - Contacting Pipedrive support

    Here’s how to get notified about what’s coming down the line:

  • Justus Lubahn
    Justus Lubahn Posts: 56
    10 Comments
    edited December 2021 #3
    Helio said:

    Hello,

    Thank you for your feedback! It has been shared internally.

    As a workaround, you could create a multiple option custom field and use it to label deals. You can learn more about custom fields here. If you'd like to explore this further and have any doubts, please reach out to our support - Contacting Pipedrive support

    Here’s how to get notified about what’s coming down the line:

    This has been requested so many times by so many people... It just does not make sense to me, why you should only be able to apply one label to a Deal. 
    Could we please get some more feedback on this, @Helio ?

  • Agreed - please make deal labels like lead labels

  • +1 on this feature request 🙋‍♂️

  • Lukas
    Lukas Posts: 1
    First Comment

    Hello everyone, this feature has been requested so many times, and it still is not here. I am using Pipedrive with 3 different accounts, and in each one this would be a very helpful feature. Check out an app like Clickup, with probably the same level of complexity as Pipedrive, and see how helpful the multiple label option is. The "multiple option custom field" is really a bad workaround. //.,..+1 for this request.

  • We would also find this a very useful feature