The help center is included on paid Intercom plans. A separate charge applies if you want it on a custom domain.

How should you structure help center collections?

By customer task, not by your product’s feature names. Customers search for “cancel my subscription”, not “billing management”. Collections should mirror that language.

A practical structure for a SaaS product:

• Getting started (account setup, invitations, first project)
• Billing and plans (upgrades, invoices, cancellation, refunds)
• Using [core feature] (one collection per major feature, not per button)
• Integrations (one article per integration, not a giant list)
• Troubleshooting (error messages, exactly as they appear on screen)

Five collections is plenty. Ten is a sign you’re documenting your roadmap rather than your customers’ questions.

Step 1: Mine your actual ticket subjects

Export the last 90 days of conversations and group subjects by hand. You’ll find that maybe 20 topics generate 60% of volume. Those 20 become your first articles — write them before you write anything else.

Don’t trust intuition here. Every team I’ve seen do this found at least one high-volume topic nobody had guessed.

Step 2: Write articles Fin can use

Fin resolves conversations by matching user language to article content. That has direct writing consequences:

• One question per article. An article titled “Account and billing FAQ” with nine answers is nearly useless to a matching system across rephrasings.
• Put the answer in the first 60 words. Fin summarises from the top; burying the answer under three context paragraphs produces hedged replies.
• Use the customer’s word and your product’s word. “Delete your workspace (sometimes called a project)” covers both vocabularies.
• Add exact error strings. People paste error messages. Including them verbatim is the cheapest matching win available.

Step 3: Make search the primary navigation

Most visitors land on a help center from an in-app link and immediately type something. Keep the search bar above the collections and above the fold. Enable article suggestions in the Messenger so typing surfaces articles before a conversation starts.

Meta title and excerpt for each article should describe the problem, not the feature. “Fix: invoices showing $0 on annual plans” outperforms “Annual invoicing overview” for both search and scanners.

Step 4: Set up Fin only after the content exists

Turning Fin on against a thin help center produces confident wrong answers, which is worse than no bot. The order that works: write articles, verify Fin’s answers against a test set of 20 real customer questions, then enable live.

Configure Fin to hand off on low confidence and to always hand off when a user asks for a human. Keep that path obvious in the widget.

Step 5: Measure deflection, not views

Help center views are a vanity number. The signal that matters is: did the conversation end without a human reply? Intercom reports Fin resolution rates and help center article reactions (thumbs down on an article predicts a ticket).

Track three numbers monthly: top 10 articles by views, thumbs-down rate per article, and tickets tagged with topics you have articles for. If tickets keep arriving for a documented topic, the article isn’t the problem — the in-product discoverability is.

When is Fin not worth the money?

Under roughly 500 conversations a month. At that volume the per-resolution pricing rarely beats a human checking the Inbox twice a day, and the tuning effort to get Fin reliable will consume more time than the tickets it saves. A well-organised help center with a good search bar does 80% of the work for free.

Also skip Fin if your product changes weekly. Stale articles produce wrong answers, and a bot confidently wrong about your feature set costs trust you’ll spend months recovering.

Quick Summary

• Structure collections around customer tasks, not product feature names.
• One question per article, answer in the first 60 words.
• Include exact error strings — they’re the most-matched query type.
• Test Fin against 20 real questions before enabling live resolution.
• Measure conversations resolved without a human, not article views.

Intercom pricing starts around $39/month for the Essential seat, with a separate charge per resolved conversation for Fin, its AI agent. Budget both.

What does the Intercom Messenger actually do?

The Messenger is the chat widget: a launcher bubble, a home screen with your links and help articles, and a conversation view that becomes a ticket in the Inbox. Behind it sits your Inbox, help center, and optionally Fin.

It is a sales and support surface, and the same widget serves both. That’s the core tension — a bot built for support triage will ambush a pricing-page visitor if you let it.

Step 1: Install on every page, configure per page

The install snippet goes into your site head, ideally loaded for all pages. Hiding the Messenger per-page with CSS is a mistake: you lose the ability to open it programmatically and you break the conversation continuity when someone navigates.

Instead, use Audience rules to control what shows and when. That’s the lever that matters.

Step 2: Quiet the launcher on transactional pages

In Settings > Channels > Messenger > Launcher, set the launcher to a plain circle rather than a text label on checkout, pricing and signup pages. A text label like “Chat with sales” on a checkout page invites people to abandon the purchase and ask a question.

Use audience rules to apply this only where relevant: page URL contains /checkout or /pricing. Everyone else keeps the fuller launcher.

Step 3: Gate the bot by page and by signal

Fin or a custom bot should open automatically on exactly one kind of page: help articles and the help center. That’s where someone is stuck and a bot genuinely helps. Turn auto-open off everywhere else.

On marketing pages, let the visitor click first. The click is the strongest intent signal you’ll get, and a bot that only appears after a click avoids the “chatbot ambushed me” effect that makes people distrust the whole widget.

Step 4: Write outbound messages that aren’t advertisements

Outbound messages (the proactive popups) are where most accounts go wrong. The default “Hi there, how can we help?” on a 5-second delay is noise.

Better rules:

• One outbound message per session, maximum.
• Trigger on behaviour — 60 seconds on the pricing page, or scrolled 70% of a long feature page — not on time alone.
• Content answers a question that page raises, e.g. “Need to know if the API supports webhooks?”

Measure with the built-in outbound stats: replies per impression, not impressions.

Step 5: Connect the Inbox before you turn it on

The Messenger is useless without someone watching the Inbox and a rotation that actually covers your hours. Set business hours, enable the away mode with a clear response time, and route conversations to a real team rather than the default.

If nobody is on chat after 6pm, say so in the away message and collect the email. A widget that promises chat and delivers silence costs more than no widget.

Does the Messenger hurt page speed?

A little. The Intercom script is heavy — expect it to add several hundred kilobytes and a network request chain on first load. Load it after your main content renders rather than in the blocking head, or keep it off landing pages where Core Web Vitals are being measured against competitors.

Test with Lighthouse before and after. If your LCP regresses by more than a few hundred milliseconds, defer the snippet.

Who should use Intercom and who shouldn’t?

Fit: SaaS products with in-app support needs, a team of 3+ people answering, and a reason to qualify leads in chat. The Messenger’s depth — help center integration, bots, product tours — justifies the price.

Not a fit: a brochure site with 200 visits a day and no one to staff chat. You’ll pay $39/month for an inbox nobody reads and a bot that frustrates the three people who click it. A contact form performs the same job for nothing until you have inbound volume worth routing.

Quick Summary

• Install the Messenger on all pages; control behaviour with audience rules, not CSS hiding.
• Auto-open the bot only on help center pages; require a click everywhere else.
• Limit outbound messages to one per session, triggered by behaviour.
• Essential starts around $39/month; Fin is billed per resolved conversation.
• Defer the script if it regresses LCP on key landing pages.