# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/single-collection-home-for-each-public-help-article/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/9357931-create-and-manage-public-articles)
- GrowthDex source hub: [Intercom Help](/sources/intercom-help-intercom-com/)
- Last checked: 2026-05-28
- Rarity: uncommon
- Budget: free
- Channels: Support, UX, Documentation
- Stages: information architecture, support-led growth, navigation design, content governance


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where single collection home for each public help article can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and UX channel.
3. Use the evidence from intercom.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Intercom says that once a public article is added to the Help Center, it can belong to only one collection.

## Adjacent tactics in the same lane

- [Highest-volume question first in each help collection](/growth-ideas/highest-volume-question-first-in-each-help-collection/) - same source, 2 shared channels, 2 shared stages
- [Help-center homepage section order by job](/growth-ideas/help-center-homepage-section-order-by-job/) - same source, 2 shared channels, 1 shared stage
- [Help-center search terms in title, description, and body](/growth-ideas/help-center-search-terms-in-title-description-and-body/) - same source, 2 shared channels, 1 shared stage
- [High-traffic help articles linking to low-traffic answers](/growth-ideas/high-traffic-help-articles-linking-to-low-traffic-answers/) - same source, 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The help center stops feeling generic when the brand context stays intact](/blog/the-help-center-stops-feeling-generic-when-the-brand-context-stays-intact/) - support-led growth, technical SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.