# The help center should stay private until it can carry the work > Why setup mode, promoted answers, manual order, timed publishing, and browseable collections make a help launch safer and more useful. - Canonical HTML: https://growth.iangoh.com/blog/the-help-center-should-stay-private-until-it-can-carry-the-work/ - Published: 2026-05-29 - Updated: 2026-05-29T22:05:00Z - Categories: support-led growth, documentation, brand trust - Niches: SaaS, AI products, developer tools, customer support software, marketplaces ## On this page - Privacy is useful when it buys rehearsal time - The homepage needs an opinion about what should be seen first - Order is part of the answer - Temporary knowledge should expire on purpose - Browsing should still work when search is not the first move ## Start with these related tactics - [Help center setup mode before public activation](/growth-ideas/help-center-setup-mode-before-public-activation/): Keep the help center private while the team brands it, tests it, sets language defaults, and checks the route before end users ever see it. - [Promoted help articles for homepage first-click routing](/growth-ideas/promoted-help-articles-for-homepage-first-click-routing/): Pin the few articles that answer the highest-volume problems so the first click from the homepage lands on the page most likely to stop a ticket. - [Manual help-center order before automatic sorts](/growth-ideas/manual-help-center-order-before-automatic-sorts/): Arrange categories, sections, and flagship articles by hand before defaulting to alphabetical or date-based ordering. A help center should not go public the moment the first articles exist. That is usually the moment the team is most tempted to ship it. The pages are written, the theme looks acceptable, and somebody wants to stop answering the same questions in chat. But a half-routed help center does not reduce support load. It turns uncertainty into a nicer-looking maze. The better standard is simple. Keep the surface private until it can carry a real customer job from the first click to the answer. ## Privacy is useful when it buys rehearsal time [Help center setup mode before public activation](/growth-ideas/help-center-setup-mode-before-public-activation/) is the cleanest starting point in this batch. Zendesk gives the team a private window to brand the surface, test it, set the default language, and check the route before end users ever arrive. That sounds procedural. It is really conversion work. The launch goes better when the first visitor does not feel like the first tester. I would keep that next to [unlisted public article preview before search release](/growth-ideas/unlisted-public-article-preview-before-search-release/) and [preview docs noindex before cutover](/growth-ideas/preview-docs-noindex-before-cutover/). They all defend the same idea. A page can be live for operators before it is ready to be live for discovery. ## The homepage needs an opinion about what should be seen first [Promoted help articles for homepage first-click routing](/growth-ideas/promoted-help-articles-for-homepage-first-click-routing/) is a small control with outsized effect. If the top issues are account setup, billing confusion, migration steps, or a live incident, the help surface should admit that immediately. Making the likely answer visible near the top beats another generic welcome sentence. That belongs beside [help-center homepage section order by job](/growth-ideas/help-center-homepage-section-order-by-job/) as an operating habit. The page is not a brochure. It is triage. ## Order is part of the answer [Manual help-center order before automatic sorts](/growth-ideas/manual-help-center-order-before-automatic-sorts/) is useful because alphabetical order often reflects how the team named things, not how the customer thinks. Manual ordering lets the operator choose the route that costs the queue the least. Sometimes that means a beginner flow comes first. Sometimes it means a painful migration page gets pinned above everything else for two weeks. I would pair that with [title-first help-center instant-search phrasing](/growth-ideas/title-first-help-center-instant-search-phrasing/). One tactic shapes the route for browsers. The other helps the searcher recognize the answer before they even hit Enter. ## Temporary knowledge should expire on purpose [Scheduled help-article publish and expire window](/growth-ideas/scheduled-help-article-publish-and-expire-window/) fixes a common launch mess. A temporary migration guide, regional payment note, or maintenance workaround gets published in a rush and then lingers for months after the job is over. Scheduled publish and unpublish windows keep temporary answers useful for the people who need them without turning the archive into a museum of old exceptions. This matters more than it sounds. A stale article does not only mislead users. It teaches search, support macros, and AI retrieval to keep dragging dead instructions back into circulation. ## Browsing should still work when search is not the first move [Multi-level help-center collections with breadcrumbs](/growth-ideas/multi-level-help-center-collections-with-breadcrumbs/) is the reminder that not every stressed customer wants to type the perfect query. Some people want to browse. Intercom's counts, descriptions, and breadcrumbs make that route safer because the user can see what lives in a branch and back out without starting over. I would keep it near [source-filtered multi-brand help-center search](/growth-ideas/source-filtered-multi-brand-help-center-search/). One helps when the user chooses search. The other helps when they choose navigation. Both reduce the feeling that the archive is one big undifferentiated pile. This cluster is strongest for SaaS, AI products, developer tools, support software, and marketplaces where the help center is doing onboarding, troubleshooting, and trust work all at once. If I were auditing one this week, I would ask five plain questions. Can the team rehearse privately. Does the homepage reveal the obvious first answer. Is the order chosen by customer need. Do temporary articles disappear on purpose. Can a stressed user browse without getting lost. If you want help turning docs, support, and trust surfaces into a cleaner acquisition and retention system, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Help center setup mode before public activation](/growth-ideas/help-center-setup-mode-before-public-activation/) - Support, Documentation, Website - [Promoted help articles for homepage first-click routing](/growth-ideas/promoted-help-articles-for-homepage-first-click-routing/) - Support, Documentation, SEO - [Manual help-center order before automatic sorts](/growth-ideas/manual-help-center-order-before-automatic-sorts/) - Support, Documentation, Website - [Scheduled help-article publish and expire window](/growth-ideas/scheduled-help-article-publish-and-expire-window/) - Support, Documentation, Lifecycle - [Multi-level help-center collections with breadcrumbs](/growth-ideas/multi-level-help-center-collections-with-breadcrumbs/) - Support, Documentation, Product ## Essay chronology - [Newer essay: The support forum should stop acting like a chat room](/blog/the-support-forum-should-stop-acting-like-a-chat-room/) - community-led growth, support-led growth, documentation - [Older essay: The Atlassian Marketplace page should close the diligence gap](/blog/the-atlassian-marketplace-page-should-close-the-diligence-gap/) - marketplaces, brand trust, pricing ## Keep reading - [The docs page should show signs of life before support does](/blog/the-docs-page-should-show-signs-of-life-before-support-does/) - documentation, proof surfaces, support-led growth - [The answer should interrupt the ticket before it opens](/blog/the-answer-should-interrupt-the-ticket-before-it-opens/) - support-led growth, technical SEO, brand trust - [The support surface should separate audiences before the queue gets noisy](/blog/the-support-surface-should-separate-audiences-before-the-queue-gets-noisy/) - support-led growth, brand trust, AI operations ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Zendesk Help: Getting started with your help center](https://support.zendesk.com/hc/en-us/articles/4408846795674-Getting-started-with-your-help-center) · [GrowthDex source hub](/sources/zendesk-help-getting-started-with-your-help-center-support-zendesk-com/) - [Zendesk Help: Promoting an article to the top of the section](https://support.zendesk.com/hc/en-us/articles/4408822265754-Promoting-an-article-to-the-top-of-the-section) · [GrowthDex source hub](/sources/zendesk-help-promoting-an-article-to-the-top-of-the-section-support-zend/) - [Zendesk Help: Reordering knowledge base content within categories and sections](https://support.zendesk.com/hc/en-us/articles/4408843983258-Reordering-knowledge-base-content-within-categories-and-sections) · [GrowthDex source hub](/sources/zendesk-help-reordering-knowledge-base-content-within-categories-and-sec/) - [Zendesk Help: Scheduling articles for publishing and unpublishing](https://support.zendesk.com/hc/en-us/articles/4408820403226-Scheduling-articles-for-publishing-and-unpublishing) · [GrowthDex source hub](/sources/zendesk-help-scheduling-articles-for-publishing-and-unpublishing-support/) - [Intercom Help: Create collections in your Help Center](https://www.intercom.com/help/en/articles/56647-create-collections-in-your-help-center) · [GrowthDex source hub](/sources/intercom-help-create-collections-in-your-help-center-intercom-com/) ## Editing notes - Kept the essay on one operator standard: do not make the help center public until it can actually finish common jobs. - Used concrete scenes like setup mode, pinned answers, stale migration guides, and breadcrumb navigation instead of generic support language. - Let the vendor mechanics carry the proof and kept the tone plain rather than turning product settings into grand strategy. - Ended with five blunt audit questions and the advisory CTA instead of a padded conclusion. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.