Client Intelligence currently generates knowledge base articles based on detected patterns across ticket history, but there is no way to control which topics or ticket types are included in that analysis. This means teams have no mechanism to exclude noise — one-off issues, irrelevant ticket categories, or vendor-generated tickets that inflate pattern detection — and no way to focus article generation on the recurring, meaningful issues that actually warrant documentation.

We'd like the ability to define the scope of what Client Intelligence considers when generating articles. This could take the form of inclusion/exclusion rules based on ticket type, board, category, keyword, or other metadata — so teams can direct article generation toward the signal rather than the noise.

The expected outcome is a knowledge base that reflects genuine, recurring issues worth documenting, rather than a broad dump of everything that passed a frequency threshold.