Intercom — Help center

Support & HelpSee it liveintercom.com

A landscape hero carries a prominent help search, followed by a grid of knowledge categories with article and author counts.

Intercom — Help center — captured interface — Viewport capture · opening screen

Source capture · 2026-09-05Open full image ↗

Search & discovery

Why this pattern works

Help centers that offer both direct search and a browsable knowledge structure.

Design notes

Surface: Intercom public English help center.
Navigation: Small product and language utilities above a large knowledge search.
Layout: Illustrated search hero followed by a consistent grid of topic cards.
Density: Low in the hero, moderate across the category grid.
Color: Muted landscape colors, white cards, dark text and fine gray borders.
Type: Clear search and topic labels with small metadata.
Pattern: Pair prominent search with category cards that communicate the breadth of each topic.
States: Public help-center index; search results and support conversations are not shown.
Don't: Avoid making visitors open every category just to understand what it contains.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Intercom — Help center
Source: https://www.intercom.com/help/en/
Swipefile reference: https://swipefile.design/ref/saas-ui-intercom-help-center/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Intercom public English help center.
- nav: Small product and language utilities above a large knowledge search.
- layout: Illustrated search hero followed by a consistent grid of topic cards.
- density: Low in the hero, moderate across the category grid.
- color: Muted landscape colors, white cards, dark text and fine gray borders.
- typography: Clear search and topic labels with small metadata.
- pattern: Pair prominent search with category cards that communicate the breadth of each topic.
- states: Public help-center index; search results and support conversations are not shown.
- dont: Avoid making visitors open every category just to understand what it contains.

Useful for: Help centers that offer both direct search and a browsable knowledge structure.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Help centers that offer both direct search and a browsable knowledge structure.

Intercom — Help center

Make it your own

Keep exploring