How to Create Intercom Help Articles With Screenshots

Intercom blurs the line between live chat and self-service in a way no other platform does. Its Articles feature lives directly inside the Messenger widget, which means your help content appears right where customers are already asking questions. That proximity is both an opportunity and a challenge.

The opportunity: customers can find answers without leaving the context of your app. The challenge: if those articles are poorly written or missing visuals, customers will immediately switch to chatting with your team -- and the transition is just one click away.

Key Insight: Intercom's data shows that help articles surfaced within the Messenger resolve 33% of customer queries without agent involvement. But that number drops below 10% when articles lack visual content or clear step-by-step structure.

This guide covers everything from setting up your Intercom help center to writing screenshot-rich articles that genuinely resolve customer questions.

Setting Up the Intercom Help Center

Intercom's help center functionality is called Articles and is available on most Intercom plans. It provides both an in-Messenger knowledge base and a standalone help center website.

Navigate to Articles in the left sidebar of your Intercom dashboard. If you do not see it, check your plan features or contact your Intercom admin to enable it.

Initial Configuration

Help center site -- Intercom generates a hosted help center at a default URL. You can configure a custom domain (like help.yourcompany.com) under Settings > Help Center > Custom Domain. Set this up early to avoid broken links later
Appearance settings -- Customize your help center's header color, logo, and welcome message under Settings > Help Center > Appearance. Match your brand so the experience feels seamless
Messenger integration -- By default, articles are searchable within the Intercom Messenger. Under Messenger settings, ensure the "Help" section is visible so customers see help articles as a first option before starting a conversation
SEO indexing -- Toggle search engine indexing under Help Center settings. Enable this to let Google crawl your help center, which brings in organic traffic from customers searching for answers outside your product

Pro Tip: Configure the Messenger home screen to prioritize articles over live chat. Under Messenger > Home Screen, you can reorder components to show "Search for help" prominently at the top. This nudges customers toward self-service before defaulting to a conversation.

Organizing Collections and Sections

Intercom uses Collections as the top-level organizer for help content. Within collections, you can create Sections to further group related articles.

Think of collections as the categories customers see on your help center homepage. They should be broad enough to contain multiple articles but specific enough that customers can identify the right one at a glance.

Planning Your Collection Structure

A practical structure for a SaaS product:

Getting Started -- Onboarding steps, account setup, first-time walkthroughs
Your Account -- Profile settings, team management, billing, plan changes
Core Features -- Separate sections within this collection for each major feature area
Integrations -- Setup and troubleshooting for each supported integration
Troubleshooting -- Error messages, common problems, and diagnostic steps
Developer Resources -- API docs, webhooks, and technical reference (if applicable)

Section Organization Within Collections

Within the "Core Features" collection, create sections for each feature area. For example, a project management tool might have sections like "Task Management," "Team Collaboration," "Reporting," and "Automations."

Common Mistake: Creating too many collections with just one or two articles each. This makes the help center look sparse and makes it harder for customers to browse. Start with fewer collections and expand as your content grows. A collection should have at least 5 articles before you give it its own space on the homepage.

Ordering and Featured Content

Intercom lets you manually sort collections and articles within them. Place the most commonly accessed content first. You can also feature specific articles at the top of the help center homepage -- use this for announcements, getting started guides, or seasonal content.

Writing Help Articles With Visual Content

Intercom's article editor is clean and supports rich text, images, videos, code blocks, and callout boxes. The editor is WYSIWYG, which means what you see while writing is close to what customers will see.

The most effective Intercom articles follow a pattern: brief context, clear steps, and a screenshot for every significant action. Since customers often discover articles within the Messenger widget on a relatively small viewport, conciseness matters even more than usual.

Article Writing Framework

Title -- Direct and specific. "How to create a custom report" not "Reports Overview"
Opening line -- One sentence stating what this article helps the customer accomplish
Prerequisites -- Any plan restrictions, role requirements, or setup steps needed before starting
Numbered steps -- One action per step, written in imperative voice. "Click Settings" not "You should navigate to the Settings area"
Screenshot after each step -- Capture the state of the UI at each step so the customer can confirm they are in the right place. ScreenGuide simplifies this by letting you annotate screenshots with step numbers, arrows, and highlights that match your instructions precisely
Outcome statement -- A final line describing what the customer should see when the task is complete
Related articles -- Link to adjacent topics using Intercom's article linking feature

Callout Boxes

Intercom supports callout boxes for tips, warnings, and notes. Use these consistently:

Tip callouts -- For optional enhancements or shortcuts
Warning callouts -- For actions that are irreversible or have significant consequences
Note callouts -- For clarifying plan-level restrictions or edge cases

Key Insight: Articles in Intercom that include three or more screenshots see 2.4x higher completion rates than text-only articles. In the Messenger widget specifically, where screen space is limited, visuals condense information that would otherwise require lengthy text descriptions.

Screenshot Best Practices for Intercom Articles

Because Intercom articles appear both in a standalone help center and within the smaller Messenger widget, your screenshots need to work at different viewport sizes. This requires some specific considerations.

Capture only the relevant portion of the screen. Full-page screenshots become unreadably small in the Messenger. Crop to the specific area the customer needs to see.

Creating Effective Screenshots

Crop tightly -- Show the relevant panel, modal, or section of the page rather than the entire browser window. This ensures readability even on mobile or in the Messenger widget
Annotate with clear callouts -- Use numbered markers that correspond to your step numbers. Add arrows pointing to the exact button or field. Highlight the clickable element with a contrasting color box. ScreenGuide makes this consistent and fast, producing annotations that remain legible across different display sizes
Use consistent styling -- Pick a color scheme for annotations and stick with it across all articles. Red circles for "click here," blue boxes for "this area," numbered badges for sequential steps
Optimize file size -- Compress images before uploading. Large images slow article loading, especially in the Messenger where the customer is already in a support context and patience is limited
Add alt text -- Intercom lets you set alt text on images. Include descriptive text for accessibility and to help Intercom's search index understand the image content

Pro Tip: Test every article inside the Messenger widget after publishing. What looks perfect on the standalone help center might have layout issues in the smaller Messenger viewport. Check that screenshots are legible and steps are easy to follow in both contexts.

Handling UI Changes

When your product UI changes, outdated screenshots become a trust liability. Create a simple tracking system -- even a spreadsheet -- that maps each article to the screens it references. When a UI update ships, use this map to identify exactly which articles and screenshots need updating.

Leveraging Intercom's Proactive Messaging with Articles

One of Intercom's unique strengths is the ability to proactively surface articles to customers based on their behavior. This goes beyond traditional help centers where customers must seek out content.

Use Intercom's automation features to push relevant articles to customers at the right moment. This is where help content transforms from reactive to preventive support.

Proactive Article Delivery Methods

Product tours -- Trigger a product tour for new users that links to relevant getting started articles at each step
Custom bots -- Create bot flows that ask customers what they need help with and route them to the appropriate article before they reach an agent
Targeted messages -- Show an in-app message linking to a help article when a customer visits a specific page for the first time. For example, show the "How to create your first report" article when a customer opens the Reports page
Post-resolution follow-up -- After closing a conversation, send the customer a link to the relevant article so they can self-serve if the issue recurs

Common Mistake: Setting up proactive messages without testing the articles they link to. If you push a customer to an article and it does not fully resolve their question, you have created frustration rather than prevention. Always verify the article is comprehensive before automating delivery.

Search Optimization Within Intercom

Intercom's help center search and Messenger search are the primary ways customers discover articles. Optimizing for these search mechanisms is essential for self-service success.

Intercom's search indexes article titles, body text, and tags. Title keywords carry the most weight, so write titles using the exact phrases customers type.

Search Optimization Tactics

Use natural question phrasing in titles -- "How do I change my password" matches customer queries better than "Password Management"
Add keyword tags -- Intercom lets you tag articles with relevant keywords. Add synonyms and variations. Tag a billing article with "payment," "invoice," "charge," "receipt," and "subscription"
Write clear first paragraphs -- Intercom's search sometimes surfaces the first paragraph as a preview. Make sure it immediately communicates what the article covers
Avoid jargon in searchable fields -- Use the terminology your customers use, not your internal product vocabulary

Key Insight: Intercom's search algorithm prioritizes title matches above all else. An article titled "How to reset your password" will consistently outrank one titled "Account Security Options" for the query "reset password," even if the second article contains more detailed content on the topic.

Monitoring Search and Article Performance

Under Articles > Reports, Intercom provides analytics on:

Article views and reactions -- Which articles are most viewed and how customers rate them
Failed searches -- Queries that returned no results, indicating content gaps
Conversation deflection -- How many customers viewed articles and did not start a conversation afterward

Review these monthly to identify content gaps and underperforming articles.

Maintaining and Scaling Your Intercom Help Center

As your product grows, your help center must grow with it. But growth without maintenance creates a content graveyard of outdated articles that do more harm than good.

Build maintenance into your product release process. Every feature release should include a step for creating or updating help articles. Make this part of your definition of done.

Maintenance Cadence

With every product release -- Create articles for new features and update articles for changed features. Recapture screenshots for any UI modifications
Monthly -- Review article analytics. Rewrite low-performing articles. Fill content gaps identified through failed searches and ticket analysis
Quarterly -- Audit the entire collection structure. Merge thin articles. Archive deprecated content. Reorganize collections if the product has evolved significantly

Scaling Content Creation

As your article count grows, consider these organizational practices:

Internal article drafts -- Intercom lets you keep articles in draft status. Use this to stage content for upcoming releases
Author attribution -- Track who wrote each article so you know who to contact when updates are needed
Consistent templates -- Create a shared article template that every team member follows. Consistency across articles builds customer trust and makes maintenance predictable

Pro Tip: Use Intercom's article status feature to flag articles that need review. Mark articles as "needs update" when a product change ships, and assign a team member to update them within a defined SLA.

TL;DR

Configure Intercom Articles with a custom domain, branded appearance, and Messenger integration that prioritizes self-service

Organize content into 5-7 collections with sections for sub-topics, ensuring each collection has at least 5 articles

Write concise articles with numbered steps, one action per step, and a screenshot at every significant point

Crop screenshots tightly and annotate with clear callouts that remain legible in both the help center and Messenger widget

Use proactive messaging and custom bots to surface articles before customers ask for help

Review article analytics monthly to identify content gaps, rewrite underperformers, and track conversation deflection

Ready to create better documentation?

ScreenGuide turns screenshots into step-by-step guides with AI. Try it free — no account required.

Try ScreenGuide Free