# Full font family upload before help-center rebrand

> Upload the whole font family before rebranding the help center, not just one nice-looking file, so the support surface does not fracture across headings, buttons, and body copy.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/full-font-family-upload-before-help-center-rebrand/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/8429204-using-custom-fonts-in-the-help-center)
- GrowthDex source hub: [Intercom Help: Using custom fonts in the Help Center](/sources/intercom-help-using-custom-fonts-in-the-help-center-intercom-com/)
- Last checked: 2026-05-30T21:15:00Z
- Rarity: rare
- Budget: low
- Channels: Brand, Support, Website
- Stages: brand system, typography, trust, help center


## Why this can grow

Brand systems usually break in support pages first because the team treats typography as a cosmetic pass. It is not cosmetic once the reader is scanning headings, emphasis, buttons, and long-form instructions under pressure. Intercom's custom-font guidance makes the practical rule explicit: a branded help center needs the real weight map, not a single regular file and hope. When the whole family is present, the support surface feels maintained. When it is not, the page starts looking improvised even if the copy is good.

## 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 full font family upload before help-center rebrand can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Brand 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 says custom fonts should include Regular, Medium, Semi Bold, and Bold weights, plus italic versions for each, unless the team is using a variable font.

## Adjacent tactics in the same lane

- [Public metrics dashboard as a buyer-trust surface](/growth-ideas/public-metrics-dashboard-as-buyer-trust-surface/) - 2 shared channels, 1 shared stage
- [Custom-domain gate for private help-center articles](/growth-ideas/custom-domain-gate-for-private-help-center-articles/) - 3 shared channels
- [Translated collection gate before multilingual help-center launch](/growth-ideas/translated-collection-gate-before-multilingual-help-center-launch/) - 2 shared channels, 1 shared stage
- [Collection-description scan copy for support routing](/growth-ideas/collection-description-scan-copy-for-support-routing/) - 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 look like the company, not the tooling](/blog/the-help-center-should-look-like-the-company-not-the-tooling/) - brand trust, SEO, support-led growth

## Advisory

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