# Manual help-center order before automatic sorts

> Arrange categories, sections, and flagship articles by hand before defaulting to alphabetical or date-based ordering.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/manual-help-center-order-before-automatic-sorts/
- Source: [support.zendesk.com](https://support.zendesk.com/hc/en-us/articles/4408843983258-Reordering-knowledge-base-content-within-categories-and-sections)
- GrowthDex source hub: [Zendesk Help: Reordering knowledge base content within categories and sections](/sources/zendesk-help-reordering-knowledge-base-content-within-categories-and-sec/)
- Last checked: 2026-05-29
- Rarity: uncommon
- Budget: free
- Channels: Support, Documentation, Website
- Stages: information architecture, first-click design, docs ops, support-led growth


## Why this can grow

Auto-sorts feel tidy from the admin side and random from the customer side. Zendesk is explicit that teams can manually reorder categories, sections, and articles, and that manual ordering is what lets the editor decide what gets seen first. That matters when the archive is doing product onboarding, switcher education, and support at the same time. The useful route is rarely alphabetical. It usually starts with the jobs, frictions, and mistakes that cost the queue the most money.

## 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 manual help-center order before automatic sorts 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 support.zendesk.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

Zendesk's Arrange content view lets admins drag categories, sections, and articles into manual order, with changes saved directly to the live help center.

## Adjacent tactics in the same lane

- [Help center setup mode before public activation](/growth-ideas/help-center-setup-mode-before-public-activation/) - 3 shared channels, 1 shared stage
- [Single collection home for each public help article](/growth-ideas/single-collection-home-for-each-public-help-article/) - 2 shared channels, 2 shared stages
- [Promoted help articles for homepage first-click routing](/growth-ideas/promoted-help-articles-for-homepage-first-click-routing/) - 2 shared channels, 1 shared stage
- [Title-first help-center instant-search phrasing](/growth-ideas/title-first-help-center-instant-search-phrasing/) - 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.