CTA Reasons limit

While I don’t know the technical answer, I very highly recommend rationalizing the Reasons to a reasonable list size. The more Reasons an instance has, the more likely a CSM could be haphazard when selecting a Reason. 

I look at Reasons as a path to actionable data. What are the big issues that we’re working on, and then can we programmatically get in front of some of those issues? Too many reasons can lead to data quality input issues, and can dilute the signal we hope to produce by using Reasons in the first place.