---
title: "Help Scout Docs vs Intercom: Architecture, TCO & Migration"
slug: help-scout-docs-vs-intercom-architecture-tco-migration
date: 2026-09-14
author: Roopendra Talekar
categories: [Migration Guide, Help Scout Docs, Intercom]
excerpt: "Help Scout Docs vs Intercom Help Center compared on architecture, pricing, API constraints, TCO math, and step-by-step migration paths in both directions."
tldr: Help Scout Docs suits budget-conscious SMBs needing simple email-first support with low-cost multi-site KBs. Intercom's Help Center fits chat-first SaaS teams betting on AI resolution. TCO diverges fast once AI add-ons are factored in.
canonical: https://clonepartner.com/blog/help-scout-docs-vs-intercom-architecture-tco-migration
---

# Help Scout Docs vs Intercom: Architecture, TCO & Migration


# Help Scout Docs vs Intercom: Architecture, TCO & Migration

Help Scout Docs is a knowledge base bundled inside a shared-inbox help desk built for SMB email-first support. Intercom's Help Center is a knowledge base embedded in a messaging-first, AI-driven customer platform aimed at SaaS companies that want chat-led deflection. If you're choosing between the two — or planning a migration — the decision hinges on content architecture, total cost of ownership (TCO) at your team size, and how much you need the knowledge base to power AI resolution.

This guide breaks down the architectural differences, gives you real pricing math, and walks through the migration path with API-level specifics.

## How Help Scout Docs and Intercom Help Center are structured

**Help Scout Docs** organizes content into **Sites → Collections → Articles**. There is no limit to the number of articles per site. All paid plans include at least one Docs site, with additional sites available at $20/site/month.

Help Scout's **Beacon** widget surfaces Docs articles contextually on your site using a rules-based approach: articles are matched to pages based on URL patterns you configure, not behavioral signals or query intent.

**Intercom's Help Center** uses **Help Centers → Collections → Articles**. The structural hierarchy maps nearly 1:1 to Help Scout's, but the architectural intent differs: Intercom's Help Center exists primarily as a content source for Fin AI, not as a standalone self-service tool. Articles that aren't ingested by Fin have diminishing value in the Intercom model.

### Knowledge base feature limits

| Capability | Help Scout Docs | Intercom Help Center |
|---|---|---|
| Article limit | Unlimited | Unlimited |
| Docs sites / Help Centers included | 2 (Standard), 3 (Plus), 5 (Pro) | 1 (Essential/Advanced), multiple on Expert only |
| Extra sites cost | $20/site/month | Expert plan required ($132/seat/mo) |
| Multilingual support | Yes | Yes |
| Public + private articles | Yes | Yes |
| AI-powered self-service | AI Answers ($0.75/resolution) | Fin AI Agent ($0.99/resolution) |
| Content versioning | No | No |
| Approval/publishing workflows | No | No |
| Content staleness detection | No | No |
| Custom CSS/branding | Yes | Yes |
| Search implementation | Basic full-text | Semantic (Fin-powered) |

One key architectural difference: multiple help centers on Intercom require the Expert plan at $132/seat/month. All Help Scout paid plans include multiple Docs sites. For multi-brand or multi-product teams, this is a significant cost driver.

Neither platform is a purpose-built documentation tool. Both lack version control, multi-tenant portals, content reuse workflows, and approval gating. Know this going in.

### Search quality: a primary UX differentiator

Help Scout Docs uses basic full-text search: keyword matching against article titles and bodies. There is no semantic ranking, synonym expansion, or behavioral tuning.

Intercom's Help Center search, when Fin AI is active, operates semantically — it interprets query intent rather than matching literal strings. A user searching "can't log in" may surface an article titled "Account access troubleshooting" rather than requiring exact keyword overlap. This matters significantly for deflection rates: semantic search consistently outperforms keyword search on open-ended support queries by 20–40% in documented enterprise deployments. If your self-service deflection rate is the primary KPI, this is the most underappreciated difference between the two platforms.

## What does Help Scout Docs actually cost?

Help Scout's pricing has changed twice in recent years. For most of its history, the platform charged per user. Around November 2024, it eliminated per-seat fees and moved to contact-based billing (per "contacts helped" per month). The change drew significant criticism, and Help Scout walked much of it back. As of 2026, new signups see per-user pricing.

**Current per-user pricing (new signups, billed annually):**

- **Standard** — $25/user/month, includes 2 Docs sites
- **Plus** — $45/user/month, includes 3 Docs sites
- **Pro** — $75/user/month, includes 5 Docs sites

Help Scout Docs is not sold standalone — it is bundled into all paid plans.

**AI Answers cost modeling:**

AI Answers costs $0.75 per resolved conversation after a three-month free trial. For a 10-person team on Plus ($4,500/year in seats):

| AI resolution volume | Annual AI Answers cost | Total annual cost |
|---|---|---|
| 200/month | $1,800 | $6,300 |
| 500/month | $4,500 | $9,000 |
| 1,500/month | $13,500 | $18,000 |

At 1,500 AI resolutions/month, AI Answers alone costs more than 3× the seat cost. This is the most common source of bill shock for Help Scout customers.

> **Important:** Help Scout maintains a legacy contact-based billing model for existing customers on the 2024 plan. If you're migrating to Help Scout, confirm which billing model applies to your account before signing. The per-user pricing quoted above applies to new signups only.

## What does Intercom's Help Center actually cost?

Intercom's pricing has two distinct layers: per-seat plan fees and usage-based AI charges.

**Seat pricing (billed annually):**

| Plan | Annual/seat/month | Monthly/seat/month |
|---|---|---|
| Essential | $29 | $39 |
| Advanced | $85 | $99 |
| Expert | $132 | $139 |

**AI and add-on costs on top of seats:**

- **Fin AI Agent:** $0.99 per resolution (conversations fully resolved by AI without human handoff)
- **Fin AI Copilot:** $29/agent/month — drafts replies and summarizes conversations for human agents; this is a separate product from Fin AI Agent and is frequently conflated with it
- **Pro add-on:** $99/month, includes analysis of 1,000 conversations/month

**Realistic cost for 10 Advanced seats with Copilot, Pro, and 500 Fin resolutions/month:**

| Component | Monthly cost |
|---|---|
| 10 × Advanced seats | $850 |
| 10 × Fin Copilot | $290 |
| Pro add-on | $99 |
| 500 × Fin resolutions | $495 |
| **Total** | **~$1,734/month (~$20,808/year)** |

The headline "$85/seat" describes roughly 49% of this bill. Customers who budget based on seat cost alone routinely underestimate Intercom spend by 50–100%.

### The Salesforce acquisition risk

Salesforce signed a definitive agreement to acquire Intercom (now operating under the product name "Fin") on June 15, 2026, for approximately $3.6 billion. The deal is signed but not yet closed; Salesforce expects to complete it in its fiscal Q4 2027 (ending January 2027).

Until closing, Fin/Intercom operates as an independent product. After closing, the following risks are material for multi-year platform commitments:

- **Pricing:** Salesforce acquisitions have historically resulted in price increases within 12–24 months of integration (see: Slack, MuleSoft, Tableau). There is no contractual commitment from Salesforce on Intercom/Fin pricing continuity.
- **API deprecation:** Salesforce has a documented pattern of deprecating acquired platform APIs and routing customers toward Salesforce-native equivalents. The Intercom REST API at version 2.15 has no stated long-term deprecation timeline.
- **Roadmap absorption:** Features unique to Intercom's Messenger and Help Center may be merged into Salesforce Service Cloud or Einstein AI, potentially eliminating the standalone product positioning that makes Intercom attractive.
- **Migration path:** Customers who want to stay within the Salesforce ecosystem post-acquisition would likely migrate to Service Cloud, not Help Scout. Factor this into your platform strategy if Salesforce is already part of your stack.

If you are making a 2–3 year platform commitment, Intercom's acquisition status is a legitimate input to the decision.

## TCO comparison: 10-agent team, 12 months

Realistic side-by-side for a 10-person support team using the knowledge base plus moderate AI deflection (500 AI resolutions/month), billed annually:

| Cost component | Help Scout (Plus) | Intercom (Advanced) |
|---|---|---|
| Seat cost (annual) | $45 × 10 × 12 = $5,400 | $85 × 10 × 12 = $10,200 |
| AI per-resolution | $0.75 × 500 × 12 = $4,500 | $0.99 × 500 × 12 = $5,940 |
| Extra Docs sites (1) | $20 × 12 = $240 | $0 (1 included; more require Expert) |
| AI Copilot (10 agents) | N/A | $29 × 10 × 12 = $3,480 |
| **Year 1 total** | **~$10,140** | **~$19,620** |

**The critical variable missing from this table is AI resolution rate.** The TCO comparison changes substantially depending on what percentage of inbound volume each platform's AI actually resolves:

- If Fin resolves 35% of tickets and Help Scout AI Answers resolves 15% on equivalent article sets, Intercom may justify its premium by reducing headcount requirements.
- If you are understaffed on knowledge base content (fewer than ~100 well-structured articles covering your top 20 issue categories), neither AI will resolve much — and the per-resolution cost becomes irrelevant because resolutions won't occur at meaningful volume.
- The break-even point where Intercom's AI premium pays for itself in avoided headcount is approximately 800–1,000 additional AI resolutions/month compared to what Help Scout AI Answers would achieve. At $29/agent/month for a replaced headcount equivalent, each avoided support hire saves roughly $50,000–70,000/year fully loaded.

**Decision rule:** If your knowledge base has fewer than 150 comprehensive articles and your team handles under 2,000 tickets/month, the additional cost of Intercom's AI layer is unlikely to return measurable deflection gains. Help Scout is the cost-rational choice at this scale. Above 5,000 tickets/month with a mature knowledge base (300+ articles covering 80%+ of issue surface area), Intercom's semantic search and Fin resolution rate become defensible at the price difference.

## How do the APIs compare for migration?

Both platforms expose knowledge base content through REST APIs. The specifics differ in ways that directly affect migration planning.

### Help Scout Docs API

- **Auth:** HTTP Basic Auth using API keys (passed as the username, password left blank)
- **Rate limit:** Account-level, based on number of Docs sites; resets every 10 minutes
- **Critical detail:** The Docs administration UI generates API requests that count against this same rate limit. If an admin is editing articles during a bulk export, quota burns faster than expected.
- **No native export:** There is no ZIP export containing HTML, CSS, or assets. Bulk extraction requires scripted API calls.
- **Separate API surface:** The Docs API (`/v1/collections`, `/v1/articles`) is separate from the Mailbox API. Different authentication context, different rate limits.

**Core Docs API endpoints:**

```
GET /v1/sites              — list all Docs sites
GET /v1/collections        — list collections (filter by site ID)
GET /v1/articles           — list articles (filter by collection ID)
GET /v1/articles/{id}      — retrieve single article with full HTML body
POST /v1/articles          — create article
PUT /v1/articles/{id}      — update article
```

### Intercom Articles API

- **Auth:** Bearer token (OAuth 2.0 access token or personal access token)
- **Rate limit:** 10,000 calls/minute per app; 25,000 calls/minute per workspace
- **API version:** Currently 2.15
- **Pagination:** Cursor-based using `starting_after` parameter
- **Region routing:** Workspaces are hosted in US, EU, or Australia. Calls to `api.intercom.io` are routed automatically, but if you need explicit region targeting (for data residency compliance), use region-specific base URLs. EU customers should verify their data residency configuration before any migration that moves content out of the EU region and back.

**Article object schema (key fields):**

```json
{
  "id": "string",
  "title": "string",
  "body": "HTML string",
  "parent_id": "integer",
  "parent_type": "collection | section",
  "state": "published | draft",
  "created_at": "unix timestamp",
  "updated_at": "unix timestamp",
  "author_id": "integer",
  "description": "string",
  "url": "string"
}
```

**Core Articles API endpoints:**

```
GET /articles              — list articles (paginated, sorted by updated_at desc)
GET /articles/{id}         — retrieve single article
POST /articles             — create article
PUT /articles/{id}         — update article
DELETE /articles/{id}      — delete article
GET /help_center/sections  — list collections/sections
```

### Key technical differences between the two APIs

| Dimension | Help Scout Docs API | Intercom Articles API |
|---|---|---|
| Rate limit | Per-account, per 10 min (low) | 10,000 req/min per app (high) |
| Pagination | Page-based | Cursor-based (`starting_after`) |
| Auth method | HTTP Basic (API key) | Bearer token (OAuth) |
| HTML tag support | Standard HTML | Strips `div`, `span`, `form`, `input`, `textarea`, `script` |
| Internal articles via API | Yes | No — internal articles inaccessible via API |
| Image URL expiry | No (CDN stable while account active) | Yes — attachment URLs are time-limited |
| Bulk export tooling | None (script required) | None (script required) |

**Two underdocumented API behaviors that cause migration data loss:**

1. **Intercom silently strips unsupported HTML tags.** The elements `<div>`, `<span>`, `<form>`, `<input>`, `<textarea>`, and `<script>` are not supported in Intercom article bodies. During import, Intercom replaces them with `<p>` tags or removes them entirely without returning an error. Articles containing embedded forms, custom widgets, or div-based layouts will lose structure silently. Run a sanitizer against your source HTML before import — don't rely on Intercom's processing to preserve intent.

2. **Intercom's internal articles are inaccessible via API.** Articles marked as internal (visible only to agents in the Knowledge Hub) have no API endpoint for retrieval. They must be copied manually. If you're migrating from Intercom and have a substantial internal knowledge base, budget time for manual extraction before your account closes.

> **Rate limit planning:** For a knowledge base migration of 500 articles, neither platform's rate limit is a practical constraint on article operations alone. The constraint becomes relevant when migrating articles, conversations, contacts, and tags simultaneously in overlapping API windows. Serialize your migration jobs by data type and add exponential backoff for 429 responses.

## How to migrate from Help Scout Docs to Intercom

### Step 1: Audit and export from Help Scout

Script a [full extraction using the Docs API](https://clonepartner.com/blog/blog/how-to-export-data-from-help-scout-methods-api-limits-formats) before touching anything in Intercom.

**Extract per article:**
- Title, body (HTML), status (`published` / `draft`), collection ID, category assignments
- All inline image URLs (download immediately — images are hosted on Help Scout's CDN and will become inaccessible when you close the account)
- Internal links between articles (record source article ID → target article URL mapping for later rewriting)
- Created/updated timestamps if you want to preserve publication history

**Recommended extraction order:** Sites → Collections → Articles. Maintain a local mapping of `collection_id → collection_name` before pulling articles, since articles reference collection IDs numerically.

### Step 2: Transform content for Intercom

Intercom's article body accepts HTML, but with restrictions:

**Tag sanitization (required before import):**

Strip or convert the following before submitting to Intercom's API: `<div>`, `<span>`, `<form>`, `<input>`, `<textarea>`, `<script>`. Replace div-based layout structures with semantic HTML (`<p>`, `<ul>`, `<ol>`, `<table>`). Intercom's editor supports: `<p>`, `<h1>`–`<h3>`, `<ul>`, `<ol>`, `<li>`, `<a>`, `<img>`, `<code>`, `<pre>`, `<blockquote>`, `<strong>`, `<em>`, `<table>`, `<tr>`, `<td>`, `<th>`.

**Image re-hosting (required):**

Upload all article images to your own CDN or S3 bucket before import. Update image `src` attributes to point to your new URLs. Do not rely on Help Scout CDN URLs surviving account closure.

**Internal link rewriting (two-pass process):**

You cannot rewrite internal links until Intercom article IDs exist. On first import, replace internal links with placeholder markers (e.g., `[[ARTICLE:original-helpscout-slug]]`). After import, build a mapping of `old slug → new Intercom article URL` and run a second pass to replace all placeholders via `PUT /articles/{id}`.

### Step 3: Configure the Intercom workspace

Before importing content, create the destination structure:

1. Create Collections in Intercom that correspond to your Help Scout collection hierarchy
2. Note the numeric `id` of each collection — you'll pass these as `parent_id` in article creation
3. Create any custom contact/conversation attributes you want preserved from Help Scout conversations (if migrating support history alongside docs)
4. Confirm your workspace region (US, EU, AU) and that your API tokens have `write` scope on Articles

### Step 4: Import articles

Use `POST /articles` for each article. Set `state: "draft"` for all articles initially — validate before publishing.

```json
POST /articles
{
  "title": "Article title",
  "body": "<p>Sanitized HTML content</p>",
  "parent_id": 12345,
  "parent_type": "collection",
  "state": "draft",
  "author_id": 9876
}
```

At Intercom's 10,000 requests/minute limit, 500 articles import in under 5 minutes of API time. Real-world time including image upload and transformation is typically 2–6 hours for 500 articles depending on content complexity.

### Step 5: Validate content and test Fin

After import:

- Verify each article appears under the correct Collection
- Check image rendering (confirm CDN URLs resolve correctly)
- Test internal links (run the second-pass link rewrite)
- **Test Fin AI against your newly imported articles.** Fin requires articles to be indexed before it can cite them — indexing typically completes within a few hours of publishing. Ask Fin 10–20 of your most common support questions and verify it surfaces the correct articles. Poor Fin performance at this stage usually indicates either content gaps (articles don't cover the issue at sufficient depth) or article structure problems (key information buried in non-semantic HTML).

### Step 6: Set up 301 redirects

Before canceling Help Scout, export your full article URL list and configure 301 redirects from each old Help Scout Docs URL to its new Intercom Help Center equivalent. This preserves search engine equity and prevents dead links for bookmarked articles. Help Scout Docs URLs follow the pattern `https://[subdomain].helpscoutdocs.com/article/[id]-[slug]`. Intercom article URLs follow `https://www.intercom.com/help/en/articles/[id]-[slug]` (or your custom domain if configured).

## How to migrate from Intercom to Help Scout Docs

The reverse migration has distinct complications.

### Export from Intercom

Use `GET /articles` to [retrieve all published articles](https://clonepartner.com/blog/blog/how-to-export-data-from-intercom-methods-api-limits-transcripts). Articles are returned sorted by `updated_at` descending; paginate using `starting_after` with the last returned article's `id`.

**Critical extraction requirements:**

- **Download images during extraction.** Intercom attachment URLs are time-limited. If you store the URLs and try to download images later (after your Intercom subscription lapses or the session expires), the URLs will return 403 or 404. Download binary files during your extraction pass and re-host them before import.
- **Internal articles require manual extraction.** There is no API endpoint for articles in the internal Knowledge Hub. Identify them in the UI before extraction and plan for manual copy.
- **Multilingual content structure.** Intercom stores translations as separate article objects with a `translated_content` field containing locale-keyed content. Help Scout Docs handles multilingual content differently — typically separate articles per language or separate Docs sites per locale. Map your translation strategy before import, not after.
- **Messenger-specific content blocks.** Some Intercom articles embed Messenger-specific UI components (conversation starters, Fin handoff prompts). These render as broken HTML in Help Scout Docs. Identify and rewrite them during transformation.

### Import to Help Scout Docs

Help Scout Docs accepts HTML article bodies via `POST /v1/articles`. The API is more permissive on HTML than Intercom's — standard HTML structures import cleanly. Assign articles to collections via `collection` parameter using the numeric collection ID.

A community-maintained open-source script handles the Intercom → Help Scout direction. It migrates Intercom collections to Help Scout categories, re-hosts images, migrates articles, and generates redirects from old Intercom URLs to new Help Scout URLs. It processes approximately 100 articles per hour under normal API conditions and works reliably for knowledge bases under 500 articles with flat or single-level collection structure. Complex nested hierarchies or heavy multimedia content require custom handling beyond the script's scope.

### Authentication and SSO considerations

Both platforms handle private (authenticated) articles differently:

- **Help Scout Docs** supports private collections accessible only when visitors are identified via the Beacon `identify()` JavaScript call. There is no native SSO connector — identification relies on your application passing a signed user token to Beacon.
- **Intercom Help Center** supports identity verification via HMAC-signed tokens passed to the Messenger. Private articles are accessible to identified users only.

If you are migrating private or internal-facing articles, the authentication implementation is not portable — you must reconfigure identity verification for the destination platform regardless of which direction you're moving.

## When Help Scout Docs is the better choice

**Choose Help Scout if:**

- Your primary support channel is email, not chat
- Your team is under 15 agents and budget predictability matters more than AI deflection rate
- You operate multiple brands or products and need multiple knowledge bases — Help Scout includes 2–5 Docs sites depending on plan; Intercom requires Expert ($132/seat/month) for multiple Help Centers
- Your knowledge base has fewer than 150 articles and low inbound volume (under 2,000 tickets/month) — at this scale, AI deflection ROI is marginal on either platform
- You want simple setup with minimal configuration overhead — Help Scout Docs is functional within hours; Intercom's full configuration (Messenger, Fin, Help Center, routing rules) takes days to weeks

**Specific strengths:** Predictable per-seat billing, lower floor cost, simpler architecture, no acquisition overhang.

## When Intercom's Help Center is the better choice

**Choose Intercom if:**

- Chat is your primary support channel and you want the knowledge base to power end-to-end AI resolution (not just article surfacing)
- Your inbound volume exceeds 5,000 tickets/month and your knowledge base covers 80%+ of issue types — this is where Fin's semantic search and resolution capability generate measurable headcount ROI
- You want to blend support with proactive messaging, product tours, or in-app campaigns — Intercom's platform goes substantially beyond support
- You are already embedded in Intercom's Messenger ecosystem and the migration cost of moving away exceeds the cost of staying
- Your articles need semantic search — Fin's AI-powered search meaningfully outperforms Help Scout's keyword matching for open-ended queries

**Specific strengths:** Semantic search, end-to-end AI resolution, unified messaging and support platform, richer Messenger customization.

**Caveat:** Factor the Salesforce acquisition into any commitment beyond 18 months. Pricing continuity, API stability, and product roadmap are all uncertain post-close.

## What both platforms get wrong

Both Help Scout and Intercom treat their knowledge base as a bundled secondary feature. Neither offers:

- **Version control** — no diff history, no rollback to previous article versions
- **Approval workflows** — any agent with edit access can publish; there is no review gate
- **Content staleness detection** — articles don't flag when the underlying product has changed
- **Automatic article suggestions from conversations** — despite having both inbox and Docs access, neither platform automatically identifies recurring questions and suggests new article topics
- **Content reuse / single-source-of-truth** — content repeated across articles must be updated in every instance; there is no transclusion or shared content blocks
- **Multi-tenant portals** — no support for customer-specific knowledge base views with row-level content permissions
- **Video-to-documentation conversion** — neither platform ingests screen recordings or support call transcripts to generate article drafts
- **Training and certification workflows** — internal knowledge bases on both platforms lack quiz, attestation, or completion tracking

If your documentation requirements include any of the above, you are choosing between two platforms with the same gap. A purpose-built documentation tool (Confluence, Notion, GitBook, Guru) or headless CMS would be required in parallel.

## Migration complexity matrix

| Scenario | Estimated effort | Main risks |
|---|---|---|
| < 100 articles, flat structure, no internal articles | 1–2 engineer-days | Image re-hosting, link rewriting |
| 100–500 articles, 1–2 collection levels | 3–5 engineer-days | HTML sanitization, multilingual content |
| 500–2,000 articles, nested structure, multilingual | 2–4 engineer-weeks | Translation mapping, internal article extraction, redirect volume |
| > 2,000 articles or heavy multimedia | Custom scoping required | Content loss risk, performance, validation at scale |

**Universal requirements regardless of scale:**
1. Image download and re-hosting before account closure
2. Two-pass internal link rewriting (create articles first, rewrite links second)
3. HTML sanitization matched to destination platform's tag support
4. 301 redirect generation for all migrated article URLs
5. [Post-migration Fin/AI Answers testing](https://clonepartner.com/blog/blog/the-ultimate-knowledge-base-migration-checklist-a-zero-downtime-plan) against actual support queries

---

Whether you're going [Help Scout → Intercom](https://clonepartner.com/blog/blog/help-scout-to-intercom-migration-guide) or Intercom → Help Scout, the real work isn't moving articles — it's the cleanup, link rewriting, image re-hosting, and post-migration validation. For a knowledge base with fewer than 100 articles and simple structure, a competent engineer can handle it in one to two days using the APIs above. At 500+ articles with cross-references, embedded media, and multilingual content, plan for a week of engineering time minimum, plus a validation period before cutting DNS.

## Frequently asked questions

### Can I migrate articles from Help Scout Docs to Intercom?

Yes. Help Scout Docs Sites map to Intercom Help Centers, Collections map 1:1, and Articles map directly. Use the Help Scout Docs API to export HTML articles, sanitize unsupported HTML tags (Intercom strips div, span, form, script), re-host images, and import via Intercom's POST /articles endpoint. Plan a second pass to fix internal links once Intercom article URLs exist.

### How much does Help Scout Docs cost compared to Intercom's knowledge base?

Help Scout starts at $25/user/month (Standard, 2 Docs sites included) with AI Answers at $0.75/resolution. Intercom starts at $29/seat/month (Essential) with Fin AI at $0.99/resolution plus optional Copilot at $29/agent/month. For a 10-agent team with moderate AI usage, expect roughly $10,000/year on Help Scout Plus vs $19,600/year on Intercom Advanced.

### Does Intercom support multiple help centers?

Only on the Expert plan at $132/seat/month (annual). Essential and Advanced plans include a single Help Center. Help Scout includes multiple Docs sites on all paid plans — 2 on Standard, 3 on Plus, and 5 on Pro — making it the cheaper option for multi-brand documentation.

### What are the API rate limits for Help Scout Docs vs Intercom?

Help Scout's Docs API rate limit is based on the number of Docs sites on your account and resets every 10 minutes. Admin UI usage counts against the same limit. Intercom allows 10,000 API calls per minute per app and 25,000 per workspace. For most KB migrations, neither is a bottleneck.

### Will the Salesforce acquisition of Intercom affect my knowledge base?

Salesforce signed a definitive agreement to acquire Fin (formerly Intercom) for $3.6 billion in June 2026, with closing expected in Salesforce's FQ4 2027. Until then, Intercom operates independently. Long-term pricing, feature roadmap, and platform continuity are unknown — factor this into multi-year platform decisions.