# Multi-level help-center collections with breadcrumbs

> Use a shallow multi-level collection tree with descriptions, counts, and breadcrumbs so users can browse to the answer without starting over.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/multi-level-help-center-collections-with-breadcrumbs/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/56647-create-collections-in-your-help-center)
- GrowthDex source hub: [Intercom Help: Create collections in your Help Center](/sources/intercom-help-create-collections-in-your-help-center-intercom-com/)
- Last checked: 2026-05-29
- Rarity: uncommon
- Budget: low
- Channels: Support, Documentation, Product
- Stages: information architecture, browse ux, messenger support, self-serve conversion


## Why this can grow

A flat help center turns everything into search, and search is not always how stressed users think. Intercom's collection model is useful because it gives teams up to three levels of hierarchy, visible counts, descriptions, drag-and-drop ordering, and breadcrumbs back up the tree. That turns browsing into a legitimate route instead of a consolation prize for failed search. Users can stay oriented, see what lives in each branch, and recover from a wrong click without feeling lost.

## 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. For conversion, I would strip the test down to one promise, one proof point, and one next step. Confusion kills good demand. 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 multi-level help-center collections with breadcrumbs can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Documentation 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 lets teams build up to three levels of Help Center collections, show collection descriptions and article counts, and let customers navigate back through breadcrumbs on the web and Messenger surfaces.

## Adjacent tactics in the same lane

- [Customer card sort before Help Center IA lock](/growth-ideas/customer-card-sort-before-help-center-ia-lock/) - 2 shared channels, 1 shared stage
- [Hide unreleased docs until the version is real](/growth-ideas/hide-unreleased-docs-until-the-version-is-real/) - 3 shared channels
- [Discourse topic template before support post submit](/growth-ideas/discourse-topic-template-before-support-post-submit/) - 2 shared channels, 1 shared stage
- [Manual help-center order before automatic sorts](/growth-ideas/manual-help-center-order-before-automatic-sorts/) - 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 should stay private until it can carry the work](/blog/the-help-center-should-stay-private-until-it-can-carry-the-work/) - support-led growth, documentation, brand trust

## Advisory

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