# Intercom Help

- Canonical HTML: https://growth.iangoh.com/sources/intercom-help-intercom-com/
- Original source: https://www.intercom.com/help/en/articles/9357931-create-and-manage-public-articles
- Domain: intercom.com
- Latest check: 2026-05-28
- Channels: Activation, AI, AI Search, Brand, Conversion, CRM, Customer Success, Docs, Documentation, Email, Internal Comms, Lifecycle, Localization, Onboarding, Operations, Product, Research, Sales, SEO, Support, UX, Website

## Cited GrowthDex tactics

- [Audience-gated public article answers by segment](/growth-ideas/audience-gated-public-article-answers-by-segment/) - Apply audience rules to public help articles so Fin only uses each answer for the customer segments that should actually see it.
- [Brand-matched AI help-center content scoping](/growth-ideas/brand-matched-ai-help-center-content-scoping/) - Scope AI support answers to the active brand's help center and duplicate critical docs across brands when needed, instead of assuming the model will search every knowledge base.
- [Collection-description scan copy for support routing](/growth-ideas/collection-description-scan-copy-for-support-routing/) - Write collection descriptions like routing copy, because a short line of context often decides whether a visitor opens the right support section or starts guessing.
- [Collection-only search gate before Help Center launch](/growth-ideas/collection-only-search-gate-before-help-center-launch/) - Do not call a help article live until it sits inside the right collection, because orphaned articles are harder to find and cannot be searched in the Help Center.
- [Customer card sort before Help Center IA lock](/growth-ideas/customer-card-sort-before-help-center-ia-lock/) - Test your support categories with real customers before freezing the Help Center structure, because the internal taxonomy is usually worse than the team thinks.
- [Help-center homepage section order by job](/growth-ideas/help-center-homepage-section-order-by-job/) - Reorder articles and collections on the help-center homepage around the first job the visitor needs done, not the internal information architecture.
- [Highest-volume question first in each help collection](/growth-ideas/highest-volume-question-first-in-each-help-collection/) - Put the most asked question at the top of each support collection so the page answers the likeliest job before the visitor has to scan the rest.
- [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.
- [Messenger-brand-linked help center suggestions](/growth-ideas/messenger-brand-linked-help-center-suggestions/) - Link each Messenger brand to the right help center so article suggestions inherit the same brand context as the support conversation.
- [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.
- [Same-workspace 301 map after help-center migration](/growth-ideas/same-workspace-301-map-after-help-center-migration/) - Keep a same-workspace 301 map for imported or renamed help-center URLs so old article paths continue carrying traffic and trust after a migration.
- [Single collection home for each public help article](/growth-ideas/single-collection-home-for-each-public-help-article/) - Give every public help article one deliberate collection home instead of scattering the same answer across multiple support buckets.
- [Unlisted public article preview before search release](/growth-ideas/unlisted-public-article-preview-before-search-release/) - Publish a help article as an unlisted public page first so the team can review the live URL before the page becomes searchable in the help center or crawlable by search engines.
- [Workflow-step sequencing inside help collections](/growth-ideas/workflow-step-sequencing-inside-help-collections/) - Order help articles by the real task sequence when the reader is trying to complete a workflow, so the collection doubles as guided onboarding instead of a static archive.
- [Action-led help article titles and meta descriptions](/growth-ideas/action-led-help-article-titles-and-meta-descriptions/) - Write help article titles around the task and keep the description crisp, because the same copy often decides both internal search relevance and the public search snippet.
- [Analytics priority queue for help-center translation](/growth-ideas/analytics-priority-queue-for-help-center-translation/) - Translate the help articles real visitors already read first, instead of trying to localize the whole support archive at once.
- [Custom-domain gate for private help-center articles](/growth-ideas/custom-domain-gate-for-private-help-center-articles/) - Treat private help articles as a real distribution surface only after they live on a custom domain that supports audience targeting.
- [Friction-triggered help article promotion](/growth-ideas/friction-triggered-help-article-promotion/) - Trigger the relevant help article from the product right before a known friction step so the answer meets the job while the user is still trying to finish it.
- [Help-center search terms in title, description, and body](/growth-ideas/help-center-search-terms-in-title-description-and-body/) - Match help article titles, descriptions, and body copy to the exact terms users search so the right answer wins inside your own help center before they bounce away.
- [High-traffic help articles linking to low-traffic answers](/growth-ideas/high-traffic-help-articles-linking-to-low-traffic-answers/) - Use your busiest help articles to internally link readers into overlooked but relevant answers, with anchor text that promises the job rather than just naming the topic.
- [One help article per search job](/growth-ideas/one-help-article-per-search-job/) - Split support content into one article per customer question so search, linking, and recirculation work on a clear job instead of a blended catch-all page.
- [Product-limitation FAQ with best alternative path](/growth-ideas/product-limitation-faq-with-best-alternative-path/) - When the product cannot do the requested job, publish a help article that says so plainly and routes the reader to the closest workable path instead of leaving support to repeat the same dead-end answer.
- [Related articles block on every public answer](/growth-ideas/related-articles-block-on-every-public-answer/) - Show a small set of related articles on every help page so one solved question can naturally hand off to the next one without sending the reader back to search.
- [Search-intent collection copy in every help-center language](/growth-ideas/search-intent-collection-copy-in-every-help-center-language/) - Write collection names and descriptions in the words customers actually search for in each language, because those labels often become the public search snippet.
- [Shared article library across multiple brand help centers](/growth-ideas/shared-article-library-across-multiple-brand-help-centers/) - Reuse one article across multiple brand help centers and let internal article links resolve in the active help center, instead of duplicating the same doc for every brand.
- [Translated collection gate before multilingual help-center launch](/growth-ideas/translated-collection-gate-before-multilingual-help-center-launch/) - Do not call a help center multilingual until each visible collection has a translated title and at least one translated article behind it.
- [Contact and attribute preload before support history import](/growth-ideas/contact-and-attribute-preload-before-support-history-import/) - Create the customer contacts and required attributes before importing historical threads so every migrated record lands with the right identity and fields attached.
- [Cutover runbook and rollback plan before support launch](/growth-ideas/cutover-runbook-and-rollback-plan-before-support-launch/) - Write the first migration run and the formal cutover as a runbook with a rollback path before launch day so the switch does not depend on memory or Slack improvisation.
- [Drain-and-fill cutover before final support history batch](/growth-ideas/drain-and-fill-cutover-before-final-support-history-batch/) - Move new support traffic to the new tool first, work both systems temporarily, and migrate the remaining closed history after the old queue drains.
- [Full transcript reply instead of message-by-message replay](/growth-ideas/full-transcript-reply-instead-of-message-by-message-replay/) - Import the thread as one created record plus one full transcript reply when the buyer mainly needs readable history, not a perfect recreation of every old event.
- [History structure choice before support import](/growth-ideas/history-structure-choice-before-support-import/) - Decide whether imported history should become conversations or tickets before scripting the migration so the buyer sees one coherent system instead of a messy hybrid.
- [Automatic forwarding and domain auth before support cutover](/growth-ideas/automatic-forwarding-and-domain-auth-before-support-cutover/) - Set up automatic forwarding and authenticate the support domain before the inbox migration goes live so the new workspace can handle real mail without looking improvised.
- [Batch test migration on sample records first](/growth-ideas/batch-test-migration-on-sample-records-first/) - Run the first real migration on a small sample set in a test workspace so the switch learns on safe data before touching the live queue.
- [Cross-domain help-center 301s before docs move](/growth-ideas/cross-domain-help-center-301s-before-docs-move/) - Before moving a help center to a new host, ship domain-level 301 redirects from the old support domain so rankings and bookmarked answers survive.
- [Delta-date cutover for support migration](/growth-ideas/delta-date-cutover-for-support-migration/) - Choose a fixed delta date, move closed history first, then bring over the remaining open and pending work at formal cutover.
- [Help-center collection link cleanup after domain switch](/growth-ideas/help-center-collection-link-cleanup-after-domain-switch/) - After a help-center domain switch, audit collection and index pages separately instead of assuming the article redirects covered the whole docs surface.
- [Legacy docs redirect map during help-center migration](/growth-ideas/legacy-docs-redirect-map-during-help-center-migration/) - When migrating a help center or docs corpus, ship permanent redirects from every legacy URL so search traffic, backlinks, and in-product links survive the move.
- [Simplest-form history import for reporting continuity](/growth-ideas/simplest-form-history-import-for-reporting-continuity/) - Migrate historical support data in the lightest useful format so buyers keep reporting continuity without turning the switch into a transcript reconstruction project.
- [Single indexed help center during knowledge sync](/growth-ideas/single-indexed-help-center-during-knowledge-sync/) - When syncing one public help center into another system, keep only one version indexable so the migration does not create duplicate content.
- [Workflow exceptions before API-led migration](/growth-ideas/workflow-exceptions-before-api-led-migration/) - Before importing conversations by API, disable or exempt the automations that would treat imported records like fresh customer activity.

## Related reading

- [GrowthDex Blog](/blog/)
- [All growth ideas](/growth-ideas/index.md)