# Collection-description scan copy for support routing

> Write collection descriptions like routing copy, because a short line of context often decides whether a visitor opens the right support section or starts guessing.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/collection-description-scan-copy-for-support-routing/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/1970126-set-up-your-help-center)
- GrowthDex source hub: [Intercom Help](/sources/intercom-help-intercom-com/)
- Last checked: 2026-05-28
- Rarity: rare
- Budget: free
- Channels: Support, Brand, Documentation
- Stages: help center, brand trust, navigation copy, information architecture


## Why this can grow

A lot of help-center navigation is skimmed, not studied. The collection title may name the bucket, but the description tells the reader whether the bucket actually matches the job they came to do. Good scan copy reduces wrong clicks, makes collections feel intentional, and helps the archive behave more like guided product navigation than a loose pile of articles.

## 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 collection-description scan copy for support routing can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Brand 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 recommends giving each collection a short description and says the description provides important context for people scanning the Help Center.

## Adjacent tactics in the same lane

- [Customer card sort before Help Center IA lock](/growth-ideas/customer-card-sort-before-help-center-ia-lock/) - same source, 2 shared channels, 3 shared stages
- [One help article per search job](/growth-ideas/one-help-article-per-search-job/) - same source, 2 shared channels, 2 shared stages
- [Collection-only search gate before Help Center launch](/growth-ideas/collection-only-search-gate-before-help-center-launch/) - same source, 2 shared channels, 2 shared stages
- [Translated collection gate before multilingual help-center launch](/growth-ideas/translated-collection-gate-before-multilingual-help-center-launch/) - same source, 1 shared channel, 3 shared stages

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The help center homepage should route the first click](/blog/the-help-center-homepage-should-route-the-first-click/) - 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.