Single collection home for each public help article
Give every public help article one deliberate collection home instead of scattering the same answer across multiple support buckets.
Why this can grow a startup
Support archives get harder to scan when the same answer appears under several competing paths. Intercom's public-article model forces a cleaner decision because each public article can belong to only one collection. Treating that limitation as a design rule sharpens your routing, keeps collection intent clearer, and reduces the chance that searchers land on an answer whose surrounding context points them in the wrong direction.
Company example
Intercom says that once a public article is added to the Help Center, it can belong to only one collection.
Source and metric
Source: Intercom Help · Browse Intercom Help tactics
Intercom restricts each public article to a single collection
Source discovered: May 28, 2026
When to use it
Use this when Support, UX, Documentation is relevant to information architecture, support-led growth, navigation design and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Intercom Help and identify what is directly supported.
- Choose one channel context: Support, UX, Documentation.
- Define the test around Intercom restricts each public article to a single collection.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.