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.
Why this can grow a startup
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.
Company 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.
Source and metric
Source: Intercom Help: Using custom fonts in the Help Center
Intercom recommends four core weights plus italics for each when uploading a custom font family.
When to use it
Use this when Brand, Support, Website is relevant to brand system, typography, trust and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Intercom Help: Using custom fonts in the Help Center and identify what is directly supported.
- Choose one channel context: Brand, Support, Website.
- Define the test around Intercom recommends four core weights plus italics for each when uploading a custom font family..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.