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

- Canonical HTML: https://growth.iangoh.com/growth-ideas/friction-triggered-help-article-promotion/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/56655-optimize-your-help-center-search)
- GrowthDex source hub: [Intercom Help](/sources/intercom-help-intercom-com/)
- Last checked: 2026-05-27
- Rarity: rare
- Budget: low
- Channels: Product, Support, Activation
- Stages: contextual help, activation, support-led growth, lifecycle timing


## Why this can grow

A good article still gets missed if the user has to leave the task to go hunting for it. Triggered article promotion closes that gap. It moves support content from passive library to active workflow aid, which improves self-serve completion and gives the same page a better chance to collect useful traffic and links over time.

## 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. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. 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 friction-triggered help article promotion can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Support channel.
3. Use the evidence from intercom.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

Intercom's guidance suggests sending a help article before a specific milestone, such as when a customer reaches their third project, so the article arrives at the moment the question is likely to appear.

## Adjacent tactics in the same lane

- [Batch test migration on sample records first](/growth-ideas/batch-test-migration-on-sample-records-first/) - same source, 2 shared channels, 1 shared stage
- [Localized help-center homepage CTA cards](/growth-ideas/localized-help-center-homepage-cta-cards/) - same source, 1 shared channel, 1 shared stage
- [History structure choice before support import](/growth-ideas/history-structure-choice-before-support-import/) - same source, 2 shared channels
- [Workflow exceptions before API-led migration](/growth-ideas/workflow-exceptions-before-api-led-migration/) - same source, 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The help-center search starts working when the archive stops guessing](/blog/the-help-center-search-starts-working-when-the-archive-stops-guessing/) - support-led growth, seo, content strategy

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.