# The help center should know who it is for > Why login redirects, picked homepage answers, localized CTA cards, section order, and brand-scoped AI usually beat one more generic docs refresh. - Canonical HTML: https://growth.iangoh.com/blog/the-help-center-should-know-who-it-is-for/ - Published: 2026-05-28 - Updated: 2026-05-28T04:10:00Z - Categories: support-led growth, brand trust, technical SEO - Niches: SaaS, AI products, customer support software, marketplaces, developer tools ## On this page - Private articles need a real handoff, not a hard stop - The homepage should pick a few answers on purpose - Support homepages can carry a market-specific next step - Order is where the page admits what job matters most - AI support gets worse when brand context is fuzzy ## Start with these related tactics - [Private help-article login redirect before publish](/growth-ideas/private-help-article-login-redirect-before-publish/): Set a real login-page redirect before you hide help articles behind a user-only gate, so the reader lands on the answer after authentication instead of at a dead end. - [Locale-picked help-center homepage articles](/growth-ideas/locale-picked-help-center-homepage-articles/): Curate a homepage strip of published help articles per locale instead of assuming the collection grid will route everyone to the right answer. - [Localized help-center homepage CTA cards](/growth-ideas/localized-help-center-homepage-cta-cards/): Use a localized homepage content card to push one feature, webinar, or support action without sending every market to the same generic banner. A lot of help centers still act like one public square. The buyer, the logged-in customer, the churn-risk account, and the user asking an AI assistant all get roughly the same surface. Then the team wonders why support feels noisy and trust feels thin. Usually the problem is not that the archive is too small. It is that the page does not know who it is for. ## Private articles need a real handoff, not a hard stop The plainest example is [private help-article login redirect before publish](/growth-ideas/private-help-article-login-redirect-before-publish/). A user-only article is fine. Sending the reader into a login dead end is not. That belongs with [portal SSO redirect back to the intended page](/growth-ideas/portal-sso-redirect-back-to-intended-page/). Both ideas preserve the original question instead of forcing the customer to restate it after authentication. ## The homepage should pick a few answers on purpose I like [locale-picked help-center homepage articles](/growth-ideas/locale-picked-help-center-homepage-articles/) because it stops pretending the collection grid is always enough. Sometimes the right move is to surface the exact answer block the reader probably needs first. This sits in the same family as [highest-volume question first in each help collection](/growth-ideas/highest-volume-question-first-in-each-help-collection/) and [high-traffic help articles linking to low-traffic answers](/growth-ideas/high-traffic-help-articles-linking-to-low-traffic-answers/). One improves the homepage shortcut. The others improve what happens after the click. ## Support homepages can carry a market-specific next step The underrated growth move here is [localized help-center homepage CTA cards](/growth-ideas/localized-help-center-homepage-cta-cards/). A support homepage does not have to be a sales page, but it can still carry the right webinar, setup guide, or product action for a specific language or market. That pairs well with [search-intent collection copy in every help-center language](/growth-ideas/search-intent-collection-copy-in-every-help-center-language/). One tactic makes the page easier to choose from search. The other gives the reader a better next move after they land. ## Order is where the page admits what job matters most The tactical layout version is [help-center homepage section order by job](/growth-ideas/help-center-homepage-section-order-by-job/). If the page leads with collections because the internal org chart says it should, while the fastest answer is sitting in a curated article strip below the fold, the page is serving the team instead of the reader. That sounds small, but first-screen order decides whether the visitor scans once and clicks, or scans twice and opens a ticket. ## AI support gets worse when brand context is fuzzy The newest risk in this cluster is [brand-matched AI help-center content scoping](/growth-ideas/brand-matched-ai-help-center-content-scoping/). Intercom is clear that Fin does not search every Help Center in a workspace. It uses the active brand context plus matching audience rules. That puts it next to [shared article library across multiple brand help centers](/growth-ideas/shared-article-library-across-multiple-brand-help-centers/). Reuse is fine, but only if the system still knows which brand and audience the answer belongs to when the user asks for help. This cluster is strongest for SaaS, AI products, support software, marketplaces, and developer tools where docs, portals, and AI answers all shape product trust before a human ever replies. If I were tightening one this week, I would ask five blunt questions. Does every private article hand off cleanly to login. Which answers deserve homepage placement by locale. Does each market get its own support CTA. Is the homepage ordered around the first job. Does the AI assistant know which brand's content it is allowed to use. ## Related GrowthDex tactics - [Private help-article login redirect before publish](/growth-ideas/private-help-article-login-redirect-before-publish/) - Support, Website, Customer Success - [Locale-picked help-center homepage articles](/growth-ideas/locale-picked-help-center-homepage-articles/) - Support, SEO, Website - [Localized help-center homepage CTA cards](/growth-ideas/localized-help-center-homepage-cta-cards/) - Support, Conversion, Localization - [Help-center homepage section order by job](/growth-ideas/help-center-homepage-section-order-by-job/) - Support, UX, Website - [Brand-matched AI help-center content scoping](/growth-ideas/brand-matched-ai-help-center-content-scoping/) - AI, Support, Brand ## Essay chronology - [Newer essay: The help center stops feeling generic when the brand context stays intact](/blog/the-help-center-stops-feeling-generic-when-the-brand-context-stays-intact/) - support-led growth, technical SEO, brand trust - [Older essay: The help center homepage should route the first click](/blog/the-help-center-homepage-should-route-the-first-click/) - support-led growth, technical SEO, brand trust ## Keep reading - [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 docs page should know when to finish the job and when to hand off](/blog/the-docs-page-should-know-when-to-finish-the-job-and-when-to-hand-off/) - support-led growth, brand trust, technical SEO - [The help center stops feeling generic when the brand context stays intact](/blog/the-help-center-stops-feeling-generic-when-the-brand-context-stays-intact/) - support-led growth, technical SEO, brand trust ## 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 - [Intercom Help: Customize your Help Center](https://www.intercom.com/help/en/articles/56644-customize-your-help-center) · [GrowthDex source hub](/sources/intercom-help-customize-your-help-center-intercom-com/) - [Intercom Help: Manage audiences for Fin and Copilot](https://www.intercom.com/help/en/articles/9357948-manage-audiences-for-fin-and-copilot) · [GrowthDex source hub](/sources/intercom-help-manage-audiences-for-fin-and-copilot-intercom-com/) - [Intercom Help: Audience rules in Intercom](https://www.intercom.com/help/en/articles/14654636-audience-rules-in-intercom) · [GrowthDex source hub](/sources/intercom-help-audience-rules-in-intercom-intercom-com/) ## Editing notes - Kept the essay on one claim about audience fit instead of turning it into a general support manifesto. - Used physical page elements like login redirects, article strips, CTA cards, section order, and brand scope so the argument stays concrete. - Let Intercom's product rules carry the evidence rather than padding the piece with vague AI-support claims. - Closed on a hard review checklist instead of a generic wrap-up. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.