Manual help-center order before automatic sorts
Arrange categories, sections, and flagship articles by hand before defaulting to alphabetical or date-based ordering.
Why this can grow a startup
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.
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.
Source-reported evidence
Source: Zendesk Help: Reordering knowledge base content within categories and sections
Zendesk says manual ordering updates the help center automatically, while alphabetical or date sorts block article reordering inside that section.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 29, 2026
When to use it
Use this when Support, Documentation, Website is relevant to information architecture, first-click design, docs ops 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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Support and Documentation, using evidence from Zendesk Help: Reordering knowledge base content within categories and sections as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.