Customized Closed Lost Drop Downs By Pipeline

[AValentine4]

I'm searching for a way to have different closed lost options depending on the pipeline being used. Scenario: We have different pipelines for different teams/product offerings. The Closed Lost reasons will be different depending on the pipeline. Any way to do this?

Pipeline A 

Closed Lost Reason 1

Closed Lost Reason 2 

Closed Lost Reason 3

Pipeline B

Closed Lost Reason 4

Closed Lost Reason 5

Closed Lost Reason 6

[Jnix284]

HI @AValentine4 ,

I've run into this situation once before and the solution we came up with at the time was to set up the closed lost reason as follows:

[A] - Closed Lost Reason 1

[A] - Closed Lost Reason 2 

[A] - Closed Lost Reason 3

[B] - Closed Lost Reason 4

[B] - Closed Lost Reason 5

[B] - Closed Lost Reason 6

As long as you follow a clear naming convention and communicate clearly with your two teams, you should rarely have a mixup.

We also setup two workflows to check for errors (only ever had 2 for multiple years):

workflow 1

trigger: pipeline = A, status = closed lost, closed lost reason contains "B"

add a task to the rep to update

workflow 2

trigger: pipeline = B, status = closed lost, closed lost reason contains "A"

add a task for rep to update

Not sure if there has been an update in more recent years that would provide a better solution, but hopefully this gives you an option to explore.

[TiphaineCuisset]

Hi @AValentine4 

Thank you for reaching out.

I want to tag some of our experts on this - @ChrisoKlepke @Jnix284 @johnelmer do you have any thought for @AValentine4 on this? 

Thank you!

Best

Tiphaine