# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/help-center-setup-mode-before-public-activation/
- Source: [support.zendesk.com](https://support.zendesk.com/hc/en-us/articles/4408846795674-Getting-started-with-your-help-center)
- GrowthDex source hub: [Zendesk Help: Getting started with your help center](/sources/zendesk-help-getting-started-with-your-help-center-support-zendesk-com/)
- Last checked: 2026-05-29
- Rarity: uncommon
- Budget: free
- Channels: Support, Documentation, Website
- Stages: launch hygiene, support-led growth, docs launch, brand trust


## Why this can grow

A weak help center creates support load before it ever removes any. Zendesk's setup mode matters because it gives the team a live place to shape the structure, theme, language defaults, and launch checks without exposing half-finished navigation to customers. That changes the launch from a copy dump into an operational handoff. When the help center first appears, it already feels intentional enough to deflect tickets instead of creating them.

## 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 help center setup mode before public activation 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 says end users cannot see the help center while it is in setup mode, and recommends using that window to brand, test, set the default language, add content, and prepare the launch.

## Adjacent tactics in the same lane

- [Manual help-center order before automatic sorts](/growth-ideas/manual-help-center-order-before-automatic-sorts/) - 3 shared channels, 1 shared stage
- [Private help-article login redirect before publish](/growth-ideas/private-help-article-login-redirect-before-publish/) - 2 shared channels, 2 shared stages
- [Category banners from About-topic copy](/growth-ideas/category-banners-from-about-topic-copy/) - 2 shared channels, 1 shared stage
- [Hide unreleased docs until the version is real](/growth-ideas/hide-unreleased-docs-until-the-version-is-real/) - 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.